Build Mars real-time per-ticket support→PM-channel DM (clone PLUTO-191) — unbuilt EVO-31 leg, caused SOP-16 59.8h-unseen; BLOCKED on cross-app mechanism decision (pm-venus consolidating to Elazar)

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-22
• wi-cli-venus blocked · 2026-06-22
  cross-app mechanism choice (pluto dedicated pg_notify listener vs applog-rail vs app-direct-hub-POST) pending pm-venus's consolidated call to Elazar; do not build until direction set
• wi-cli-venus commented · 2026-06-22
  Scope expanded (Elazar fleet directive via pm-venus 2026-06-22): besides the real-time per-ticket support→PM-channel DM (clone PLUTO-191), the weekly Monday report must ALSO surface open support tickets + solicitudes de acceso. Both legs HELD on Elazar's Q-menu pick (real-time mechanism + weekly-report delivery/scope). Mars weekly-KPI cron is a candidate rail for the weekly surfacing. pm-venus relays decision + loops nw-venus.
• wi-cli-venus unblocked · 2026-06-22
  Elazar locked mechanism (1a 2b 3a+b 4a) via pm-venus 2026-06-22. Leg1 real-time = clone PLUTO-191 pg_notify trigger on supportTickets+accessRequests INSERT → per-row DM pm-mars (db-mars builds trigger; nw-venus owns host-side listener daemon, NO mars-local daemon). Leg2 weekly = extend Mon weekly-KPI cron to surface open tickets+access-requests (counts+list+age/SLA, >48h flag) as PM-channel DM not email (coder). Both dispatched.
• wi-cli-venus completed · 2026-06-22
  Both legs shipped+PTD: leg-1 per-ticket pm_triage NOTIFY trigger on supportTickets+accessRequests (2f45c6f/v2.18.20, fail-open), leg-2 weekly open-work triage emit cron→pg_notify{kind:weeklyReport,text}+appEvents durability backstop (76f3b51/v2.18.21). audit PASS both. CAP: emitters live; PM-channel e2e delivery pends nw-venus pm-triage-listen daemon (no-listener=harmless no-op, reports recoverable from appEvents.detail.report); first Mon-09:00-UTC cron fire = live-exercise watch.