EVO-70 tail: retire redundant after() email-outbox enqueue now that T1 trigger-wake is live

EVO-70 tail (pmmaster-flagged, non-urgent, dup-safe). Now that MARS-520 Tier-1 trigger-wake is live and proven (net.http_get fires ~5s on emailOutbox INSERT, alongside T0 */5 cron), the app-side after()-enqueue that also pokes the drain route is redundant belt-and-suspenders. Evaluate retiring it: confirm trigger + T0 cron fully cover the wake path, then remove the after() call. Dup-safe by design (all three wake sources idempotent via FOR UPDATE SKIP LOCKED), so no urgency — do only after trigger soaks in prod. Permanent T0 cron backstop stays regardless. coder+db confer before removing.