--boot --script= parsed, was stored, and did nothing. The script only starts at
_menu_enter, and a --boot run without --play never enters a menu -- it holds on
the title and quits. The run completed, exit 0, no menu line, no press: a clean
result to a question never asked. This file already warns about that exact shape
600 lines above the bug, where --capture used to photograph the first frame of a
scripted run. The warning was written, kept, and did not stop the same class
recurring in the neighbouring flag. Now push_errors and exits 2, naming both
working forms, refusing rather than implying --play since the two runs differ by
157 s of intro. Verified: --boot --play --script walks power-on through splashes,
ADV, title, (A), main menu, down, (A).
A comment above audio.play_bed described the port as CHOOSING the menu track,
which HANDOFF Q10 refuted a week ago -- BGM_103 is measured on three independent
legs and audio.json says so. Third instance of the drifted-comment trap. The dead
phrase is now a check-claims register row, controlled: a planted revival fails and
removing it passes.
And the boot's wall-clock seconds are a property of this container. ADV takes
146.6 s of wall clock for 137.44 s of media, +6.7%, while S00A runs real time at
-0.4%. Not a post-roll and not a general deficit: ADV is 1280x720 and S00A is
768x432, this box has no GPU, and 720p Theora decodes below real time here. The
transcode is faithful against a 137.71 s source and the exporter does not rescale.
P3/P7 artifacts quote seconds containing that deficit -- reproducible here, not a
statement about the port or the game. Comparisons with the Decoder's measurements
must go through media length, not wall clock; they carry an explicit emulator
pacing factor for the same reason and I had been quoting mine as exact.
Their negative result on LOAD GAME, TUTORIAL and OPTIONS leaves guard_focus_scope
right to count them UNMEASURED rather than 'resets'. The transferable part is
their instrument story: a narrow calibrated reader failed, so they generalised to
a whole-frame comparison, which died the moment a crash dialog overlaid the frame
while the narrow reader kept working. contract-check is deliberately narrow,
individually anchored checks for the same reason, and the temptation after an
ANCHOR LOST will be to loosen the matching -- trading a failure I can see for one
I cannot.
Every asserting check passes.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
7df386e07d