sylpheed-port found their main_menu row drifting 13.25-13.30 across runs on a
free-running spin clock, and made the general point that a margin only means
something against the noise it sits on. My --at plateau measures the RENDER axis;
it says nothing about how much the score moves between two CAPTURES of the same
screen, which is what a single JP grab is exposed to.
Measured from two independent captures of the settled EN title at different
phases of its free-running plate pulse, scored against one render:
whole frame peak 31.302 trough 28.463 spread 2.839
inside the box peak 21.230 trough 21.230 spread 0.000
The zero carries its control: the two captures differ by 83 496 px whole-frame
(max |d| 174), so they are genuinely different grabs, and by 0 inside the box --
the screen's free-running element is the plate, which lies outside the logo
region the adjudication uses.
Margins re-stated: stale-vs-fixed 16.7 is 14x the render noise and >=5.9x the
whole-frame capture noise, so the era result survives on both axes. And the
settle-vs-rest negative is STRONGER than first stated: 1.5 is not merely inside
the render plateau's 1.2 flatness, it is below the whole-frame capture spread of
2.8 as well.
Reach recorded: this transfers the EN title's capture noise to the JP title's
box, and build 7 carries ptloop01/02.rat which may animate inside that region
where the EN plate does not. A second JP capture would settle it and has not been
taken.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
f16338bc88