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).
Activity
-
parent=#2186
-
Gated on: db pg_net-timeout bump landing + passive production evidence that the trigger reliably wakes/drains on normal payloads + PM explicit go. Trigger is live alongside after()+cron; retirement is redundancy-cleanup, not urgent.
-
unassigned
-
Assignee cleared by pmmaster-evolutiva-cc 2026-09-12: coder-venus-cc / db-venus-cc / coder-pluto-cc / db-pluto-cc are absent from the hub roster and have no pane, and venus and pluto have no staffed coder or db lane. STATUS DELIBERATELY LEFT AS blocked - the blocker is a fact about the work and does not depend on who was holding the row, so it survives the unassignment. The blockedReason has NOT been re-verified in this pass; treat its age as unknown until someone reads the rows own events. Restaffing is Elazars call.