Release v0.1.24: SSE Pipeline Monitoring Now Uses Postgres LISTEN/NOTIFY

What changed

• Replaced 3-second polling with Postgres LISTEN/NOTIFY — Pipeline SSE connections now receive real-time updates via database triggers instead of continuous polling.
• 10-second fallback poll — A coarse fallback continues running in parallel as a safety net for missed notifications or LISTEN setup failures.
• Added database triggers — Two triggers on pipeline_runs and agent_jobs tables automatically fire NOTIFY on insert or update, with zero code changes required to existing agents.
• Improved SSE stream route — Rewritten to establish a WebSocket-backed LISTEN connection and gracefully degrade to polling if needed.

Why it matters

SSE connections were generating ~2,000 database queries per minute per 100 idle users. LISTEN/NOTIFY reduces that by ~90% during active pipeline runs — down to 1–2 queries per actual state change instead of every 3 seconds. Update latency drops from up to 3 seconds to sub-second.

Technical notes

• New file: src/lib/pipeline-notify.ts — utilities for creating a LISTEN client and firing NOTIFYs
• New migration: 0018_pipeline_notify_triggers.sql — creates the trigger function and two event triggers
• The LISTEN connection uses Node 22's native globalThis.WebSocket via Neon's serverless Client
• If LISTEN setup fails, the stream continues via fallback polling — no user-facing degradation