EVO-70b (Tier 1): venus emailOutbox AFTER INSERT trigger -> pg_net wake marker (event-driven send)

Fleet EVO-70 Tier 1 (feasibility PASS, audit-pluto-ca fleet + db-venus-cc per-app confirming). AFTER INSERT FOR EACH STATEMENT trigger on emailOutbox (transition table, nonempty check, NOT row-level) -> pg_net POST signed WAKE MARKER to the drain route. Fixes venus poll-dependence (venus has NO after() path today). Guardrails: trigger fn owned by postgres, fixed search_path, SECURITY DEFINER only if needed, REVOKE EXECUTE from PUBLIC/anon/authenticated; drain URL+secret from VAULT inside fn (never in pg_proc/cron cmd/payload/migration); payload=wake marker only; short pg_net timeout; worker keeps secret check + FOR UPDATE SKIP LOCKED + lease + idempotency. DURABILITY: pg_net tables UNLOGGED/beta => trigger is latency accelerator ONLY; emailOutbox stays durable SSOT and the EVO-70a guarded cron is PERMANENT recovery, NEVER retired. Venus=100% outbox (no bypass sync sends to carve out), proving ground. Proof set: commit->one wake, rollback->zero, multi-row stmt->one, empty cron->zero net-queue rows, due-retry->one, concurrent trigger/cron->single send. Observability: log wake/worker failures+processed counts (not empty polls), alert oldest-eligible-pending age + dead-letter count. Sequenced AFTER EVO-70a proves out.