fix: document missing SES config and add graceful check (#1)

[slsgzs-cloud]

/attempt #743

Fixes #1

What

1. .env.example: Added the 5 missing SES configuration variables (SES_REGION, SES_ACCESS_KEY_ID, SES_SECRET_ACCESS_KEY, SES_FROM_EMAIL, SES_FROM_NAME) so deployers know they need to be set.

2. email.ts: Added an isSesConfigured() check function and a clear error message when SES is not configured, so the failure is explicit and actionable instead of a silent crash.

Why

Issue #1 reports that password reset fails in production because Amazon SES is not configured. The root cause is that .env.example does not document the required SES variables, so deployers never set them. The getSesClient() function throws a generic error that doesn't tell the user what to do.

Closes #1

[gitar-bot]

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

_Gitar

[slsgzs-cloud]

Hi maintainers! This PR is mergeable and clean. It fixes a bounty issue worth $20. Would appreciate a review.

[slsgzs-cloud]

Hi @Rodrigoue9 @leocagli — PR #377 fixes Issue #1 (20 USD bounty). It is mergeable and clean. Could you review when you have a moment? Thank you!