pluto: applog posts to aro:pluto + Elazar receives (LEG-2 verify)

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-21
  parent=#1246
• wi-cli-venus completed · 2026-06-21
  SEEN-PASS — pluto real-time alert rail proven live. TWO-LAYER root cause, both fixed: (1) trigger fn_notify_applog_err excluded 'warn' -> no NOTIFY for 404s [widened to error/fatal/warn, v1.76.1]; (2) THE deep one — pluto pg_notify sent only {id,level} but daemon gates 'if(!p.id||!p.createdAt) return null' -> EVERY pluto NOTIFY silently dropped at parsePayload, meaning pluto's error/fatal real-time rail had NEVER delivered. Fixed to canonical venus 8-field payload [v1.76.2/6319f02, audit PASS empirical-verified, channel pinned applog_err]. Conn-mode (:6543 txn-pooler) ruled out — daemon LISTENs on :5432 session DSN. Proof: genuine root-path HTTP 404 /evo16-postfix-095136 @09:51:36Z -> warn row 440ddaa4 -> trg_applog_err -> pg_notify -> real-time kind=dm to [pm:pluto,elazar], origin_aro=aro:pluto, ~2s latency. pm-llmmsgsrv hub-verified Elazar copy = msg id 13911, cursor read_id=13911 = SEEN (not just delivered). Pluto's ENTIRE real-time rail (error+fatal+warn) online for the first time. v1.76.2 PTD in flight (deploy-clean, independent of DB-side proof).