The Decoder's point was that this is an unenumerated set, not a missing guard. The
enumeration is possible on my side and found a THIRD clock: the leaf sets
holding = false explicitly and reads time_units, pinned only by --leaf-time or
--time, biting on loop_leaf_on_screens = [title]. I would not have found it by
waiting for a row to drift.
But the general answer is a test that fails when the set is non-empty. Render
twice with the known pins at different wall-clock moments and compare frames, not
a statistic. --screen + --time + --loop-phase: all 16 byte-identical, though
--time freezes time_units itself so that pins every derived clock. --menu
--script=wait + --loop-phase, where the drift lived: frames differ by 4378 px --
but max per-channel 2.86 against 158.4 for a genuinely moving element, 55x apart.
Nothing moves; the residual is rasterisation noise. The discriminating scale is
what makes the test an answer.
And the reason I nearly missed it: last iteration I reported three pinned runs
returning 13.26 and called the harness reproducible. verify-capture prints RMSE to
two decimals and the residual is 0.0565 -- below its own resolution. The frames
were never identical; the statistic could not tell. I verified reproducibility
with an instrument that rounds away the thing being verified.
Conclusion unchanged: 2.86/255 changes no result.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
df03c057f5