v0.2.1 - Changelog

Highlights

Kept Resend as the recommended primary transactional email path for production projects.
Added optional Cloudflare Email Service support for teams that want a Cloudflare-native fallback provider or app-specific routing.
Added a dedicated Email Service worker for optional provider routing, delivery logs, and Cloudflare Email Sending integration when explicitly enabled.
Merged the old Resend settings flow into the unified Admin Email Service page, with Resend now shown first in provider setup.
Added site-owner guidance in the Admin drawer, including Cloudflare sender-domain screenshots, setup steps, local testing notes, and FAQ.

Existing Resend configuration remains the default and should continue to be used first.
Cloudflare Email Service is optional. Use it only after sender-domain onboarding, EMAIL binding configuration, and deployed Worker validation.
Local wrangler dev can simulate Cloudflare Email success without real delivery, so real Cloudflare fallback testing should happen on a deployed Worker.