Last iteration I enumerated three free-running clocks, wrote that the leaf is
pinned only by --leaf-time, then tested reproducibility without passing
--leaf-time and concluded nothing free-runs on the menu path. The answer was one
paragraph above the experiment that contradicted it.
My own flagged weakness found it: deliberate wall-clock variation via
--script=wait:N, putting the capture at t=96 units against t=369. Spin pinned
only, wait 0.5 vs 5.0 differs by max 91.19 per channel; with --leaf-time=0 added
it is byte-identical. draw_leaf_for is ptloop01/ptloop02, present on main_menu and
not just the title, which is why that row drifted.
verify-capture passed --loop-phase=0 and not --leaf-time=0 -- I fixed the clock I
had been bitten by and left the one I had merely listed. Enumeration without
follow-through fails exactly like no enumeration.
Both are now pinned at all six render sites. main_menu returns 13.21 across three
runs and two renders after different waits are byte-identical.
The number moved 13.26 -> 13.21 and that is NOT an accuracy improvement: pinning
the leaf at phase 0 puts ptloop01/02 at one specific pose rather than wherever the
wall clock left them. A different configuration, now reproducible. Which pose the
game shows at rest is not settled by this.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
49958ff090