mirror of
https://github.com/turnstonelabs/turnstone.git
synced 2026-08-12 23:12:23 -06:00
c0261c907c
E5's retry never fetches, so it cannot exercise the render-time check. E6 reaches it the only way available: the retry fires on a live stream, its /history is held at the fault layer, and a close-on-hide drops the transport while the payload is in flight. The detector is the stale-but-real PRE-rewind transcript surviving a RESOLVED fetch — three user rows with the latch still set. The latch leg is what makes it honest: replayHistory is the latch's only clear site, so a held latch proves no render ran rather than inferring it from row counts alone.