Transactional email only sends when RESEND_API_KEY is set; without it
sendEmail() silently no-ops. Combined with requireEmailVerification: true,
that meant every newly registered account was permanently locked out — the
verification link was never delivered and unverified users could not log in.
Verification mail is still sent on signup when email is configured; it is no
longer a barrier to signing in. Re-enable once transactional email is live.
Note: password reset still depends on email delivery, so users who forget a
password remain stuck until RESEND_API_KEY is configured.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Turnstile bot protection (sign-in, sign-up, password-reset):
- Register Better Auth's captcha plugin with the cloudflare-turnstile
provider; endpoints listed explicitly rather than relying on defaults.
/reset-password is intentionally excluded — it is reached only via a
single-use emailed token.
- Add an explicit-render Turnstile widget component. Tokens are single-use,
so each form resets the challenge after a failed submit; submit stays
disabled until a token is held.
- Read the site key server-side and pass it down as a prop, so rotating it
does not require a rebuild.
- Fail fast in production when TURNSTILE_SECRET_KEY is missing, and when a
secret is set without a site key (that combination would demand a token
no form can produce, locking every user out).
- Pass a throwaway secret during `next build` in the Dockerfile, mirroring
the existing BETTER_AUTH_SECRET treatment, so image builds don't need it.
CSP fixes in middleware (these blocked Turnstile entirely):
- Add frame-src for challenges.cloudflare.com. Without it the widget's
iframe fell back to default-src 'self' and was blocked outright.
- Allow 'unsafe-eval' and websockets in DEVELOPMENT only. `next dev`
compiles with eval(), so the strict policy threw EvalError and killed
hydration — no client JS ran at all, which also meant form submit
handlers never fired. Production policy is unchanged and still strict.
Also included (concurrent work in the tree):
- Admin organizations pages and lib/admin/orgs.
- Episode moderation migration, SEO metadata (sitemap, robots, JSON-LD,
OG/Twitter images, manifest), Umami analytics, not-found page.
Local dev database: docker-compose.dev.yml provisions Postgres 18 on port
5443 (5432-5442 are in use by other local projects).
Note: `npx tsc --noEmit` currently fails in app/(app)/team/page.tsx — an
`invitations` prop the component does not accept. This predates the commit
and will fail `next build` until fixed.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Cross-cutting input-validation, isolation, and DoS-resistance fixes across
the app, API, billing, queue, and infra layers.
- Runtime validation (zod) for client-supplied admin actions (role/plan/
limits), series generation index, and all pg-boss queue payloads
- Auth: require email verification before sign-in; reject weak/placeholder/
short BETTER_AUTH_SECRET in production
- Billing: sanitize Stripe/PayPal errors (log server-side, generic to client);
race-safe subscription upsert; only count "processed" webhook events as
handled; verify org membership in getEffectivePlan to block plan escalation
- Series generation: reserve usage up front and refund on failure; bill the
owning org, not the caller's active org
- Injection defenses: HTML-escape user fields in emails, strip CR/LF from
subject/recipient, validate ElevenLabs voiceId before URL interpolation
- Media routes: stream off disk instead of buffering whole files; rate-limit
anonymous public audio/cover endpoints by client IP
