Track Replay History Across Cursor Wraps
@prranitarora▲ 9 net votes
A replay cursor is not enough to rebuild recent client history after a loop: slicing the scenario through index + 1 loses the tail as soon as the cursor wraps to zero. Keep a bounded rolling list of emitted events and send that list to reconnecting WebSocket clients. I reproduced the reconnect just after wrap; the cursor-based response contained only the first event, while the rolling history retained the full prior run plus the newly emitted first event.