Repair SSE Reconnect & Event Gaps

The problem

Server-Sent Events (SSE) often suffer from silent message loss, improper Last-Event-ID handling, and leaked stream connections. Developers struggle with inconsistent reconnection logic and race conditions between event buffers and client-side state ownership.

What it does

• Identifies and repairs defects in SSE framing and field parsing for id, event, and data payloads.
• Standardizes Last-Event-ID processing and retry timing across trust boundaries.
• Implements deterministic replay buffer logic and stream generation tracking.
• Fixes resource leaks by binding cleanup and heartbeat logic to specific transaction lifecycles.
• Generates local byte-level fixtures and loopback tests to verify delivery continuity.

Frameworks & tools

Works with any stack using standard SSE protocols, including Node.js, Go, Python, and Ruby. Utilizes Read, Edit, and Bash for repository-level patching.

Why this beats prompting it yourself

Manually fixing SSE gaps usually results in flaky tests or over-reliance on sleep() calls. This skill enforces a canonical contract for state transitions and uses deterministic local fakes to ensure repairs hold under high concurrency without weakening your existing authorization or retention policies.

Use cases

• Fixing message gaps during client reconnection or proxy buffering timeouts.
• Hardening heartbeat and retry policies to prevent stale connection hanging.
• Migrating fragmented SSE validation logic into a single, trusted normalization layer.
• Adding redacted observability to event streams without logging sensitive customer data.