[Gap-Audit] 023 EmailJS Integration: provider health dashboard + rate-limit handling

[TortoiseWolfe]

Summary

Dual-provider email abstraction with failover works transparently to users. Optional admin-facing health dashboard and rate-limit handling are gaps.

What's shipped

• src/lib/email/ — dual-provider abstraction
• Failover logic
• tests/e2e/forms/email-failover.spec.ts (incomplete)
• Retry + backoff logic operational

Gaps

• Provider health dashboard not built (admin-only, optional)
• Rate-limit handling incomplete

Reference

• Spec: features/integrations/023-emailjs-integration/spec.md

[TortoiseWolfe]

Next-session primer

Goal: build the admin-facing provider health dashboard; complete rate-limit handling on the email service.

Effort: small to medium (~3-4h)
Blocked on: nothing

What's already shipped

• src/lib/email/ — dual-provider abstraction (Web3Forms primary, EmailJS fallback)
• Failover logic with retry + backoff
• src/utils/email/email-service.test.ts — 15 tests covering provider priority, failure tracking, fallback, rate limiting

Two gaps

A. Provider health dashboard (admin UI)

• New route: src/app/admin/email/page.tsx
• New component: src/components/organisms/EmailProviderHealth/ (5-file pattern via generator)
• Reads from src/utils/email/email-service.ts's status getter (getProviderStatus() per the existing test names)
• Shows: per-provider failure count, last-success time, current health status, manual reset button
• Mirror src/components/organisms/AdminPaymentPanel/ for layout

B. Rate-limit handling

• The existing test 'should provide rate limit status' exists but the implementation may be incomplete
• Look at src/utils/email/email-service.ts for getRateLimitStatus() or similar
• Make it surface in the new health dashboard
• Add UI feedback when a user submission is rate-limited (the existing form should already gracefully fail; just surface why)

Verification

1. New tests: src/components/organisms/EmailProviderHealth/EmailProviderHealth.test.tsx
2. Manually: navigate to /admin/email, see provider statuses
3. Force a Web3Forms failure (mock environment), verify the dashboard reflects it and the failover path activates
4. Submit a contact form repeatedly to trigger rate-limit; verify UI shows the limit reason

Watch-outs

• Both providers have free-tier daily limits; document them in the dashboard
• Admin gating: route should be wrapped in ProtectedRoute + AdminGate per the pattern from src/app/admin/layout.tsx (fixed in batch 1 [Gap-Audit] Stability: re-introduced auth-race regression in admin layout #6)