EVO-70 Tier 1 follow-up: retire app after() calls (gated on passive prod evidence)

PLUTO-613 Tier 1 follow-up (coder-lane): retire the app-layer after() immediate-send-attempt calls now that the DB AFTER INSERT trigger-wake (migration 081, cdee659) provides the same immediate wake for ALL emailOutbox inserts — removing the app-layer coupling was the original Tier-1 goal (a future producer that forgets after() is still covered by the trigger). GATED, do NOT start until: (1) db's pg_net-timeout bump lands (readable passive-evidence window), (2) passive PRODUCTION evidence from normal payloads confirms the trigger reliably wakes+drains on real traffic (not just the controlled E2E), (3) PM explicit go. The permanent Tier-0 guarded cron stays mandatory backstop regardless — retire ONLY the app after() calls, never the cron. Dedup safety already proven (FOR UPDATE SKIP LOCKED). Class-S once gated (removing redundant app calls, reversible).