Files
pad/internal/server
xarmian 86b0f7508f docs(server): name the subscribe-then-replay window where it lives (BUG-2730)
Codex round 18 was asked to assume exactly one defect survived sixteen
rounds and to find it rather than survey. What it returned is the
subscribe-then-replay duplicate window — a REAL defect, and one already
filed on BUG-2730 by two earlier rounds.

That it went that deep and surfaced a known residual rather than a new
defect is the useful result. But the code said nothing at the site, so a
successor reading handleSSE would have to re-derive it, exactly as three
review rounds did.

Now stated where it happens: the window, what it costs (a duplicate toast
and duplicate work, never a lost event), how internal/watchevents closed
the same window with SubscribeAndReplaySince, and why closing it here is
its own unit — a new method on events.EventBus across three
implementations, folded together with the admission check
SubscribeIfAllowed already performs. That is a change about DELIVERY, and
this one is about COVERAGE.

No behaviour change.

Refs BUG-2730, BUG-2731
2026-08-22 17:23:55 +00:00
..