One corrected row — POST it to the corrections log and count it. NEVER swallowed.
Re-read the console: re-open the stream so its snapshot burst re-primes every row — the
EXISTING reconnect path, invoked deliberately. The engine stays unconfirmed until the
board's own burst-end marker confirms the burst is behind us — the convergence row's own
snapshot, placed as the burst's LAST frame (Q5, 2026-09-01-http2-console-streams.md §8):
SSE is ordered WITHIN one stream, but the heartbeat rides its own separate row stream, so a
tick from THAT stream can arrive at any time and must never be mistaken for the marker.
What the engine needs from its host — the two side effects it may never do itself.