Render/server errors in appEvents (appLog): verify capture parity across pluto, mars, venus + fill gaps

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-19
• wi-cli-venus commented · 2026-06-19
  Origin: Elazar 2026-06-19. Pluto's appEvents DOES capture render/action errors (the soporte-evolutiva error emails are generated FROM appEvents rows; pg-pool storm errors were all present). Task: verify Mars + Venus capture render/server/action errors into appEvents the SAME way (level=error, category, action + the error-email pipeline), and fill any gaps so all 3 apps have parity. NOTE: separate but related — the venus real-time alert RELAY (applog-listen@<app>) was just fixed 2026-06-19 (was dialing dead direct :5432; repointed to session pooler aws-1-sa-east-1.pooler.supabase.com:5432). That fixed DELIVERY of alerts; THIS WI is about whether the errors are CAPTURED into appEvents in the first place across all 3 apps. Ref mem:pluto-applog-alert-pipeline, mem:pluto-venus-direct-port-dead-6543-workaround.