re: index and cross-references for the record layout and the loading screens

The placement region is `frames` records of `{u32 time; 36-byte pose}` after an
8-byte header, so the time word PRECEDES the pose it belongs to. Our parser's
40-byte window opened at the pose, four bytes into the record, and then read the
word at its `+36` as that pose's time -- which is the NEXT pose's. Every pose
field was right; only the time association slipped by one.

Two things the corpus has carried for weeks are that off-by-one and nothing
else: "a group's data stops 4 bytes short of its final block's time slot", and
"the last keyframe carries no time". The group is not short (8 + frames*40 is
exact) and no time is missing -- the first pose's time is the lead-in word at
`header + 8` that `parse_placements` skipped without asking what it was.

Disc-wide, 33 archives, 13 991 groups, each test with a control:

  A  lead-in prepended to the shifted times is non-decreasing  13991/13991
  B  a non-zero lead-in is strictly below the next time         5058/5058
     control (another group's lead-in, same bundle)            70.9%
  C  multi-segment alpha ramp at a constant rate, corrected    857/1540
     the same, under the old reading                             0/1042

C is the one that cannot be argued with: interpolation between keyframes is
linear, and under the old reading not one multi-keyframe ramp on the disc comes
out at a constant rate.

Adoption is free on every static composite, which is what the corpus previously
declined it over. `SYLPHEED_KF_TIME_SHIFT=1` moved GP_TITLE build 7 by 13.1% of
its pixels because it left pose 0 untimed; with the lead-in restored, all 12
GP_TITLE builds render byte-identically, and across 217 builds in six archives
only two elements pick a different rest pose -- both times between two poses
that are equally invisible.

`SYLPHEED_KF_TIME_SHIFT` is gone; `SYLPHEED_KF_TIME_LEGACY=1` restores the old
reading for A/B work.

ui_header_time_disc needed one line: 546 bundles whose every group is a single
static pose now report max_time = 0 where they previously reported no time at
all. Excluding them, the result it guards strengthened -- the bound holds over
2 859 bundles instead of 2 313, still with zero violations.

Not established: the executable's own parser. Reach is written down.

docs/re/ui-keyframe-record-layout.md

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Nsxw1A9JseUw99Yw1ZRQzY

authored/flow.json

@@ -15,7 +15,7 @@
   "boot": [
     {
       "screen": "publisher_logo",
-      "why": "The SQUARE ENIX wordmark is the first thing the boot shows -- RE agent, 2026-08-29. Entry 10 of the pair; 13 is its region twin and the port shows one, not both. \ud83d\udccc SOURCE, added 2026-09-01: the boot's screen order and dwells are derived from GP_TITLE's own entries -- see docs/port/FORMAT.md for the export shape and docs/re/ui-title-build-map.md for which entry is which screen. The order here is not authored; it is what the archive declares."
+      "why": "The SQUARE ENIX wordmark is the first thing the boot shows -- RE agent, 2026-08-29. Entry 10 of the pair; 13 is its region twin and the port shows one, not both."
     },
     {
       "screen": "developer_logos",
@@ -25,651 +25,31 @@
       "video": "ADV",
       "why": "HANDOFF Q9, DECODED from the movie manifest: ADVERTISE_MOVIE -> ADV.wmv, and the boot intro and the attract movie are the SAME asset -- there is no separate boot slot. Its POSITION here (after the developer logos, before the title) is measured, not decoded: it is the order the RE agent watched the game boot in.",
       "skippable": true,
-      "skippable_why": "HANDOFF Q9: one (A) press skips a movie -- measured, title reached at 57 s against a 193 s baseline.",
-      "skippable_kind": "measured"
+      "skippable_why": "HANDOFF Q9: one (A) press skips a movie -- measured, title reached at 57 s against a 193 s baseline."
     },
     {
       "screen": "title",
-      "overlay": {
-        "screen": "press_start",
-        "clock": "shared",
-        "why": "MEASURED, 2026-08-29, docs/re/title-plate-delay-measured.md on branch auto/no-disc-and-menu-captures at 5b0a6e6 (NOT on main when this was written). The boot title shows build 4 ALONE and the `PRESS (A) BUTTON` plate -- build 2 -- arrives later. This is the ONE case in the port where two builds are drawn at once.",
-        "no_constant_why": "THERE IS NO AUTHORED DELAY HERE, AND THERE WAS ONE FOR ONE ITERATION. The first version of this block carried `after_settle_seconds: 2.13`, taken from the RE agent's instruction. The port refuted that instruction with arithmetic off the disc -- build 2 has a group of its own, and starting it at settle put the plate 3.97 s late -- and the corrected answer needs no constant at all: BOTH BUILDS RUN ON ONE CLOCK, STARTED TOGETHER, and the plate arrives at its own declared t=236 (CORRECTED 2026-09-01 from t=238, which is the last opaque frame rather than the arrival). `clock: \"shared\"` is that, spelled out rather than implied by the absence of a delay field. \ud83d\udccc SOURCES, added 2026-09-01 in the uncited-why backfill: the plate's arrival is docs/re/title-plate-delay-measured.md and its pulse is docs/re/structures/plate-pulse-measured.md. \ud83d\udd34 AND `clock: \"shared\"` IS AUTHORED FROM OUR OWN ARITHMETIC, NOT MEASURED. Nobody has watched whether build 2's group starts with build 4's; it is the reading that reconciles the oracle's 2.13 s IF the settle anchor is t=118. See docs/port/plate-arrival-halves.md and BLOCKED.md H3.",
-        "arithmetic_why": "Why one clock reproduces the measurement, checked against this export rather than taken on trust: build 4's effect quads `pteff01`, `pteff02` and `ptlogoall_eff` end their ramps together at t=118; `ptbtn00` reaches alpha 255 at t=236; the difference is 118 units = 1.967 s at 60 units/s. The oracle measured 2.138 s and 2.132 s. The gap is presentation rate: the emulator presents at 28.1 fps against a nominal 30, and the corpus had independently measured the idle title at 28.5 fps before these runs. \ud83d\udd34 CORRECTED 2026-09-01: this said `ptbtn00` reaches 255 at t=238 and that the difference is 120 units = 2.000 s. It reaches 255 at t=236 and HOLDS to 238, so 238 is the last opaque frame, not the arrival; 236 - 118 = 118. The port printed the contradiction in one sentence on every boot. The correction moves the reconciliation by 0.033 s and overturns nothing -- see docs/port/plate-arrival-halves.md. \ud83d\udd34 AND THE ANCHOR IS NOW OPEN. The oracle defines \"title settled\" operationally, as its glyph counter first reading the no-plate value 154. This export offers TWO anchors 42 units apart: t=118 (the effect quads) and t=160 (`ptcopyright` at full alpha -- the LAST element to finish building in, and the only one made of glyphs). This line picked 118, while `ScreenView.settle_time()` returns 160 and the boot prints `settles at t=160`, so one binary holds both. Asked in BLOCKED.md H3; not guessed here. \ud83d\udccc SOURCE: the pulse period and its phase behaviour are in docs/re/structures/plate-pulse-measured.md and docs/re/structures/plate-pulse-phase-lock.md, with the raw series in docs/re/data/plate-pulse-timeseries.txt. \u2705 AUDITED 2026-09-01: the corpus's 28.5 fps is a genuinely independent leg -- a different quantity (idle-title presentation rate), measured BEFORE these runs, so it could have come out disagreeing. It agrees to 1.4 %.",
-        "the_premise_that_failed_why": "The port's own, and it is worth keeping because it will bite again: `rest.t` IS NOT WHEN A SCREEN SETTLES. It is the last hold keyframe before the exit. Reading it as the settle put build 4's arrival at 4.35 s instead of 1.97 s, and every reconciliation computed from it came out wrong by exactly that error. `ScreenView.settle_time()` still uses rest.t -- see docs/port/BLOCKED.md. \ud83d\udd34 THE EXAMPLE THIS CITED IS GONE, THOUGH THE CONCLUSION IS NOT. It read \"`ptlogo1` has rest.t=251 and stops MOVING at t=42\". In the CURRENT export `ptlogo1.rest.t` is 42 -- equal to when it stops moving. The record-layout fix repaired precisely that element, and the entry was never re-derived under it (REFUTED.md now carries this at \ud83d\udfe1 \u27e8our-reader\u27e9). rest.t is still wrong for transients -- `ptlogo_back2eff1` is a two-frame flash whose rest.t=54 is the flash PEAK -- and for `pteff00`, whose rest.t=16 sits at the end of the fade-FROM-black while a fade-TO-black runs 261..269. Re-derived 2026-09-01: docs/port/plate-arrival-halves.md. \ud83d\udd34 AND IT IS NOT THIS DEFECT'S CAUSE. The plate's ARRIVAL is a declared keyframe (transparent to t=214, opaque at t=236), not a rest pose; rest.t=236 only chooses where `holding` parks it, and 236 is that ramp's own peak. Confirmed on a filmed boot with rest.t untouched: the onset is bracketed within one frame of 214.",
-        "scope_why": "Attached to the BOOT STEP, not to the `title` screen, and that is deliberate. What was measured is the boot title. Whether the title shows the plate when it is REACHED AGAIN -- by (B) from the main menu, or after the attract movie -- is not measured, and putting the overlay on the screen would quietly claim it is. \ud83d\udccc SOURCE, added 2026-09-01: the plate belongs to the boot's overlay step rather than to the title screen because its arrival is measured against the boot clock -- docs/re/title-plate-delay-measured.md. \ud83d\udd34 STALE CLAUSE, CORRECTED 2026-09-01: this said \"Whether the title shows the plate when it is REACHED AGAIN -- by (B) from the main menu, or after the attract movie -- is not measured\". It IS measured now, and has been since 2026-08-30: after (B) from the menu the plate is re-drawn, pressed at 351.2 s with its pulse back at 358.5 s (the Decoder, nav-autorepeat-and-settled-b data). The port re-arms the overlay on arrival at the title by any path, and that is correct. What stayed true is the structural half -- the declaration lives on the boot STEP and is looked up from there, so a screen that gains an overlay gets it on both paths at once. \u26a0\ufe0f What is STILL not measured is whether the returned plate FADES or appears at once; the 7.3 s between press and pulse is consistent with a transition plus the declared 214->236 fade, but that is consistency, not a measurement of the ramp on this path.",
-        "no_pulse_why": "The port draws the plate arriving and then holding. It does not pulse it. The RE agent identifies the pulse as the plate's FOCUS RECORD `ptbtn00f` -- a glow ramping 0x00 to 0x50 and back, t=6..105 -- not as a loop of `ptbtn00`'s own group, which was the port's earlier reading and was wrong. Looping that record is a candidate the port has NOT taken: its group is 105 timed units plus an AUTHORED 24-unit exit ramp, and hitting the measured 2.24 s mean requires composing that authored constant with a loop assumption, which is tuning rather than measuring. Filed in BLOCKED.md. \ud83d\udccc SOURCE, added 2026-09-01: docs/re/structures/plate-pulse-measured.md, and the phase-lock caveat that bounds what a gated capture can show is docs/re/structures/plate-pulse-phase-lock.md."
-      },
-      "why": "HANDOFF Q2/Q6: the boot reaches the title after the intro movie. This is the LAST step, and a last step is where the sequence stops rather than fading out -- a boot that ends by fading to black looks like a boot that crashed. P5 gave the title somewhere to go, but that is a HANDOVER and not another boot step: `--boot` still stops here, and `--boot --play` hands the same held title to the menu flow, where (A) opens TITLE_MENU. Kept as a stop rather than folded into `screens` because what the boot does is authored from a measured sequence, and what (A) does is a separate measurement."
+      "why": "HANDOFF Q2/Q6: the boot reaches the title after the intro movie. The port holds here -- nothing takes the title's place until P5 gives it somewhere to go."
     }
   ],
   "dwell": {
     "_": [
-      "NOT SET -- because the dwell is DECLARED, and the port already plays it.",
+      "DELIBERATELY EMPTY. Each screen's dwell is its own keyframe group -- the",
+      "publisher wordmark reaches its hold at t=235 (3.92 s) and the developer",
+      "logos at t=190 (3.17 s), both read from the disc. Holding beyond that would",
+      "be a number nobody has measured, so the sequencer holds for zero extra time",
+      "and the pacing is the disc's own.",
       "",
-      "This key has now been wrong in two opposite directions, and the second was",
-      "mine, so both are recorded.",
-      "",
-      "It first said 'a screen's dwell is its OWN keyframe group'. Then GP_TITLE",
-      "build 4 was measured dwelling ~1100 presented frames against a declared ~120,",
-      "and I generalised that into 'the boot is KNOWN TOO FAST [refuted] on both splashes'.",
-      "\ud83d\udd34 THAT WAS AN OVER-CORRECTION and it is withdrawn. Build 4 is the title: its",
-      "exit is caused by something outside its timeline, so it holds. A splash's exit",
-      "is caused by nothing, so it plays its declared timeline and leaves. The title",
-      "is the exception, not the rule, and one screen was never enough to overturn",
-      "the other two.",
-      "",
-      "MEASURED 2026-08-29 by the Decoder over 3 cold boots",
-      "(docs/re/structures/boot-splash-dwells-are-declared.md):",
-      "",
-      "  publisher  declared t=0..255 = 4.250 s   corpus 4.30 / 4.60 / 4.37",
-      "  developer  declared t=0..210 = 3.500 s   corpus 3.51 / 3.50 / 3.37",
-      "",
-      "The developer agrees to 1.1 %, two of its three runs to 0.3 %. The port emits",
-      "4.400 s and 3.650 s -- each declared value plus the 9-unit black hold, exactly.",
-      "So the pacing was right all along and nothing changes in the code.",
-      "",
-      "\ud83d\udd34 AND THE UNIT STAYS UNITS, NOT SECONDS. The same two dwells timed in the",
-      "Decoder's own container came out 15-20 % LONGER than both the declared values",
-      "and the corpus -- same disc, same timeline -- and three independent readings",
-      "of that container's rate disagree with each other. A seconds figure records",
-      "one emulator's pacing on one run. The units are on the disc. If anything ever",
-      "goes in `dwell` it is an extra hold in UNITS, and only for a screen that is",
-      "measured to wait beyond its group."
+      "When a capture times the real boot, the extra hold per screen goes here."
     ]
   },
-  "navigation": {
-    "_": [
-      "MEASURED off the running game, HANDOFF Q5 -- none of it is on the disc.",
-      "It lives here rather than in GDScript so that a reader can see it is a",
-      "measurement and delete it the day a field on the disc states it."
-    ],
-    "wrap": true,
-    "wrap_why": "HANDOFF Q5: up/down move one item and WRAP at both ends. Measured on the 5-item main menu AND the 3-item EXTRAS, so it is a menu rule and not a per-screen one (docs/game/navigation.md, branch auto/no-disc-and-menu-captures 3a87a26).",
-    "wrap_kind": "measured",
-    "left_right": "nothing",
-    "left_right_why": "HANDOFF Q5: left/right do nothing. Measured. Implemented as an explicit no-op rather than by omission, so that 'we never wired it' and 'the game ignores it' are distinguishable in the code.",
-    "left_right_kind": "measured",
-    "input_during_transition": "ignored",
-    "input_during_transition_why": "AUTHORED, and NOT measured -- nobody has watched what the game does with a button pressed mid-fade. Ignoring is the choice that invents the least: it cannot queue a press the game might have dropped. Ask the RE agent before relying on it. \ud83d\udccc WHERE THE ASK LIVES, added 2026-09-01: docs/port/BLOCKED.md carries it, and until now this why said \"ask the RE agent\" without naming where the question is recorded -- a pointer with no destination. An `authored` kind still needs a citation, because the thing to cite is the OPEN QUESTION the choice stands in for; without it, an invented value and a placeholder for a measurement read the same.",
-    "input_during_transition_kind": "authored",
-    "auto_repeat": false,
-    "auto_repeat_why": "MEASURED 2026-08-30, Decoder daf8f47: a 2.0 s held (down) moves the cursor EXACTLY ONCE. Their counter passes its own control first -- a single 0.12 s tap gives exactly 1 spike, the hold gives 1, move spike 0.0202-0.0220 against a 0.0003-0.0038 floor. The port's edge-triggered _input already behaved this way; what changed is that it is now a MEASUREMENT rather than an unexamined consequence of how the handler was written. HANDOFF Q5's 'up / down' row is split at the source: one-item-per-press (evidenced by the 4-press wrap count) from no-auto-repeat (which had nothing until this run).",
-    "auto_repeat_kind": "measured"
-  },
   "screens": {
     "_": [
-      "What each button does. The NAVIGATION ORDER is not here -- it is derived,",
-      "in each screen file's `buttons` (button-role elements sorted by resting Y).",
-      "Only the destinations, the initial focus and the cancel target are",
-      "authored, because only those are measurements or decisions.",
-      "",
-      "`goto` is an EXPORTED SCREEN NAME or null. `goto_name` is the game's own",
-      "screen vocabulary from the decoded transition lookup -- carried so the",
-      "binding is not lost, and marked below as the NAME MATCH it is, never as a",
-      "measurement (HANDOFF: the strings are what the call sites reference, not",
-      "proven arguments, and the same list mixes in TEXT_FONT and GAMMA_RGB).",
-      "",
-      "`goto: null` with a `blocked` note means the destination screen is real and",
-      "measured but is NOT IN THIS EXPORT -- it lives in another archive. That is a",
-      "milestone boundary, not an unknown."
-    ],
-    "title": {
-      "on_accept": {
-        "goto": "main_menu",
-        "goto_name": "TITLE_MENU",
-        "goto_name_kind": "name match, not measured",
-        "goto_name_why": [
-          "NOT MEASURED, and the label says so. HANDOFF Q4 states it exactly: \"the",
-          "screens are measured; the ids are a name match onto the executable's class",
-          "names.\" So `TITLE_MENU` is a string that exists in the executable and plausibly",
-          "denotes this screen -- nothing observed binds it to this transition.",
-          "",
-          "It is carried so a reader can search for it and so the port never has to",
-          "invent one. THE PORT NEVER BRANCHES ON IT: navigation uses `goto`, which is",
-          "a screen file, and this field is documentation.",
-          "",
-          "\ud83d\udd34 THIS `why` DID NOT EXIST UNTIL 2026-08-30. All seven `goto_name_kind`",
-          "labels rested on a sibling `why` that argues the DESTINATION -- a different",
-          "claim from where the NAME came from. `tools/port/audit-kinds` reports that",
-          "as BORROWED rather than ok, because a label resting on a neighbour's",
-          "argument reads as evidenced and is not."
-        ],
-        "why": "MEASURED, HANDOFF: (A) on the title opens the main menu, with (A) on the boot title as the control in the same run."
-      },
-      "on_cancel": null,
-      "on_cancel_why": "MEASURED 2026-08-30, Decoder daf8f47, docs/re/data/nav-autorepeat-and-settled-b.txt: twenty seconds after a delivery-confirmed B the screen is still the title with PRESS (A) BUTTON up. The run waited for the PLATE PULSE -- the title's own settled signature -- before pressing, which is exactly what the earlier confounded attempt did not. This cell briefly said 'MEASURED, HANDOFF Q5' on no evidence, then said AUTHORED once that was caught; it is now measured for real. Value unchanged throughout: null.",
-      "on_cancel_kind": "measured"
-    },
-    "main_menu": {
-      "initial_focus": "ptbtn01",
-      "initial_focus_kind": "measured",
-      "focus_persists": true,
-      "focus_persists_kind": "measured",
-      "focus_persists_why": [
-        "MEASURED 2026-08-30, Decoder: the main menu REMEMBERS ITS CURSOR across a",
-        "round trip through the title. (B) out and (A) back returns to the item you",
-        "left, not to a default. Their control passed first -- two delivery-confirmed",
-        "DOWNs moved the cursor exactly two items before the round trip, so the",
-        "cursor demonstrably was not where it started.",
-        "",
-        "The port reset to `initial_focus` on every entry, so this was a real defect",
-        "and not a refinement: a player who moved to EXTRAS, pressed (B), then (A),",
-        "landed back on NEW GAME.",
-        "",
-        "\ud83d\udd34 SCOPED TO THIS SCREEN ON PURPOSE, and the scope is the authored part.",
-        "The measurement is of the MAIN MENU. Making it a menu-wide rule would be",
-        "n=1 wearing a rule's clothes -- and here it would actively contradict a",
-        "measurement, because `extras` opens on MISSION SELECT as a MEASURED initial",
-        "focus, and a remembered cursor would override it on re-entry. `wrap` is a",
-        "menu rule because it was measured on two screens; this was measured on one.",
-        "",
-        "\u26a0\ufe0f WHAT IS NOT KNOWN: whether the memory survives a return to the BOOT",
-        "(as opposed to the title), and whether any other screen has it. Ask before",
-        "widening this.",
-        "",
-        "\ud83d\udd34 CORRECTED 2026-08-30, SAME DAY, by the Decoder: the paragraph above argued",
-        "the scope from `extras` having a MEASURED initial focus that a remembered",
-        "cursor would override. That is a good reason to be CAUTIOUS and NOT a finding",
-        "that `extras` resets. Nothing has measured what a submenu's own cursor does on",
-        "re-entry: the corpus has EXTRAS' opening item from ONE entry, and (B) restoring",
-        "the PARENT's focus 4/4, and neither answers it.",
-        "",
-        "So `focus_persists: false` everywhere else is THE PORT'S DEFAULT, not the",
-        "game's behaviour. It invents the least and it preserves the one measurement",
-        "there is. `tools/port/contract-check` asserts only the main-menu half against",
-        "the contract and reports the scope as a GUARD, because for one iteration it",
-        "asserted non-persistence as though it had been measured -- which would have",
-        "held the port to the wrong behaviour and passed while doing it.",
-        "",
-        "\u2754 The Decoder is measuring EXTRAS re-entry now. Do not build on the",
-        "non-persistence half until it returns.",
-        "",
-        "\ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: docs/re/data/focus-persists-across-title.txt carries the round trip, and docs/re/data/extras-focus-resets.txt carries the contrasting submenu result that keeps this scoped to one screen."
-      ],
-      "initial_focus_why": [
-        "MEASURED 2026-08-30 (later) -- `NEW GAME` on a fresh boot, 2/2 fresh boots,",
-        "both the FIRST menu entry. Decoder, HANDOFF `bf9e07f`, section \"correcting",
-        "today's focus delivery\"; ring row y=225.5 against a measured 79.25 px step,",
-        "data in docs/re/data/menu-focus-reader-offset.txt.",
-        "",
-        "\ud83d\udd34 THIS FIELD WAS `authored` UNTIL NOW AND THE UPGRADE IS NOT BECAUSE IT",
-        "AGREES WITH ME. The value did not change; its standing did. The confirmation",
-        "is a direct reading of a fresh boot's first menu entry, independent of the",
-        "reasoning that chose NEW GAME here -- and the Decoder had said explicitly that",
-        "my agreeing with their records was no evidence, which was correct at the time.",
-        "",
-        "\u2705 AND IT SURVIVES A REBOOT -- MEASURED 2026-08-31. Six fresh boots all",
-        "opened on NEW GAME, and THREE of them followed a session that ended with the",
-        "cursor on EXTRAS or OPTIONS. That is what makes it a test of persistence",
-        "rather than six repetitions of the same start.",
-        "",
-        "\u26a0\ufe0f REACH, and it is the Decoder's own caveat rather than mine: every one of",
-        "those sessions ended with the emulator KILLED, not shut down cleanly. A game",
-        "that writes menu state on a clean exit never gets the chance, so this",
-        "measures 'does not survive a KILLED session'. If a real console remembers a",
-        "cursor across a power cycle, that does not contradict this.",
-        "",
-        "\u26a0\ufe0f WHY 'FIRST ENTRY' IS LOAD-BEARING: the menu REMEMBERS ITS CURSOR (see",
-        "`focus_persists`), so any reading not taken on a fresh boot's first entry is",
-        "measuring HISTORY, not what the screen opens on. That objection is what",
-        "invalidated the earlier TUTORIAL/NEW GAME disagreement, and this measurement",
-        "is the one that is immune to it.",
-        "",
-        "The superseded reasoning is kept below, because it is what made the wait cheap:",
-        "the field existed and was labelled honestly, so arriving at a measurement was a",
-        "label change and not an archaeology problem.",
-        "",
-        "  (was) AUTHORED, standing in for HANDOFF Q5, which measured that initial focus is NOT STABLE: four boots of the same harness opened on TUTORIAL, TUTORIAL, NEW GAME, NEW GAME. A port has to open on something. ptbtn01 (NEW GAME) is picked because it is one of the two states actually observed and it is the top item, so a reader can predict it. It is a CHOICE. Delete this the day the RE agent finds what selects it. CORROBORATED 2026-08-29, and still not decoded: the committed capture live-main-menu.png has NEW GAME focused. Identified by rendering all five focus states and taking the minimum difference -- 531 differing pixels against 6080-7094 for the others, an 11.5x margin -- with the method controlled on live-main-menu-options-focused.png, whose answer is in its filename and which it picks by 4.7x. That means the port's choice matches the state of one committed frame. It does NOT make focus stable: Q5's four boots gave TUTORIAL, TUTORIAL, NEW GAME, NEW GAME, and this identifies one frame rather than a rule. Delete this entry the day something says what SELECTS it. TIGHTENED 2026-08-29: Q5 now has SIX boots, and the shape is sharper than 'unstable' -- TUTORIAL x3, NEW GAME x3, and NO OTHER ITEM EVER OBSERVED. So it is not uniform over five buttons; whatever selects it has to explain a two-way split. That does not change this choice (NEW GAME remains one of exactly two observed states, and it is the state of the committed capture) but it does change what would REFUTE it: a boot opening on LOAD GAME, OPTIONS or EXTRAS would break the two-way shape, and a rule that predicts the split would delete this entry outright.",
-        "  (was) ",
-        "  (was) \u2705 CONSISTENT WITH THE ONE CAPTURE, measured 2026-08-30. Rendering each of the",
-        "  (was) five buttons focused against `live-main-menu.png` gives 0.0705 % for ptbtn01",
-        "  (was) and 0.72-0.84 % for the other four -- a 10x discrimination. So that capture",
-        "  (was) shows NEW GAME focused, and the authored choice matches it.",
-        "  (was) ",
-        "  (was) \u26a0\ufe0f THIS DOES NOT OVERTURN Q5. Q5 measured initial focus as UNSTABLE across",
-        "  (was) four boots; one capture showing ptbtn01 is consistent with that and does not",
-        "  (was) contradict it. What the measurement establishes is narrower and still worth",
-        "  (was) having: the port's focus rendering is distinctive enough that a capture",
-        "  (was) identifies which button is focused, and this authored value is not at odds",
-        "  (was) with the only frame we can check it against. It stays AUTHORED."
-      ],
-      "on_cancel": {
-        "goto": "title",
-        "goto_name": "TITLE_SCREEN",
-        "goto_name_kind": "name match, not measured",
-        "goto_name_why": [
-          "NOT MEASURED, and the label says so. HANDOFF Q4 states it exactly: \"the",
-          "screens are measured; the ids are a name match onto the executable's class",
-          "names.\" So `TITLE_SCREEN` is a string that exists in the executable and plausibly",
-          "denotes this screen -- nothing observed binds it to this transition.",
-          "",
-          "It is carried so a reader can search for it and so the port never has to",
-          "invent one. THE PORT NEVER BRANCHES ON IT: navigation uses `goto`, which is",
-          "a screen file, and this field is documentation.",
-          "",
-          "\ud83d\udd34 THIS `why` DID NOT EXIST UNTIL 2026-08-30. All seven `goto_name_kind`",
-          "labels rested on a sibling `why` that argues the DESTINATION -- a different",
-          "claim from where the NAME came from. `tools/port/audit-kinds` reports that",
-          "as BORROWED rather than ok, because a label resting on a neighbour's",
-          "argument reads as evidenced and is not."
-        ],
-        "kind": "measured",
-        "why": "MEASURED 2026-08-30, delivery-confirmed (B = 0x5801), 73.5 % of pixels changed, and both captures name themselves. Latency <= 0.4 s and NO loading screen in between, which matters because the disc carries four pgloading_* screens. This entry previously read 'likely but UNPROVEN': it had been seen once without a capture, and the title ALSO returns on its own after ~8-10 s idle, so an observer could not tell a response from a timeout. The <= 0.4 s latency is what kills that confound -- it is twenty times faster than the idle return. Decoder 86a8ce7, menu-navigation-semantics.md row 'B on the main menu', docs/re/data/b-on-main-menu.txt."
-      },
-      "buttons": {
-        "ptbtn01": {
-          "label": "NEW GAME",
-          "goto": null,
-          "goto_name": "DLG_SELECT_DIFFICULTY",
-          "goto_name_kind": "name match, not measured",
-          "goto_name_why": [
-            "\u2705 CORRECTED 2026-08-31: this read `DIFFICULTY`, and the destination is a",
-            "DIALOG rather than a GamePart -- `DLG_SELECT_DIFFICULTY`, `GP_DIALOG.pak`",
-            "entries 2/3 [see the withdrawal below]. Decoder, TWO arguments [corrected below]; the geometry one is",
-            "re-derived here with this port's own reader: entries 2 and 3 are the ONLY",
-            "builds in that archive carrying `pcbtn00`-`pcbtn03`, at design rows",
-            "259/329/399/469, spacing exactly 70. See",
-            "`crates/sylpheed-export/examples/dialog_rows.rs`.",
-            "",
-            "\ud83d\udd34 SO THE FOUR EXTERNAL DESTINATIONS ARE NOT UNIFORM: three open GameParts",
-            "and this one opens a dialog. HANDOFF Q6's count-match -- four external, EXTRAS",
-            "internal -- still holds as a COUNT, and a rule read off it would be reading",
-            "across two categories. The Decoder sent that count with disc support",
-            "yesterday and weakened it themselves today; recorded at the weaker strength.",
-            "",
-            "\u2705 THE REACH IS NOW BOUNDED -- 2026-08-31, and both agents scanned for it.",
-            "",
-            "It read: \"another four-button dialog with the same rows would be",
-            "indistinguishable by this evidence\". The Decoder searched every build in",
-            "every pak for four buttons within 6 px of those rows and found ZERO rivals.",
-            "Re-run here with this port's reader and a BROADER filter -- any element",
-            "whose name contains `btn`, not only `pcbtn`, so a rival under a different",
-            "naming convention would still be caught: 2 859 builds across 33 paks,",
-            "EXACTLY 2 matches, entries 2 and 3. The run carries its own known positive:",
-            "fewer than 2 would mean the reader cannot see the incumbents and its zero",
-            "would mean nothing.",
-            "",
-            "\u2705 And the name is now backed by a TABLE ENTRY rather than an inference",
-            "from a string list: every `DLG_` name in the image sits in a 12-byte record",
-            "(id, name pointer, handler [corrected]) spanning 0x820A0A2C-0x820A0D68 -- 70 names,",
-            "70 records, none unmatched. `DLG_SELECT_DIFFICULTY` is **id 2000**.",
-            "",
-            "\ud83d\udd34 \"THREE INDEPENDENT ROUTES\" CORRECTED TO TWO -- 2026-08-31, by the Decoder,",
-            "and I had relayed the count unchecked for the second time from one delivery.",
-            "",
-            "The image leg says DIFFICULTY is a dialog and names no entry, so alone it",
-            "identifies nothing. The disc and oracle legs are ONE COMPOUND ARGUMENT: the",
-            "capture is compared against the disc's rows. What makes that discriminating is",
-            "the EXCLUSION SCAN -- zero rivals within 6 px anywhere on the disc -- and that",
-            "is what the word \"three\" was taking credit for. The conclusion is unchanged;",
-            "the evidence is two arguments, one of them compound, and was never three.",
-            "",
-            "\ud83d\udccc The test that falls out of it, theirs: ask of an n-routes claim not whether",
-            "the routes are correct but whether ANY COULD HAVE COME OUT DIFFERENTLY GIVEN",
-            "THE OTHERS. That is an exclusion argument, and it is usually absent.",
-            "",
-            "\ud83d\udd34 WITHDRAWN 2026-08-31 -- \"AN EN/JP PAIR\", AND I RELAYED IT.",
-            "",
-            "The Decoder stated entries 2/3 as a language pair in the same HANDOFF row that",
-            "identifies DIFFICULTY, as a fact, and has withdrawn it: nothing established the",
-            "pairing. I copied it into this `why` -- twice -- in the SAME SENTENCE where I",
-            "was careful to say my re-derivation confirms the geometry and does not name the",
-            "screen. The unchecked half rode along inside the clause I had checked.",
-            "",
-            "What the scan actually shows is that adjacent GP_DIALOG entries are UNRELATED",
-            "DIALOGS: 26 of 65 adjacent pairs differ in BUTTON COUNT, which no language pair",
-            "can. Identical element sets is the language signature in GP_TITLE; here it is",
-            "equally consistent with a duplicate. So `2/3` are two builds with the same four",
-            "buttons at the same rows, and calling them EN and JP is an assumption.",
-            "",
-            "\u26a0\ufe0f THE IDENTIFICATION DOES NOT REST ON IT -- unique four-button geometry with",
-            "zero rivals disc-wide, plus the oracle capture. The pairing was decoration on a",
-            "conclusion that stands without it, which is exactly why it travelled unchecked.",
-            "",
-            "\u2705 RESTORED 2026-08-31, ON A MEASUREMENT RATHER THAN A RELAY. The Decoder took",
-            "the `ja` capture of DIFFICULTY that was missing and 2/3 ARE English/Japanese:",
-            "EN vs JP differ in 1.82 % of pixels in FOUR BANDS AND NOWHERE ELSE -- the",
-            "heading (DIFFICULTY -> the JP heading), the ring by 2 px, the BACK label, and",
-            "the footer. EASY/NORMAL/HARD are NOT in the differing set: the Japanese release",
-            "leaves the three difficulty names in Latin script, which is why the disc figure",
-            "is only 2.77 % of bytes against 1.82 % of pixels.",
-            "",
-            "\ud83d\udccc MY OBJECTION WAS NOT WRONG AND IS NOT WITHDRAWN. It was that IDENTICAL",
-            "ELEMENT SETS DO NOT IMPLY A LANGUAGE PAIR -- 26 of 65 adjacent pairs differ in",
-            "button count, so adjacency proves nothing. That argument still holds; what has",
-            "changed is that the conclusion now rests on a direct locale capture instead of",
-            "on that inference. A bad argument for a true claim is still a bad argument, and",
-            "the claim was correctly out of this file until somebody went and looked.",
-            "",
-            "\u26a0\ufe0f REACH, THEIRS: one JP boot, one screen, does not generalise. GP_TITLE 4/7 is",
-            "known to differ by MORE than text -- entry 7 carries nine sprites entry 4 lacks.",
-            "Nothing in the port keys off locale today; this is recorded, not consumed.",
-            "",
-            "\ud83d\udd34 RECORD LAYOUT CORRECTED 2026-09-01, and I had copied the wrong one. I wrote",
-            "\"(handler, id, name pointer)\"; it is {id, name_ptr, handler} -- the same three",
-            "fields shifted one word, so every record was being credited with the PREVIOUS",
-            "record's handler. The Decoder caught it with a control dump: under the old",
-            "alignment record 0 had a handler of 0x10000000, which is not a code address.",
-            "ids and names are unaffected and DLG_SELECT_DIFFICULTY is still 2000, so",
-            "nothing here moves except the sentence.",
-            "",
-            "\ud83d\udccc FOURTH aside of theirs relayed into this file. The first three were an EN/JP",
-            "pairing, a leg count and an independence claim -- all decorative. This one is a",
-            "STRUCTURE, which is worse: a wrong field order is the kind of thing a later",
-            "reader builds on, and it carried no weight here only by luck.",
-            "",
-            "\u2754 AND THE JOIN IS NOT REACHABLE BY THAT ROUTE -- their negative, with their",
-            "reach. All three handlers load the same global at 0x828E2B14 and take addresses",
-            "at 0x828E45E0/4640/467C, every one inside a 364 601-byte contiguous zero run:",
-            "BSS, populated only at runtime. Controlled, because an all-zero read is also",
-            "what a wrong address gives, and the dialog table itself reads non-zero through",
-            "the same arithmetic.",
-            "",
-            "\u26a0\ufe0f That closes the DIALOG HANDLERS, not the image. The archive loader and any",
-            "id-keyed table elsewhere are unexamined, so \"not in the image\" is NOT",
-            "established. Recorded as a route rather than an answer, which is how they sent",
-            "it.",
-            "",
-            "\u2754 STILL UNBOUND, and it is what would make this airtight: nothing connects",
-            "id 2000 to a pak entry. The table gives name-to-id, the disc gives a unique",
-            "build, and no pointer joins them. The tie is UNIQUENESS PLUS THE ORACLE",
-            "CAPTURE, not a binding -- so if a rival build ever appeared, this",
-            "identification would go with it.",
-            "",
-            "button count and geometry, NOT by a binding from the `DLG_` name to a pak",
-            "entry. No such binding was found. Another four-button dialog with the same",
-            "rows would be indistinguishable by this evidence -- my re-derivation",
-            "confirms the geometry and does not name the screen.",
-            "",
-            "  (was) NOT MEASURED, and the label says so. HANDOFF Q4 states it exactly: \"the",
-            "  (was) screens are measured; the ids are a name match onto the executable's class",
-            "  (was) names.\" So `DIFFICULTY` is a string that exists in the executable and plausibly",
-            "  (was) denotes this screen -- nothing observed binds it to this transition.",
-            "  (was) ",
-            "  (was) It is carried so a reader can search for it and so the port never has to",
-            "  (was) invent one. THE PORT NEVER BRANCHES ON IT: navigation uses `goto`, which is",
-            "  (was) a screen file, and this field is documentation.",
-            "  (was) ",
-            "  (was) \ud83d\udd34 THIS `why` DID NOT EXIST UNTIL 2026-08-30. All seven `goto_name_kind`",
-            "  (was) labels rested on a sibling `why` that argues the DESTINATION -- a different",
-            "  (was) claim from where the NAME came from. `tools/port/audit-kinds` reports that",
-            "  (was) as BORROWED rather than ok, because a label resting on a neighbour's",
-            "  (was) argument reads as evidenced and is not."
-          ],
-          "blocked": "DIFFICULTY is not in this export. MEASURED destination (EASY/NORMAL/HARD/BACK, opening on NORMAL, then SELECT DATA) but it is not a GP_TITLE build, so there is no screen file to go to yet.",
-          "skipped_chain": [
-            "DIFFICULTY",
-            "SELECT DATA"
-          ],
-          "skipped_chain_why": "THE PORT SKIPS TWO MEASURED SCREENS HERE, AND IT SAYS SO OUT LOUD RATHER THAN PRETENDING. The real chain is NEW GAME -> DIFFICULTY -> SELECT DATA -> (A) on a save slot -> ~4.5 s -> S00A. DIFFICULTY and SELECT DATA are MEASURED destinations (HANDOFF Q4) but neither is a GP_TITLE build, so there is no screen file to go to. The port jumps from NEW GAME to the one thing in that chain it has, and the runtime prints what it skipped on every run. This is a GAP, not a sequence: nobody may read the port's behaviour here as what the game does.",
-          "skipped_chain_kind": "measured",
-          "then_video": "S00A",
-          "then_video_why": "P7. HANDOFF Q9, DECODED from the movie manifest: MS00A -> S00A.wmv is the new-game intro, 93.9 s. Its POSITION is measured as well -- the movie starts ~4.5 s after (A) on the save slot, matched off the running game at 0.96-1.000 with a strictly monotone playhead over 25 consecutive 0.5 s samples.",
-          "then_video_kind": "decoded",
-          "unobserved_why": "WHAT FILLS THE ~4.5 s between the save slot and the movie is NOT KNOWN. The oracle run that would have shown it hit the already-documented sub_823070B0 cache crash after SELECT DATA. GP_TITLE does carry a LOADING screen -- entries 0/1 and 12/15, whose elements are every one of them named pgloading_* -- and LOADING is in the game's own screen vocabulary, but nobody has watched it appear here and the port does NOT put it in the chain on that basis. \ud83d\udccc WHERE THE OPEN QUESTION LIVES, added 2026-09-01: docs/port/BLOCKED.md carries the row -- 'what fills the 4.5 s before S00A'. An explicit unknown still needs a citation, or it cannot be distinguished from an unexamined one.",
-          "skippable": true,
-          "skippable_why": "HANDOFF Q9, MEASURED: one (A) press skips a movie -- the title was reached at 57 s against a 193 s baseline. Same rule the boot intro already uses.",
-          "skippable_kind": "measured",
-          "after_video": {
-            "goto": "title",
-            "kind": "authored",
-            "why": "AUTHORED, and it has to be: the game goes into MISSION 1, and gameplay is out of scope (PORT-MISSION section 7). P7's gate asks for 'plays, then returns to a defined state' -- this is that state. The title is chosen over the main menu because the boot's own end state is the title, so a run that finishes the new-game intro lands somewhere a player can start again from. Nothing measured says the game does this."
-          }
-        },
-        "ptbtn02": {
-          "label": "LOAD GAME",
-          "goto": null,
-          "goto_name": null,
-          "blocked": "The save-slot list is GP_SAVE_LOAD, not in this export. Destination MEASURED."
-        },
-        "ptbtn03": {
-          "label": "TUTORIAL",
-          "goto": null,
-          "goto_name": "TUTORIAL_MENU",
-          "goto_name_kind": "name match, not measured",
-          "goto_name_why": [
-            "NOT MEASURED, and the label says so. HANDOFF Q4 states it exactly: \"the",
-            "screens are measured; the ids are a name match onto the executable's class",
-            "names.\" So `TUTORIAL_MENU` is a string that exists in the executable and plausibly",
-            "denotes this screen -- nothing observed binds it to this transition.",
-            "",
-            "It is carried so a reader can search for it and so the port never has to",
-            "invent one. THE PORT NEVER BRANCHES ON IT: navigation uses `goto`, which is",
-            "a screen file, and this field is documentation.",
-            "",
-            "\ud83d\udd34 THIS `why` DID NOT EXIST UNTIL 2026-08-30. All seven `goto_name_kind`",
-            "labels rested on a sibling `why` that argues the DESTINATION -- a different",
-            "claim from where the NAME came from. `tools/port/audit-kinds` reports that",
-            "as BORROWED rather than ok, because a label resting on a neighbour's",
-            "argument reads as evidenced and is not."
-          ],
-          "blocked": "The lesson list is not a GP_TITLE build. Destination MEASURED."
-        },
-        "ptbtn04": {
-          "label": "OPTIONS",
-          "goto": "options",
-          "goto_name": null,
-          "goto_why": "UNBLOCKED 2026-09-03. This read goto:null with blocked: 'The settings menu is GP_OPTIONS, not in this export.' GP_OPTIONS is in the export now -- authored/screen_names.json export_archives -- and entry 19 is its root, named `options` from the text it renders: GAME SETTINGS, CONTROL SETTINGS, SOUND SETTINGS, SCREEN SETTINGS, BACK. docs/port/options-screens.md. The destination itself was always MEASURED; only the screen file was missing.",
-          "goto_kind": "measured-destination-newly-exported",
-          "limits": [
-            "\ud83d\udd34 THE SCREEN OPENS BUT DOES NOT NAVIGATE. Its five rows are kind 0x3003 and the exporter only treats 0x3002 as a button, so export buttons[] is empty and up/down move nothing. \u24b7 backs out correctly.",
-            "What 0x3003 MEANS is a decode question and is with the Decoder -- not widened here on the port's authority. The circumstantial case is strong (five rows, each with a focus record, on a screen whose own text lists five options) and circumstantial is exactly the standard this project keeps getting burned by.",
-            "None of the sub-screens is wired. Which row leads where is read off content, not measured navigation."
-          ]
-        },
-        "ptbtn05": {
-          "label": "EXTRAS",
-          "goto": "extras",
-          "goto_name": "EXTRA_MENU",
-          "goto_name_kind": "name match, not measured",
-          "goto_name_why": [
-            "NOT MEASURED, and the label says so. HANDOFF Q4 states it exactly: \"the",
-            "screens are measured; the ids are a name match onto the executable's class",
-            "names.\" So `EXTRA_MENU` is a string that exists in the executable and plausibly",
-            "denotes this screen -- nothing observed binds it to this transition.",
-            "",
-            "It is carried so a reader can search for it and so the port never has to",
-            "invent one. THE PORT NEVER BRANCHES ON IT: navigation uses `goto`, which is",
-            "a screen file, and this field is documentation.",
-            "",
-            "\ud83d\udd34 THIS `why` DID NOT EXIST UNTIL 2026-08-30. All seven `goto_name_kind`",
-            "labels rested on a sibling `why` that argues the DESTINATION -- a different",
-            "claim from where the NAME came from. `tools/port/audit-kinds` reports that",
-            "as BORROWED rather than ok, because a label resting on a neighbour's",
-            "argument reads as evidenced and is not."
-          ],
-          "why": "MEASURED, HANDOFF Q4: EXTRAS opens GP_TITLE build 6. It is the ONLY main-menu destination inside this archive, and therefore the only (A)-into-a-submenu the P5 gate can actually walk."
-        }
-      },
-      "labels_why": "The five labels are read off live-main-menu.png, a capture of the running game (docs/game/navigation.md, branch auto/no-disc-and-menu-captures 3a87a26). They are carried for logs and for a human reading this file; nothing draws them -- the button sprite already has its own text."
-    },
-    "extras": {
-      "initial_focus": "ptbtn11",
-      "initial_focus_kind": "measured",
-      "focus_persists": false,
-      "focus_persists_kind": "measured",
-      "focus_persists_why": [
-        "MEASURED 2026-08-30 -- EXTRAS RESETS. HANDOFF `4ed75e6`: ring back to",
-        "y=347.5 on re-entry after a confirmed DOWN, frame 0.0 % different from the",
-        "first entry, and the screen confirmed by eye as EXTRAS because an earlier",
-        "run was fooled about which screen it was on.",
-        "",
-        "\ud83d\udccc WRITTEN EXPLICITLY, THOUGH THE PORT'S DEFAULT IS ALREADY false. The",
-        "absent key and the measured false behave identically and mean completely",
-        "different things: one is 'nobody looked', the other is 'the game was",
-        "watched doing it'. `tools/port/audit-kinds` can see the second and not the",
-        "first, which is the whole reason for spending a key on it.",
-        "",
-        "\ud83d\udd34 AND THIS IS NOT A VINDICATION OF HOW IT GOT HERE. For one iteration the",
-        "port ASSERTED non-persistence for EXTRAS in `contract-check` while nothing",
-        "had measured it; the Decoder flagged that, and it turned out right. Being",
-        "right by luck does not retroactively make it evidence -- declining to",
-        "generalise the memory was the correct move, and encoding 'not measured",
-        "here' as a positive claim was a different and wrong one that happened to",
-        "land. The measurement is what makes it true; the assertion never did.",
-        "",
-        "\u26a0\ufe0f Do NOT generalise in either direction: main_menu persists, EXTRAS resets,",
-        "and OPTIONS / LOAD GAME / TUTORIAL are untouched."
-      ],
-      "initial_focus_why": [
-        "MEASURED, unlike the main menu's: EXTRAS opens focused on MISSION SELECT (live-extras.png). It is authored here only because there is nowhere else to put a measurement -- it is not a choice.",
-        "",
-        "",
-        "\u2705 CAVEAT LIFTED 2026-08-30 -- MEASURED, not a single-entry reading any more.",
-        "HANDOFF `4ed75e6`, docs/re/data/extras-focus-resets.txt: EXTRAS opens at ring",
-        "y=347.5 on MISSION SELECT, moves to 427.5 after one delivery-confirmed DOWN,",
-        "and returns to 347.5 on re-entry with the frame 0.0 % different from the first",
-        "entry. Because this screen RESETS, a single-entry reading of it is not",
-        "measuring history -- which is precisely what made the caveat necessary while",
-        "persistence here was unknown.",
-        "",
-        "\u2705 THE AMBIGUITY IS RESOLVED -- MEASURED 2026-08-31, and it went the way",
-        "that makes `ptbtn11` right for a REASON rather than by coincidence.",
-        "",
-        "A submenu resets to ITS OWN OPENING ITEM, and that item is a per-screen",
-        "default which need NOT be the first. Decoder, docs/re/data/",
-        "difficulty-resets-to-named-item.txt: DIFFICULTY opens on NORMAL (second of",
-        "four); after one confirmed DOWN to HARD, (B) out and (A) back returns to",
-        "NORMAL -- in-cursor 1.0 from where it opened against 93.9 from where it was",
-        "left. Reproduced on a FRESH BOOT and confirmed by eye, not read off the",
-        "2026-08-29 capture.",
-        "",
-        "So the port's `initial_focus` is the reset target, and `buttons[0]` in",
-        "`MenuFlow.initial_focus` is a REPAIR rather than a default -- which is how",
-        "it was already documented, and is now measured rather than principled.",
-        "",
-        "\u2754 STILL OPEN, and not leaned on: whether the reset target MOVES once a",
-        "difficulty has actually been confirmed. A game that remembered your last",
-        "choice would behave differently, and the probe never confirms one -- the",
-        "same SELECT DATA crash that constrains the run prevents testing it.",
-        "",
-        "",
-        "\ud83d\udd34 CORRECTED 2026-08-31. This read \"it matters IF another screen is ever",
-        "authored\" whose opening item is not its first. Such a screen exists and is",
-        "recorded IN THIS FILE: DIFFICULTY, under `main_menu/buttons/ptbtn01`, is",
-        "EASY/NORMAL/HARD/BACK and opens on NORMAL -- the SECOND of four. Measured:",
-        "driven with no d-pad, unchanged for 90 s, matching the committed capture at",
-        "r=+0.999 (Decoder, docs/re/captures/newgame-path/newgame-difficulty.png).",
-        "",
-        "So \"a screen opens on its first item\" is REFUTED as a general description of",
-        "this game. On EXTRAS, TUTORIAL and OPTIONS the named item and the top item",
-        "coincide BY ACCIDENT. A top-item rule would be wrong on DIFFICULTY.",
-        "",
-        "nobody can separate \"resets to MISSION SELECT\" from \"resets to the TOP ITEM\".",
-        "They coincide here -- ptbtn11 is both. The port's value is correct under either",
-        "reading, and the REASON is not established.",
-        "",
-        "The superseded caveat is kept below.",
-        "  (was) \u26a0\ufe0f WEAKENED 2026-08-30 -- the OBSERVATION stands, its reading as an INITIAL",
-        "  (was) focus does not. It was taken on a single entry. Now that the main menu is known",
-        "  (was) to remember its cursor across a round trip, a one-entry reading of any screen",
-        "  (was) may be measuring HISTORY rather than what the screen opens on -- the same",
-        "  (was) objection that reframed the main menu's TUTORIAL/NEW GAME disagreement.",
-        "  (was) ",
-        "  (was) Kept as `measured` because the frame really does show MISSION SELECT focused,",
-        "  (was) and kept as the port's opening item because it is the only reading there is.",
-        "  (was) \ud83d\udd34 If EXTRAS turns out to persist, this becomes history and the kind must",
-        "  (was) change with it.",
-        "",
-        "\ud83d\udd34 CHECKED AGAINST THE BYTES 2026-08-31 by both agents -- and NOT independently.",
-        "Settled by fact, not by my inference: the Decoder's 282/362/442 came from",
-        "`crates/sylpheed-formats/examples/extras_button_order.rs`, which calls",
-        "`ui_layout::parse_build` -- THE SAME CRATE this port's export uses. The",
-        "Python RATC parsers in their tree exist and did not produce that number.",
-        "So the two legs are ONE READER USED TWICE, and the agreement carries no",
-        "information about the reader being right; it carries information only about",
-        "two callers of it agreeing, which they could not fail to do.",
-        "",
-        "\u26a0\ufe0f The VALUE is unaffected -- `ptbtn11` is decided by the DIFFICULTY",
-        "measurement and by the reset finding. What died is a word I used about the",
-        "evidence, which is the third such word in three iterations.",
-        "",
-        "is WEAKENED, by my own audit rather than by theirs.",
-        "",
-        "Applying their test to my own sentence: could my reading have come out",
-        "differently given theirs? Only if the implementations differ. Mine is",
-        "`sylpheed_formats::ui_layout::parse_build` via this port's export. Their tree",
-        "does carry separate Python RATC parsers (`kf_record_census.py` and others),",
-        "so a second implementation EXISTS -- but which reader produced their",
-        "282/362/442 is not established by me, and if they used the same crate the",
-        "two legs are one reader used twice.",
-        "",
-        "So: the values agreeing is still evidence, and calling it INDEPENDENT was a",
-        "claim about their tooling that I did not check. Recorded at the strength I",
-        "can support. \u26a0\ufe0f Nothing rests on it -- the row order is also decided by the",
-        "DIFFICULTY measurement -- which is exactly why it went unexamined.",
-        "",
-        "Decoder attempted to refute this value and it survives: `ptbtn11` is the TOP",
-        "button on this screen -- y 282 against 362 and 442 -- so the port is right",
-        "whichever reading of the reset target applies. Confirmed from THIS port's own",
-        "export, a different reader of the same disc: extras 282/362/442, and the main",
-        "menu as a control at 162/242/322/401/482.",
-        "",
-        "\ud83d\udd34 WHICH ALSO MEANS EXTRAS CANNOT SEPARATE the two readings -- named item and",
-        "top item coincide here. It was DIFFICULTY, opening on its second of four, that",
-        "settled it."
-      ],
-      "on_cancel": {
-        "goto": "main_menu",
-        "goto_name": "TITLE_MENU",
-        "goto_name_kind": "name match, not measured",
-        "goto_name_why": [
-          "NOT MEASURED, and the label says so. HANDOFF Q4 states it exactly: \"the",
-          "screens are measured; the ids are a name match onto the executable's class",
-          "names.\" So `TITLE_MENU` is a string that exists in the executable and plausibly",
-          "denotes this screen -- nothing observed binds it to this transition.",
-          "",
-          "It is carried so a reader can search for it and so the port never has to",
-          "invent one. THE PORT NEVER BRANCHES ON IT: navigation uses `goto`, which is",
-          "a screen file, and this field is documentation.",
-          "",
-          "\ud83d\udd34 THIS `why` DID NOT EXIST UNTIL 2026-08-30. All seven `goto_name_kind`",
-          "labels rested on a sibling `why` that argues the DESTINATION -- a different",
-          "claim from where the NAME came from. `tools/port/audit-kinds` reports that",
-          "as BORROWED rather than ok, because a label resting on a neighbour's",
-          "argument reads as evidenced and is not."
-        ],
-        "why": "MEASURED, HANDOFF Q5: (B) goes up one level and RESTORES FOCUS to the item you came from. EXTRAS advertises (B) in its own footer -- the red glyph is in ptmsg2.png and absent from the main menu's ptmsg.png."
-      },
-      "buttons": {
-        "ptbtn11": {
-          "label": "MISSION SELECT",
-          "goto": null,
-          "goto_name": null,
-          "blocked": "The stage list is GP_MISSION_SELECT, not in this export. Destination MEASURED."
-        },
-        "ptbtn12": {
-          "label": "MOVIE THEATER",
-          "goto": null,
-          "goto_name": null,
-          "blocked": "NEVER OPENED. docs/game/navigation.md marks this one unknown -- not merely unexported. Do not assume it opens GP_MOVIE_THEATER; that would be a name match dressed as a destination."
-        },
-        "ptbtn13": {
-          "label": "BACK",
-          "goto": "main_menu",
-          "goto_name": "TITLE_MENU",
-          "goto_name_kind": "name match, not measured",
-          "goto_name_why": [
-            "NOT MEASURED, and the label says so. HANDOFF Q4 states it exactly: \"the",
-            "screens are measured; the ids are a name match onto the executable's class",
-            "names.\" So `TITLE_MENU` is a string that exists in the executable and plausibly",
-            "denotes this screen -- nothing observed binds it to this transition.",
-            "",
-            "It is carried so a reader can search for it and so the port never has to",
-            "invent one. THE PORT NEVER BRANCHES ON IT: navigation uses `goto`, which is",
-            "a screen file, and this field is documentation.",
-            "",
-            "\ud83d\udd34 THIS `why` DID NOT EXIST UNTIL 2026-08-30. All seven `goto_name_kind`",
-            "labels rested on a sibling `why` that argues the DESTINATION -- a different",
-            "claim from where the NAME came from. `tools/port/audit-kinds` reports that",
-            "as BORROWED rather than ok, because a label resting on a neighbour's",
-            "argument reads as evidenced and is not."
-          ],
-          "same_as_cancel": true,
-          "why": "MEASURED: EXTRAS' third item is BACK (live-extras.png). Treated as (B): it pops the stack, so focus is restored on the main menu exactly as (B) does. Whether the game distinguishes them is untested and there is no reason here to invent a difference."
-        }
-      }
-    }
+      "What each button does. NOT FILLED IN -- that is P5. HANDOFF Q4 measured the",
+      "destination screens and the RE agent later decoded that a transition is a",
+      "lookup by NAME, giving a candidate vocabulary (TITLE_SCREEN, TITLE_MENU,",
+      "LOADING, DIFFICULTY, EXTRA_MENU, TUTORIAL_MENU). Those are the right `goto`",
+      "targets when this is written, marked as the name match they are."
+    ]
   }
 }

authored/screen_names.json

@@ -16,151 +16,55 @@
     "",
     "Delete an entry here the day the RE agent decodes a name field."
   ],
-  "export_archives": [
-    "dat/GP_TITLE.pak",
-    "dat/GP_OPTIONS.pak",
-    "dat/GP_SAVE_LOAD.pak"
-  ],
-  "export_archives_why": [
-    "WHICH disc archives the export reads screen builds from.",
-    "",
-    "GP_TITLE was the only one for the whole project, hardcoded in the",
-    "exporter. That single constant is why four of the five main-menu",
-    "destinations are dead: authored/flow.json records LOAD GAME, TUTORIAL,",
-    "OPTIONS and NEW GAME's difficulty chain as MEASURED destinations,",
-    "blocked only because 'there is no screen file to go to'.",
-    "",
-    "GP_OPTIONS ADDED 2026-09-03, and deliberately alone. The probe",
-    "(crates/sylpheed-export/examples/probe_archives.rs) finds screen builds",
-    "in 24 archives with the EXISTING detector -- GP_OPTIONS 14,",
-    "GP_SAVE_LOAD 18, GP_DIALOG 105, GP_TUTORIAL 2. Adding all four at once",
-    "would land 139 new screens together and make any regression",
-    "unattributable, so this takes the smallest archive first.",
-    "",
-    "\u26a0\ufe0f is_build() PARSING IS NOT RENDERING. It says the record is a build,",
-    "not that its sprites resolve or that anyone has identified the screen.",
-    "Unnamed builds export as build_NN by entry index. Expect names to be",
-    "wrong-looking until someone drives the game to them; that is a naming",
-    "gap, not a decode failure.",
-    "",
-    "GP_SAVE_LOAD ADDED 2026-09-03, again alone. 18 builds. It is main_menu",
-    "ptbtn02 (LOAD GAME)'s destination, recorded in authored/flow.json as a",
-    "MEASURED destination blocked only by 'not a GP_TITLE build'. It may also",
-    "hold SELECT DATA, the second screen of the NEW GAME chain, but that is a",
-    "guess from the name until the screens are rendered and read.",
-    "",
-    "\u26a0\ufe0f OUT OF SCOPE ON PURPOSE: GP_HANGAR_ARSENAL (390 builds), the",
-    "GP_MAIN_GAME_* set and the rest of the gameplay archives. MISSION",
-    "section 7 scopes gameplay out, and a screen that parses is not a screen",
-    "this milestone wants."
-  ],
   "archives": {
     "dat/GP_TITLE.pak": {
       "2": {
         "name": "press_start",
-        "why": "HANDOFF Q2: builds 2/3 are the PRESS (A) BUTTON plate -- a build of its own, composited over the title and faded in a beat later. English of the EN/JP pair. Measured against a live capture. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "HANDOFF Q2: builds 2/3 are the PRESS (A) BUTTON plate -- a build of its own, composited over the title and faded in a beat later. English of the EN/JP pair. Measured against a live capture."
       },
       "3": {
         "name": "press_start_jp",
-        "why": "HANDOFF Q2: the Japanese twin of build 2. Out of scope for this milestone; named so it is not mistaken for a screen we need. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "HANDOFF Q2: the Japanese twin of build 2. Out of scope for this milestone; named so it is not mistaken for a screen we need."
       },
       "4": {
         "name": "title",
-        "why": "HANDOFF Q2: build 4 is the English title art. Measured against a live capture. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "HANDOFF Q2: build 4 is the English title art. Measured against a live capture."
       },
       "5": {
         "name": "main_menu",
-        "why": "HANDOFF Q2: builds 5/8 are the five-button main menu; 5 is English. Measured against a live capture. (An earlier reading called 8 a submenu and was withdrawn -- 8 is the Japanese main menu.) \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "HANDOFF Q2: builds 5/8 are the five-button main menu; 5 is English. Measured against a live capture. (An earlier reading called 8 a submenu and was withdrawn -- 8 is the Japanese main menu.)"
       },
       "6": {
         "name": "extras",
-        "why": "HANDOFF Q2: builds 6/9 are the EXTRAS submenu, the only submenu inside this archive. Measured against a fresh EXTRAS capture. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "HANDOFF Q2: builds 6/9 are the EXTRAS submenu, the only submenu inside this archive. Measured against a fresh EXTRAS capture."
       },
       "7": {
         "name": "title_jp",
-        "why": "HANDOFF Q2: the Japanese twin of build 4. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "HANDOFF Q2: the Japanese twin of build 4."
       },
       "8": {
         "name": "main_menu_jp",
-        "why": "HANDOFF Q2: the Japanese twin of build 5. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "HANDOFF Q2: the Japanese twin of build 5."
       },
       "9": {
         "name": "extras_jp",
-        "why": "HANDOFF Q2: the Japanese twin of build 6. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "HANDOFF Q2: the Japanese twin of build 6."
       },
       "10": {
         "name": "publisher_logo",
-        "why": "The SQUARE ENIX PUBLISHER wordmark -- the FIRST thing the boot sequence shows, before the developer logos. Measured by the RE agent 2026-08-29, render grid at docs/re/captures/title-builds/splash-both-halves-rendered.png. Entries 10/13 are region twins distinguished by the trademark glyph; 10 carries the (TM). \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "The SQUARE ENIX PUBLISHER wordmark -- the FIRST thing the boot sequence shows, before the developer logos. Measured by the RE agent 2026-08-29, render grid at docs/re/captures/title-builds/splash-both-halves-rendered.png. Entries 10/13 are region twins distinguished by the trademark glyph; 10 carries the (TM)."
       },
       "13": {
         "name": "publisher_logo_r",
-        "why": "The region twin of entry 10, carrying (R) where 10 carries (TM). Named so it is not mistaken for a second screen the boot path needs. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "The region twin of entry 10, carrying (R) where 10 carries (TM). Named so it is not mistaken for a second screen the boot path needs."
       },
       "11": {
         "name": "developer_logos",
-        "why": "The GAME ARTS / SETA / studio anima logos -- the developer splash, shown after the publisher wordmark. HANDOFF Q2 and the RE agent's 2026-08-29 render grid; draws 7/7 elements. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "The GAME ARTS / SETA / studio anima logos -- the developer splash, shown after the publisher wordmark. HANDOFF Q2 and the RE agent's 2026-08-29 render grid; draws 7/7 elements."
       },
       "14": {
         "name": "developer_logos_r",
-        "why": "The region twin of entry 11, as 13 is to 10. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
-      }
-    },
-    "dat/GP_OPTIONS.pak": {
-      "3": {
-        "name": "sound_settings",
-        "why": "SOUND SETTINGS -- Music/Movie/Voice/SFX Volume. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "4": {
-        "name": "control_settings",
-        "why": "CONTROL SETTINGS -- Control Type, Throttle, sensitivities, Vibration. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "5": {
-        "name": "sound_settings_jp",
-        "why": "\u30b5\u30a6\u30f3\u30c9\u8a2d\u5b9a, the JP pair of entry 3. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "6": {
-        "name": "screen_settings",
-        "why": "Gamma Correction with R/G/B and a NEXT PAGE affordance. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "7": {
-        "name": "screen_settings_page2",
-        "why": "White Level / Black Level Adjust, PREVIOUS PAGE. Page 2 of entry 6. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "8": {
-        "name": "control_settings_jp",
-        "why": "\u64cd\u4f5c\u8a2d\u5b9a, the JP pair of entry 4. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "9": {
-        "name": "screen_settings_jp",
-        "why": "\u30ac\u30f3\u30de\u88dc\u6b63\u30ec\u30d9\u30eb, the JP pair of entry 6. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "10": {
-        "name": "screen_settings_page2_jp",
-        "why": "\u767d\u30ec\u30d9\u30eb/\u9ed2\u30ec\u30d9\u30eb\u8abf\u6574, the JP pair of entry 7. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "16": {
-        "name": "game_settings",
-        "why": "GAME SETTINGS -- Auto-Save, View Point, Radio Log, Subtitles. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "18": {
-        "name": "game_settings_jp",
-        "why": "\u30b2\u30fc\u30e0\u8a2d\u5b9a, the JP pair of entry 16. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "19": {
-        "name": "options",
-        "why": "\ud83d\udd34 THE OPTIONS ROOT. Rows: GAME SETTINGS, CONTROL SETTINGS, SOUND SETTINGS, SCREEN SETTINGS, BACK -- the four screens named here plus a back row. This is main_menu ptbtn04's destination. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "20": {
-        "name": "control_customize",
-        "why": "CUSTOMIZE -- per-action key remapping, reached from CONTROL SETTINGS. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "21": {
-        "name": "options_jp",
-        "why": "The JP OPTIONS root, pair of entry 19. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
-      },
-      "22": {
-        "name": "control_customize_jp",
-        "why": "\u30ad\u30fc\u30ab\u30b9\u30bf\u30de\u30a4\u30ba, the JP pair of entry 20. Named from the screen's OWN RENDERED TEXT. Each was exported, rendered by the port at rest and read: the title and row labels are legible English or Japanese. That is identification by CONTENT THE SCREEN STATES ABOUT ITSELF, not by position, size or ordinal -- the three this project has been burned by. Contact sheets were reviewed 2026-09-03; docs/port/options-screens.md."
+        "why": "The region twin of entry 11, as 13 is to 10."
       }
     }
   },
@@ -171,19 +75,19 @@
     "dat/GP_TITLE.pak": {
       "10": {
         "name": "publisher_logo",
-        "why": "LOCATED BY ENTRY INDEX, not by a rule. These four bundles declare their sprites directly and have no .rat layout child, so `is_build` cannot see them -- and the RE agent established that NO content rule can: design size fails (every extra composable bundle sampled is 1280x720, the same as every screen) and element count fails (fragments run 2..15 elements in GP_OPTIONS/GP_SAVE_LOAD while these are 3 and 7 -- the ranges overlap). Safe here and not in general: in GP_TITLE the widened set adds exactly these four and all four are real screens, zero fragments. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "LOCATED BY ENTRY INDEX, not by a rule. These four bundles declare their sprites directly and have no .rat layout child, so `is_build` cannot see them -- and the RE agent established that NO content rule can: design size fails (every extra composable bundle sampled is 1280x720, the same as every screen) and element count fails (fragments run 2..15 elements in GP_OPTIONS/GP_SAVE_LOAD while these are 3 and 7 -- the ranges overlap). Safe here and not in general: in GP_TITLE the widened set adds exactly these four and all four are real screens, zero fragments."
       },
       "11": {
         "name": "developer_logos",
-        "why": "As entry 10: located by index because no content rule distinguishes a splash from a fragment. 7 elements, all drawn. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "As entry 10: located by index because no content rule distinguishes a splash from a fragment. 7 elements, all drawn."
       },
       "13": {
         "name": "publisher_logo_r",
-        "why": "As entry 10, region twin. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "As entry 10, region twin."
       },
       "14": {
         "name": "developer_logos_r",
-        "why": "As entry 11, region twin. \ud83d\udccc SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. \u26a0\ufe0f The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
+        "why": "As entry 11, region twin."
       }
     }
   }

crates/sylpheed-export/examples/probe_archives.rs

@@ -1,42 +0,0 @@
-//! Which disc archives contain UI screen builds?
-//!
-//! The exporter reads `dat/GP_TITLE.pak` and nothing else, so four of the five
-//! main-menu destinations have no screen file to go to: `authored/flow.json`
-//! records LOAD GAME as `GP_SAVE_LOAD`, OPTIONS as `GP_OPTIONS`, and NEW GAME's
-//! chain as `DLG_SELECT_DIFFICULTY` -> `SELECT DATA`, all measured destinations
-//! that this export cannot reach.
-//!
-//! This asks the cheap question before anyone refactors the exporter: does the
-//! EXISTING build detector find anything in those archives? It changes nothing
-//! and writes nothing.
-//!
-//!   cargo run --release -p sylpheed-export --example probe_archives
-use sylpheed_formats::{pak::PakArchive, ui_layout};
-
-fn main() -> anyhow::Result<()> {
-    let disc = std::env::var("SYLPHEED_DISC").unwrap_or_else(|_| "/disc".into());
-    let mut names: Vec<String> = std::fs::read_dir(format!("{disc}/dat"))?
-        .filter_map(|e| e.ok())
-        .map(|e| e.file_name().to_string_lossy().into_owned())
-        .filter(|n| n.ends_with(".pak"))
-        .collect();
-    names.sort();
-    println!("{:<32} {:>7} {:>8}", "archive", "entries", "builds");
-    for n in names {
-        let path = format!("{disc}/dat/{n}");
-        let Ok(ar) = PakArchive::open(&path) else {
-            println!("{n:<32} {:>7} {:>8}", "-", "open failed");
-            continue;
-        };
-        let total = ar.entries().len();
-        let builds = ar
-            .entries()
-            .iter()
-            .filter(|e| ar.read(e).map(|b| ui_layout::is_build(&b)).unwrap_or(false))
-            .count();
-        if builds > 0 || n.contains("OPTIONS") || n.contains("SAVE") || n.contains("DIALOG") {
-            println!("{n:<32} {total:>7} {builds:>8}");
-        }
-    }
-    Ok(())
-}

crates/sylpheed-export/src/main.rs

@@ -12,7 +12,6 @@
 //!
 //! See `docs/FORMAT.md` for the schema and `docs/MISSION.md` for scope.
 
-mod audio;
 mod check;
 mod video;
 mod screen;
@@ -21,7 +20,7 @@ use anyhow::{Context, Result};
 use clap::Parser;
 use serde::Serialize;
 use std::path::{Path, PathBuf};
-use sylpheed_formats::{media, pak::PakArchive, ui_layout};
+use sylpheed_formats::{pak::PakArchive, ui_layout};
 
 /// The revision of `sylpheed-formats` this exporter is pinned to, recorded in
 /// every file it writes. Keep in step with `Cargo.toml` — it is what makes an
@@ -77,48 +76,6 @@ struct ManifestVideo {
     /// dislikes the quality re-runs one line rather than reverse-engineering it.
     command: String,
     why: &'static str,
-    /// What the runtime should have played, so it can report what it did.
-    /// See `video::Transcoded::duration_s` — the port measured its player
-    /// presenting 28–47 % of a stream's frames, and seconds alone hide that.
-    duration_s: f64,
-    fps: f64,
-}
-
-/// One exported audio file. Carries the same provenance a video does, plus the
-/// measured peak and duration: silence and clipping are the two audio failures
-/// that pass every check that is not looking for them.
-#[derive(Serialize)]
-struct ManifestAudio {
-    /// `se` or `bgm`. The runtime dispatches on it, so it is a field rather
-    /// than a prefix on `name` that a consumer would have to parse.
-    kind: &'static str,
-    name: String,
-    file: String,
-    command: String,
-    why: String,
-    #[serde(skip_serializing_if = "Option::is_none")]
-    peak_dbfs: Option<f32>,
-    #[serde(skip_serializing_if = "Option::is_none")]
-    duration_s: Option<f32>,
-    /// 🔴 One line saying what this asset is KNOWN to be missing, for the
-    /// runtime to announce. Absent means nothing is known to be missing --
-    /// never that the asset was checked and is complete.
-    ///
-    /// It exists because the export could already say this and the RUNTIME
-    /// could not. `why` carries the full account, but it is a paragraph aimed
-    /// at a reader of the manifest; a player hears clean dialogue and has no
-    /// way to learn that a stream is absent from it. This port already
-    /// announces the two measured screens NEW GAME jumps over, on the principle
-    /// that a gap is announced before it is opened. Audio had no equivalent.
-    #[serde(skip_serializing_if = "Option::is_none")]
-    incomplete: Option<String>,
-    /// The game's own cue identifier where one is a NAME MATCH. Absent means
-    /// nobody has claimed one -- never that the binding is unknown.
-    #[serde(skip_serializing_if = "Option::is_none")]
-    name_match: Option<String>,
-    /// What the runtime does at the end of the file, where that was authored.
-    #[serde(skip_serializing_if = "Option::is_none")]
-    loop_mode: Option<String>,
 }
 
 #[derive(Serialize)]
@@ -131,8 +88,6 @@ struct Manifest {
     screens: Vec<ManifestScreen>,
     #[serde(skip_serializing_if = "Vec::is_empty")]
     videos: Vec<ManifestVideo>,
-    #[serde(skip_serializing_if = "Vec::is_empty")]
-    audio: Vec<ManifestAudio>,
     warnings: Vec<String>,
 }
 
@@ -208,54 +163,6 @@ fn load_also_export(authored: &Path) -> Result<AlsoExport> {
 /// exactly four bundles and all four are real screens, with zero fragments. In
 /// another archive it would not be, which is why this is an allow-list and not
 /// a widened predicate.
-/// Which archives the export reads, from `authored/screen_names.json`
-/// `export_archives`.
-///
-/// 🔴 THIS WAS ONE HARDCODED CONSTANT AND IT COST FOUR MENU DESTINATIONS.
-/// `authored/flow.json` records LOAD GAME, TUTORIAL, OPTIONS and NEW GAME's
-/// difficulty chain as MEASURED destinations that are `blocked` because "not a
-/// GP_TITLE build, so there is no screen file to go to". The blocker was never
-/// the disc or the reader -- `examples/probe_archives.rs` finds screen builds in
-/// 24 archives using the EXISTING detector. It was this line.
-///
-/// Absent from the authored file, it stays exactly what it was, so an old
-/// `authored/` tree exports what it always did.
-fn load_export_archives(authored: &Path) -> Result<Vec<String>> {
-    let path = authored.join("screen_names.json");
-    let Ok(text) = std::fs::read_to_string(&path) else {
-        return Ok(vec!["dat/GP_TITLE.pak".into()]);
-    };
-    let v: serde_json::Value = serde_json::from_str(&text)
-        .with_context(|| format!("parse {}", path.display()))?;
-    match v.get("export_archives").and_then(|a| a.as_array()) {
-        None => Ok(vec!["dat/GP_TITLE.pak".into()]),
-        Some(list) => Ok(list
-            .iter()
-            .filter_map(|e| e.as_str().map(str::to_owned))
-            .collect()),
-    }
-}
-
-/// The sprite subdirectory for an archive: `dat/GP_OPTIONS.pak` -> `options`.
-///
-/// ⚠️ NOT cosmetic. Sprites are written to `sprites/<group>/<screen>/`, so two
-/// archives sharing a group would collide by screen name -- and unnamed builds
-/// are named `build_NN` by ENTRY INDEX, which restarts at 0 in every archive.
-/// `GP_TITLE` keeps its historical `title` so no existing path moves.
-fn group_for(archive: &str) -> &'static str {
-    match archive {
-        "dat/GP_TITLE.pak" => "title",
-        "dat/GP_OPTIONS.pak" => "options",
-        "dat/GP_SAVE_LOAD.pak" => "save_load",
-        "dat/GP_TUTORIAL.pak" => "tutorial",
-        "dat/GP_DIALOG.pak" => "dialog",
-        // Deliberately not derived from the filename: a new archive should be a
-        // decision someone made, not a directory that appears because a string
-        // parsed. An unmapped archive is rejected below.
-        _ => "",
-    }
-}
-
 fn screen_builds(ar: &PakArchive, also: Option<&std::collections::BTreeMap<String, NameEntry>>)
     -> Vec<(usize, Vec<u8>)>
 {
@@ -288,275 +195,86 @@ fn main() -> Result<()> {
 fn run_export(disc: &Path, out: &Path, authored_dir: &Path) -> Result<()> {
     let names = load_names(authored_dir)?;
 
-    // Built up as the export runs. A warning is a thing a CONSUMER of the tree
-    // has to know about; it is not an error, and it is not a log line, because
-    // the person who needs it reads `manifest.json` and never sees stdout.
-    let mut warnings: Vec<String> = vec![
-        String::new(), // replaced below once the archive list is known
-        "The four splash bundles (entries 10/13 publisher, 11/14 developer) have no .rat \
-         layout child, so `is_build` cannot see them and no content rule can: element \
-         count and design size both overlap with two-element fragments in other archives. \
-         They are located by ENTRY INDEX from authored/screen_names.json `also_export`, \
-         which is a locator and not a claim -- see each one's name_why."
-            .into(),
-    ];
-
     // Derived output is regenerated wholesale: clear it, so a screen that stops
     // being exported stops existing rather than lingering as a stale file that
     // still validates.
-    //
-    // 🔴 EXCEPT `video/`, and leaving it out was a bug that hid in plain sight.
-    // `video::transcode` has always carried a cache -- it writes a `.cmd`
-    // sidecar with the exact command, the source size and the channel count, and
-    // skips the encode when all three still match. Its own doc comment says
-    // "without it every re-export pays ~4 minutes to produce a byte-identical
-    // file". **This wipe deleted the sidecar and the output immediately before
-    // the check, so the cache had never hit once.** Six exports in one session
-    // paid ~48 minutes of Theora to produce five byte-identical files, and
-    // nothing reported it: the cache is silent when it works and silent when it
-    // does not.
-    //
-    // The wholesale guarantee is kept rather than weakened -- everything else is
-    // still cleared outright, and `prune_videos` below deletes any file in
-    // `video/` that this run did not claim, so a movie that stops being exported
-    // still stops existing.
     if out.exists() {
-        for entry in std::fs::read_dir(&out).context("clear the output tree")? {
-            let entry = entry?;
-            if entry.file_name() == "video" {
-                continue;
-            }
-            if entry.file_type()?.is_dir() {
-                std::fs::remove_dir_all(entry.path())
-            } else {
-                std::fs::remove_file(entry.path())
-            }
-            .with_context(|| format!("clear {}", entry.path().display()))?;
-        }
+        std::fs::remove_dir_all(&out).context("clear the output tree")?;
     }
     std::fs::create_dir_all(&out)?;
 
+    let archive = "dat/GP_TITLE.pak";
+    let pak = disc.join(archive);
+    let ar = PakArchive::open(&pak).with_context(|| format!("open {}", pak.display()))?;
     let also = load_also_export(authored_dir)?;
-    let archives = load_export_archives(authored_dir)?;
-    warnings[0] = format!(
-        "Screen builds from {} only ({}). Other archives on the disc also contain UI \
-         builds and are not exported. Only the two movies MISSION section 6 puts in scope.",
-        archives.len(),
-        archives.join(", ")
-    );
-    let mut screens = Vec::new();
-    for archive in archives.iter().map(String::as_str) {
-        let group = group_for(archive);
-        if group.is_empty() {
-            anyhow::bail!(
-                "authored/screen_names.json export_archives lists {archive}, which has no \
-                 sprite group in group_for(). Add one deliberately -- deriving it from the \
-                 filename would let a typo create a directory."
-            );
-        }
-        let pak = disc.join(archive);
-        let ar = PakArchive::open(&pak).with_context(|| format!("open {}", pak.display()))?;
-        let archive_also = also.get(archive);
-        let builds = screen_builds(&ar, archive_also);
-        println!("{archive}: {} screen build(s) -> sprites/{group}/", builds.len());
+    let archive_also = also.get(archive);
+    let builds = screen_builds(&ar, archive_also);
+    println!("{archive}: {} screen build(s)", builds.len());
 
-        let archive_names = names.get(archive);
-        for (build_idx, (entry, bytes)) in builds.iter().enumerate() {
-            // Keyed by ENTRY, not by the ordinal: widening the enumeration to reach
-            // the splash renumbers ordinals, and a name that moves when the rule
-            // changes is not a name.
-            let key = entry.to_string();
-            let named = archive_names
-                .and_then(|m| m.get(&key))
-                .or_else(|| archive_also.and_then(|m| m.get(&key)));
-            let (name, name_source, why) = match named {
-                Some(e) => (e.name.clone(), "authored", e.why.clone()),
-                // Nobody has identified this build. Emit a stable synthetic id and
-                // say in the file that the name is not a recovered one.
-                None => (format!("build_{entry:02}"), "index", None),
-            };
-            let ex = screen::export_build(
-                &out,
-                archive,
-                *entry,
-                build_idx,
-                bytes,
-                &name,
-                name_source,
-                why,
-                group,
-                EXPORTER,
-                FORMATS_REV,
-            )
-            .with_context(|| format!("export build {build_idx} of {archive}"))?;
-            println!(
-                "  [{build_idx}] entry {entry:<3} -> {}  ({} sprites{})",
-                ex.json_path,
-                ex.sprites,
-                if ex.missing.is_empty() {
-                    String::new()
-                } else {
-                    format!(", {} missing", ex.missing.len())
-                }
-            );
-            screens.push(ManifestScreen {
-                name: ex.name,
-                file: ex.json_path,
-                sprites: ex.sprites,
-                missing_sprites: ex.missing,
-            });
-        }
+    let archive_names = names.get(archive);
+    let mut screens = Vec::new();
+    for (build_idx, (entry, bytes)) in builds.iter().enumerate() {
+        // Keyed by ENTRY, not by the ordinal: widening the enumeration to reach
+        // the splash renumbers ordinals, and a name that moves when the rule
+        // changes is not a name.
+        let key = entry.to_string();
+        let named = archive_names
+            .and_then(|m| m.get(&key))
+            .or_else(|| archive_also.and_then(|m| m.get(&key)));
+        let (name, name_source, why) = match named {
+            Some(e) => (e.name.clone(), "authored", e.why.clone()),
+            // Nobody has identified this build. Emit a stable synthetic id and
+            // say in the file that the name is not a recovered one.
+            None => (format!("build_{entry:02}"), "index", None),
+        };
+        let ex = screen::export_build(
+            &out,
+            archive,
+            *entry,
+            build_idx,
+            bytes,
+            &name,
+            name_source,
+            why,
+            "title",
+            EXPORTER,
+            FORMATS_REV,
+        )
+        .with_context(|| format!("export build {build_idx} of {archive}"))?;
+        println!(
+            "  [{build_idx}] entry {entry:<3} -> {}  ({} sprites{})",
+            ex.json_path,
+            ex.sprites,
+            if ex.missing.is_empty() {
+                String::new()
+            } else {
+                format!(", {} missing", ex.missing.len())
+            }
+        );
+        screens.push(ManifestScreen {
+            name: ex.name,
+            file: ex.json_path,
+            sprites: ex.sprites,
+            missing_sprites: ex.missing,
+        });
     }
 
     // MISSION §6: the boot intro and the one new-game intro only.
     let mut videos = Vec::new();
-    let mut movie_lengths: Vec<(&'static str, Option<f32>)> = Vec::new();
-    // 🔴 The export deviates from a HUMAN decision, and until this warning
-    // existed nobody could tell. MISSION §6 pins the 5.1 fold; `video.rs` ships
-    // that matrix scaled by 0.4142, i.e. 7.65 dB quieter. The deviation is
-    // justified for one of the two movies and over-broad for the other, and
-    // which of the three options to take is not the exporter's call -- so it is
-    // reported on every run rather than left in a doc comment nobody opens.
-    if video::MOVIES.iter().any(|m| disc.join(m.src).exists()) {
-        warnings.push(
-            "video/*.ogv: the 5.1->stereo fold is NOT the matrix MISSION §6 pins. §6 fixes it at              FL = 1.0*FL + 0.707*FC + 0.707*BL (a human decision, 2026-08-29); this export ships              that matrix scaled by 0.4142 -- same weighting, 7.65 dB quieter. Measured over the              whole of both movies, float-decoded so nothing is pre-clamped: under the PINNED              matrix ADV peaks at +4.26 dBFS with 4406 samples at or over full scale (1874 more              than 1 dB over, longest clamped run 0.333 ms), while S00A peaks at -1.34 dBFS and              never clips. So the pin overloads ADV and this constant is over-broad for S00A; the              smallest single scalar under which neither clamps is 1/1.6339 = 0.612. NOT changed              on the exporter's own authority -- the level of a mix is what §6 reserves to a              human. See docs/port/DECISIONS.md."
-                .to_string(),
-        );
-    }
     for m in video::MOVIES {
         match video::transcode(disc, out, m)? {
             Some(t) => {
                 println!("  video {} -> {}", m.src, t.file);
-                movie_lengths.push((m.stem, audio::probe_duration(&out.join(&t.file))));
                 videos.push(ManifestVideo {
                     name: t.name,
                     file: t.file,
                     command: t.command,
                     why: t.why,
-                    duration_s: t.duration_s,
-                    fps: t.fps,
                 });
             }
             None => println!("  video {} not on this disc -- skipped", m.src),
         }
     }
-    prune_videos(out, &videos)?;
-
-    // P6. Both tables are AUTHORED, for two different reasons -- the cue offsets
-    // because they were measured off the running game and are on the disc in no
-    // findable form, the BGM choice because HANDOFF Q10 is a negative and
-    // nothing states which track a menu plays. See `authored/audio.json`.
-    let mut audio = Vec::new();
-    let audio_cfg = audio::load(authored_dir)?;
-    match &audio_cfg {
-        None => println!("  no authored/audio.json -- no audio exported"),
-        Some(cfg) => {
-            let source = media::DirectorySource::new(disc);
-            for a in audio::export_cues(&source, out, &cfg.se)? {
-                println!(
-                    "  se    {:<8} -> {}  ({})",
-                    a.name,
-                    a.file,
-                    describe(&a)
-                );
-                audio.push(ManifestAudio::from(a));
-            }
-            for (role, spec) in &cfg.bgm {
-                match audio::export_bgm(&source, out, role, spec)? {
-                    Some(a) => {
-                        println!(
-                            "  bgm   {:<8} -> {}  ({}, bank {}, {} sub-wave(s))",
-                            a.name,
-                            a.file,
-                            describe(&a),
-                            spec.bank,
-                            a.sub_waves
-                        );
-                        // HANDOFF Q10's census is "exactly two waves of
-                        // identical duration, 32/32 banks on the disc". When
-                        // `media` hands back a different number, SAY SO -- the
-                        // port does not get to decide that one of them is not a
-                        // stem, and silently summing an extra region into the
-                        // music is precisely the media-assembly mistake MISSION
-                        // section 2 names. The decoder's answer is what ships;
-                        // the disagreement is what gets reported.
-                        if a.sub_waves != 2 {
-                            warnings.push(format!(
-                                "audio/bgm/{role}.ogg: sylpheed_formats::media::sound_bank_riffs \
-                                 returned {} sub-wave(s) for `{}`, but HANDOFF Q10's bank census \
-                                 says a music bank is EXACTLY TWO waves of identical duration \
-                                 (32/32 banks). All {} are summed, because choosing which to drop \
-                                 is a decoding question and this exporter does not answer those. \
-                                 See docs/port/BLOCKED.md.",
-                                a.sub_waves, spec.bank, a.sub_waves
-                            ));
-                        }
-                        audio.push(ManifestAudio::from(a));
-                    }
-                    // Not an error: the authored bank may simply not be on this
-                    // disc, and the export of everything else is still good.
-                    None => warnings.push(format!(
-                        "authored/audio.json bgm.{role} names bank `{}`, which is not in \
-                         this disc's sound.pak -- no BGM exported for that role.",
-                        spec.bank
-                    )),
-                }
-            }
-        }
-    }
-
-    // The cutscene voices are DERIVED, not authored, so this runs outside the
-    // `authored/audio.json` block above: the binding comes off the disc (the
-    // movie manifest in `tables.pak`), and an export with no authored audio
-    // should still carry the dialogue for the movies it ships.
-    //
-    // A movie that resolves to no region is genuinely unvoiced and gets a
-    // warning rather than a substitute -- for both movies in scope this port
-    // expects a region, so a warning here is a real signal and not noise.
-    {
-        let source = media::DirectorySource::new(disc);
-        for (stem, len) in &movie_lengths {
-            // The presentation choice is AUTHORED and this block runs even when
-            // there is no `authored/audio.json` -- the voice binding is decoded,
-            // so the dialogue exports either way and only the choice defaults.
-            let want = audio_cfg.as_ref().map(|c| c.voice).unwrap_or_default();
-            let weights = audio_cfg.as_ref().map(|c| c.stream_weights.clone()).unwrap_or_default();
-            match audio::export_voice(&source, out, stem, *len, want, &weights)? {
-                Some(a) => {
-                    // 🔴 A TOP-LEVEL WARNING, not just a `why` on the entry. The
-                    // export is known to be missing audio the game plays, and
-                    // the failure sounds like success: one stream decodes to
-                    // clean dialogue, so nobody listening finds out.
-                    if a.kept_waves < a.content_waves {
-                        warnings.push(format!(
-                            "{}: KNOWN INCOMPLETE. This region holds {} streams and the RUNNING \
-                             GAME DECODES ALL OF THEM CONCURRENTLY (Canary --xma_param_probe: \
-                             three XMA contexts, byte sizes matching the disc payloads exactly). \
-                             The export carries ONE. Nothing in the audio reveals this -- a \
-                             single stream is clean audible dialogue. Held rather than summed \
-                             because an equal-gain sum of channel pairs is not a downmix and \
-                             would be a second guess, not a fix. See authored/audio.json voice \
-                             and docs/port/BLOCKED.md.",
-                            a.file, a.sub_waves
-                        ));
-                    }
-                    println!(
-                        "  voice {:<8} -> {}  ({}, {} of {} stream(s){})",
-                        a.name,
-                        a.file,
-                        describe(&a),
-                        a.kept_waves,
-                        a.sub_waves,
-                        if a.kept_waves < a.content_waves { " -- KNOWN INCOMPLETE, see warnings" } else { "" }
-                    );
-                    audio.push(ManifestAudio::from(a));
-                }
-                None => warnings.push(format!(
-                    "movie `{stem}`: the movie manifest binds it to no voice region, so no                      dialogue was exported. That is a real answer for an unvoiced cutscene --                      nothing is substituted, because resolving an unbound movie through a                      shared demo line was measured to play the WRONG recording."
-                )),
-            }
-        }
-    }
 
     let manifest = Manifest {
         format: "sylpheed.manifest/1",
@@ -565,8 +283,16 @@ fn run_export(disc: &Path, out: &Path, authored_dir: &Path) -> Result<()> {
         disc: disc.display().to_string(),
         screens,
         videos,
-        audio,
-        warnings,
+        warnings: vec![
+            "P0 scope: GP_TITLE screen builds only. No audio, no video, no other archive."
+                .into(),
+            "The four splash bundles (entries 10/13 publisher, 11/14 developer) have no .rat \
+             layout child, so `is_build` cannot see them and no content rule can: element \
+             count and design size both overlap with two-element fragments in other archives. \
+             They are located by ENTRY INDEX from authored/screen_names.json `also_export`, \
+             which is a locator and not a claim -- see each one's name_why."
+                .into(),
+        ],
     };
     std::fs::write(
         out.join("manifest.json"),
@@ -575,81 +301,3 @@ fn run_export(disc: &Path, out: &Path, authored_dir: &Path) -> Result<()> {
     println!("wrote {}/manifest.json", out.display());
     Ok(())
 }
-
-
-impl From<audio::Exported> for ManifestAudio {
-    fn from(a: audio::Exported) -> Self {
-        ManifestAudio {
-            kind: a.kind,
-            name: a.name,
-            file: a.file,
-            command: a.command,
-            why: a.why,
-            peak_dbfs: a.peak_dbfs,
-            duration_s: a.duration_s,
-            incomplete: (a.kept_waves < a.content_waves).then(|| {
-                format!(
-                    "{} of {} streams. The running game decodes all {} concurrently. \
-                     Nothing in the audio reveals the gap -- what plays is clean dialogue. \
-                     WHICH streams are dropped and why differs per asset; the manifest \
-                     entry's `why` says, and it is not the same story twice.",
-                    a.kept_waves, a.sub_waves, a.sub_waves
-                )
-            }),
-            name_match: a.name_match,
-            loop_mode: a.loop_mode,
-        }
-    }
-}
-
-/// The two numbers worth reading on an audio line, in the console.
-///
-/// Printed rather than left to the manifest because the failure this catches is
-/// a SILENT file: the right duration, the right channel count, the right size,
-/// and nothing in it. `-inf dB` on stdout is the one form of that failure a
-/// person notices without being told to look.
-fn describe(a: &audio::Exported) -> String {
-    let peak = match a.peak_dbfs {
-        Some(p) => format!("peak {p:.1} dBFS"),
-        None => "peak unmeasured".into(),
-    };
-    match a.duration_s {
-        Some(d) => format!("{d:.3} s, {peak}"),
-        None => peak,
-    }
-}
-
-
-/// Delete anything in `video/` this run did not produce.
-///
-/// `video/` is the one directory the wholesale wipe spares, so that the
-/// transcode cache survives to be consulted. This restores the guarantee the
-/// wipe exists for: a movie that stops being exported stops existing, rather
-/// than lingering as a file the manifest no longer lists.
-fn prune_videos(out: &Path, kept: &[ManifestVideo]) -> Result<()> {
-    let dir = out.join("video");
-    if !dir.exists() {
-        return Ok(());
-    }
-    let mut keep: Vec<String> = Vec::new();
-    for v in kept {
-        if let Some(name) = Path::new(&v.file).file_name() {
-            let name = name.to_string_lossy().into_owned();
-            keep.push(name.clone());
-            // The cache sidecar goes with the file it stamps.
-            if let Some(stem) = Path::new(&name).file_stem() {
-                keep.push(format!("{}.cmd", stem.to_string_lossy()));
-            }
-        }
-    }
-    for entry in std::fs::read_dir(&dir)? {
-        let entry = entry?;
-        let name = entry.file_name().to_string_lossy().into_owned();
-        if keep.contains(&name) {
-            continue;
-        }
-        println!("  video {name} is no longer exported -- removed");
-        let _ = std::fs::remove_file(entry.path());
-    }
-    Ok(())
-}

crates/sylpheed-export/src/screen.rs

@@ -17,27 +17,13 @@ use sylpheed_formats::{t8ad, ui_layout};
 ///
 /// ⚠️ `0x3002` is one member of a `0x3000` family and is **not** a general
 /// button test — `GP_READY_ROOM` uses `0x3000`/`0x3004`/`0x300c`/`0x3008` and
-/// has zero `0x3002`. The mapping is decoded for the kinds listed; anything else
-/// exports as `unknown` with its raw kind visible.
+/// has zero `0x3002`. Every screen in this milestone is `GP_TITLE`, where the
+/// mapping is decoded; anything else exports as `unknown` with its raw kind.
 fn role_of(kind: u32, has_sprite: bool) -> &'static str {
-    // 🔴 BIT 0 IS THE PARENT FLAG AND CARRIES NO ROLE INFORMATION. Decoded
-    // disc-wide: `kind & 1` agrees with "has a parent" on 15 493 elements with
-    // zero disagreements (`docs/re/ui-kind-bit0-is-has-parent.md`). So a role
-    // table keyed on the raw kind splits every class in two and calls the
-    // parented half `unknown` -- which is how the OPTIONS menu's rows came out
-    // roleless while the exporter had already accepted them as buttons.
-    //
-    // ⚠️ APPLIED TO EVERY PAIR, NOT JUST THE ONE THAT FAILED. Fixing only
-    // `0x3003` would have left `0x1` as `unknown` while `0x0` is `decoration`,
-    // i.e. the same inconsistency one kind along -- and half-applying this
-    // decode is exactly what produced the failure this is fixing.
-    //
-    // ⚠️ `0x73002`/`0x73003` are NOT folded in. Their `0x70000` bits are
-    // undecoded, so they stay `unknown` with their raw kind visible.
     match kind {
-        0x3002 | 0x3003 => "button",
-        0x10 | 0x11 if !has_sprite => "primitive",
-        0x0 | 0x1 => "decoration",
+        0x3002 => "button",
+        0x10 if !has_sprite => "primitive",
+        0x0 => "decoration",
         _ => "unknown",
     }
 }
@@ -117,14 +103,6 @@ pub struct FocusElement {
     pub id: String,
     pub declared: String,
     pub sprite: Option<String>,
-    /// `true` when the game draws this sprite ADDITIVE — `T8aD +0x04` bit
-    /// `0x02`, decoded. Absent when the sprite resolves to no `T8aD` header.
-    ///
-    /// A leaf's sprite may live in the leaf's own table or in the parent
-    /// bundle's, so the bit is looked up in the same two places, in the same
-    /// order, that the PNG is written from.
-    #[serde(skip_serializing_if = "Option::is_none")]
-    pub blend_additive: Option<bool>,
     pub pivot: [u32; 2],
     pub rest: Rest,
     pub keyframes: Vec<Keyframe>,
@@ -134,34 +112,6 @@ pub struct FocusElement {
 pub struct Focus {
     /// The `.rat` leaf this came from, e.g. `ptbtn01f.rat`.
     pub record: String,
-    /// The record header's `+0x08`: **where the cycle restarts**, in keyframe
-    /// units — which is not the same thing as the last keyframe's time.
-    ///
-    /// `ptbtn00f`, the `PRESS Ⓐ` plate's glow, ramps 0→80→0 over **105** units
-    /// inside a **120**-unit cycle and rests dark for the remaining 15. Deriving
-    /// the period from the largest keyframe time — what the port did until now —
-    /// runs it 14 % fast and deletes the dark rest entirely.
-    ///
-    /// Decoded by the Decoder (`07e93ce`, `docs/re/structures/ui-record-loop-length.md`,
-    /// delivered in HANDOFF `27938aa`) and **re-run here before adoption**, with
-    /// their falsifier and their non-triviality control (⚠️ the 92.3 % below is
-    /// "of records where the question is meaningful" -- 1 643 of the 1 781 with a
-    /// timed keyframe. 3 311 nested records exist; the other 1 530 have no
-    /// keyframe time at all, so `+0x08 == max t` is not a question there. Quoted
-    /// bare until 2026-09-01, which is a population-scoped statistic reported
-    /// without its population):
-    /// `cargo run -p sylpheed-export --example record_loop_control`. Disc-wide
-    /// 1 781 timed records, 92.3 % exact, 7.7 % hold, **0 declaring less than
-    /// their own last pose**; on the eight records this port animates, seven
-    /// exact and `ptbtn00f` the one hold.
-    ///
-    /// ✅ **The port no longer owns this reading.** For one iteration `screen.rs`
-    /// held its own guard and byte read, because the field was decoded in an
-    /// example and a test and exposed in no public API on any ref. It is now
-    /// `ui_layout::loop_length_units`, taken at `formats-pin-2026-08-30b`, and
-    /// the local copy is deleted — the doc comment that promised that deletion
-    /// is the only reason it did not quietly become permanent.
-    pub loop_length_units: Option<u32>,
     /// Back-to-front, in the leaf's own declaration order.
     pub elements: Vec<FocusElement>,
 }
@@ -191,59 +141,6 @@ pub struct Element {
     /// convention and a consumer may still want the bare highlight texture.
     #[serde(skip_serializing_if = "Option::is_none")]
     pub focus: Option<Focus>,
-
-    /// This element's own `.rat` leaf, when its declared name is itself a
-    /// record in the bundle.
-    ///
-    /// 🔴 **DECODED DATA THE EXPORTER USED TO DROP.** `ptloop01`/`ptloop02` on
-    /// the title declare scale 100 % and rotation 0 at the parent, and their
-    /// leaves declare **(100, 600) at +30°** and **(100, 800) at −45°** — and
-    /// the leaves *move*, x from −639 → 1521 and 1721 → −839. `ui_layout`'s own
-    /// note says so: *"the rotated quads come from its two nested `.rat` leaf
-    /// records, which the census never opened."* Neither did this exporter: it
-    /// opened a leaf only for a FOCUS record, via `highlight_name`.
-    ///
-    /// That omission is measurable. It is the whole of the title's 1.82 %
-    /// disagreement with the oracle — the port draws two 400 px sprites upright
-    /// and static at (441, 270) where the game sweeps two ~1080 and ~1440 px
-    /// quads across the frame at opposite leans.
-    ///
-    /// ⚠️ **Emitted, not yet drawn.** Parent and leaf each carry their own alpha
-    /// ramp on a different span — parent 0→255 over t=70…238, leaf
-    /// 255→0x80→255 over t=150…600 — so how the two compose is a *decoding*
-    /// question and not the port's to answer. The data is exported so it stops
-    /// being invisible; `ScreenView` ignores it until the composition rule is
-    /// known.
-    #[serde(skip_serializing_if = "Option::is_none")]
-    pub leaf: Option<Focus>,
-
-    /// True when the leaf's geometry DIFFERS from the parent's, so the leaf is
-    /// what the game draws.
-    ///
-    /// Decided here rather than in the runtime because it is disc knowledge.
-    /// The Decoder's rule: *"the discriminator is which record carries the
-    /// geometry, not a fixed order"* — and the census over this export splits
-    /// cleanly, with no ambiguous middle:
-    ///
-    /// * **30 of 46** leaf elements duplicate the parent's scale and rotation
-    ///   exactly. That is the BASE-record case `screen.rs` already handled: the
-    ///   leaf may differ by a unit of position (`ptbtn04`: parent y=401, leaf
-    ///   y=402) and the parent wins. Flag is false; nothing changes.
-    /// * **16 differ**, and all of them differ in scale or rotation, not by a
-    ///   rounding unit: the ten `ptloop01`/`ptloop02` sweeps ((100,600) at +30°
-    ///   and (100,800) at −45° against an identity parent), two
-    ///   `pgloading_ring` (leaf scale **(0,0)**), and `title_jp`'s
-    ///   `ptlogo_eff2` (**parent 125 %, leaf 100 %**).
-    ///
-    /// ⚠️ **Only the `ptloop` case is decoded.** The Decoder fitted the game's
-    /// own composed alpha — vertex colours `C3FFFFFF`/`B6FFFFFF`, i.e. 195 and
-    /// 182 — against the two leaf ramps and got one consistent time, t=355, then
-    /// *predicted* the quad centres at 981 and 478 against 992.0 and 467.2
-    /// measured. The other two are the same shape and are **not** separately
-    /// confirmed; they are flagged so the harness can adjudicate them rather
-    /// than being asserted.
-    #[serde(skip_serializing_if = "std::ops::Not::not")]
-    pub leaf_carries_geometry: bool,
     /// The raw `opt ` link inside this element's `.rat` record.
     ///
     /// ⚠️ **This is not a focus link.** It was read as one, and that was
@@ -264,23 +161,6 @@ pub struct Element {
     /// Paint-order key. `"sprite"` = read from the `T8aD` header at `+0x0A`.
     /// `"implied"` = **measured off the running game**, for elements that carry
     /// no header. `"none"` = neither; sorts last.
-    /// `true` when the game draws this element ADDITIVE — `T8aD +0x04` bit
-    /// `0x02`.
-    ///
-    /// 🔴 **DECODED, and it replaces an authored map.** The port carried an
-    /// `additive_elements` table in `authored/rendering.json`, keyed by SCREEN
-    /// NAME and transcribed from the Decoder's per-draw `RB_BLENDCONTROL0` log.
-    /// A name-keyed map cannot answer for a screen nobody drove the game to,
-    /// which is why the port was drawing the English menus additive and the
-    /// Japanese ones alpha-over — asserting by omission that the JP build
-    /// blends differently. The bit is on the disc for every screen at once.
-    ///
-    /// ⚠️ `kind_raw` is NOT this field. `kind` is `+40` of the RATC declaration
-    /// entry; this is `+0x04` of the sprite's own `T8aD` header. Tested over
-    /// four screens: `kind & 0x2` is *anti*-correlated with the measured map —
-    /// 0 of 14 additive elements set it and 9 non-additive ones do.
-    #[serde(skip_serializing_if = "Option::is_none")]
-    pub blend_additive: Option<bool>,
     pub layer_source: &'static str,
     #[serde(skip_serializing_if = "Option::is_none")]
     pub layer: Option<String>,
@@ -321,35 +201,6 @@ pub struct Screen {
     /// **Geometric, not a decoded neighbour graph** — right for a vertical menu
     /// and not to be trusted for anything else.
     pub buttons: Vec<String>,
-
-    /// The instant every element of this screen is settled at, and the width of
-    /// the interval it was taken from — `[start, end, midpoint]` in keyframe
-    /// units, absent when the screen has fewer than two keyframe times.
-    ///
-    /// 🔴 **A SETTLED SCREEN IS ONE INSTANT, AND THE DISC SAYS WHICH.** Posing
-    /// each element at its own `rest()` is right for anything that ends the
-    /// screen settled and **exactly wrong for a transient**: the title's
-    /// `ptlogo_back2eff1` is a two-frame flash — 0 until t52, 255 at t54–56, 0
-    /// again by t58 — so its last *hold* is the flash peak and `rest()` leaves
-    /// it burning forever. There are five of these, and `rest()` draws all five
-    /// at once, saturating the light arc.
-    ///
-    /// The window is the **longest interval containing no keyframe time**, over
-    /// this bundle's TOP-LEVEL elements only. Nested leaves are excluded, and
-    /// that exclusion is what reproduces the Decoder's independently computed
-    /// `[160, 236]` for the title: including the `ptloop` leaves gives
-    /// `[269, 540]` instead.
-    ///
-    /// ⚠️ **Emitted for every screen; USABLE only where it is wide.** Across this
-    /// export the widths split with nothing in between — `press_start` 214,
-    /// `publisher_logo` 190, `developer_logos` 145, `title` 76, then
-    /// `main_menu` 12, `extras` 12, the loading screens 8 and 4. A 12-unit
-    /// "settle" on a menu that builds in until t=70 is not a settled pose, it is
-    /// a gap between staggered ramps. The Decoder's disc-wide census agrees on
-    /// the shape: only 30 % of bundles have a window ≥ 30 units and 42 % have
-    /// one under 10, the latter mostly `loop*` fragments meant to be in motion.
-    #[serde(skip_serializing_if = "Option::is_none")]
-    pub settle_window: Option<[i64; 3]>,
     /// What this file does not answer. A consumer needing one of these must get
     /// it from `authored/`.
     pub unresolved: Vec<&'static str>,
@@ -465,76 +316,6 @@ pub fn export_build(
         // Contrast with a BASE record, where the leaf duplicates the parent's
         // placement and the two can differ by a unit (ptbtn04: parent y=401,
         // leaf y=402). There the parent wins. Here there is no parent.
-        // Reads one record in the bundle as a nested build and returns its
-        // elements. Used twice: for a FOCUS record (`ptbtn0Nf.rat`) and for an
-        // element whose OWN declared name is a record (`ptloop01.rat`). One
-        // implementation, because the second case was missing for eight
-        // milestones and a second copy is how it would go missing again.
-        let read_leaf = |rec: &str,
-                         written: &mut std::collections::BTreeMap<String, ()>,
-                         missing: &mut Vec<String>|
-         -> Result<Option<Focus>> {
-            let Some(&(off, size)) = b.records.get(rec) else { return Ok(None) };
-            let Some(leaf) = ui_layout::parse_build(&bundle[off..off + size]) else {
-                return Ok(None);
-            };
-            let mut fes = Vec::new();
-            for fe in &leaf.elements {
-                let sp: &str = fe.sprite.as_deref().unwrap_or(&fe.name);
-                let mut fsprite = None;
-                if write_from(&sprite_dir, written, sp, &bundle[off..off + size], &leaf.sprites)?
-                    || write_from(&sprite_dir, written, sp, bundle, &b.sprites)?
-                {
-                    fsprite = Some(sprite_rel(sp));
-                } else if sp.ends_with(".t32") {
-                    missing.push(sp.to_string());
-                }
-                let Some(r) = fe.rest() else { continue };
-                fes.push(FocusElement {
-                    id: id_of(&fe.name),
-                    declared: fe.name.clone(),
-                    sprite: fsprite,
-                    blend_additive: ui_layout::blend_additive_by_name(
-                        &leaf, &bundle[off..off + size], sp)
-                        .or_else(|| ui_layout::blend_additive_by_name(&b, bundle, sp)),
-                    pivot: [fe.pivot_x, fe.pivot_y],
-                    rest: Rest {
-                        pos: [r.x, r.y],
-                        scale: [r.scale_x, r.scale_y],
-                        tint_rgba: hex32(r.tint),
-                        fade_argb: hex32(r.fade),
-                        rotation_deg: r.rotation_deg,
-                        t: r.time,
-                    },
-                    keyframes: fe
-                        .keyframes
-                        .iter()
-                        .map(|k| Keyframe {
-                            t: k.time,
-                            pos: [k.x, k.y],
-                            scale: [k.scale_x, k.scale_y],
-                            tint_rgba: hex32(k.tint),
-                            fade_argb: hex32(k.fade),
-                            rotation_deg: k.rotation_deg,
-                        })
-                        .collect(),
-                });
-            }
-            Ok(if fes.is_empty() {
-                None
-            } else {
-                Some(Focus {
-                    record: rec.to_string(),
-                    loop_length_units: ui_layout::loop_length_units(&bundle[off..off + size]),
-                    elements: fes,
-                })
-            })
-        };
-
-        // An element whose own declared name is a record in this bundle carries
-        // its geometry THERE, not in its parent entry. See `Element::leaf`.
-        let leaf = read_leaf(&el.name, &mut written, &mut missing)?;
-
         let mut focus = None;
         if let Some(rec) = highlight_name(&el.name) {
             if let Some(&(off, size)) = b.records.get(&rec) {
@@ -560,9 +341,6 @@ pub fn export_build(
                             id: id_of(&fe.name),
                             declared: fe.name.clone(),
                             sprite: fsprite,
-                            blend_additive: ui_layout::blend_additive_by_name(
-                                &leaf, &bundle[off..off + size], sp)
-                                .or_else(|| ui_layout::blend_additive_by_name(&b, bundle, sp)),
                             pivot: [fe.pivot_x, fe.pivot_y],
                             rest: Rest {
                                 pos: [r.x, r.y],
@@ -587,11 +365,7 @@ pub fn export_build(
                         });
                     }
                     if !fes.is_empty() {
-                        focus = Some(Focus {
-                            record: rec,
-                            loop_length_units: ui_layout::loop_length_units(&bundle[off..off + size]),
-                            elements: fes,
-                        });
+                        focus = Some(Focus { record: rec, elements: fes });
                     }
                 }
             }
@@ -623,21 +397,10 @@ pub fn export_build(
             sprite: sprite_out,
             focus_sprite,
             focus,
-            leaf_carries_geometry: leaf.as_ref().is_some_and(|l| {
-                let p = el.rest();
-                l.elements.iter().any(|le| {
-                    p.is_none_or(|p| {
-                        le.rest.scale != [p.scale_x, p.scale_y]
-                            || le.rest.rotation_deg != p.rotation_deg
-                    })
-                })
-            }),
-            leaf,
             opt_link: el.focus_link.clone(),
             pivot: [el.pivot_x, el.pivot_y],
             size: (role == "primitive").then(|| [el.pivot_x * 2, el.pivot_y * 2]),
             parent: el.parent,
-            blend_additive: ui_layout::sprite_blend_additive(&b, bundle, el),
             layer_source,
             layer,
             focused: el.focused,
@@ -656,33 +419,14 @@ pub fn export_build(
 
     // Navigation order is geometric: buttons top-to-bottom by resting Y. A
     // focused-state record is not itself a menu item.
-    //
-    // 🔴 `0x3003` IS `0x3002`. Bit 0 of `kind` is the PARENT FLAG and carries no
-    // role information: decoded disc-wide over every `.pak` in `dat/`, `kind & 1`
-    // agrees with "has a parent" on 15 493 elements with ZERO disagreements
-    // (`docs/re/ui-kind-bit0-is-has-parent.md`). Matching only `0x3002` meant the
-    // OPTIONS menu's five rows -- parented, hence `0x3003` -- were not buttons,
-    // so the screen opened and could not be navigated.
-    //
-    // ⚠️ TWO VALUES, LISTED, NOT A MASK. `kind & 0xFFFE == 0x3002` would also
-    // match `0x73002`/`0x73003` -- 160 elements whose `0x70000` bits nobody has
-    // decoded -- and it would do it silently, on screens neither agent has
-    // looked at. Those are excluded by construction until somebody decides about
-    // them deliberately.
     let mut buttons: Vec<(i32, String)> = b
         .elements
         .iter()
-        .filter(|e| matches!(e.kind, 0x3002 | 0x3003) && !e.focused)
+        .filter(|e| e.kind == 0x3002 && !e.focused)
         .filter_map(|e| e.rest().map(|k| (k.y, id_of(&e.name))))
         .collect();
     buttons.sort_by(|a, b| a.0.cmp(&b.0).then_with(|| a.1.cmp(&b.1)));
 
-    let window = settle_window(&elements);
-    let order = forced_backdrop_first(
-        ui_layout::derived_paint_order(&b, bundle),
-        &elements,
-        [b.design_w, b.design_h],
-    );
     let screen = Screen {
         format: "sylpheed.screen/3",
         exporter: exporter.to_string(),
@@ -697,9 +441,8 @@ pub fn export_build(
         name_why,
         design: [b.design_w, b.design_h],
         elements,
-        paint_order: order,
+        paint_order: ui_layout::derived_paint_order(&b, bundle),
         buttons: buttons.into_iter().map(|(_, n)| n).collect(),
-        settle_window: window,
         unresolved: vec![
             // The time unit is measured off the running game, not on the disc.
             "keyframe_time_unit",
@@ -730,234 +473,3 @@ pub fn export_build(
         missing,
     })
 }
-
-
-/// The longest interval containing no keyframe time, over TOP-LEVEL elements.
-///
-/// See [`Screen::settle_window`] for why this is the settled instant and why
-/// nested leaves are excluded. Returns `[start, end, midpoint]`.
-fn settle_window(elements: &[Element]) -> Option<[i64; 3]> {
-    let mut times: Vec<i64> = elements
-        .iter()
-        .flat_map(|e| e.keyframes.iter().filter_map(|k| k.t.map(i64::from)))
-        .collect();
-    times.sort_unstable();
-    times.dedup();
-    if times.len() < 2 {
-        return None;
-    }
-    // 🔴 A GAP IN WHICH NOTHING IS VISIBLE IS NOT A SETTLE WINDOW.
-    //
-    // The widest keyframe-free interval is only a settled state if the screen is
-    // actually PRESENTING something across it. `press_start` is the case that
-    // proves it: its keyframes are 0, 214, 236, 238, 244, so the widest gap is
-    // 0..214 -- the dead stretch BEFORE the plate appears, where `ptbtn00` is
-    // alpha 0 throughout. Taking its midpoint gave a settle instant of t=107,
-    // and the runtime then answered every question about that screen at t=107.
-    // The result was that the PRESS (A) plate could not be drawn at any instant
-    // at all, including the boot's own end state, whose entire purpose is to
-    // show it.
-    //
-    // The fix is not a tuned threshold: it is that the heuristic was reading an
-    // interval where the screen is BLANK as the interval where it has arrived.
-    // Rejecting those leaves `press_start` with 214..236 (22 units), which is
-    // under the runtime's 30-unit bar, so it falls back to each element's own
-    // hold -- which is the plate, opaque, exactly as the disc declares it.
-    //
-    // ⚠️ This does not disturb the windows the settle instant was measured on.
-    // `title` keeps [160, 236]: elements are visible across it, and the
-    // Decoder's draw stream independently found the game's clock freezing in
-    // that same interval.
-    let visible_at = |t: i64| elements.iter().any(|e| alpha_at(e, t) > 0);
-    let (a, b) = times
-        .windows(2)
-        .map(|w| (w[0], w[1]))
-        .filter(|(a, b)| visible_at((a + b) / 2))
-        .max_by_key(|(a, b)| b - a)?;
-    Some([a, b, (a + b) / 2])
-}
-
-
-/// Alpha of one element at instant `t`, under the linear ramp the port uses.
-fn alpha_at(e: &Element, t: i64) -> u8 {
-    let ks = &e.keyframes;
-    let a = |k: &Keyframe| (u32::from_str_radix(k.fade_argb.trim_start_matches("0x"), 16)
-        .unwrap_or(0) >> 24) as i64;
-    let timed: Vec<&Keyframe> = ks.iter().filter(|k| k.t.is_some()).collect();
-    if timed.is_empty() {
-        return 0;
-    }
-    if t <= timed[0].t.unwrap() as i64 {
-        return a(timed[0]) as u8;
-    }
-    for w in timed.windows(2) {
-        let (t0, t1) = (w[0].t.unwrap() as i64, w[1].t.unwrap() as i64);
-        if t < t1 {
-            if t1 <= t0 {
-                return a(w[0]) as u8;
-            }
-            let f = (t - t0) as f64 / (t1 - t0) as f64;
-            return (a(w[0]) as f64 + (a(w[1]) - a(w[0])) as f64 * f).round() as u8;
-        }
-    }
-    a(timed[timed.len() - 1]) as u8
-}
-
-/// Scale of one element at instant `t`, in percent per axis, under the same
-/// linear ramp as the fade. Interpolated rather than stepped, because a scale
-/// that animates passes through every value between its keyframes.
-fn scale_at(e: &Element, t: i64) -> [f64; 2] {
-    let timed: Vec<&Keyframe> = e.keyframes.iter().filter(|k| k.t.is_some()).collect();
-    if timed.is_empty() {
-        return [100.0, 100.0];
-    }
-    let g = |k: &Keyframe, i: usize| k.scale[i] as f64;
-    if t <= timed[0].t.unwrap() as i64 {
-        return [g(timed[0], 0), g(timed[0], 1)];
-    }
-    for w in timed.windows(2) {
-        let (t0, t1) = (w[0].t.unwrap() as i64, w[1].t.unwrap() as i64);
-        if t < t1 {
-            if t1 <= t0 {
-                return [g(w[0], 0), g(w[0], 1)];
-            }
-            let f = (t - t0) as f64 / (t1 - t0) as f64;
-            return [
-                g(w[0], 0) + (g(w[1], 0) - g(w[0], 0)) * f,
-                g(w[0], 1) + (g(w[1], 1) - g(w[0], 1)) * f,
-            ];
-        }
-    }
-    let l = timed[timed.len() - 1];
-    [g(l, 0), g(l, 1)]
-}
-
-/// Move a full-screen opaque primitive to the FRONT of the paint order when the
-/// file forces it there.
-///
-/// 🔴 **The rule is a constraint, not a preference**, and it is the Decoder's:
-/// *an element that covers the screen and is fully opaque at some instant cannot
-/// paint above anything visible at that instant; where the elements visible
-/// during its opaque span are ALL of them, its position is forced to first.*
-///
-/// It was found because `build_12`/`build_15` are **black at every instant** of
-/// their declared timeline under the old rule — `pgloading_eff00` is opaque for
-/// 39 instants while all 9 other elements live and die inside that span. A
-/// screen that is black for its whole life is impossible on its face, which is
-/// the only kind of check that survives two renderers sharing an assumption:
-/// `sylpheed-cli` agreed with the port here because it agreed about
-/// `implied_layer_key`.
-///
-/// Two measured controls, both prior orders off the running game:
-///
-/// | primitive | measured | opaque instants | forced below | |
-/// |---|---|---|---|---|
-/// | `palogo_eff0.prm` | **first** | 211 | 6 of 6 | ✅ forced |
-/// | `pteff00.prm` | **last** | 2 | 3 of 23 | ✅ permitted on top |
-///
-/// ⚠️ **Do NOT reduce this to a name heuristic.** `*base*` first / `*eff*` last
-/// matches 77 of 80 and fails on exactly the three families that cross it —
-/// `palogo_eff0`, `pgloading_eff00`, `pzeff00`. `palogo_eff0.prm` is *named like
-/// an overlay* and is measured painting first. The name is not the rule.
-///
-/// 🔴 **And it is restricted to elements with NO SPRITE**, which is the limit
-/// that the rule's own disc-wide test caught: applied to sprites it claimed 22
-/// `.t32` textures must sort first *against their own layer keys*. **An
-/// element's alpha says nothing about whether its texture covers the screen** —
-/// most of a sprite may be transparent.
-///
-/// ⚠️ Reach: assumes straight alpha-over. Blend mode is undecoded, and an
-/// additive quad at alpha 255 would not occlude. It is a lower bound, not an
-/// ordering — it says nothing about elements that are constrained but not
-/// forced. Delete this when a pinned `sylpheed-formats` does it.
-fn forced_backdrop_first(order: Vec<usize>, elements: &[Element], design: [u32; 2]) -> Vec<usize> {
-    let screen_end: i64 = elements
-        .iter()
-        .flat_map(|e| e.keyframes.iter().filter_map(|k| k.t))
-        .map(i64::from)
-        .max()
-        .unwrap_or(0);
-    let forced: Vec<usize> = elements
-        .iter()
-        .enumerate()
-        .filter(|(_, e)| {
-            // 🔴 UNTEXTURED SOLID QUAD, tested positively -- NOT merely "has no
-            // sprite". Those coincide in GP_TITLE and the distinction is still
-            // the whole point, because the negative test guards a SYMPTOM.
-            //
-            // The rule needs the element's alpha to BE its pixels' alpha. That
-            // is true of a `.prm` solid quad and of nothing else. The Decoder
-            // found this the expensive way twice: first `.t32` sprites (an
-            // element's alpha says nothing about a texture that is mostly
-            // transparent), guarded with "no sprite" -- and then `.tbm`, which
-            // is 38 of their 80 forced-first verdicts and declares fade
-            // `ffffffff`. A solid WHITE quad painted first at alpha 255 would
-            // make the screen white; no screen is white, so a `.tbm`'s white is
-            // a modulation ON a texture and its element alpha proves nothing
-            // about coverage either.
-            //
-            // "No sprite" would keep admitting a `.tbm` that this exporter
-            // happens not to emit a sprite for. `role == "primitive"` cannot.
-            // GP_TITLE has no full-screen `.tbm` at all -- every layerless
-            // full-screen element here is `.prm` and pure black, checked -- so
-            // this changes no verdict today and is a guard against a corpus
-            // that grows.
-            // Cheap prefilter only -- the binding coverage test is per-instant,
-            // in `covers` below. An element scaled ABOVE 100 could cover the
-            // screen from a smaller declared size, so this deliberately does
-            // not reject on size.
-            e.role == "primitive" && e.sprite.is_none() && e.size.is_some()
-        })
-        .filter(|(i, e)| {
-            let span: Vec<i64> = e
-                .keyframes
-                .iter()
-                .filter_map(|k| k.t)
-                .map(i64::from)
-                .collect();
-            let Some(&lo) = span.first() else { return false };
-            // 🔴 COVERAGE IS TESTED AT EACH INSTANT, NOT ONCE FROM `size`.
-            // Declared size alone is not what the element draws: scale is a
-            // percent per axis and it animates. `pbafc.prm` is the disc's own
-            // counterexample -- declared 844x600, scaled 2 % x 3 %, so it draws
-            // about 17x18 px, a moving glint rather than a wash. A rule that
-            // read its declared size would call it screen-covering.
-            //
-            // Nothing in GP_TITLE needs this: every layerless full-screen
-            // element here is at scale 100 on every keyframe, so no verdict
-            // moves. It is in because the data that would break it exists on
-            // this disc, which is a better reason than a failure would have been.
-            let covers = |t: i64| {
-                let sc = scale_at(e, t);
-                e.size.is_some_and(|s| {
-                    s[0] as f64 * sc[0] / 100.0 >= design[0] as f64
-                        && s[1] as f64 * sc[1] / 100.0 >= design[1] as f64
-                })
-            };
-            // An element HOLDS ITS FINAL POSE to the end of the screen -- it does
-            // not vanish at its own last keyframe. `palogo_eff0.prm` is the case
-            // that shows why: it declares ONE keyframe, opaque black full-screen
-            // at t=0, and reading its span as `0..=0` makes the splash's backdrop
-            // a single-instant event instead of the thing that is on screen for
-            // the whole splash. So the span runs to the SCREEN's last keyframe.
-            let hi = screen_end.max(*span.last().unwrap());
-            let opaque: Vec<i64> = (lo..=hi)
-                .filter(|&t| alpha_at(e, t) == 255 && covers(t))
-                .collect();
-            if opaque.is_empty() {
-                return false;
-            }
-            // Every OTHER element must be visible somewhere inside that span.
-            elements.iter().enumerate().all(|(j, o)| {
-                j == *i || opaque.iter().any(|&t| alpha_at(o, t) > 0)
-            })
-        })
-        .map(|(i, _)| i)
-        .collect();
-    if forced.is_empty() {
-        return order;
-    }
-    let mut out = forced.clone();
-    out.extend(order.into_iter().filter(|i| !forced.contains(i)));
-    out
-}

crates/sylpheed-formats/src/slb.rs

@@ -377,6 +377,39 @@ pub fn leading_data_offset(first_riff: usize) -> usize {
     first_riff % XMA1_PACKET
 }
 
+/// Length of the **bank header** when an entry begins with one, in bytes.
+///
+/// A music bank opens with a header the header itself sizes: big-endian, the
+/// 2048-byte block size sits at `+0x18`, the bank id is repeated at `+0x00` and
+/// `+0x20`, and `+0x24` is the header's length **in blocks** (5, i.e. 10 240 B,
+/// on every music bank on this disc).
+///
+/// This exists because [`leading_data_offset`] derives a leading packet stream's
+/// start as `first_riff % XMA1_PACKET`, which is only correct when the header is
+/// SMALLER than one packet. A music bank's header is exactly five packets, so
+/// the modulus returns 0 and the whole header was being emitted as a sub-wave —
+/// a third "stem" on a bank the corpus documents as two
+/// (`docs/re/structures/bgm-two-stems.md`).
+///
+/// Disc-wide over `sound.pak`'s 9 519 entries the signature fires on **28**, all
+/// of them music banks (ids 1001–1023, 1101–1105), and on every one of the 28
+/// the declared header ends **exactly** at the first `RIFF` — so no bank on this
+/// disc has both a header at offset 0 and a leading packet stream. Zero false
+/// positives on the 7 993 mid-bank windows, where the leading region IS real.
+pub fn bank_header_len(slb: &[u8]) -> Option<usize> {
+    if slb.len() < 0x38 {
+        return None;
+    }
+    if slb[0x18..0x1c] != [0x00, 0x00, 0x08, 0x00] {
+        return None;
+    }
+    if slb[0x00..0x04] != slb[0x20..0x24] {
+        return None;
+    }
+    let blocks = u32::from_be_bytes(slb[0x24..0x28].try_into().ok()?) as usize;
+    blocks.checked_mul(XMA1_PACKET)
+}
+
 pub fn to_xma_riffs(slb: &[u8]) -> Vec<Vec<u8>> {
     let mut out = Vec::new();
     let first_riff = find(slb, b"RIFF", 0);
@@ -422,7 +455,15 @@ pub fn to_xma_riffs(slb: &[u8]) -> Vec<Vec<u8>> {
     // bound to `VOICE_D_453`/`454`, i.e. precisely the broken ones — and
     // ≤0.25 s to 66 of the rest. Callers clamp to the movie length anyway.
     if let Some(ri) = first_riff {
-        let start = leading_data_offset(ri);
+        // A bank that carries its OWN header at offset 0 states how long it is,
+        // and on this disc that header always runs right up to the first `RIFF`
+        // — so there is no leading packet stream at all. Without this the
+        // modulus below returns 0 for a 5-packet header and the header itself is
+        // emitted as a sub-wave: `BGM_103.slb` came back as THREE waves against a
+        // census, an executable reference and a runtime XMA probe that all say
+        // two. It decodes to 0.009 s of PCM (the same chain returns 87.744 s for
+        // the bank's real wave 0), and it is 99.1 % zero bytes.
+        let start = bank_header_len(slb).unwrap_or_else(|| leading_data_offset(ri));
         if ri > start {
             if let Some(data) = slb.get(start..ri) {
                 if data.iter().any(|b| *b != 0) {

crates/sylpheed-formats/src/ui_layout.rs

@@ -111,12 +111,22 @@ pub struct Keyframe {
     /// starts are negative.
     pub x: i32,
     pub y: i32,
-    /// Keyframe time, or `None` for the group's **last** frame.
+    /// The time at which this pose is reached.
     ///
-    /// A group's data stops 4 bytes short of its final block's time slot — that
-    /// word is already the next group's element index. Reading it anyway is
-    /// where a stray `time = 1869640736` comes from, and it silently corrupts
-    /// the max-dwell pick in [`Element::rest`].
+    /// ✅ Always `Some` since 2026-08-29. A placement group is an 8-byte header
+    /// followed by `frames` records of `{ u32 time; 36-byte pose }`, so the time
+    /// word **precedes** the pose it belongs to. Our block window starts at the
+    /// pose, so pose `k`'s time is the previous stride's `+36` word, and pose
+    /// 0's is the group's lead-in word at `header + 8`.
+    ///
+    /// ⚠️ The old reading took `+36` as *this* pose's time. That left the final
+    /// pose — the end of every fade-out — untimed, and it is where the "a
+    /// group's data stops 4 bytes short of its final block's time slot" note and
+    /// the stray `time = 1869640736` both came from. There is no short group and
+    /// no missing word; the association was off by one.
+    /// See `docs/re/ui-keyframe-record-layout.md`.
+    ///
+    /// `Option` is retained for the `SYLPHEED_KF_TIME_LEGACY=1` escape hatch.
     pub time: Option<u32>,
 }
 
@@ -493,8 +503,10 @@ fn mark_focused_states(elements: &mut [Element]) {
 /// Read the placement region that follows the declaration table, filling in each
 /// element's keyframe group.
 fn parse_placements(bundle: &[u8], elements: &mut [Element]) -> Vec<usize> {
-    // Experiment gate, default off; see the `time` field below.
-    let shift_times = std::env::var("SYLPHEED_KF_TIME_SHIFT").as_deref() == Ok("1");
+    // Escape hatch for the pre-2026-08-29 reading, which mis-associated every
+    // keyframe time by one slot and could not time a group's final pose at all.
+    // See `docs/re/ui-keyframe-record-layout.md`.
+    let legacy_times = std::env::var("SYLPHEED_KF_TIME_LEGACY").as_deref() == Ok("1");
     let count = elements.len();
     let mut order = Vec::with_capacity(count);
     let mut pos = DECL_TABLE_AT + count * DECL_ENTRY;
@@ -507,7 +519,13 @@ fn parse_placements(bundle: &[u8], elements: &mut [Element]) -> Vec<usize> {
         if idx >= count || frames == 0 || frames > 4096 {
             break;
         }
-        // Group header is (index, count) then one lead-in word; blocks follow.
+        // The region is `frames` records of 40 bytes, each `{ u32 time; 36-byte
+        // pose }`, after an 8-byte header — so the word at `pos + 8` is the
+        // FIRST pose's time, and each 40-byte stride's `+36` word is the time of
+        // the pose that follows it. Our block window is offset 4 bytes into the
+        // record (it starts at the pose), which is why the pose field offsets
+        // below are right while the times were off by one.
+        let first_time = be32(bundle, pos + 8);
         let first = pos + 12;
         // The region is packed so that the next group's header sits 4 bytes
         // inside the last block — i.e. the group owns `frames * 40 - 4` bytes of
@@ -529,16 +547,17 @@ fn parse_placements(bundle: &[u8], elements: &mut [Element]) -> Vec<usize> {
                 tint: be32(bundle, blk + 24),
                 x: be32(bundle, blk + 28) as i32,
                 y: be32(bundle, blk + 32) as i32,
-                // Only a block wholly inside the group carries a time.
-                //
-                // ⚠️ Which block a time word BELONGS TO is under test — see
-                // `docs/re/ui-keyframe-time-unit.md`. Set `SYLPHEED_KF_TIME_SHIFT=1`
-                // to read `W[k-1]` as block `k`'s time ("the word is the time the
-                // NEXT pose is reached") instead of `W[k]`. Default is unchanged.
-                time: if shift_times {
-                    (k >= 1).then(|| be32(bundle, blk - KEYFRAME + 36))
-                } else {
+                // Pose `k`'s time is the word that PRECEDES it: the group's
+                // lead-in word for `k == 0`, and the previous stride's `+36`
+                // otherwise. Every pose is timed; nothing is missing and nothing
+                // is special-cased. Checked disc-wide — see
+                // `docs/re/ui-keyframe-record-layout.md`.
+                time: if legacy_times {
                     (blk + 40 <= group_end).then(|| be32(bundle, blk + 36))
+                } else if k == 0 {
+                    Some(first_time)
+                } else {
+                    Some(be32(bundle, blk - KEYFRAME + 36))
                 },
             });
         }

crates/sylpheed-formats/tests/slb_leading_segment_disc.rs

@@ -269,3 +269,62 @@ fn a_waves_declared_size_is_confirmed_by_the_next_seek() {
     assert!(checked >= 30, "expected banks to check, got {checked}");
     eprintln!("wave-boundary identity held for {checked} banks");
 }
+
+/// A **music** bank has no leading segment — the bytes before its first `RIFF`
+/// are the bank header, and emitting them made `BGM_103` look like three stems.
+///
+/// The header sizes itself (`+0x24`, in 2048-byte blocks), and on every bank on
+/// this disc that size lands exactly on the first `RIFF`. So the guard is not a
+/// heuristic and has no threshold: if a bank states a header, believe it.
+#[test]
+fn a_bank_that_states_its_own_header_has_no_leading_segment() {
+    skip_without_disc!(root);
+    let snd = PakArchive::open(root.join("dat/sound.pak")).expect("sound.pak");
+    let mut with_header = 0usize;
+    let mut mid_bank = 0usize;
+    // Peek at the 56-byte header through the archive's flat data rather than
+    // decompressing 9 519 entries: `sound.pak` stores them uncompressed, and a
+    // full read of all of them is several GB (it OOM-killed the test runner).
+    for entry in snd.entries() {
+        let Some(head) = snd.data_at(entry.offset as usize, 0x38) else { continue };
+        match slb::bank_header_len(head) {
+            Some(h) => {
+                let b = snd.read(entry).expect("read a bank that states a header");
+                let ri = b.windows(4).position(|w| w == b"RIFF").expect("has a RIFF");
+                // Declared header ends exactly at the first RIFF: no gap, so
+                // nothing before it can be a packet stream.
+                assert_eq!(h, ri, "a bank header that does not end at its first RIFF");
+                with_header += 1;
+            }
+            None => mid_bank += 1,
+        }
+    }
+    // 28 music banks (ids 1001-1023, 1101-1105); the rest are mid-bank windows,
+    // where the leading region IS real and must keep being emitted.
+    assert_eq!(with_header, 28, "banks stating their own header at offset 0");
+    assert!(mid_bank > 9000, "mid-bank windows, got {mid_bank}");
+    eprintln!("{with_header} banks state a header; {mid_bank} mid-bank windows");
+}
+
+/// The regression itself: the menu's music bank is **two** sub-waves, and they
+/// are the two the corpus names — matching the executable's `BGM_103` and the
+/// two streams the runtime XMA probe saw at the main menu.
+#[test]
+fn the_menu_music_bank_is_exactly_two_sub_waves() {
+    skip_without_disc!(root);
+    let snd = PakArchive::open(root.join("dat/sound.pak")).expect("sound.pak");
+    for (name, sizes) in [
+        ("BGM_103.slb", [3_876_864usize, 3_930_112]),
+        ("BGM_001.slb", [4_466_688, 4_673_536]),
+    ] {
+        let entry = snd.find_by_name(name).expect("bank present");
+        let b = snd.read(entry).expect("read");
+        let riffs = slb::to_xma_riffs(&b);
+        assert_eq!(riffs.len(), 2, "{name}: sub-wave count");
+        for (r, want) in riffs.iter().zip(sizes) {
+            let di = r.windows(4).position(|w| w == b"data").expect("data chunk");
+            let got = u32::from_le_bytes(r[di + 4..di + 8].try_into().unwrap()) as usize;
+            assert_eq!(got, want, "{name}: sub-wave payload size");
+        }
+    }
+}

crates/sylpheed-formats/tests/ui_header_time_disc.rs

@@ -120,8 +120,17 @@ fn header_0x08_against_the_keyframe_times() {
                 worst.push(format!("{pak}: max keyframe {max_time} > header {dur}"));
             }
         }
-        let r = ((max_time as f64 / dur as f64) * 10.0).round() as u32;
-        *ratio.entry(r.min(30)).or_default() += 1;
+        // ⚠️ Bundles whose every group is a single static pose contribute
+        // `max_time == 0` and say nothing about whether `+0x08` is a length.
+        // Before 2026-08-29 they were invisible here, because the old keyframe
+        // time reading left a one-frame group's only pose untimed; the corrected
+        // record layout (`docs/re/ui-keyframe-record-layout.md`) gives it the
+        // group's lead-in time, which is 0. They are excluded rather than
+        // allowed to swamp the histogram's zero bucket — 546 of them do.
+        if max_time > 0 {
+            let r = ((max_time as f64 / dur as f64) * 10.0).round() as u32;
+            *ratio.entry(r.min(30)).or_default() += 1;
+        }
     });
 
     eprintln!("bundles with keyframe times and a non-zero +0x08: {animated}");
@@ -142,11 +151,18 @@ fn header_0x08_against_the_keyframe_times() {
 
     assert!(animated > 0, "no animated bundles — the sweep is broken");
 
-    // MEASURED 2026-08-24. +0x08 bounds the keyframe times in EVERY one of the
-    // 2313 bundles that have both, and 444 of them reach it exactly. The
+    // MEASURED 2026-08-24, re-measured 2026-08-29 under the corrected keyframe
+    // record layout. +0x08 bounds the keyframe times in EVERY one of the 2 859
+    // bundles that have both (2 313 before the correction, which could not time
+    // a group's final pose at all), and 444 of them reach it exactly. The
     // spread-out ratio histogram is what rules out the boring explanation: a
     // large unrelated constant would bound everything too, but then the ratios
     // would pile up near zero instead of peaking at 1.0.
+    //
+    // ✅ The correction STRENGTHENS this result rather than weakening it: 546
+    // more bundles now carry a readable last-pose time, and `over` is still 0 —
+    // i.e. the newly-visible times, which are the LATEST in every group, still
+    // do not run past the header's.
     assert_eq!(over, 0, "a keyframe time runs past the header's +0x08");
     assert!(exact > 400, "the bound is never attained — it may be unrelated");
     let near_one = ratio.get(&10).copied().unwrap_or(0);

crates/sylpheed-formats/tests/ui_keyframe_record_disc.rs

@@ -0,0 +1,204 @@
+//! A placement group's time word **precedes** the pose it belongs to.
+//!
+//! A group is an 8-byte header `{u32 element_index, u32 frame_count}` followed
+//! by `frame_count` records of 40 bytes, each `{u32 time; 36-byte pose}`. The
+//! parser's block window starts at the *pose*, four bytes into the record, so
+//! the word at a block's `+36` is the time of the pose that FOLLOWS it, and the
+//! first pose's time is the group's lead-in word at `header + 8`.
+//!
+//! The old reading took `+36` as the block's own time. That is off by one, and
+//! it is where two long-standing oddities came from: the group looked four bytes
+//! short, and the final pose — the end of every fade-out — carried no time.
+//!
+//! Full argument and disc-wide census: `docs/re/ui-keyframe-record-layout.md`.
+//!
+//! Two checks here, both disc-wide:
+//!
+//! 1. **Every pose is timed, and the times are non-decreasing.** Under the old
+//!    reading the last pose has no time at all, so this cannot even be asked.
+//! 2. **A monotone alpha ramp of three or more segments runs at a constant
+//!    rate.** Interpolation between keyframes is linear
+//!    (`docs/re/ui-keyframe-time-unit.md`), so a correct time assignment makes
+//!    multi-keyframe ramps come out at a constant d(alpha)/d(time). The old
+//!    reading achieves this on **zero** ramps on the whole disc.
+
+use std::path::{Path, PathBuf};
+
+use sylpheed_formats::{pak::PakArchive, ratc, ui_layout};
+
+fn disc_root() -> Option<PathBuf> {
+    if let Ok(p) = std::env::var("SYLPHEED_DISC") {
+        let p = PathBuf::from(p);
+        if p.join("dat").is_dir() {
+            return Some(p);
+        }
+    }
+    let default = Path::new(
+        "/home/fabi/RE - Project Sylpheed/Project Sylpheed - Arc of Deception (USA, Europe) (En,Ja)",
+    );
+    if default.join("dat").is_dir() {
+        return Some(default.to_path_buf());
+    }
+    None
+}
+
+fn for_each_build(root: &Path, mut f: impl FnMut(&str, &[u8])) {
+    let mut paks: Vec<PathBuf> = std::fs::read_dir(root.join("dat"))
+        .expect("dat/")
+        .flatten()
+        .map(|e| e.path())
+        .filter(|p| p.extension().and_then(|s| s.to_str()) == Some("pak"))
+        .collect();
+    paks.sort();
+    for p in &paks {
+        let name = p.file_name().unwrap().to_string_lossy().to_string();
+        let Ok(arc) = PakArchive::open(p) else { continue };
+        for e in arc.entries() {
+            let Ok(bytes) = arc.read(e) else { continue };
+            if ratc::is_ratc(&bytes) {
+                f(&name, &bytes);
+            }
+        }
+    }
+}
+
+/// Maximal runs of strictly monotone alpha with at least `min_seg` segments.
+fn monotone_ramps(alphas: &[i32], min_seg: usize) -> Vec<(usize, usize)> {
+    let mut out = Vec::new();
+    let (mut i, n) = (0usize, alphas.len());
+    while i + 1 < n {
+        if alphas[i] == alphas[i + 1] {
+            i += 1;
+            continue;
+        }
+        let up = alphas[i + 1] > alphas[i];
+        let mut j = i + 1;
+        while j + 1 < n && ((alphas[j + 1] > alphas[j]) == up) && alphas[j + 1] != alphas[j] {
+            j += 1;
+        }
+        if j - i >= min_seg {
+            out.push((i, j));
+        }
+        i = j;
+    }
+    out
+}
+
+fn constant_rate(times: &[u32], alphas: &[i32], a: usize, b: usize) -> Option<bool> {
+    let mut rates = Vec::new();
+    for k in a..b {
+        let dt = times[k + 1].checked_sub(times[k])?;
+        if dt == 0 {
+            return None;
+        }
+        rates.push((alphas[k + 1] - alphas[k]).unsigned_abs() as f64 / dt as f64);
+    }
+    let mean = rates.iter().sum::<f64>() / rates.len() as f64;
+    if mean == 0.0 {
+        return None;
+    }
+    let worst = rates.iter().map(|r| (r - mean).abs()).fold(0.0, f64::max);
+    Some(worst / mean <= 0.06)
+}
+
+#[test]
+fn every_pose_is_timed_and_the_times_are_ordered() {
+    let Some(root) = disc_root() else {
+        eprintln!("SKIP: extracted disc not found (set SYLPHEED_DISC to enable)");
+        return;
+    };
+    if std::env::var("SYLPHEED_KF_TIME_LEGACY").as_deref() == Ok("1") {
+        eprintln!("SKIP: the legacy time reading is selected");
+        return;
+    }
+
+    let (mut groups, mut untimed, mut out_of_order) = (0usize, 0usize, 0usize);
+    let mut examples: Vec<String> = Vec::new();
+    for_each_build(&root, |pak, bytes| {
+        let Some(build) = ui_layout::parse_build(bytes) else {
+            return;
+        };
+        if build.from_fallback {
+            return;
+        }
+        for el in &build.elements {
+            if el.keyframes.is_empty() {
+                continue;
+            }
+            groups += 1;
+            if el.keyframes.iter().any(|k| k.time.is_none()) {
+                untimed += 1;
+                if examples.len() < 8 {
+                    examples.push(format!("{pak}: {} has an untimed pose", el.name));
+                }
+                continue;
+            }
+            let t: Vec<u32> = el.keyframes.iter().map(|k| k.time.unwrap()).collect();
+            if t.windows(2).any(|w| w[1] < w[0]) {
+                out_of_order += 1;
+                if examples.len() < 8 {
+                    examples.push(format!("{pak}: {} times {t:?} descend", el.name));
+                }
+            }
+        }
+    });
+
+    eprintln!("placement groups: {groups}; untimed: {untimed}; out of order: {out_of_order}");
+    for e in &examples {
+        eprintln!("  {e}");
+    }
+    assert!(groups > 10_000, "expected the whole disc, saw {groups} groups");
+    assert_eq!(untimed, 0, "every pose must carry a time");
+    assert_eq!(out_of_order, 0, "keyframe times must not descend");
+}
+
+#[test]
+fn multi_segment_alpha_ramps_run_at_a_constant_rate() {
+    let Some(root) = disc_root() else {
+        eprintln!("SKIP: extracted disc not found (set SYLPHEED_DISC to enable)");
+        return;
+    };
+    if std::env::var("SYLPHEED_KF_TIME_LEGACY").as_deref() == Ok("1") {
+        eprintln!("SKIP: the legacy time reading is selected");
+        return;
+    }
+
+    let (mut ramps, mut constant) = (0usize, 0usize);
+    for_each_build(&root, |_pak, bytes| {
+        let Some(build) = ui_layout::parse_build(bytes) else {
+            return;
+        };
+        if build.from_fallback {
+            return;
+        }
+        for el in &build.elements {
+            if el.keyframes.iter().any(|k| k.time.is_none()) {
+                continue;
+            }
+            let t: Vec<u32> = el.keyframes.iter().map(|k| k.time.unwrap()).collect();
+            let a: Vec<i32> = el
+                .keyframes
+                .iter()
+                .map(|k| ((k.fade >> 24) & 0xff) as i32)
+                .collect();
+            for (lo, hi) in monotone_ramps(&a, 3) {
+                if let Some(ok) = constant_rate(&t, &a, lo, hi) {
+                    ramps += 1;
+                    constant += usize::from(ok);
+                }
+            }
+        }
+    });
+
+    let share = 100.0 * constant as f64 / ramps as f64;
+    eprintln!("multi-segment alpha ramps: {constant}/{ramps} at a constant rate ({share:.1}%)");
+    assert!(ramps > 500, "expected the whole disc, saw {ramps} ramps");
+    // The old reading scores 0 of 1042. Half is a floor, not a target: the rest
+    // are genuinely shaped ramps, authored with keyframes that are not evenly
+    // spaced. Anything near zero means the time assignment has slipped again.
+    assert!(
+        share > 45.0,
+        "only {share:.1}% of ramps run at a constant rate — the time \
+         association has probably slipped (the old off-by-one scored 0%)"
+    );
+}

crates/sylpheed-viewer/src/iso_loader.rs

@@ -843,37 +843,6 @@ pub struct CutsceneBrowser {
     pub cues_generation: u64,
     /// Set by the window to ask for the selected row's transcript.
     pub want_cues: bool,
-    /// Where this cutscene's voice actually lives, versus where its name says.
-    pub voice: Option<VoiceLocation>,
-}
-
-/// A cutscene's voice, located two ways — because they disagree.
-///
-/// The movie voices are one continuous XMA stream chunked into `VOICE_*.slb`
-/// TOC entries whose boundaries do **not** match the cutscene cues. So the bank
-/// named after a movie need not hold that movie's audio: `RT01A`'s voice sits
-/// inside the byte range of the entry named `VOICE_ADV.slb`.
-///
-/// Showing both is the point. A viewer that played the name-matched bank would
-/// be confidently wrong for exactly the cutscenes where it matters.
-#[derive(Clone)]
-pub struct VoiceLocation {
-    /// The bank the naming convention points at, e.g. `eng\Movie\VOICE_ADV.slb`.
-    pub named_bank: String,
-    /// That bank's byte range in the sound stream, if it is in the TOC at all.
-    pub named_range: Option<(u64, u64)>,
-    /// Where the audio for this movie actually is.
-    pub region: Option<(u64, u64)>,
-}
-
-impl VoiceLocation {
-    /// True when the resolved audio lies inside the bank named after the movie.
-    pub fn name_is_honest(&self) -> bool {
-        match (self.named_range, self.region) {
-            (Some((a, b)), Some((s, e))) => s >= a && e <= b,
-            _ => false,
-        }
-    }
 }
 
 /// Ask the loader to read the cutscene manifest from `tables.pak`.
@@ -1049,7 +1018,6 @@ enum IsoLoaderMsg {
     CutsceneCuesLoaded {
         generation: u64,
         cues: Vec<sylpheed_formats::SubCue>,
-        voice: Option<VoiceLocation>,
     },
     /// The sound-bank library enumerated from `<lang>\sounds.tbl`.
     AudioLibraryLoaded {
@@ -2310,15 +2278,10 @@ fn poll_loader_channel(
                     cutscenes.loaded = true;
                 }
             }
-            Ok(IsoLoaderMsg::CutsceneCuesLoaded {
-                generation,
-                cues,
-                voice,
-            }) => {
+            Ok(IsoLoaderMsg::CutsceneCuesLoaded { generation, cues }) => {
                 if generation == cutscenes.cues_generation {
                     cutscenes.cues_loading = false;
                     cutscenes.cues = cues;
-                    cutscenes.voice = voice;
                 }
             }
             Ok(IsoLoaderMsg::AudioLibraryLoaded { entries }) => {
@@ -4888,7 +4851,6 @@ fn handle_cutscene_cues_request(
     cut.cues_generation = cut.cues_generation.wrapping_add(1);
     cut.cues_loading = true;
     cut.cues.clear();
-    cut.voice = None;
     let generation = cut.cues_generation;
     let lang = cut.lang;
     let source = iso_state.source_kind.clone();
@@ -4906,41 +4868,7 @@ fn handle_cutscene_cues_request(
             ))
         })()
         .unwrap_or_default();
-
-        // Locate the voice BOTH ways, so the window can show that they differ.
-        // The naming convention is the obvious route and it is wrong often
-        // enough to matter -- resolving the region is the only reading that
-        // yields the right audio.
-        let voice = (|| {
-            use sylpheed_formats::{hash::name_hash, media, PakArchive};
-            let vlang = match lang.pak_code() {
-                "jpn" => sylpheed_formats::slb::VoiceLang::Japanese,
-                _ => sylpheed_formats::slb::VoiceLang::English,
-            };
-            let named_bank = sylpheed_formats::slb::movie_voice_name(&movie, vlang);
-            let named_range = read_source_file(&source, "dat/sound.pak")
-                .ok()
-                .and_then(|toc| PakArchive::parse_toc(&toc).ok())
-                .and_then(|entries| {
-                    let h = name_hash(&named_bank);
-                    entries
-                        .iter()
-                        .find(|e| e.name_hash == h)
-                        .map(|e| (e.offset as u64, e.offset as u64 + e.comp_size as u64))
-                });
-            let region = media::resolve_movie_voice_region(&source, &movie, vlang);
-            (named_range.is_some() || region.is_some()).then_some(VoiceLocation {
-                named_bank,
-                named_range,
-                region,
-            })
-        })();
-
-        let _ = sender.send(IsoLoaderMsg::CutsceneCuesLoaded {
-            generation,
-            cues,
-            voice,
-        });
+        let _ = sender.send(IsoLoaderMsg::CutsceneCuesLoaded { generation, cues });
     });
 }
 

crates/sylpheed-viewer/src/ui.rs

@@ -2416,8 +2416,6 @@ fn draw_cutscenes_ui(
     mut requests: EventReader<RequestCutscenes>,
     mut file_selected: EventWriter<FileSelected>,
     mut browser: ResMut<FileBrowserState>,
-    mut audio: ResMut<AudioPreview>,
-    mut compose_audio: EventWriter<RequestAudio>,
 ) {
     if requests.read().next().is_some() {
         cut.open = true;
@@ -2429,7 +2427,6 @@ fn draw_cutscenes_ui(
     let mut open = true;
     let mut pick: Option<usize> = None;
     let mut play: Option<String> = None;
-    let mut play_voice: Option<String> = None;
 
     egui::Window::new("🎬 Cutscenes")
         .default_width(880.0)
@@ -2584,79 +2581,6 @@ fn draw_cutscenes_ui(
                         );
                     });
                 ui.separator();
-
-                // ── Voice ───────────────────────────────────────────────────
-                // Two locations, shown together because they disagree. The bank
-                // named after a movie is the obvious place to look and is often
-                // not where the audio is: RT01A's voice sits inside the byte
-                // range of the entry named VOICE_ADV.slb. Playing the
-                // name-matched bank would be confidently wrong for exactly the
-                // cutscenes where it matters.
-                ui.horizontal(|ui| {
-                    ui.label(egui::RichText::new("Voice").strong());
-                    if let Some(v) = &cut.voice {
-                        if v.region.is_some() && ui.button("▶ Play").clicked() {
-                            play_voice = Some(row.movie.clone());
-                        }
-                        if v.region.is_none() {
-                            ui.colored_label(
-                                egui::Color32::from_rgb(224, 168, 86),
-                                "no region resolves — this cutscene may be unvoiced",
-                            );
-                        }
-                    } else if cut.cues_loading {
-                        ui.spinner();
-                    }
-                });
-                if let Some(v) = &cut.voice {
-                    egui::Grid::new("cutscene_voice")
-                        .num_columns(2)
-                        .striped(true)
-                        .show(ui, |ui| {
-                            let mut kv2 = |k: &str, val: String, warn: bool| {
-                                ui.label(egui::RichText::new(k).weak().small());
-                                let t = egui::RichText::new(val).monospace();
-                                ui.label(if warn {
-                                    t.color(egui::Color32::from_rgb(224, 168, 86))
-                                } else {
-                                    t
-                                });
-                                ui.end_row();
-                            };
-                            kv2("named bank", v.named_bank.clone(), false);
-                            kv2(
-                                "its byte range",
-                                match v.named_range {
-                                    Some((a, b)) => format!("{a} .. {b}  ({} B)", b - a),
-                                    None => "not in the TOC".into(),
-                                },
-                                false,
-                            );
-                            let honest = v.name_is_honest();
-                            kv2(
-                                "resolved region",
-                                match v.region {
-                                    Some((a, b)) => format!("{a} .. {b}  ({} B)", b - a),
-                                    None => "—".into(),
-                                },
-                                !honest && v.region.is_some(),
-                            );
-                            if v.region.is_some() {
-                                kv2(
-                                    "name honest?",
-                                    if honest {
-                                        "yes — the audio is inside its own bank".into()
-                                    } else {
-                                        "NO — the audio is outside the bank named after this movie"
-                                            .into()
-                                    },
-                                    !honest,
-                                );
-                            }
-                        });
-                }
-
-                ui.separator();
                 ui.label(egui::RichText::new("Transcript").strong());
                 if cut.cues_loading {
                     ui.horizontal(|ui| {
@@ -2699,26 +2623,6 @@ fn draw_cutscenes_ui(
         cut.selected = Some(i);
         cut.want_cues = true;
     }
-    if let Some(movie) = play_voice {
-        // Routed through the movie form of RequestAudio, which resolves the
-        // continuous region rather than reading the name-matched bank.
-        audio.generation = audio.generation.wrapping_add(1);
-        audio.loading = true;
-        audio.active = true;
-        audio.error = None;
-        audio.name = format!("VOICE_{movie}");
-        let vlang = match cut.lang.pak_code() {
-            "jpn" => sylpheed_formats::slb::VoiceLang::Japanese,
-            _ => sylpheed_formats::slb::VoiceLang::English,
-        };
-        compose_audio.send(RequestAudio {
-            clip: String::new(),
-            display: format!("VOICE_{movie}"),
-            movie: Some((movie, vlang)),
-            mono: true,
-            generation: audio.generation,
-        });
-    }
     if let Some(path) = play {
         // Route through the normal file-open path, so the existing video player
         // handles it exactly as it would from the tree.

docker/decoder/bin/claude-autonomous

@@ -39,44 +39,6 @@ set answered_trust 0
 set answered_bypass 0
 
 spawn -noecho claude --dangerously-skip-permissions {*}$argv
-set child_pid [exp_pid]
-
-# 🔴 THIS WRAPPER USED TO SWALLOW BOTH THE SIGNAL AND THE EXIT STATUS, and those
-# two omissions caused most of this project's multi-hour outages. Found
-# 2026-09-03 by tracing the signal path, after a tooling review predicted exactly
-# this from the symptoms.
-#
-# The path is:  tini (PID 1) -> entrypoint.sh (exec'd) -> expect -> spawn -> claude
-#
-# `spawn` CANNOT be an exec: expect has to stay alive to drive the pty. So expect
-# is the process Docker signals, and everything below it depends on expect
-# passing things along. It did not.
-#
-# 1. NO SIGNAL FORWARDING. `docker stop` sent SIGTERM to expect, which died and
-#    took the pty with it. Claude Code never received a SIGTERM, so it never ran
-#    its `SessionEnd` hooks and never wrote `lastSessionId`/`history` to
-#    `~/.claude.json` -- which are written only at a GRACEFUL shutdown. That is
-#    the whole reason `claude --continue` answered "No conversation found to
-#    continue" with 33 MB of transcripts sitting in the volume beside it, and why
-#    we resume by scraping a session id off a transcript filename instead.
-#
-# 2. `eof { exit }` RETURNED 0 FOR EVERY DEATH. A bare `exit` in expect is exit
-#    ZERO. So when the kernel OOM-killer took the child, expect saw EOF and
-#    reported a clean exit -- `OOMKilled: true` with `ExitCode 0`, which is not
-#    Docker being odd, it is this line. It also meant `--restart on-failure`
-#    would have treated a memory kill as success, which is why the policy had to
-#    be `unless-stopped`.
-#
-# Both are fixed here. Signals are forwarded to the child and its real status is
-# propagated, so a kill reads as 137, a clean stop lets Claude Code shut down
-# properly, and the exit code means what it says.
-proc forward {sig} {
-    global child_pid
-    catch { exec kill -$sig $child_pid }
-}
-trap { forward TERM } SIGTERM
-trap { forward INT }  SIGINT
-trap { forward HUP }  SIGHUP
 
 expect {
     -re {Choose} {
@@ -108,18 +70,3 @@ expect {
 
 # Hand the terminal over for the rest of the run.
 interact
-
-# Propagate the child's REAL exit status. `interact` returns when the child is
-# gone; `wait` then yields {pid spawnid os_error status}. Without this the script
-# simply ran off the end and returned 0 -- see the note at `spawn` above for what
-# that cost.
-catch wait result
-set status 0
-if {[info exists result] && [llength $result] >= 4} {
-    # os_error_flag (index 2) is -1 for a normal exit; anything else means the
-    # wait itself failed and the status field is not a status.
-    if {[lindex $result 2] == 0} {
-        set status [lindex $result 3]
-    }
-}
-exit $status

docker/decoder/entrypoint.sh

@@ -84,26 +84,11 @@ if [ -r /sys/fs/cgroup/memory.max ]; then
   [ "$_m" != max ] && mem_gib=$(( _m / 1073741824 ))
 fi
 [ "${mem_gib:-0}" -lt 1 ] && mem_gib=1
-# 🔴 THIS CONSTANT WAS WRONG, AND IT COST A RUN. `mem_gib * 2 / 3` assumes
-# ~1.5 GB per job. On 2026-09-01 a raw `cargo test --release -p sylpheed-formats`
-# ran 4 jobs in a 6 GB container and was OOM-killed mid-task. Release-mode rustc
-# on this workspace needs closer to 2 GB, so the divisor is 2, not 3/2.
-#
-# ⚠️ And the kill reported `OOMKilled: true` with **ExitCode 0**, so it read as a
-# clean exit — which is why the restart policy is `unless-stopped` rather than
-# `on-failure`.
-by_mem=$(( mem_gib / 2 ))
+by_mem=$(( mem_gib * 2 / 3 ))
 [ "$by_mem" -lt 1 ] && by_mem=1
 jobs=$(( cpus < by_mem ? cpus : by_mem ))
-# An EXPLICIT cap from the launcher wins. Without this the launcher's
-# `-e CARGO_BUILD_JOBS=...` was computed, exported over, and silently discarded
-# — the guardrail was set and then removed three lines later.
-if [ -n "${CARGO_BUILD_JOBS:-}" ] && [ "${CARGO_BUILD_JOBS}" -ge 1 ] 2>/dev/null; then
-  jobs="$CARGO_BUILD_JOBS"
-  _why=" (explicit, from the launcher)"
-fi
 export SYLPH_JOBS="$jobs" CARGO_BUILD_JOBS="$jobs" CMAKE_BUILD_PARALLEL_LEVEL="$jobs"
-log "build parallelism: $jobs${_why:-} (cpus=$cpus, mem=${mem_gib}GiB avail)"
+log "build parallelism: $jobs (cpus=$cpus, mem=${mem_gib}GiB avail)"
 
 mkdir -p "$HOME/shots" "$HOME/logs"
 
@@ -148,32 +133,13 @@ mkdir -p /exchange/files 2>/dev/null || true
 # Seeded rather than shared because credentials live in .credentials.json and a
 # token refresh must be able to write. Copying once means each agent refreshes
 # its own token and neither can corrupt the host's.
-# Re-seed whenever the HOST's credentials are newer than ours, not only when
-# ours are missing. The missing-only guard meant an expired token could never be
-# replaced: the file existed, so the copy was skipped, and restarting the
-# container changed nothing. A human re-logging in on the host is exactly the
-# recovery path, and it has to reach here.
-#
-# Newer-wins rather than always-copy, because the container refreshes its own
-# token during a run and that copy may legitimately be the fresher one.
-# 🔴 A LONG-LIVED TOKEN WINS, AND THE SEEDING MUST NOT FIGHT IT.
-#
-# With CLAUDE_CODE_OAUTH_TOKEN set, copying the host's rotating credential file
-# in would re-create the exact collision the token exists to remove: three
-# clients on one rotating refresh token, the losers of a rotation race getting
-# their stored tokens CLEARED to empty strings and parking at "Login expired".
-# Measured 2026-09-04 -- see the launcher.
-if [ -n "${CLAUDE_CODE_OAUTH_TOKEN:-}" ]; then
-  log "auth: using the long-lived token from the environment; not seeding OAuth"
-elif [ -d "$HOME/.claude.seed" ] && \
-   { [ ! -s "$HOME/.claude/.credentials.json" ] || \
-     [ "$HOME/.claude.seed/.credentials.json" -nt "$HOME/.claude/.credentials.json" ]; }; then
+if [ -d "$HOME/.claude.seed" ] && [ ! -s "$HOME/.claude/.credentials.json" ]; then
   mkdir -p "$HOME/.claude"
   cp -a "$HOME/.claude.seed/.credentials.json" "$HOME/.claude/" 2>/dev/null || true
   for f in settings.json CLAUDE.md; do
     [ -e "$HOME/.claude.seed/$f" ] && cp -a "$HOME/.claude.seed/$f" "$HOME/.claude/" 2>/dev/null || true
   done
-  echo "[entrypoint] refreshed ~/.claude credentials from the host"
+  echo "[entrypoint] seeded ~/.claude from the host (credentials only)"
 fi
 
 # Seed ~/.claude.json from the host's read-only copy, then stamp onboarding as
@@ -184,10 +150,6 @@ fi
 if [ -f "$HOME/.claude.host.json" ] && [ ! -s "$HOME/.claude.json" ]; then
   cp "$HOME/.claude.host.json" "$HOME/.claude.json" 2>/dev/null || true
 fi
-
-# Nothing is restored into `~/.claude.json` on purpose. Resuming is done by
-# SESSION ID off the transcript instead — see the resume block below for why
-# the index is useless for this.
 # `credential.helper=store` rewrites this file by rename-over-target, which
 # fails with EBUSY on a bind mount -- reported as `fatal: unable to write
 # credential store`, while the push itself succeeds. A fatal line that is
@@ -209,77 +171,6 @@ if [ "${SYLPH_AUTONOMOUS:-0}" = "1" ]; then
   if [ "$#" -eq 1 ] && [ "$1" = "bash" ]; then
     set --
   fi
-  # ── Resume across a restart ────────────────────────────────────────────────
-  #
-  # The container restarts automatically now, and a restart that opens a BLANK
-  # session throws away everything the agent knew. That is not hypothetical: on
-  # 2026-09-01 an OOM kill ended a run mid-task with a 2.7 MB transcript and two
-  # files uncommitted in the volume.
-  #
-  # 🔴 RESUME BY SESSION ID, NOT BY `--continue`. Measured 2026-09-01:
-  #
-  # `--continue` resolves through `~/.claude.json`'s per-project `history` and
-  # `lastSessionId`. Those are written at a GRACEFUL SHUTDOWN — mid-session the
-  # live file has `history: None`, `lastSessionId: None`. A container that is
-  # OOM-killed or `docker rm -f`ed never writes them, which is exactly the case
-  # this feature exists for. So `--continue` answered "No conversation found to
-  # continue" with 33 MB of perfectly good transcripts in the volume beside it,
-  # and persisting `.claude.json` did not help because the fields were never
-  # populated in the first place.
-  #
-  # The TRANSCRIPTS are durable and are named by session id, so read the id off
-  # the newest one for this working directory. Claude Code has not started yet
-  # at this point, so the newest is the previous run's.
-  #
-  # The /loop prompt is still passed, so the loop is RE-ARMED rather than merely
-  # restored — a resumed conversation with no wake-up scheduled answers once and
-  # stops, which looks like resuming and is not.
-  SYLPH_STAMP="$HOME/.claude/.sylph-last-start"
-  SYLPH_RESUME=0
-  SYLPH_SESSION=""
-  SYLPH_PROJ="$HOME/.claude/projects/$(printf '%s' "$PWD" | sed 's#/#-#g')"
-  if [ -d "$SYLPH_PROJ" ]; then
-    _newest=$(ls -1t "$SYLPH_PROJ"/*.jsonl 2>/dev/null | head -1)
-    if [ -n "$_newest" ]; then
-      SYLPH_SESSION=$(basename "$_newest" .jsonl)
-      SYLPH_RESUME=1
-    fi
-  fi
-  # 🔴 A POISONED TRANSCRIPT MUST NOT CRASH-LOOP. If the last start was under
-  # two minutes ago we are already in a restart loop, and continuing back into
-  # whatever killed us is the one thing guaranteed not to help. Start fresh and
-  # say so, rather than burning tokens on the same death repeatedly.
-  if [ "$SYLPH_RESUME" = "1" ] && [ -f "$SYLPH_STAMP" ]; then
-    _last=$(cat "$SYLPH_STAMP" 2>/dev/null || echo 0)
-    _now=$(date +%s)
-    if [ $((_now - _last)) -lt 120 ]; then
-      SYLPH_RESUME=0
-      log "restarted <120s after the last start — restart loop suspected;"
-      log "  starting a FRESH session rather than continuing into the same death"
-    fi
-  fi
-  mkdir -p "$HOME/.claude" 2>/dev/null || true
-  date +%s > "$SYLPH_STAMP" 2>/dev/null || true
-
-  if [ "$SYLPH_RESUME" = "1" ] && [ "$#" -eq 1 ]; then
-    set -- "$1
-
-⚠️ YOU WERE RESTARTED, and this session was resumed — your context is intact,
-but the process that was running when it died is gone. Before anything else:
-
-1. \`git -C /work status\`. Whatever you had in progress is still in the tree,
-   UNCOMMITTED. Commit it and \`push-work\` before starting anything new.
-2. Any build, test or capture you had running did NOT finish. Do not read its
-   absence as a result.
-3. The likeliest cause is an OOM kill — this container is capped at 6 GB.
-   \`CARGO_BUILD_JOBS\` is now set for you in the environment; do not raise it,
-   and prefer \`build-reborn test\` over a raw \`cargo test --release\`, which
-   bypasses the wrapper's job cap. That is exactly what killed the run on
-   2026-09-01."
-    log "resuming session ${SYLPH_SESSION%%-*}… with a restart notice"
-  fi
-  [ "$SYLPH_RESUME" = "1" ] && set -- --resume "$SYLPH_SESSION" "$@"
-
   # The flag the user asked for. It is refused under root, which is why this
   # image runs as `agent`.
   # Remote Control registers the session with your account so you can chat with

docker/decoder/sylph-decoder

@@ -130,19 +130,6 @@ docker_args() {
     -e "PROJECT_DIR=/work"
     -e "SYLPH_EXCHANGE=/exchange"
     -e "SYLPH_AGENT=decoder"
-    # 🔴 THE JOB CAP LIVES IN THE ENVIRONMENT, NOT IN THE WRAPPER.
-    #
-    # `build-reborn` has always exported CARGO_BUILD_JOBS, and on 2026-09-01
-    # that was not enough: the agent ran a RAW `cargo test --release -p
-    # sylpheed-formats`, which never touches the wrapper, got one rustc per
-    # granted CPU, and the container was OOM-killed at its 6 GB cap mid-task.
-    # Docker reported ExitCode 0 with OOMKilled true, so it read as a clean
-    # exit and cost a diagnosis.
-    #
-    # A guardrail reachable only through a wrapper protects the calls that use
-    # the wrapper. This one is inherited by every process in the container, so
-    # bypassing it takes an explicit override rather than forgetting.
-    -e "CARGO_BUILD_JOBS=${SYLPH_JOBS:-2}"
     -e "SYLPH_REPO_URL=https://git.mc02.dev/fabi/Sylpheed.git"
     -e "XENIA_SRC=/canary"
     # ── claude ──
@@ -185,33 +172,6 @@ docker_args() {
   # Read-only, and only ever used by `push-work`, which refuses anything but an
   # auto/* branch and never force-pushes. Without this the agent's work only
   # exists inside the container and dies with it.
-  # ── Claude auth ──
-  #
-  # 🔴 THE ROTATING OAUTH FILE IS WHY THIS AGENT KEPT PARKING, and a long-lived
-  # token removes the failure by construction rather than recovering from it.
-  #
-  # Measured 2026-09-04: `~/.claude/.credentials.json` holds a REFRESH TOKEN THAT
-  # ROTATES ON USE. Seeding both containers from the host's copy left three
-  # clients holding one token; the first to refresh invalidated the other two,
-  # and on the failed refresh **Claude Code CLEARS the stored tokens** -- it
-  # writes empty strings, keeps the metadata, and parks at "Login expired". The
-  # decoder's file was caught emptied at 13:04:28 with its last work at 13:04:29.
-  # A hollow file passes every "does it exist" check, which is why three separate
-  # diagnoses missed it.
-  #
-  # `claude setup-token` issues a LONG-LIVED token against the same Claude
-  # subscription (not Console/API billing -- `claude auth login` defaults to
-  # `--claudeai`, and `--console` is the billed one). Passed as an environment
-  # variable it cannot be rotated out from under a peer and there is no file for
-  # Claude Code to empty, so both halves of the failure are gone.
-  #
-  # Inert until the file exists: without it the OAuth path below is unchanged.
-  CLAUDETOK="${SYLPH_CLAUDE_TOKEN:-$HOME/.sylph-claude-token}"
-  if [ -f "$CLAUDETOK" ]; then
-    _out+=(-e "CLAUDE_CODE_OAUTH_TOKEN=$(tr -d '[:space:]' < "$CLAUDETOK")")
-    echo "==> auth: long-lived token from $CLAUDETOK (no rotating credential file)" >&2
-  fi
-
   GITCRED="${SYLPH_GIT_CREDENTIALS:-$HOME/.sylph-git-credentials}"
   if [ -f "$GITCRED" ]; then
     _out+=(-v "$GITCRED:/sylph-home/re/.git-credentials.host:ro")
@@ -309,17 +269,7 @@ case "${1:-}" in
     echo "==> repo:    own clone in volume sylpheed-decoder-repo -> /work"
     echo "==> pacing:  ${INTERVAL:-self-paced}"
     docker rm -f "$NAME" >/dev/null 2>&1 || true
-    # 🔴 `unless-stopped`, NOT `on-failure` -- and the reason is a trap worth
-    # keeping. When this container was OOM-killed on 2026-09-01, Docker reported
-    # `OOMKilled: true` with **ExitCode 0**. `on-failure` keys off the exit code,
-    # so it would have treated a memory kill as a clean finish and left the agent
-    # down. `unless-stopped` restarts regardless, and still honours an explicit
-    # `./sylph-agent stop`.
-    #
-    # Restarting into the same death is handled at the other end: the entrypoint
-    # refuses to `--continue` if the last start was under two minutes ago.
-    docker run -d -i -t --restart unless-stopped "${ARGS[@]}" "$IMAGE" \
-      "/loop ${INTERVAL:+$INTERVAL }$TASK" >/dev/null
+    docker run -d -i -t "${ARGS[@]}" "$IMAGE" "/loop ${INTERVAL:+$INTERVAL }$TASK" >/dev/null
     echo
     echo "    running detached as '$NAME'."
     echo "      ./sylph-agent remote      link to chat with it from anywhere"

docker/port/bin/claude-autonomous

@@ -39,44 +39,6 @@ set answered_trust 0
 set answered_bypass 0
 
 spawn -noecho claude --dangerously-skip-permissions {*}$argv
-set child_pid [exp_pid]
-
-# 🔴 THIS WRAPPER USED TO SWALLOW BOTH THE SIGNAL AND THE EXIT STATUS, and those
-# two omissions caused most of this project's multi-hour outages. Found
-# 2026-09-03 by tracing the signal path, after a tooling review predicted exactly
-# this from the symptoms.
-#
-# The path is:  tini (PID 1) -> entrypoint.sh (exec'd) -> expect -> spawn -> claude
-#
-# `spawn` CANNOT be an exec: expect has to stay alive to drive the pty. So expect
-# is the process Docker signals, and everything below it depends on expect
-# passing things along. It did not.
-#
-# 1. NO SIGNAL FORWARDING. `docker stop` sent SIGTERM to expect, which died and
-#    took the pty with it. Claude Code never received a SIGTERM, so it never ran
-#    its `SessionEnd` hooks and never wrote `lastSessionId`/`history` to
-#    `~/.claude.json` -- which are written only at a GRACEFUL shutdown. That is
-#    the whole reason `claude --continue` answered "No conversation found to
-#    continue" with 33 MB of transcripts sitting in the volume beside it, and why
-#    we resume by scraping a session id off a transcript filename instead.
-#
-# 2. `eof { exit }` RETURNED 0 FOR EVERY DEATH. A bare `exit` in expect is exit
-#    ZERO. So when the kernel OOM-killer took the child, expect saw EOF and
-#    reported a clean exit -- `OOMKilled: true` with `ExitCode 0`, which is not
-#    Docker being odd, it is this line. It also meant `--restart on-failure`
-#    would have treated a memory kill as success, which is why the policy had to
-#    be `unless-stopped`.
-#
-# Both are fixed here. Signals are forwarded to the child and its real status is
-# propagated, so a kill reads as 137, a clean stop lets Claude Code shut down
-# properly, and the exit code means what it says.
-proc forward {sig} {
-    global child_pid
-    catch { exec kill -$sig $child_pid }
-}
-trap { forward TERM } SIGTERM
-trap { forward INT }  SIGINT
-trap { forward HUP }  SIGHUP
 
 expect {
     -re {Choose} {
@@ -108,18 +70,3 @@ expect {
 
 # Hand the terminal over for the rest of the run.
 interact
-
-# Propagate the child's REAL exit status. `interact` returns when the child is
-# gone; `wait` then yields {pid spawnid os_error status}. Without this the script
-# simply ran off the end and returned 0 -- see the note at `spawn` above for what
-# that cost.
-catch wait result
-set status 0
-if {[info exists result] && [llength $result] >= 4} {
-    # os_error_flag (index 2) is -1 for a normal exit; anything else means the
-    # wait itself failed and the status field is not a status.
-    if {[lindex $result 2] == 0} {
-        set status [lindex $result 3]
-    }
-}
-exit $status

docker/port/entrypoint.sh

@@ -30,30 +30,13 @@ echo "[entrypoint] display $DISPLAY ready ($SCREEN_GEOMETRY)"
 # Seeded rather than shared because credentials live in .credentials.json and a
 # token refresh must be able to write. Copying once means each agent refreshes
 # its own token and neither can corrupt the host's.
-# Re-seed whenever the HOST's credentials are newer than ours, not only when
-# ours are missing. The missing-only guard meant an expired token could never be
-# replaced: the file existed, so the copy was skipped, and restarting the
-# container changed nothing. A human re-logging in on the host is exactly the
-# recovery path, and it has to reach here.
-#
-# Newer-wins rather than always-copy, because the container refreshes its own
-# token during a run and that copy may legitimately be the fresher one.
-# 🔴 A LONG-LIVED TOKEN WINS, AND THE SEEDING MUST NOT FIGHT IT. With
-# CLAUDE_CODE_OAUTH_TOKEN set, copying the host's rotating credential file in
-# would re-create the collision the token exists to remove: three clients on one
-# rotating refresh token, and the loser of a rotation race gets its stored tokens
-# CLEARED to empty strings by Claude Code and parks. Measured 2026-09-04.
-if [ -n "${CLAUDE_CODE_OAUTH_TOKEN:-}" ]; then
-  echo "[entrypoint] auth: long-lived token from the environment; not seeding OAuth"
-elif [ -d "$HOME/.claude.seed" ] && \
-   { [ ! -s "$HOME/.claude/.credentials.json" ] || \
-     [ "$HOME/.claude.seed/.credentials.json" -nt "$HOME/.claude/.credentials.json" ]; }; then
+if [ -d "$HOME/.claude.seed" ] && [ ! -s "$HOME/.claude/.credentials.json" ]; then
   mkdir -p "$HOME/.claude"
   cp -a "$HOME/.claude.seed/.credentials.json" "$HOME/.claude/" 2>/dev/null || true
   for f in settings.json CLAUDE.md; do
     [ -e "$HOME/.claude.seed/$f" ] && cp -a "$HOME/.claude.seed/$f" "$HOME/.claude/" 2>/dev/null || true
   done
-  echo "[entrypoint] refreshed ~/.claude credentials from the host"
+  echo "[entrypoint] seeded ~/.claude from the host (credentials only)"
 fi
 
 # Seed ~/.claude.json from the host's read-only copy, then stamp onboarding as
@@ -64,10 +47,6 @@ fi
 if [ -f "$HOME/.claude.host.json" ] && [ ! -s "$HOME/.claude.json" ]; then
   cp "$HOME/.claude.host.json" "$HOME/.claude.json" 2>/dev/null || true
 fi
-
-# Nothing is restored into `~/.claude.json` on purpose. Resuming is done by
-# SESSION ID off the transcript instead — see the resume block below for why the
-# index cannot serve.
 # Same reason as .claude.json above: `credential.helper=store` rewrites this
 # file by rename-over-target, which fails with EBUSY on a bind mount. Copy it to
 # a writable path; nothing is ever written back to the host's file.
@@ -121,70 +100,6 @@ if [ "${SYLPH_AUTONOMOUS:-0}" = "1" ]; then
   if [ "$#" -eq 1 ] && [ "$1" = "bash" ]; then
     set --
   fi
-  # ── Resume across a restart ────────────────────────────────────────────────
-  #
-  # The container restarts automatically now, and a restart that opens a BLANK
-  # session throws away everything the agent knew.
-  #
-  # 🔴 RESUME BY SESSION ID, NOT BY `--continue`. Measured on the decoder
-  # 2026-09-01: `--continue` resolves through `~/.claude.json`'s per-project
-  # `history` / `lastSessionId`, and those are written at a GRACEFUL SHUTDOWN --
-  # mid-session the live file has both as `None`. A container that is OOM-killed
-  # or `docker rm -f`ed never writes them, which is exactly the case this exists
-  # for, so `--continue` answered "No conversation found to continue" with the
-  # transcripts sitting in the volume beside it.
-  #
-  # The TRANSCRIPTS are durable and named by session id. Claude Code has not
-  # started yet here, so the newest is the previous run's.
-  #
-  # The /loop prompt is still passed so the loop is RE-ARMED rather than merely
-  # restored -- a resumed conversation with no wake-up scheduled answers once
-  # and stops, which looks like resuming and is not.
-  SYLPH_STAMP="$HOME/.claude/.sylph-last-start"
-  SYLPH_RESUME=0
-  SYLPH_SESSION=""
-  SYLPH_PROJ="$HOME/.claude/projects/$(printf '%s' "$PWD" | sed 's#/#-#g')"
-  if [ -d "$SYLPH_PROJ" ]; then
-    _newest=$(ls -1t "$SYLPH_PROJ"/*.jsonl 2>/dev/null | head -1)
-    if [ -n "$_newest" ]; then
-      SYLPH_SESSION=$(basename "$_newest" .jsonl)
-      SYLPH_RESUME=1
-    fi
-  fi
-  # 🔴 A POISONED TRANSCRIPT MUST NOT CRASH-LOOP. Restarted under two minutes
-  # after the last start, we are already looping: continuing back into whatever
-  # killed us is the one thing guaranteed not to help.
-  if [ "$SYLPH_RESUME" = "1" ] && [ -f "$SYLPH_STAMP" ]; then
-    _last=$(cat "$SYLPH_STAMP" 2>/dev/null || echo 0)
-    _now=$(date +%s)
-    if [ $((_now - _last)) -lt 120 ]; then
-      SYLPH_RESUME=0
-      echo "[entrypoint] restarted <120s after the last start -- restart loop"
-      echo "[entrypoint]   suspected; starting FRESH rather than continuing"
-    fi
-  fi
-  mkdir -p "$HOME/.claude" 2>/dev/null || true
-  date +%s > "$SYLPH_STAMP" 2>/dev/null || true
-
-  if [ "$SYLPH_RESUME" = "1" ] && [ "$#" -eq 1 ]; then
-    set -- "$1
-
-⚠️ YOU WERE RESTARTED, and this session was resumed — your context is intact,
-but the process that was running when it died is gone. Before anything else:
-
-1. \`git -C /work status\`. Whatever you had in progress is still in the tree,
-   UNCOMMITTED. Commit it and \`push-work\` before starting anything new.
-2. Any build, test, export or Godot run you had going did NOT finish. Do not
-   read its absence as a result.
-3. The likeliest cause is an OOM kill — this container is capped at 4 GB.
-   \`CARGO_BUILD_JOBS\` is now set for you in the environment; do not raise it,
-   and prefer \`build-export\` / \`build-reference-cli\` over a raw
-   \`cargo build --release\`, which bypasses the wrapper's job cap. That is what
-   killed the decoder's run on 2026-09-01."
-    echo "[entrypoint] resuming session ${SYLPH_SESSION%%-*}… with a restart notice"
-  fi
-  [ "$SYLPH_RESUME" = "1" ] && set -- --resume "$SYLPH_SESSION" "$@"
-
   # Remote Control registers the session with the account so the agent can be
   # reached from claude.ai -- the point of a detached run being that nobody is
   # sitting in front of it. The name is passed EXPLICITLY: the flag's value is

docker/port/sylph-port

@@ -67,12 +67,6 @@ docker_args() {
     -v "${SYLPH_CLAUDE_JSON:-$HOME/.claude.json}:/sylph-home/port/.claude.host.json:ro"
     -v "sylpheed-exchange:/exchange"
     -e "PROJECT_DIR=/work"
-    # Same guardrail as the decoder, added the same day and for its reason: the
-    # decoder was OOM-killed mid-task by a RAW `cargo test --release`, which
-    # never reaches `build-export`/`build-reference-cli` and so never saw their
-    # CARGO_BUILD_JOBS. This container is smaller (4 GB, 3 CPUs), so the same
-    # bypass is at least as easy to hit here.
-    -e "CARGO_BUILD_JOBS=${SYLPH_PORT_JOBS:-2}"
     -e "SYLPH_EXCHANGE=/exchange"
     -e "SYLPH_AGENT=port"
     -e "SYLPH_REPO_URL=https://git.mc02.dev/fabi/Sylpheed.git"
@@ -105,20 +99,6 @@ docker_args() {
   # routinely wrong teaches the reader to ignore the one that is real. Mounting
   # rw would also silence it, but then the container can clobber the host's
   # credential file; copying cannot.
-  # ── Claude auth ──
-  # See the decoder's launcher for the full note. Short version: the OAuth
-  # credential file holds a refresh token that ROTATES ON USE, three clients were
-  # seeded from one copy, and the loser of a rotation race has its tokens CLEARED
-  # to empty strings by Claude Code and parks at "Login expired". A long-lived
-  # `claude setup-token` credential passed in the environment has nothing to
-  # rotate and no file to empty. Same subscription, not API billing.
-  # Inert until the file exists.
-  local claudetok="${SYLPH_CLAUDE_TOKEN:-$HOME/.sylph-claude-token}"
-  if [ -f "$claudetok" ]; then
-    _out+=(-e "CLAUDE_CODE_OAUTH_TOKEN=$(tr -d '[:space:]' < "$claudetok")")
-    echo "==> auth: long-lived token from $claudetok (no rotating credential file)" >&2
-  fi
-
   local gitcred="${SYLPH_GIT_CREDENTIALS:-$HOME/.sylph-git-credentials}"
   if [ -f "$gitcred" ]; then
     _out+=(-v "$gitcred:/sylph-home/port/.git-credentials.host:ro")
@@ -128,53 +108,6 @@ docker_args() {
   fi
 
   [ -n "${ANTHROPIC_API_KEY:-}" ] && _out+=(-e "ANTHROPIC_API_KEY=$ANTHROPIC_API_KEY")
-
-  # ── GPU ──
-  # This block did not exist until 2026-09-01, and its absence was reported as
-  # a symptom rather than a cause: **the port agent reported low FPS.** Godot 4
-  # renders through Vulkan, and with nothing passed through it was falling back
-  # to lavapipe — software Vulkan, which is correct and slow. The decoder's
-  # launcher had this logic; this one never did, so the container that actually
-  # runs a renderer was the one without a GPU.
-  #
-  # Three distinct cases, and conflating them is how you end up believing you
-  # have hardware Vulkan while running llvmpipe:
-  #
-  #   NVIDIA  needs the NVIDIA Container Toolkit (`--gpus all`). Passing
-  #           /dev/dri alone does NOT work — Mesa cannot drive an NVIDIA card,
-  #           and the proprietary userspace lives outside the image.
-  #   Mesa    (AMD/Intel) works with a plain /dev/dri passthrough plus the
-  #           host's render/video GIDs.
-  #   neither software Vulkan (lavapipe): correct, and slow.
-  if [ "${SYLPH_VULKAN:-auto}" = "sw" ]; then
-    _out+=(-e SYLPH_VULKAN=sw)
-  elif command -v nvidia-smi >/dev/null 2>&1 && nvidia-smi -L >/dev/null 2>&1; then
-    if docker info --format '{{json .Runtimes}}' 2>/dev/null | grep -q nvidia; then
-      _out+=(--gpus all)
-    else
-      echo "==> NOTE: NVIDIA GPU found but the NVIDIA Container Toolkit is not" >&2
-      echo "    installed, so Godot falls back to lavapipe (software — correct," >&2
-      echo "    slow, and the reason for any low-FPS report). To enable it:" >&2
-      echo "      curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey \\" >&2
-      echo "        | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg" >&2
-      echo "      curl -fsSL https://nvidia.github.io/libnvidia-container/stable/deb/nvidia-container-toolkit.list \\" >&2
-      echo "        | sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#g' \\" >&2
-      echo "        | sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list" >&2
-      echo "      sudo apt update && sudo apt install -y nvidia-container-toolkit" >&2
-      echo "      sudo nvidia-ctk runtime configure --runtime=docker" >&2
-      echo "      sudo systemctl restart docker" >&2
-      _out+=(-e SYLPH_VULKAN=sw)
-    fi
-  elif [ -e /dev/dri/renderD128 ]; then
-    _out+=(--device /dev/dri)
-    for g in render video; do
-      gid=$(getent group "$g" | cut -d: -f3 || true)
-      [ -n "$gid" ] && _out+=(--group-add "$gid")
-    done
-  else
-    _out+=(-e SYLPH_VULKAN=sw)
-  fi
-
   printf '%s\n' "${_out[@]}"
 }
 
@@ -207,12 +140,7 @@ case "${1:-}" in
     INTERVAL="${SYLPH_LOOP_INTERVAL-45m}"
     echo "==> loose  |  cpus=$CPUS  mem=${MEM_GB}g  pacing=${INTERVAL:-self}"
     echo "==> repo:   own clone in volume sylpheed-port-repo -> /work"
-    # `unless-stopped`, NOT `on-failure`: an OOM kill on this setup reports
-    # `OOMKilled: true` with **ExitCode 0**, so `on-failure` would read a memory
-    # kill as a clean finish and leave the agent down. Restarting into the same
-    # death is handled in the entrypoint, which refuses to `--continue` when the
-    # last start was under two minutes ago.
-    docker run -d -i -t --restart unless-stopped "${ARGS[@]}" -e SYLPH_AUTONOMOUS=1 -w /work "$IMAGE" \
+    docker run -d -i -t "${ARGS[@]}" -e SYLPH_AUTONOMOUS=1 -w /work "$IMAGE" \
       "/loop ${INTERVAL:+$INTERVAL }$TASK" >/dev/null
     echo
     echo "    running detached as '$NAME'."

docker/sylph-watchdog

@@ -1,176 +0,0 @@
-#!/usr/bin/env bash
-# Restart an agent whose Claude session is parked at an expired login.
-#
-#   ./sylph-watchdog            watch forever (run detached)
-#   ./sylph-watchdog --once     one pass, for cron or a manual check
-#   ./sylph-watchdog --status   what it would do right now, changing nothing
-#
-# Env: SYLPH_WATCH_INTERVAL (default 300s), SYLPH_WATCH_CONTAINERS
-#
-# ── Why this exists ─────────────────────────────────────────────────────────
-#
-# 🔴 `--restart unless-stopped` DOES NOT COVER THIS, and that is the whole point.
-# Docker restarts a container that EXITS. A Claude session sitting at
-#
-#     Login expired · Please run /login
-#
-# never exits. The process is healthy, the container is Up, `docker ps` is green,
-# and the agent has done nothing for hours. Three times now (2026-08-30,
-# 09-02, 09-03) that has been noticed only because a human saw Remote Control
-# report "Can't reach your computer" — which is a symptom of the session being
-# unable to attach, not a report about the machine.
-#
-# The fix is already in the entrypoint: it copies the host's credentials in when
-# they are newer than the container's. It just needs something to notice and
-# bounce the container. That is all this does.
-#
-# ⚠️ It restarts rather than logging in. A restart re-runs the entrypoint, which
-# re-seeds credentials AND resumes the session by id, so the agent keeps its
-# context. There is nothing here that could log a session in on its own, and it
-# should not pretend to: if the HOST's credentials are also stale, this loop will
-# bounce the container and the agent will park again. It says so instead of
-# retrying silently.
-set -uo pipefail
-
-CONTAINERS="${SYLPH_WATCH_CONTAINERS:-sylpheed-agent sylpheed-port}"
-INTERVAL="${SYLPH_WATCH_INTERVAL:-300}"
-
-# How far back to look. Longer than the interval so a stall spanning two passes
-# is still seen, short enough that a login expiry cured an hour ago does not
-# read as current.
-WINDOW="${SYLPH_WATCH_WINDOW:-20m}"
-
-log() { printf '[watchdog %s] %s\n' "$(date -u '+%H:%M:%S')" "$*"; }
-
-# Has this container printed an expiry recently, and NOT recovered since?
-#
-# "Recovered" matters: the string stays in the log forever, so a bare grep would
-# restart a healthy agent every pass on the strength of an hours-old line. The
-# test is whether the transcript has been written SINCE the last expiry — a
-# working agent writes constantly.
-parked() {
-  local c="$1"
-  docker ps --filter "name=^${c}$" --format '{{.Names}}' | grep -q . || return 1
-
-  local hits
-  hits=$(docker logs --since "$WINDOW" "$c" 2>&1 \
-         | sed 's/\x1b\[[0-9;?]*[a-zA-Z]//g' \
-         | grep -c 'Login expired' 2>/dev/null || true)
-  [ "${hits:-0}" -gt 0 ] || return 1
-
-  # Transcript idle for longer than one interval => it really is stuck. A busy
-  # agent that merely logged an expiry and recovered keeps writing.
-  local age
-  age=$(docker exec "$c" bash -lc '
-      f=$(ls -1t "$HOME/.claude/projects"/*/*.jsonl 2>/dev/null | head -1)
-      [ -n "$f" ] && echo $(( $(date +%s) - $(stat -c %Y "$f") )) || echo 999999
-    ' 2>/dev/null | tr -d '[:space:]')
-  case "$age" in ''|*[!0-9]*) age=999999 ;; esac
-  [ "$age" -gt "$INTERVAL" ]
-}
-
-# Is the HOST's copy actually newer? If not, a restart cannot help and saying so
-# is the useful output — otherwise this becomes a loop that bounces a container
-# every five minutes and reports success.
-host_is_newer() {
-  local c="$1"
-  docker exec "$c" bash -lc '
-    s="$HOME/.claude.seed/.credentials.json"; o="$HOME/.claude/.credentials.json"
-    [ -e "$s" ] || exit 2
-    [ ! -e "$o" ] || [ "$s" -nt "$o" ]
-  ' >/dev/null 2>&1
-}
-
-pass() {
-  local acted=0
-  for c in $CONTAINERS; do
-    if parked "$c"; then
-      if host_is_newer "$c"; then
-        log "$c is parked at an expired login; host credentials are newer -- restarting"
-        [ "${1:-}" = "--status" ] || docker restart "$c" >/dev/null 2>&1 \
-          && log "$c restarted (entrypoint re-seeds and resumes the session)"
-      else
-        log "🔴 $c is parked at an expired login and the HOST's credentials are"
-        log "   NO NEWER. A restart cannot fix this -- log in on the host first."
-      fi
-      acted=1
-    fi
-  done
-  [ "$acted" = 0 ] && log "all watched agents are alive"
-  return 0
-}
-
-# ── The control, EXECUTED ───────────────────────────────────────────────────
-#
-# 🔴 A watchdog that has never fired is a hope, not a guard. Its whole value is
-# in the true-positive path, and that path only runs when an agent is already
-# broken -- so it gets a synthetic one.
-#
-# Two cases against real containers, because the detection is `docker logs` plus
-# `docker exec` and neither can be reasoned about from the shell:
-#
-#   a container printing "Login expired" with no transcript  -> parked   (TRUE positive)
-#   a live agent                                             -> not parked (negative)
-#
-# ⚠️ Written after claiming, wrongly and without checking, that a bare grep
-# "would have fired" on a recovered container. The count was zero. That is the
-# same error this whole corpus keeps cataloguing -- asserting what an instrument
-# would have said instead of running it -- so the instrument now runs.
-selftest() {
-  local ok=0 name="sylph-watchdog-control-$$"
-  echo "control:"
-
-  docker run -d --rm --name "$name" alpine:latest \
-    sh -c 'echo "Login expired · Please run /login"; sleep 120' >/dev/null 2>&1
-  # Give docker a moment to have the line available in the log.
-  for _ in 1 2 3 4 5; do
-    docker logs "$name" 2>&1 | grep -q 'Login expired' && break
-    sleep 1
-  done
-
-  if SYLPH_WATCH_CONTAINERS="$name" parked "$name"; then
-    printf '  %-46s ✅\n' "an expired login with no transcript reads PARKED"
-  else
-    printf '  %-46s 🔴\n' "an expired login with no transcript reads PARKED"; ok=1
-  fi
-
-  # And it must NOT fire on the same container once it is gone -- a stopped
-  # container is not a parked one, and restarting it would be wrong.
-  docker rm -f "$name" >/dev/null 2>&1
-  if parked "$name"; then
-    printf '  %-46s 🔴\n' "a container that is gone reads NOT parked"; ok=1
-  else
-    printf '  %-46s ✅\n' "a container that is gone reads NOT parked"
-  fi
-
-  # The live negative, against whatever is actually running.
-  local live=0
-  for c in $CONTAINERS; do
-    docker ps --filter "name=^${c}$" --format '{{.Names}}' | grep -q . || continue
-    live=1
-    if parked "$c"; then
-      printf '  %-46s 🔴  (%s)\n' "a working agent reads NOT parked" "$c"; ok=1
-    else
-      printf '  %-46s ✅  (%s)\n' "a working agent reads NOT parked" "$c"
-    fi
-  done
-  [ "$live" = 1 ] || printf '  %-46s --  no agent running\n' "a working agent reads NOT parked"
-
-  echo
-  [ $ok -eq 0 ] && echo "the watchdog fires on a parked session and not otherwise" \
-                || echo "🔴 the watchdog cannot tell parked from alive"
-  return $ok
-}
-
-case "${1:-}" in
-  --once)     pass ;;
-  --status)   pass --status ;;
-  --selftest) selftest; exit $? ;;
-  *)
-    log "watching [$CONTAINERS] every ${INTERVAL}s"
-    while true; do
-      pass
-      sleep "$INTERVAL"
-    done
-    ;;
-esac

docs/agents/PLAYTEST-2026-09-01.md

@@ -1,106 +0,0 @@
-# Play-test, 2026-09-01 — a human, a real controller, the port
-
-**The first time a person played this port on real hardware.** It found four
-things. Two were fixed on the spot by the human; two are open and are the
-**current focus of both agents**.
-
-⚠️ This page is a record of observations, not a mission change. `PORT-MISSION.md`
-and the loop briefs carry the objective.
-
-## What was found
-
-| # | finding | status |
-|---|---|---|
-| 1 | **Ⓐ and Ⓑ did nothing on the pad.** Could not skip the intro, could not open a submenu. | ✅ fixed by the human — `port/scripts/gamepad.gd` |
-| 2 | **The left stick moved the cursor far too fast.** | ✅ fixed by the human — latched to one step per deflection |
-| 3 | **The `PRESS Ⓐ` plate appears too late.** | 🔴 **OPEN** |
-| 4 | **The splash fade/blur is wrong** — the game's is *more pronounced*. | 🔴 **OPEN** |
-
-## 1 & 2 — why no check caught them, which matters more than the fixes
-
-> **`--script` sends `InputEventAction`, which BYPASSES the input map.**
-
-Every check the port had asserted the code *below* the input map and nothing
-about the map itself. The map turned out to have **no joypad binding for
-`ui_accept` or `ui_cancel` at all** — measured on Godot 4.7.2, not remembered,
-because the remembered answer was wrong:
-
-```
-ui_accept   key:Enter, key:Kp Enter, key:Space     <- no joypad button at all
-ui_cancel   key:Escape                             <- no joypad button at all
-ui_up       key:Up, JOYBTN:11, JOYAXIS:1-          <- d-pad AND left stick
-ui_down     key:Down, JOYBTN:12, JOYAXIS:1+
-```
-
-Four actions reached the pad and two did not. Ⓐ was dead for the whole of P5
-while the unattended walk passed on every iteration.
-
-The **same blind spot** hid finding 2: an `InputEventAction` is not an analog
-axis, so nothing could observe that a stick held at deflection emits an event
-per *jitter*, each reporting the action as pressed — one cursor step per jitter.
-
-Now asserted by `tools/port/verify-input`, with a control that removes each
-check's own subject. (Its first version inverted all nine assertions when only
-two depended on the fix, and reported seven correct checks as broken. Three rows
-now say plainly they are **not controllable** — they assert Godot's own bindings
-— and one is a **negative carrying a positive control** rather than a faked
-inversion.)
-
-### The standing rule that follows
-
-**Synthetic input is not a test of input.** Anything injected below the input map
-is evidence about the code above it and nothing else. A test of input must go in
-at the device level — `InputEventJoypadButton`, `InputEventJoypadMotion`,
-`InputEventKey` — or must assert the map directly.
-
-## 3 — the plate is late
-
-The port raises the plate at `t=236`, **3.93 s** after the shared clock starts,
-which it derives as `238 − 118 = 120 units = 2.000 s` after the title's build-in
-ends. A human watching both says it is **late**.
-
-This lands in a spot the corpus already knows is soft. All of the following are
-live:
-
-* `REFUTED.md`: *"a screen has SETTLED at its `rest.t`"* → ❌ — believing `rest.t`
-  had already put a port's plate **3.97 s late** once.
-* `REFUTED.md`: the 2.13 s figure was *"a wall-clock reading stretched by Canary
-  presenting at ~28.1 fps"*, corrected to 120 units. **So the conversion between
-  units and seconds is load-bearing here and is exactly what
-  [`TEMPORAL-VERIFICATION.md`](TEMPORAL-VERIFICATION.md) says not to trust from a
-  wall clock.**
-* The keyframe **time-unit shift** is unresolved (`ui-keyframe-time-unit.md`).
-* 🔴 After the 2026-09-01 R1 pass, *"the declared keyframe timeline reproduces the
-  captured splash"* is **🟡 `⟨our-reader⟩`**, not ❌ — the record-layout fix
-  re-times a group's final pose and the entry was never re-derived under it.
-
-**Candidate causes, none established:** the unit→seconds constant; the clock
-origin (do both builds really start together?); `rest.t` again; the record layout.
-Settle it by **ordering and counts**, not by a stopwatch.
-
-## 4 — the splash fade/blur
-
-The port applies **no blur at all**. It draws declared keyframe alphas. So
-*"more pronounced in the game"* is consistent with a post-process the export does
-not describe, a different ramp shape, or both — and nothing in the export can
-distinguish those.
-
-🔴 **And the two splashes are the ONLY screens that reach `rest()`'s
-plateau-less fallback** — title, main menu and `EXTRAS` reach it zero times. So
-finding 4 lands precisely where our resting-pose heuristic is least trustworthy,
-and the R1 pass just re-opened that question **in both directions** (see the
-`rest()` pair in `REFUTED.md`). That is not a coincidence to step around.
-
-## The human's verdict on method
-
-> *"It seems the agents were essentially guessing and trying to copy what one
-> would see, but while they did get close it still is not quite right."*
-
-Close-but-not-right is the signature of reproducing **appearance** instead of
-deriving **mechanism**. A ramp tuned until it looks right is wrong in a way
-nobody can name and has no reach to the next screen.
-
-The instruction that follows: for the splashes, **find out what the game is
-doing** — is there a post-process pass, how many, what shader, what blend, what
-render targets, and where do its parameters come from — before proposing any
-curve. See the Decoder's brief.

docs/agents/PLAYTEST-2026-09-02-menus.md

@@ -1,230 +0,0 @@
-# Play-test, 2026-09-02 (second) — **P5 IS MET**, and four findings
-
-## ✅ P5's gate is MET — the human clicked through it
-
-> *"Menu walk and navigation is fine. Video skips too. Extras open. New Game
-> shows new game intro video."*
-
-**P5 is done.** Its gate was *"a human clicks through it"*, the retro said it had
-been waiting on that and not on code for the whole milestone, and it has now
-happened. `PORT-MISSION.md` is updated.
-
-The human also confirmed the NEW GAME gap is understood and acceptable:
-*"Deliberate AFAIK, in actual game the difficulty select comes first."* The port
-announces the two screens it skips; that stays as it is.
-
----
-
-## F1 — 🔴 The menu DOES repeat on a held direction. Ours does not.
-
-> *"Moving stick up/down and holding only moves one item. In game it actually
-> continues to move when holding up/down, just at a medium pace so player does
-> not need to move pad middle↔up/down, but also slow enough to see which item is
-> selected and move to target."*
-
-**This settles the existence half of H1, and it settles it against us.** One step
-per deflection was authored as the conservative choice precisely because nobody
-knew. Now somebody has watched the real game: **it repeats.**
-
-⚠️ **The RATE is still not measured, and it must not be guessed.** The human's
-description bounds it usefully and does not supply a number: fast enough that a
-player need not return the stick to centre, slow enough to read the selection as
-it passes. That is a range, not a value.
-
-* **Decoder — measure it.** Hold a direction in Canary and count. Two numbers:
-  the **initial delay** before the first repeat, and the **repeat interval**
-  after it. Frames between cursor moves, at a stated present rate — a count, not
-  a stopwatch reading ([`TEMPORAL-VERIFICATION.md`](TEMPORAL-VERIFICATION.md)).
-  Also: does the d-pad differ from the stick? Does the rate accelerate while
-  held, or stay flat?
-* **Port — implement the mechanism, take the number from the Decoder.** Do not
-  ship a placeholder rate: an invented interval here is indistinguishable from a
-  measured one a month from now, and this is the exact field where that has
-  already cost us once.
-
-## F2 — 🔴 The sound effects are too loud. There is no mix at all.
-
-> *"Largely OK. Biggest notice is the volume, many effects are too loud."*
-
-**Measured, and the human is right.** Every clip plays at unity gain, because
-**no volume or gain value exists anywhere** — not in `export/`, not in
-`authored/`, not in the manifest:
-
-| | mean | max |
-|---|---|---|
-| **`se/confirm`** | **−17.7 dB** | **−0.0 dB** — at full scale |
-| `se/move` | −24.1 | −1.4 |
-| `se/back` | −21.0 | −5.7 |
-| `bgm/main_menu` | −20.7 | −4.2 |
-
-`confirm` is the loudest thing in the export: **3 dB hotter in mean than the
-music** and 6.4 dB above `move`. A game mixes SE against BGM on separate buses;
-this port has one bus and no gains.
-
-* **Decoder — is the mix ON THE DISC?** The obvious place is the cue table: a
-  cue record commonly carries volume alongside the wave index, and
-  `sub_821C5580` is already known to play cue 1103. If per-cue or per-bus gain is
-  there, it is **decoded** and nobody has to choose. If it is provably not, say
-  so with reach and it becomes an authored mix.
-* **Port — do not normalise in the exporter to fix this.** Re-levelling the file
-  destroys the relationship between clips and cannot be undone by a modder.
-  Gains belong at playback, as data, where a measured value can replace a chosen
-  one without re-exporting.
-
-## F3 — ❔ Something is missing on the title screen
-
-> *"I also think that there is a sound track or effect missing at the title
-> screen."*
-
-The export carries exactly one music track, `bgm/main_menu.ogg`, and the port
-plays nothing on the title. Whether the game does is unestablished.
-
-* **Decoder:** which cue, if any, does the **title** play? The menu's is decoded
-  (cue 1103 = `BGM_103` via `sub_821C5580`); the same route should answer the
-  title. And is there a one-shot **sting** when the plate appears, or when Ⓐ is
-  accepted? Either would read as "something missing" to a player.
-* ⚠️ A negative here needs a positive control (R4): show the method finding the
-  menu's cue before concluding the title has none.
-
-## F4 — 🔴 Ⓐ SKIPS FORWARD through the boot. We only implement one of the three.
-
-> *"In the game one can get the plate to immediately show by pressing Ⓐ,
-> essentially skip to it. So after the logos one can immediately skip to the main
-> menu by pressing Ⓐ three times: 1. skip intro video, 2. show plate, 3. the
-> plate itself."*
-
-A measured behaviour of the real game, and a good one — it is how a returning
-player gets past the boot.
-
-| press | in the game | in the port |
-|---|---|---|
-| Ⓐ #1 | skips the intro video | ✅ implemented |
-| **Ⓐ #2** | **completes the title build-in and shows the plate immediately** | ❌ **missing** |
-| Ⓐ #3 | activates the plate → main menu | ✅ implemented |
-
-* **Port:** Ⓐ during the title build-in should jump the sequence to the plate's
-  arrival rather than being swallowed. ⚠️ **Careful what "jump" means, and do
-  not choose it.** See below — it is a test of an authored premise, not a detail.
-* **Decoder:** what does Ⓐ do to the clock? This is also a **second, cheap route
-  to the plate-arrival question** — a press that skips to the plate tells you
-  where the game thinks the plate belongs.
-
-### 🔴 F4 is a TEST OF `clock: "shared"`, which is authored and only ~20 % confirmed
-
-**Correction, by the human who wrote this page: an earlier draft said "both
-clocks". There is only ONE.** `authored/flow.json` sets `"clock": "shared"`: the
-title is two composited builds — build 4 the artwork, build 2/3 the plate — and
-they run on **one clock started together**. Build 4's artwork finishes at
-`t ≈ 118`; the plate reaches full alpha at `t = 236`. Saying "both clocks" would
-send someone hunting for a second one that this corpus says does not exist.
-
-With that fixed, the question is sharp and **observable**:
-
-| if Ⓐ … | then pressing EARLY looks like |
-|---|---|
-| **advances the shared clock** | the title artwork **snaps** to finished, and the plate appears |
-| **only forces the plate visible** | the artwork **keeps animating** its remaining build-in while the plate appears over it |
-
-So film a boot, press Ⓐ while the wordmark is still building in, and watch the
-**artwork**, not the plate.
-
-📌 **Why this matters beyond the feature.** `clock: "shared"` is **authored**, and
-`plate-arrival-halves.md` says in its own words that it is *"not falsified… not
-confirmed to better than ~20 % either"*. There is also an unresolved anchor
-disagreement **inside one binary**: the reconciliation picked `t=118`, while
-`settle_time()` returns **160** and the boot prints `settles at t=160`.
-
-If Ⓐ snaps the artwork, that is evidence **for** one shared clock. If the artwork
-carries on while the plate appears, the plate has a timeline of its own and the
-authored premise is in trouble. **Answer F4 before building on `shared`.**
-* 📌 And it bears on `REFUTED.md`: *"any title after the first one refuses
-  input"* is already narrowed to the attract-returned title. This is a third
-  input the boot title accepts.
-
----
-
-## F5 — Ⓐ: does the animation SNAP, or accelerate? **A human cannot tell.**
-
-Follow-up from the same human, and the honesty in it is the useful part:
-
-> *"I think the animation speeds up to the finished state. So it is not a snap in
-> the sense of a cut, but rather becoming much quicker — which however feels
-> instant too, so it is difficult to discern by a human. It might also actually
-> snap/cut to the finished state, but appear as a quick animation… Similar to how
-> videos work by quickly playing distinct frames. So I cannot tell certainly
-> which it is. Upon multiple attempts it does look more like a snap. Decoder
-> still should verify."*
-
-**This is a question the oracle-by-eye cannot answer, and it is being handed over
-as such rather than guessed.** A three-frame acceleration and a one-frame cut are
-indistinguishable to a person; they are trivially distinguishable to an
-instrument. Two independent routes, and they should agree:
-
-1. **Per-frame capture.** Press Ⓐ mid-build-in and read the submitted alphas
-   frame by frame. An acceleration shows **intermediate values**; a cut shows
-   one transition and none. This is a counting question — see
-   [`TEMPORAL-VERIFICATION.md`](TEMPORAL-VERIFICATION.md), and note that the eye
-   failing here is exactly why.
-2. **The code.** Whatever Ⓐ does to the clock is a store somewhere: does it
-   assign the target time, or raise a rate multiplier? A snap and a speed-up are
-   different instructions, and the image says which.
-
-⚠️ The human's *"looks more like a snap on multiple attempts"* is a **prior, not
-a result.** Do not let it stand in for the measurement, and say so if the
-measurement disagrees with it.
-
-## F6 — 🔴 The title's sweeping glow starts TOO EARLY in the port
-
-> *"…blue geometric lines (like on a PCB, straight lines and rectangular or 45°
-> turns). These have a white glow moving on them as an animation. In the game
-> this animation only starts when the plate is shown — basically the animation
-> starts the same as the 'insert' of the plate. In the port it already starts
-> before the plate arrives."*
-
-**The elements are `ptloop01` and `ptloop02`** — already known to this corpus as
-the sweeps whose leaf *"sweeps a 400 px quad whose left edge travels
-−639…1521"*, and whose free-running on the settled title is a ❌ entry in
-`REFUTED.md` (they **do** free-run). Nothing there says **when they start**, and
-that is the whole of this finding.
-
-### 📌 A lead, from the exported declaration — MINE, unverified, check it first
-
-`title.json` gives `ptloop01` and `ptloop02` keyframes at:
-
-```
-t = 0, 70, 100, 238, 250
-```
-
-and the plate reaches full alpha at **`t = 236`**. They are not alone: `pteff02`
-has a key at exactly **236**, and `ptlogo_back2eff` and `ptcopyright` at **238**.
-**236–238 is a synchronisation point in the declared data**, and the human has
-just reported a behaviour change at that instant.
-
-So the first question is cheap: **is the sweep's motion declared to begin at 238,
-with the port instead free-running the leaf from t=0?** If so this is a decode
-question with a decoded answer, and nothing needs authoring.
-
-⚠️ **Two reasons not to take that lead as the answer.** The `238…250` pair looks
-just as much like an **exit ramp** — `ptcopyright` and `ptlogo_back2eff` use
-exactly that shape and they are certainly not starting anything. And the sweep
-lives in a **nested `.rat` leaf** with its own three keyframes, so the parent's
-envelope and the leaf's motion are different timelines. Which of the two the
-human is watching is the thing to establish.
-
-### Why this one is worth prioritising
-
-It bears directly on **F4 and on `clock: "shared"`**. If a title element does not
-begin moving until the plate arrives, then either the declared data says so — in
-which case the shared clock survives and our reading of the keyframes is wrong —
-or something at the plate's arrival **starts** it, which is a mechanism nobody
-has proposed. Either answer constrains the clock question that F4 is also
-probing.
-
-## H3 — the plate delay is ACCEPTED
-
-> *"Delay feels the same. Cannot verify it is exact same, but is sufficient."*
-
-Good enough to stop working on, **not** established as correct. Leave the row as
-unattributed rather than closing it green; if the duration question is ever
-settled by the pipeline work, check it against this rather than re-opening it
-from scratch.

docs/agents/PLAYTEST-2026-09-02.md

@@ -1,193 +0,0 @@
-# Play-test, 2026-09-02 — the splash did not animate. **Now fixed and signed off.**
-
-## ✅ CLOSED THE SAME DAY — the human's verdict, which is the only gate that counts
-
-> *"Looks good! Cannot notice any obvious difference from the actual game.
-> Mark logos as done."* — 2026-09-02
-
-**The logo splashes are DONE.** Not "the check passes" — a person compared the
-port against the real game and could not tell them apart. That is the oracle,
-and it is the strongest result this port has produced.
-
-⚠️ **Both agents: the sole-focus block is lifted.** Return to your milestones.
-What remains open from the play-tests is listed at the bottom of this page; none
-of it is this.
-
-### The root cause was one word
-
-```diff
-- t = settle_instant if settle_instant >= 0.0 else min(t, settle_units(element))
-+ t = min(t, settle_instant)      # the comment above it already said "stop at"
-```
-
-`pose_at` **assigned** the settle instant instead of clamping to it, so every
-query returned the settled pose whatever the clock said.
-
-🔴 **And the same line manufactured the false green.** The capture harness shoots
-after two frames, so it was photographing t ≈ 2 units — which *looked* settled
-only because everything looked settled. **The 0.01 % agreement that closed H2 was
-measured through the accident.** One bug produced the defect and the evidence
-that the defect was absent.
-
-### Verified independently before it went to the human
-
-Filmed a real boot at 0.05 s, before against after:
-
-| | before | after |
-|---|---|---|
-| splash in motion | 1.30 s / 7.95 s (16.4 %) | **2.20 s / 7.95 s (27.7 %)** |
-| distinct luma states | 26 | **43** |
-| publisher ramp | 0.30 s, 6 steps | **0.65 s, 13 steps, one continuous run** |
-| developer splash | two bursts split by a **0.50 s freeze** | **one continuous 0.90 s run** |
-
-The publisher trajectory rises to a peak and settles back — the **crossfade
-signature**: glow alone, then both, then sharp only. The developer splash's
-interrupting freeze disappearing is the clearest single sign the clock now drives
-the poses.
-
-The port then closed a gap `motion-census` names in its own header — *"a wrong
-ramp that moves every frame passes here"* — with a shape check pre-registered
-from the disc, measured off a film, on a strip no other element overlaps, in
-**ratios** so the texture divides out: middle:last declared 0.203 / measured
-0.213, rise:last declared 1.20 / measured **1.20 exact**. It agrees with the
-Decoder's independent measurement of the running game.
-
-### 🔴 The lesson, which outlives the bug
-
-Three instruments passed a frozen screen. Keep this: **an instrument that sits
-below the thing under test cannot see it fail.** A frozen sweep drives the clock
-by hand; a settled comparison is *defined* to pass on a frozen screen; an
-achieved-fps counter counts frames drawn, not frames different. Ask of any new
-check: *what would this still report if the feature were entirely absent?*
-
----
-
-## The original report, kept for the record
-
-The human, watching the port on real hardware, on a GPU, at ~140 fps:
-
-> *"The port does no blur animation at all! I cannot discern if there is any
-> animation at all. The logos just switch without the animation."*
-
-## Measured, not paraphrased
-
-Filmed from a **real boot** at 0.05 s (`--film`), then per-frame change measured
-with [`tools/motion-census`](../../tools/motion-census):
-
-| | |
-|---|---|
-| splash moves | **1.30 s of 7.95 s — 16.4 %** |
-| publisher splash | 0.30 s of motion, then **3.20 s frozen** |
-| developer splash | 0.35 s + 0.25 s, then **2.40 s frozen** |
-| distinct luma states in 7.95 s | **26** |
-
-A 45-unit build-in cannot be drawn in 26 states, and a fade does not hold one
-picture for 3.20 s. **This is a switch with a flicker on either side.**
-
-The frame counter says 24.8 fps achieved. Both are true: the port is *drawing*
-25 times a second and *changing* almost never.
-
-## 🔴 Why three instruments all said it was correct
-
-This is the part that matters more than the bug, because it is the fourth time
-this shape has cost a milestone.
-
-| instrument | what it proved | what it could not see |
-|---|---|---|
-| **frozen sweep** (`--time=`, 3 units a step) | the renderer CAN draw pose *N* | whether the poses are ever drawn **in sequence, while running** |
-| **settled comparison** (0.01 % against the capture) | the resting pose is right | a screen frozen 84 % of the time matches a settled reference **perfectly — that is what frozen means** |
-| **achieved-fps counter** | frames are being drawn | drawing the **same pixels** 25×/s scores identically to animating |
-
-> **Every one measured throughput or a pose. Not one measured CHANGE.**
-
-That is why the port could write *"the companion quads are drawn, verified by a
-frozen sweep"* and be simultaneously right and useless: the sweep drives the
-clock by hand. It is the same defect as `InputEventAction` bypassing the input
-map — **the instrument sat below the thing that was broken**, so the thing that
-was broken could not appear in it.
-
-`tools/motion-census` exists to close this class. It measures change and nothing
-else, and its `--selftest` proves it separates a fade (97.4 % moving) from a
-switch (2.6 %) from a frozen film (0.0 %) — because a detector that cannot tell
-those apart would report the same green line on all three.
-
-## What both agents do now
-
-**Nothing else.** Not the clock rate, not the plate, not blend, not audio. This
-first.
-
-### Port
-
-1. **Reproduce it** with `--film` + `motion-census` before changing anything, and
-   quote the numbers. If your run does not reproduce 16.4 %, say so — the
-   disagreement is then the finding.
-2. **Find why the clock does not advance the poses.** Candidates, unranked and
-   none established: the keyframe interpolation returns the same pose for a
-   range of *t*; `rest()`/plateau logic snapping to an endpoint; the group clock
-   not integrating; interpolation between keyframes not happening at all
-   (nearest-keyframe rather than lerp); the screen advancing by *keyframe index*
-   instead of by time.
-3. **Every fix is gated by a film**, never by a still. A change that improves a
-   settled frame and leaves the film at 16 % has not fixed this.
-4. `motion-census` goes into `check-all`, so a future regression fails a check
-   instead of waiting for a human.
-
-### Decoder — **map the whole graphics pipeline, end to end**
-
-The human's instruction, in their words: *"get the whole graphics pipeline, from
-the xex/pe + the disc files to the final screen displayed, and take Xenia Canary
-processing into account too."*
-
-So: one continuous account, each stage with evidence and each labelled by the
-instrument that produced it —
-
-```
-disc bytes  →  RATC/T8aD decode  →  what the GAME CODE does per frame
-            →  the draw calls it submits  →  Canary's own processing
-            →  the presented frame
-```
-
-Specifically, and none of it inferable from a file alone:
-
-* **The game's per-frame update.** Which code advances a UI group's clock, in
-  what units, and what it does *between* keyframes — does it interpolate, or
-  hold to the next key? That single question decides whether the port should
-  lerp at all. It is in the image; find the function.
-* **What the game submits per frame during the splash** — the draw list frame by
-  frame, not one settled frame. If the alpha changes, it changes *somewhere*
-  observable: a vertex colour, a PS constant, a blend factor, a texture swap.
-  **Name which, with the per-frame series.**
-* **What Canary does to it.** Present cadence, any resolve/scaling/gamma between
-  the guest's draw and the pixels a capture records. A capture is evidence about
-  *Canary's output*, and the difference between that and the guest's intent has
-  bitten this corpus before (the `kernel_display_gamma_type` entry).
-
-⚠️ **Deliver a per-frame SERIES, not a settled value.** Follow
-[`TEMPORAL-VERIFICATION.md`](TEMPORAL-VERIFICATION.md): film it, align by
-content, report ordering/counts/durations. The port needs to know what the
-alpha *trajectory* is, and a single frame cannot carry one.
-
-## And this is a refutation the port should record against itself
-
-`BLOCKED.md` H2 currently reads ✅ **ANSWERED**, on the strength of the frozen
-sweep. The mechanism half stands — the blur is a baked companion texture, that
-is decoded and correct. **The behaviour half does not**: the port draws those
-quads and does not animate them, so *"the companions are drawn"* was true and
-did not mean what the row used it to mean.
-
----
-
-## What is STILL OPEN after the sign-off
-
-The logos are done. These are not, and none of them blocks a milestone gate:
-
-| | | owner |
-|---|---|---|
-| **H1** | Does a held direction **repeat** in the menus, and at what rate? One step per deflection stays authored. The 61 % arm threshold is decoded and adopted; the 0.11 hysteresis gap is still authored. | Decoder |
-| **H3** | The `PRESS Ⓐ` plate. All four named causes are dead and the port measures fractionally **early**, so what the human saw is **unattributed** — deliberately not closed green. ⚠️ Worth re-asking now: the animation fix changed what the whole boot looks like, so the original observation may simply no longer reproduce. | both |
-| **pipeline** | The end-to-end graphics account — disc → decode → the game's per-frame update → submitted draws → Canary's processing → the presented frame. Cut short by the sole-focus order and **still the right work**: it is what would let the port know whether its ramp *duration* matches the game rather than only its own declared keyframes. | Decoder |
-
-**P5's gate is "a human clicks through it" and has NOT been claimed here.** The
-human has signed off the *logos*, and separately confirmed that Ⓐ, the stick and
-the submenus work. Nobody has said the milestone is met, and an agent must not
-say it on their behalf.

docs/agents/PROTOCOL.md

@@ -152,45 +152,6 @@ asking X"** rather than approximating. An approximation from the wrong agent
 arrives with no classification attached and is indistinguishable from a
 measurement a month later.
 
-## Work in units a human can check in a minute
-
-**Set by the human, 2026-09-02, from what actually worked.** The splash bug had
-sat through a whole milestone. Scoped to *one* question — *does it animate?* — it
-was found, fixed, verified and signed off in a day.
-
-> *"I think attacking the 'whole' mission was too big for them to handle. Split
-> the given missions and tasks into even smaller tasks which they can tackle and
-> give to a human for feedback."*
-
-So: **a milestone is not a unit of work. It is a bag of them.** Before starting,
-split it, and pick one.
-
-A unit is right-sized when it ends in something **a person can judge in under a
-minute without reading anything**. Not "P6 audio" — *"the confirm SFX is no
-longer louder than the music; listen once."* Not "the title screen" — *"the glow
-starts when the plate appears; watch one boot."*
-
-Each unit, written down **before** the work:
-
-* **the question**, as one sentence a non-expert could answer;
-* **what the human looks at**, and what pass and fail each look like;
-* **what it does NOT cover** — the neighbouring thing you are deliberately not
-  fixing, so nobody reads a narrow pass as a broad one.
-
-Then: **do that one, hand it over, and stop.** Do not run ahead into the next
-unit while the first is unverified — an unverified fix underneath a second change
-is how a regression becomes two-variable and unattributable.
-
-⚠️ **The bar is a HUMAN check, not a green tool.** Three instruments passed a
-frozen screen. A tool answers *did my change do what I intended*; only the person
-answers *is it right*. When a unit needs a look, say so plainly and say what to
-look at — an ask that is buried in a document nobody opens is not an ask.
-
-📌 And this bounds the writing, which has been the other failure: the retro found
-`DECISIONS.md` past 13 000 lines while the gate did not move. **A unit's record
-is proportional to the unit.** If explaining it takes longer than doing it, the
-unit was too big or the writing is doing something other than explaining.
-
 ## Publishing
 
 * Commit to `auto/<topic>`; a human merges.

docs/agents/TEMPORAL-VERIFICATION.md

@@ -1,139 +0,0 @@
-# Verifying things that MOVE
-
-**Both agents read this.** Set by the human on 2026-09-01, after a play-test
-found the splash fade and the `PRESS Ⓐ` plate visibly wrong while every check
-either agent had was green.
-
-## The diagnosis, in one sentence
-
-> **We have been trying to photograph the game at time *t*, and *t* is never the
-> same twice.**
-
-Every temporal claim in this corpus rests on grabbing a frame at a wall-clock
-instant and comparing it to something. That instant drifts — emulator speed
-varies with host load, Canary presents at ~28.1 fps rather than 30, the capture
-path costs a variable 0.1–10.8 s, and a long-lived `x11grab` stream degrades and
-then freezes. So the comparison is between *our render at the time we meant* and
-*the game at some other time*, and the difference between those two things is
-being read as a difference in the **content**.
-
-The register already carries four separate refutations of this exact shape:
-
-* *"a latency read off a classified `x11grab` stream is a duration"* — ❌. At
-  1503 ms per classification against an 8 fps stream the consumer ran at
-  0.64 fps; four "durations" died. A screen transition, a button press and a
-  plate fade all came out at ~20–25 s, which is the tell.
-* *"2 391 frames over 600 s, max glyph 0, therefore the title never appears"* —
-  withdrawn: **the instrument stalls**, repeating one stale frame, reading
-  surface mean 5.21 where `import` read 125.65 at the same moment.
-* *"the boot harness fails because its polling loop samples every ~41 s"* —
-  the defect was real and fixing it (13.7×) **did not change the answer**.
-* *"the in-box capture noise of 0.32 between sessions"* — it was not noise, it
-  was the **trigger**: gating on the plate pulse phase-locks the shutter, so
-  0.32 is a lower bound produced by the instrument. At an arbitrary phase the
-  honest figure is 11.9.
-
-That last one is the important one, and it cuts both ways: **gating hides
-variance, and not gating produces it.** Neither is a measurement of the game.
-
-## What to do instead
-
-The rule is simple and it removes the whole class:
-
-> **Never compare at an absolute time. Record a SEQUENCE, and align it by
-> CONTENT.**
-
-### 1. Capture a film, not a photograph
-
-Record a continuous run of frames with an index and a timestamp each, spanning
-the whole animation with margin at both ends. One frame is a sample of a
-distribution you have not characterised; a film *is* the distribution.
-
-**State the achieved rate against the requested rate, every time.** A capture
-that asked for 4 fps and delivered 1.6 is not a slow capture, it is a
-**different capture**, and it has already produced two withdrawn findings here.
-An instrument that cannot report its own completeness may not be trusted (R3).
-
-### 2. Align by content, then measure
-
-Find the offset that best matches, rather than assuming offset zero:
-
-* reduce each frame to a scalar or a small vector — mean of a region, an
-  element's alpha, a per-tile amplitude;
-* do the same for the prediction;
-* **search the lag** that maximises agreement, and report *both* the lag and the
-  agreement at it.
-
-The lag is not an error to be minimised away — **it is a measurement**. A
-consistent lag across runs is a real offset in our model. A lag that varies
-run to run is the harness, and says so.
-
-### 3. Prefer quantities that have no phase
-
-Ranked by how much they survive a drifting clock:
-
-| quantity | survives drift? |
-|---|---|
-| **ordering** — A finishes before B starts | ✅ completely |
-| **counts** — 83 frames at full alpha | ✅ (given a known, reported rate) |
-| **durations and ratios** — ramp is 2× the hold | ✅ |
-| **shape** — monotone, eased, stepped, its inflections | ✅ |
-| a value **at a named event** — alpha when the plate first appears | 🟡 needs the event found, not the time |
-| a value **at wall-clock t** | ❌ this is the thing that has been failing |
-
-The two strongest existing results in the corpus are both of this kind: the
-**hold duration** (83 frames of full alpha) is called *calibration-free* in
-`ui-keyframe-time-unit.md` and decided the question; and the `_eff` glows'
-**exact steps of 34** are a shape, not a sample.
-
-### 4. Anchor on an event
-
-Quote everything relative to a frame you can *find* rather than a time you
-requested: the first frame an element is non-black, the frame the plate first
-appears, the last frame of the previous screen. Then a drifting start costs
-nothing, because every number is a difference.
-
-### 5. Say what you expected before you look (R2)
-
-*"This ramp declares 80 units, so at 30 fps I expect ~80 frames and I will
-accept 74–86."* Written first, it makes a near-miss legible as a near-miss
-instead of something to rationalise. Written after, any number can be explained.
-
-### 6. Convert units deliberately
-
-⚠️ **Canary presents at ~28.1 fps, so a wall-clock duration off this emulator is
-~6 % long.** A measured interval landing near a round number of keyframe units
-probably *is* that number of units — that is how `2.13 s` turned out to be
-`120 units = 2.000 s`. Quote the unit count, then the seconds, then the fps you
-divided by. Never the seconds alone.
-
-## The other half: stop reproducing by eye
-
-The play-test's verdict on the splashes was *"close, but not quite right"*, and
-that is the signature of **matching appearance instead of deriving mechanism**.
-A ramp tuned until it looks right will be wrong in a way nobody can name, and
-"looks right" has no reach — it does not tell you what the next screen will do.
-
-So for anything visual that is still not exact, the question is not *"what
-curve fits?"* but **"what is the game actually doing?"**:
-
-* Is there a **post-process pass at all** — a blur, a bloom, a fade quad, a tone
-  curve? That is a GPU-state question with a yes/no answer.
-* If yes: how many passes, what render targets, what blend, what shader, and
-  **where do its parameters come from** — immediate constants, a table in a pak,
-  a computed ramp?
-* Only then, what curve.
-
-A mechanism found this way is *decoded*, generalises to every screen, and cannot
-be "close". A curve fitted by eye is none of those things.
-
-## What this does not license
-
-Doing more of this is not a reason to stop shipping. A measurement that would
-take an hour is not blocked on building the perfect harness first — take the
-cheap phase-invariant version (an ordering, a count) and say what its reach is.
-
-And **an instrument that cannot pass a control is not a starting point.** A
-filter that fails its own known-positive is dead, not tuneable; a lag search
-that cannot recover a synthetic 30-frame offset cannot measure an unknown one.
-Run the control first, and record it.

docs/agents/decoder-loop.md

@@ -1,233 +1,6 @@
 You are the **Decoder**. Answer the open questions the Godot menu port is
 blocked on, one at a time.
 
-## 🔴🔴 SOLE FOCUS, 2026-09-02: **THE TITLE'S ANIMATION TIMING — F5 and F6, nothing else**
-
-**Work only these two.** Not the pipeline, not the audio mix, not the repeat
-rate — they stay queued in
-[`PLAYTEST-2026-09-02-menus.md`](PLAYTEST-2026-09-02-menus.md).
-
-> *"Let's have the agents focus on this item and only this only."*
-
-**F6 first** — it is the one with a lead. A human reports that the title's
-sweeping white glow (**`ptloop01` / `ptloop02`**, the blue PCB-like lines) **only
-starts when the plate appears** in the real game, while the port starts it
-earlier. `title.json` declares those elements at `t = 0, 70, 100, 238, 250` and
-the plate reaches full alpha at **`t = 236`** — with `pteff02` keyed at exactly
-236 and `ptlogo_back2eff`/`ptcopyright` at 238. **236–238 is a synchronisation
-point in the declared data and a human just reported a behaviour change there.**
-⚠️ `238…250` may equally be an **exit ramp** (`ptcopyright` uses that shape and
-starts nothing), and the sweep lives in a nested `.rat` leaf with its own
-timeline. Establish which of the two the human is watching.
-
-**F5 second** — does Ⓐ **snap** the title to finished, or **accelerate** it? The
-human says they cannot tell, and is right that they cannot: a three-frame
-acceleration and a one-frame cut look identical to an eye. Two routes, and they
-should agree: a **per-frame capture** (an acceleration shows intermediate alphas,
-a cut shows none) and **the code** (assigning a target time and raising a rate
-multiplier are different instructions). Their *"looks more like a snap"* is a
-**prior, not a result** — say so if the measurement disagrees.
-
-### And split it before you start
-
-**Read the new "Work in units a human can check in a minute" section of
-[`PROTOCOL.md`](PROTOCOL.md).** The human's diagnosis is that whole missions have
-been too big to hold. Break even F6 down, write the question and the
-look-at-this-and-you-will-see before working, do one, hand it over, stop.
-
-## ✅ THE LOGO SPLASHES ARE DONE — signed off by the human, 2026-09-02
-
-> *"Looks good! Cannot notice any obvious difference from the actual game.
-> Mark logos as done."*
-
-**The sole-focus order is lifted.** The port's defect was `pose_at` assigning the
-settle instant rather than clamping to it; your per-frame measurement of the real
-game (28 distinct alphas over 28 consecutive presents, modal steps −3 and −14
-against predicted −2.87 and −14.13) is what let their fix be checked for *shape*
-and not merely for motion. That is the pairing this team is for.
-
-### 🔴 The pipeline work is STILL THE RIGHT WORK — continue it, at normal priority
-
-It was cut short by the sole-focus order, and it remains the thing that decides a
-question the port cannot answer about itself: **the port matches its own declared
-keyframes; nobody has established that its 60 units/s matches the game.** The
-ramp is right in shape and unverified in duration.
-
-So carry on with the end-to-end account, unchanged in substance:
-
-```
-disc bytes → RATC/T8aD decode → what the GAME CODE does per frame
-           → the draw calls it submits → Canary's own processing
-           → the presented frame
-```
-
-The three load-bearing questions stand, and the first is now the most valuable:
-
-1. **The per-frame update** — which function advances a UI group's clock, in what
-   units, and **what it does between keyframes**. The port interpolates
-   piecewise-linearly across declared segments and your capture agrees; the
-   remaining gap is the *rate*.
-2. **What is submitted per frame** during a screen's build-in, as a series.
-3. **What Canary does to it** before a capture records it — present cadence,
-   resolve, scale, gamma.
-
-### 🔴 Four asks from the 2026-09-02 menu play-test — [`PLAYTEST-2026-09-02-menus.md`](PLAYTEST-2026-09-02-menus.md)
-
-P5's gate is **met** (a human walked the menus). These came out of the same
-session, and three of the four are yours. They are ahead of the pipeline work
-because the port is blocked on two of them.
-
-1. **F1 — MEASURE THE MENU REPEAT RATE.** The human watched the real game: a held
-   direction **repeats**, *"at a medium pace… slow enough to see which item is
-   selected"*. That settles the existence half of H1 against our authored
-   one-step-per-deflection. Two numbers, and the port will not move without
-   them: the **initial delay** before the first repeat, and the **repeat
-   interval** after it. Frames between cursor moves at a stated present rate — a
-   count, not a stopwatch. Also: does the d-pad differ from the stick? Does it
-   accelerate while held, or stay flat?
-2. **F2 — IS THE AUDIO MIX ON THE DISC?** The SFX are too loud and there is **no
-   gain value anywhere** in the export; `confirm` peaks at −0.0 dBFS and sits
-   3 dB above the music in mean. A cue record commonly carries a volume beside
-   its wave index, and you already decoded `sub_821C5580` playing cue 1103. If
-   per-cue or per-bus gain is there it is **decoded** and nobody has to choose.
-   If it provably is not, say so with reach.
-3. **F3 — WHAT DOES THE TITLE PLAY?** A human says something is missing there.
-   Which cue, if any, does the title screen play, and is there a **sting** when
-   the plate appears or when Ⓐ is accepted? ⚠️ A negative needs a positive
-   control (R4): show the method finding the *menu's* cue before concluding the
-   title has none.
-4. **F4 — WHAT DOES Ⓐ DO TO THE CLOCK?** In the real game, Ⓐ during the title
-   build-in **reveals the plate immediately** — so the boot takes three presses:
-   skip video, reveal plate, accept plate.
-
-   🔴 **This is a test of `clock: "shared"`.** The title is two composited builds
-   — build 4 the artwork (finishes `t≈118`), build 2/3 the plate (full alpha
-   `t=236`) — and the port's `authored/flow.json` runs them on **one** clock
-   started together. That premise is **authored**, and the port's own
-   `plate-arrival-halves.md` calls it *"not falsified… not confirmed to better
-   than ~20 %"*, with an unresolved anchor disagreement inside one binary
-   (`t=118` from the reconciliation, `160` from `settle_time()`).
-
-   The discriminator is observable: **press Ⓐ early, while the wordmark is still
-   building in, and watch the ARTWORK, not the plate.**
-
-   | if Ⓐ … | the artwork |
-   |---|---|
-   | advances the shared clock | **snaps** to finished |
-   | only forces the plate visible | **keeps animating** its remaining build-in |
-
-   📌 It is also a **cheap second route to the plate-arrival question** — a press
-   that skips to the plate says where the game thinks the plate belongs — and a
-   third input the boot title accepts, narrowing `REFUTED.md`'s *"any title after
-   the first refuses input"* further.
-
-⚠️ Deliver a **series, not a settled value** — see
-[`TEMPORAL-VERIFICATION.md`](TEMPORAL-VERIFICATION.md), and note that the port's
-whole defect was invisible to three instruments that each measured a pose or a
-throughput rather than a change.
-
-## Previous sole focus, 2026-09-02 — the order, kept for the method
-
-A human on real hardware: *"the logos just switch, there is no animation."*
-Measured from a real boot — **the splash moves 1.30 s of 7.95 s (16.4 %)**, the
-publisher logo frozen **3.20 s**, and the whole thing takes **26 distinct luma
-states**. The port draws the right quads in the right places and never moves
-them.
-
-Your half is not the port's bug. It is that **nobody can say what the game does
-between keyframes**, so nobody can say what the port should be doing.
-
-### The deliverable, in the human's words
-
-> *"Get the whole graphics pipeline, from the xex/pe + the disc files to the
-> final screen displayed. Take Xenia Canary processing into account too."*
-
-One continuous account, each stage carrying its evidence and its `⟨instrument⟩`:
-
-```
-disc bytes → RATC/T8aD decode → what the GAME CODE does per frame
-           → the draw calls it submits → Canary's own processing
-           → the presented frame
-```
-
-Three questions that are load-bearing and none answerable from a file alone:
-
-1. **The per-frame update.** Which function advances a UI group's clock, in what
-   units, and **what does it do BETWEEN keyframes** — interpolate, or hold to the
-   next key? That single answer decides whether the port should lerp at all. It
-   is in the image. Find it.
-2. **What is submitted per frame during the splash** — the draw list frame by
-   frame, not one settled frame. If alpha changes it changes *somewhere*
-   observable: a vertex colour, a PS constant, a blend factor, a texture swap.
-   **Name which, and give the per-frame series.**
-3. **What Canary does to it** — present cadence, and any resolve, scale or gamma
-   between the guest's draw and the pixels a capture records. A capture is
-   evidence about *Canary's output*; the gap between that and the guest's intent
-   has bitten this corpus before (`kernel_display_gamma_type`).
-
-⚠️ **Deliver a SERIES, not a settled value.** Follow
-[`TEMPORAL-VERIFICATION.md`](TEMPORAL-VERIFICATION.md): film it, align by
-content, report ordering and counts and durations. The port needs the alpha
-*trajectory*; a single frame cannot carry one.
-[`../../tools/motion-census`](../../tools/motion-census) measures change and
-nothing else — use it on your own captures too, and note that three of the
-port's instruments passed a frozen screen because each measured throughput or a
-pose rather than change.
-
-## Previous focus, 2026-09-01 (still live, but AFTER the above)
-
-A human played the port on real hardware and reported that the splashes are
-**close but not right** — the fade/blur is more pronounced in the game — and that
-the `PRESS Ⓐ` plate arrives late. Read
-[`PLAYTEST-2026-09-01.md`](PLAYTEST-2026-09-01.md) first; it has the findings and
-why none of our checks caught them.
-
-Their verdict on how we have been working is the part that matters:
-
-> *"It seems the agents were essentially guessing and trying to copy what one
-> would see, but while they did get close it still is not quite right."*
-
-**So do not fit a curve to a screenshot. Find the mechanism.** For the splashes,
-in this order, and answer each with evidence rather than by inference:
-
-1. **Is there a post-process pass at all?** A blur, a bloom, a fade quad, a tone
-   curve, a resolve-and-resample. Yes/no, from GPU state.
-2. **If yes: what is it?** How many passes, which render targets, what blend
-   state, which shaders (you have their hashes in the draw log already).
-3. **Where do its parameters come from?** Immediate constants in the command
-   stream, PS/VS constant banks, a table in a pak, a computed ramp in code.
-4. **Only then, what curve** — and it should fall out of 3, not be fitted.
-
-Use **both** routes and say which produced each fact:
-
-* **Dynamic** — Canary. Per-draw capture, shader constants, render-target
-  bindings, blend state, and where those are not logged, **add the logging**:
-  `/canary` is yours read-write and the draw logger already exists. Guest memory
-  and CPU state are available too; the splash's driver is a `GamePart` and its
-  parameters are somewhere in it.
-* **Static** — the `.pe` image, `sylpheed.db`, the paks. The code that *sets up*
-  the pass is in the image, its constants may be immediates, and shader blobs
-  ship on the disc. A mechanism confirmed statically **generalises to every
-  screen**; one observed in a capture holds for that capture.
-
-A mechanism found this way is *decoded* and cannot be "close". A curve fitted by
-eye is neither.
-
-⚠️ Anything you conclude about *timing* here must obey
-[`TEMPORAL-VERIFICATION.md`](TEMPORAL-VERIFICATION.md). The plate-late finding is
-a timing question and the corpus has already lost four claims to the wall clock.
-
-### Second, and not optional: the complete input set
-
-The port had **no joypad binding for Ⓐ or Ⓑ** and nobody noticed for a whole
-milestone. The port has fixed its side. Yours is the other half:
-
-**Decode what the game actually reads.** Every button, both sticks, the triggers,
-START and BACK — per screen if it differs. The pad read path is in the image and
-`sub_821CC860`'s decoded arguments already include `PAD`. Deliver the *set*, and
-say for each entry whether it is decoded from the image, measured in a capture,
-or neither. Guessing which buttons exist by pressing them is how we got here.
-
 ## Your objective
 
 `docs/port/MISSION.md` — read it every iteration. It lists the open questions and
@@ -246,19 +19,6 @@ an export schema, stop and go back to the question you were answering.
 git -C /work fetch origin && git -C /work merge --no-edit origin/main
 ```
 
-🔴 **On your FIRST iteration after 2026-09-01, also merge the human's branch:**
-
-```bash
-git -C /work merge --no-edit origin/human/r1-register-reclassification
-```
-
-It carries the **R1 reclassification of `REFUTED.md`** (every entry now names its
-`⟨instrument⟩`; ten moved ❌ → 🟡), R1 as standing text in `PROTOCOL.md`, and
-`tools/stale-instrument`. It branches from `auto/frame-blend-draw-path`, so if
-you are on that line it is a fast-forward. **Two of the ten re-opened entries
-land on this iteration's focus** — do not start the splashes without reading
-them.
-
 You work on a topic branch, and you read the protocol, the mission and the
 shared tooling **from your own checkout** — so without this you are following
 whichever version of the rules existed when your branch started. That is not
@@ -280,24 +40,6 @@ If the merge conflicts, resolve it, say so in your reply, and carry on.
    side**. Fill it in as you go: you are the one who sees the real screens.
 8. `docs/agents/CONTAINER-NOTES.md` — the container's tooling, and the reference
    assets described below.
-9. `docs/agents/TEMPORAL-VERIFICATION.md` — **how to verify anything that
-   moves.** Set by the human. Every temporal claim must obey it.
-10. `docs/agents/PLAYTEST-2026-09-01.md` — what a human found playing the port.
-
-⚠️ **`REFUTED.md` was reclassified by the human on 2026-09-01 under rule R1.**
-Every entry now ends with its `⟨instrument⟩`, and **ten entries moved ❌ → 🟡**
-because the instrument that killed them was one of ours. A 🟡 is *not* dead — it
-is re-openable, and each says what would settle it. Read the file's own "How to
-read this file" section once. When you improve a renderer, a reader or the
-capture harness, run `tools/stale-instrument <that instrument>`: it lists exactly
-what that instrument killed, so those claims re-open instead of staying dead
-because nobody remembered which ones rested on it.
-
-🔴 Two of the ten bear directly on the current focus. *"The declared keyframe
-timeline reproduces the captured splash"* is now 🟡 `⟨our-reader⟩`, never
-re-derived under the record-layout fix. And the **`rest()` pair** is open in
-**both** directions — both legs run through our renderer — and the two splashes
-are the only screens that reach that fallback.
 
 ## Reference assets you may not know you have
 
@@ -390,23 +132,6 @@ renderer is a claim about our renderer.
 * Verify with an **artifact**, not "it compiles".
 * Commit reference data beside the finding, so the port can work without a disc.
 
-### Anything that moves
-
-**Read `docs/agents/TEMPORAL-VERIFICATION.md` and follow it.** The short form:
-
-* **Record a film, not a photograph.** One frame is a sample of a distribution
-  you have not characterised.
-* **Align by CONTENT, not by clock.** Search the lag that best matches and report
-  the lag *and* the agreement at it. The lag is a measurement, not an error.
-* **Prefer quantities that have no phase** — ordering, counts, durations, ratios,
-  shape. The two strongest timing results in this corpus are both of that kind.
-* **Anchor on an event**, then quote differences from it.
-* **State the expected number before reading the actual one.**
-* **Report achieved fps against requested fps.** A capture that asked 4 and got
-  1.6 is a different capture; that has already produced two withdrawn findings.
-* ⚠️ Canary presents at **~28.1 fps**, so a wall-clock duration off this emulator
-  is **~6 % long**. Quote unit counts first, then seconds, then the fps used.
-
 ## Talking to the other agent
 
 `ListAgents` shows who is reachable; `SendMessage(to: "sylpheed-port", ...)` reaches

docs/agents/port-loop.md

@@ -1,167 +1,5 @@
 You are the **Port**. Build the Godot menu shell, one milestone at a time.
 
-## 🔴🔴 SOLE FOCUS, 2026-09-02: **THE TITLE'S ANIMATION TIMING — F5 and F6, nothing else**
-
-**Work only these.** Not the repeat rate, not the audio mix, not P7 — they stay
-queued in
-[`../agents/PLAYTEST-2026-09-02-menus.md`](../agents/PLAYTEST-2026-09-02-menus.md).
-
-> *"Let's have the agents focus on this item and only this only."*
-
-**F6 — the title's sweeping white glow starts too early here.** A human watching
-the real game reports that the glow travelling along the blue PCB-like lines
-(**`ptloop01` / `ptloop02`**) **only begins when the plate appears**; the port
-starts it before. **This is the Decoder's to establish and yours to implement** —
-do not choose a start time. What you *can* do now without an answer: determine
-exactly **what your renderer currently uses** to start that sweep, so that when
-the answer lands the change is one line and not an investigation.
-
-**F5 — does Ⓐ snap or accelerate the title?** The Decoder is measuring it. Until
-they answer, **do not implement Ⓐ#2** — a snap and a speed-up are different
-behaviours and picking one is exactly the guessing that has cost this project.
-
-### And split it before you start
-
-**Read the new "Work in units a human can check in a minute" section of
-[`PROTOCOL.md`](PROTOCOL.md).** The human's diagnosis is that whole missions have
-been too big to hold — the splash sat through a milestone, then took a day once
-scoped to *does it animate?*. Break the work down, write the question and what
-the human should look at **before** working, do one unit, hand it over, and stop.
-Do not stack a second change on an unverified first.
-
-## ✅ THE LOGO SPLASHES ARE DONE — signed off by the human, 2026-09-02
-
-> *"Looks good! Cannot notice any obvious difference from the actual game.
-> Mark logos as done."*
-
-**The sole-focus order is lifted. Return to your milestones.** The fix was
-`pose_at` assigning the settle instant instead of clamping to it — and that same
-line manufactured the false green, because the capture harness was photographing
-t ≈ 2 units and it *looked* settled only because everything did.
-
-📌 **Keep the lesson, it outlives the bug.** Three instruments passed a frozen
-screen: a frozen sweep drives the clock by hand, a settled comparison is
-*defined* to pass on a frozen screen, and an achieved-fps counter counts frames
-drawn rather than frames different. Ask of any new check: **what would this still
-report if the feature were entirely absent?** `tools/motion-census` exists for
-exactly that question; keep it in `check-all`.
-
-## ✅ P5's GATE IS MET — the human walked it, 2026-09-02
-
-> *"Menu walk and navigation is fine. Video skips too. Extras open. New Game
-> shows new game intro video."*
-
-`PORT-MISSION.md` is updated. The NEW GAME gap is accepted as-is — they know the
-difficulty select comes first in the real game and that the port announces it.
-
-### 🔴 Four findings from the same session — read [`../agents/PLAYTEST-2026-09-02-menus.md`](../agents/PLAYTEST-2026-09-02-menus.md)
-
-| | | yours to do |
-|---|---|---|
-| **F1** | **The menu REPEATS on a held direction. Ours does not.** One step per deflection was authored as the safe choice; the human has now watched the real game and it repeats. | **Implement the mechanism. Take the RATE from the Decoder — do NOT ship a placeholder interval.** An invented rate here is indistinguishable from a measured one later, and this is the exact field where that already cost us. |
-| **F2** | **SFX too loud, and there is no mix at all.** Measured: `confirm` −17.7 dB mean / **−0.0 dB peak**, 3 dB hotter than the music; no gain value exists anywhere in `export/` or `authored/`. | Add gains **at playback, as data** — a bus per kind. ⚠️ **Do NOT normalise in the exporter**: re-levelling destroys the relationship between clips and a modder cannot undo it. The Decoder is checking whether the mix is on the disc. |
-| **F3** | **Something is missing on the title screen** — a track or a sting. The export has one music file and the port plays nothing on the title. | Wait for the Decoder; nothing to author yet. |
-| **F4** | **Ⓐ skips FORWARD through the boot, and we implement two of three presses.** Ⓐ#1 skips the video ✅, **Ⓐ#2 reveals the plate immediately ❌ missing**, Ⓐ#3 activates it ✅. | Make Ⓐ during the title build-in jump to the plate — but **do not choose what "jump" means.** 🔴 It is a **test of `clock: "shared"`**, which is authored and, in your own words, *"not confirmed to better than ~20 %"*. If Ⓐ advances the shared clock the artwork **snaps**; if it only forces the plate visible the artwork **keeps animating**. Those look different on an early press, so the oracle can settle it. **Answer it before building on `shared`.** (Correction: an earlier draft of this brief said "both clocks" — there is only ONE, and hunting for a second would waste an iteration.) |
-
-**H3, the plate delay, is ACCEPTED** — *"feels the same… sufficient"*. Stop
-working on it. Leave the row unattributed rather than closing it green.
-
-## Previous sole focus, 2026-09-02 — RESOLVED, kept for the method
-
-> *"The port does no blur animation at all. The logos just switch."*
-
-Measured from a real boot, not paraphrased: **the splash moves 1.30 s of 7.95 s
-(16.4 %)**, the publisher logo is **frozen for 3.20 s**, the developer logo for
-2.40 s, and the whole 7.95 s takes **26 distinct luma states**. A 45-unit
-build-in cannot be drawn in 26 states.
-
-🔴 **Your three instruments all passed this, and the reason is the point:**
-
-* the **frozen sweep** drives the clock by hand — it proves the renderer can
-  draw pose *N*, never that the poses are drawn in sequence while running;
-* the **settled comparison** scored 0.01 % — a screen frozen 84 % of the time
-  matches a settled reference *perfectly*, because that is what frozen means;
-* the **achieved-fps counter** counts frames DRAWN — drawing the same pixels
-  25×/s scores exactly like animating.
-
-**Every one measured throughput or a pose. None measured CHANGE.** Same shape as
-`InputEventAction` bypassing the input map: the instrument sat below the thing
-that was broken.
-
-**Use [`tools/motion-census`](../../tools/motion-census)** — it measures change
-and nothing else, and its `--selftest` proves it separates a fade from a switch
-from a frozen film. Order of work:
-
-1. **Reproduce first**, with `--film` + `motion-census`, and quote the numbers.
-   If you do not get ~16 %, that disagreement is the finding — say so.
-2. **Find why the poses do not advance.** Unranked, none established:
-   interpolation returning one pose across a range of *t*; `rest()`/plateau
-   snapping to an endpoint; the group clock not integrating; nearest-keyframe
-   instead of lerp; advancing by keyframe *index* rather than by time.
-3. **Every fix is gated by a FILM, never a still.** A change that improves a
-   settled frame and leaves the film at 16 % has not fixed this.
-4. Put `motion-census` in `check-all` so the regression fails a check instead of
-   waiting for a human.
-
-⚠️ **And record the refutation against yourself.** `BLOCKED.md` H2 reads ✅
-ANSWERED on the strength of the frozen sweep. The *mechanism* half stands — the
-blur is a baked companion texture, decoded and correct. The *behaviour* half does
-not: you draw those quads and do not animate them, so "the companions are drawn"
-was true and did not mean what the row used it to mean.
-
-## Previous focus, 2026-09-01 (still live, but AFTER the above)
-
-A human played this port on a real controller for the first time. Read
-[`../agents/PLAYTEST-2026-09-01.md`](../agents/PLAYTEST-2026-09-01.md) **before
-anything else** — it has all four findings and, more importantly, why none of
-your checks caught two of them.
-
-**Two were fixed for you by the human. Do not re-do them; do read them.**
-
-1. **Ⓐ and Ⓑ were never bound to the pad.** Godot 4.7.2 binds no joypad button to
-   `ui_accept` or `ui_cancel`, while it binds the d-pad *and* the left stick to
-   `ui_up`/`ui_down`. Ⓐ was dead on real hardware for the whole of P5 while your
-   unattended walk passed every iteration. Fixed in `port/scripts/gamepad.gd`;
-   asserted by `tools/port/verify-input`, now in `check-all`.
-2. **The left stick fired once per jitter.** An axis is not an edge. Latched to
-   one step per deflection, with hysteresis.
-
-> ### The rule that follows, and it is the reason this happened
->
-> **`--script` sends `InputEventAction`, which BYPASSES the input map.** Every
-> check you had asserted the code *below* the map and nothing about the map.
-> Synthetic input is not a test of input.
->
-> **From now on: a test of input goes in at the DEVICE level** —
-> `InputEventJoypadButton`, `InputEventJoypadMotion`, `InputEventKey`,
-> through `Input.parse_input_event` — or it asserts the input map directly.
-> `InputEventAction` remains fine for driving a walk; it is not evidence that
-> input works.
-
-**Two are open and are your focus:**
-
-3. **The `PRESS Ⓐ` plate arrives late.** You raise it at `t=236`, derived as
-   `238 − 118 = 120 units = 2.000 s`. A human watching both says late. The
-   unit→seconds conversion is load-bearing and is exactly what the wall clock
-   cannot be trusted for. **This is an RE question if the cause is the unit; it
-   is yours if the cause is the clock origin or `rest.t`.** Establish which
-   half it is before asking, and say how you established it.
-4. **The splash fade/blur is not the game's** — the game's is more pronounced.
-   You apply **no blur at all**. Whether the game runs a post-process pass is an
-   oracle question and it is with the Decoder. **Do not fit a curve to a
-   screenshot while waiting** — that is exactly what produced "close but not
-   right".
-
-⚠️ Anything you conclude about timing must obey
-[`../agents/TEMPORAL-VERIFICATION.md`](../agents/TEMPORAL-VERIFICATION.md).
-Record a film and align by content; never compare at an absolute time.
-
-⚠️ **`REFUTED.md` was reclassified by the human on 2026-09-01 (rule R1).** Ten
-entries moved ❌ → 🟡 because our own renderer or reader killed them. Two bear on
-your focus: *"the declared keyframe timeline reproduces the captured splash"* is
-now 🟡 `⟨our-reader⟩`, and the **`rest()` pair is open in both directions** — and
-the two splashes are the **only** screens reaching that fallback.
-
 ## Your objective
 
 `docs/port/PORT-MISSION.md` — read it every iteration. Milestones P0…P7, each
@@ -177,19 +15,6 @@ guess of yours is indistinguishable from a fact and will be believed later.
 git -C /work fetch origin && git -C /work merge --no-edit origin/main
 ```
 
-🔴 **On your FIRST iteration after 2026-09-01, also merge the human's branch:**
-
-```bash
-git -C /work merge --no-edit origin/human/r1-retro-tick
-```
-
-It carries **the two input fixes made for you** (`port/scripts/gamepad.gd`,
-`tools/port/verify-input` + its control, wired into `check-all`), the new
-`BLOCKED.md` rows **H1–H3**, and the retro tick. It branches from
-`auto/port-p6-audio`, so on that line it is a fast-forward. **Merge it before
-touching input**, or you will re-derive a fix that is already written and
-asserted.
-
 You work on a topic branch, and you read the protocol, the mission and the
 shared tooling **from your own checkout** — so without this you are following
 whichever version of the rules existed when your branch started. That is not
@@ -254,14 +79,6 @@ That is the easiest thing here to get subtly wrong.
   disagree, say which is wrong rather than tuning until they match.
 * Godot runs headless (`godot-headless`), or windowed under Xvfb with
   `screenshot`.
-* **Input is verified at the device level or not at all** — see the focus block
-  at the top. `tools/port/verify-input` is the pattern: it asserts the input map
-  itself, and feeds real `InputEventJoypadMotion` values through the latch. Run
-  it and its `--control` in `check-all`.
-* **Anything that moves** follows `../agents/TEMPORAL-VERIFICATION.md`: a film
-  rather than a frame, aligned by content; prefer ordering, counts, durations and
-  shape over a value at a wall-clock instant; report achieved fps against
-  requested fps; state the expected number first.
 * Audio: `docs/port/AUDIO-VERIFICATION.md` — no sound card is needed to answer
   any of it. Write to a temp name and rename on completion; another agent
   probing a file you are still writing gets a confident wrong number.

docs/game/navigation.md

@@ -7,8 +7,9 @@ and wants to reach a mission — or who needs to script that journey.
 Internal names (`ptbtn03`, `GP_LOAD`, build numbers) appear only as footnotes,
 because they are how *we* find things, not what the game shows anyone.
 
-**Status:** skeleton. Most of it is ❔ and is *meant* to be — this page exists to
-be filled in by playing, not to look finished.
+**Status:** filling in. §1–§4 now carry what the committed oracle frames actually
+show; what is still ❔ is what no capture answers. This page exists to be filled
+in by playing, not to look finished.
 
 > ## ⚠️ Fill this in from the real game
 >
@@ -28,10 +29,20 @@ Confidence: ✅ seen in a capture · 🟡 inferred · ❔ unknown.
 
 | # | What you see | What you do | What happens |
 |---|---|---|---|
-| 1 | Publisher and developer logos on black | nothing | plays through 🟡 |
-| 2 | The opening cinematic | ❔ can it be skipped, and with which button? | ends into the title 🟡 |
-| 3 | **Title screen** — the wordmark animates in, then a prompt | press **Ⓐ** | goes to the main menu ✅ |
-| 4 | **Main menu** | — | see §2 |
+| 1 | **SQUARE ENIX** in white on black, the two dots in red, `™` after it ✅ | nothing | fades on to the next logo |
+| 2 | **GAME ARTS**, **SETA** and **studio anima** stacked on black ✅ | nothing | fades on into the cinematic |
+| 3 | The opening cinematic | **Ⓐ** skips it ✅ | ends into the title |
+| 4 | **Title screen** — the wordmark appears **first, with no prompt**; `PRESS Ⓐ BUTTON` fades in **2.13 s** later, above the 2006/2007 Square Enix copyright line, and then pulses about every 2.2 s ✅ | press **Ⓐ** | goes to the main menu ✅ |
+| 5 | **Main menu** | — | see §2 |
+
+Both logo screens are **still pictures the game draws**, not video — neither is a
+`.wmv` on the disc. Captures:
+[publisher](../re/captures/title-builds/live-splash-publisher.png) ·
+[developer](../re/captures/title-builds/live-splash-developer.png) ·
+[title](../re/captures/title-builds/live-title-press-a.png).
+
+⚠️ **One Ⓐ skips the cinematic**, and it is worth a lot of time: the title
+arrived at **57 s** with the skip against **193 s** without it ✅.
 
 ⚠️ **The title screen has two states that look identical.** The one that ends
 the boot accepts Ⓐ. The one the attract loop returns to, after the game has sat
@@ -43,6 +54,21 @@ boot.
 ⚠️ **The title is not input-ready for about ten seconds** after it appears ✅.
 And even then Ⓐ registers roughly half the time, with nothing yet found that
 predicts which ✅ — budget retries.
+🔴 **Refutation attempt, 2026-08-29 — both halves of that came out wrong on the
+runs I could test.** Two boots, Ⓐ pressed **7.29 s** and **7.28 s** after the
+title art settled (5.15 s and 5.15 s after the prompt appeared): **accepted both
+times, first press, no retry**, and each went straight on to the main menu. Ⓑ on
+the menu was then also accepted first press, both runs.
+⚠️ Reach: **n = 2**, so "half the time" is only made unlikely (2/2 has p ≈ 0.25
+under it), not excluded — but *"not input-ready for about ten seconds"* is
+contradicted outright, because 7.3 s worked twice. Keep the retry budget; drop
+the ten-second wait. Evidence:
+[run 1](../re/data/plate-timing-run1.tsv) · [run 2](../re/data/plate-timing-run2.tsv) ·
+[`title-plate-delay-measured.md`](../re/title-plate-delay-measured.md).
+
+⚠️ **The prompt takes 2.13 s to arrive, measured twice (2.138 s / 2.132 s).**
+Timed from the moment the wordmark stops animating, not from the moment it first
+appears — the build-in itself varies by half a second between runs.
 
 ---
 
@@ -51,18 +77,57 @@ predicts which ✅ — budget retries.
 Five options in a vertical stack, roughly centred, with a highlighted state on
 the focused one.
 
+> ✅ **The focused option carries a small ring to the left of its label, and the
+> ring turns — continuously, about once every 2.2 s.** It has a bright head, so
+> you can see it go round. It is the **only** thing moving on this screen once it
+> has settled: the labels, the bracket and the footer are all completely still
+> (temporal std exactly 0.000 over 20 s). Ⓑ
+> [five frames, 4 s apart](../re/captures/focus-ring/ring-single-frames-4s-apart.png) ·
+> [the measurement](../re/focus-ring-spin-measured.md)
+
 | position | label | what it opens |
 |---|---|---|
-| 1 | ❔ | ❔ |
-| 2 | ❔ | ❔ |
-| 3 | ❔ | ❔ |
-| 4 | ❔ | ❔ |
-| 5 | ❔ | ❔ |
+| 1 | **NEW GAME** | a **DIFFICULTY** prompt, then **SELECT DATA** ✅ |
+| 2 | **LOAD GAME** | the save-slot list ✅ |
+| 3 | **TUTORIAL** | the lesson list ✅ |
+| 4 | **OPTIONS** | the settings menu ✅ |
+| 5 | **EXTRAS** | a three-item submenu ✅ |
 
-**To fill in, by looking:** read the five labels off the screen and say what each
-one leads to. ❔ Which item is focused when the menu opens · ❔ does the cursor
-wrap from the last item back to the first · ❔ does left/right do anything ·
-❔ what B does here — back to the title, or nothing.
+Read off [`live-main-menu.png`](../re/captures/title-builds/live-main-menu.png);
+destinations off
+[`q4-destinations.png`](../re/captures/menu-nav/q4-destinations.png) and
+[`newgame-difficulty.png`](../re/captures/newgame-path/newgame-difficulty.png).
+
+The screen is the title art gone dim, with the wordmark ghosted behind the list
+and a bracket of glowing rule-lines drawn around it. The focused item is bright
+white with a **spinning ring** to its left; the others are dim blue. Every item
+carries a small dot-in-circle at the left end of its underline — that is on all
+five all the time and is *not* the cursor.
+
+**Moving around ✅**
+
+| you press | what happens |
+|---|---|
+| ⬆ / ⬇ | one item, and it **wraps** at both ends |
+| ⬅ / ➡ | nothing |
+| Ⓐ | opens the focused item |
+| Ⓑ | 🟡 back to the title — see the warning below |
+
+❔ **Which item is focused when the menu opens is not fixed.** Four boots of the
+same harness opened on `TUTORIAL`, `TUTORIAL`, `NEW GAME`, `NEW GAME`. Do not
+assume the top item, and do not assume the middle one either.
+
+> ⚠️ **The main menu is the one screen whose footer does not offer Ⓑ.** It reads
+> `⊙ : Select   Ⓐ : OK` — every submenu adds `Ⓑ : Back`. Measured: **zero**
+> red-Ⓑ glyph pixels anywhere in the frame, on two captures, with the same
+> detector finding the glyph on `EXTRAS` and `DIFFICULTY` ✅.
+> ✅ **But Ⓑ does leave it, and the objection that stood here is refuted
+> (2026-08-29).** This page used to say the title "returns on its own after
+> ~8–10 s idle", so an observer could not tell Ⓑ from the timer. That timer
+> belongs to the **title**, not to this screen: the main menu was held untouched
+> for **≥ 60 s** and never moved. Ⓑ is delivered and is the only input in ≥ 100 s
+> before the return, so the ordering is measured — the *latency* is not
+> ([the measurement](../re/menu-idle-and-b-2026-08-29.md)).
 
 *Internals: `GP_TITLE.pak` build 5; buttons `ptbtn01`–`ptbtn05` top to bottom.*
 
@@ -73,26 +138,82 @@ wrap from the last item back to the first · ❔ does left/right do anything ·
 One section each, in the shape of §2: what is on screen, what the cursor does,
 what each choice leads to, and what a wrong choice shows you.
 
-### Continue / Load ❔
-❔ How saves are listed · ❔ what an empty slot looks like · ❔ the confirmation
-prompt and where the cursor starts.
+### New game ✅
+Ⓐ on `NEW GAME` does **not** start a mission. It opens **DIFFICULTY** —
+`EASY` / `NORMAL` / `HARD` / `BACK`, opening focused on **NORMAL** ✅ — and Ⓐ
+there opens **SELECT DATA**, a save-slot picker headed
+`Current Storage: Dummy HDD` that asks you to choose a file for the auto-save.
+Pick one and a movie plays ✅.
+[DIFFICULTY](../re/captures/difficulty-screen.png)
+
+### Load game ✅
+A vertical list of numbered slots, **8 rows visible**, scrolling as a carousel —
+one capture shows the order `19, 20, 01, 02, 03, 04` with `01` focused, so the
+list runs past the end and back round to the start ✅. Each row shows
+`Difficulty`, `Flight Time` and `Clear Ratio`; a **Details** panel to the right
+gives `STAGE`, `Game Status`, `Points` and `Times Cleared`, and an empty slot
+leaves every one of those blank ✅. `Current Storage: Dummy HDD` sits along the
+top.
+
+Its footer offers more than the other menus:
+`⊙ : Select   Ⓐ : OK   Ⓑ : Back   Ⓧ : Delete   Ⓨ : Select Storage` ✅.
+[capture](../re/captures/menu-nav/q4-destinations.png) (left panel)
+
+❔ Still open: the overwrite / delete confirmation, and where its cursor starts.
 
 Known: `title → LOAD GAME → slot 01 → YES → READY ROOM → TAKE OFF` reaches
 flight ✅.
 
-### Options ❔
-❔ Which settings exist, what each ranges over, how a change is applied and
-whether it needs confirming.
+### Tutorial ✅
+A list of lessons in two headed groups, with a one-line description shown on the
+left for whichever is focused ✅ — e.g. `BASIC CONTROLS` reads
+*"Learn how to move and attack"*. Opens focused on the first entry.
 
-### Extras ❔
-❔ What is in it — a movie theatre, a gallery, records? ❔ what is locked at the
-start and what unlocks it.
+| group | lessons |
+|---|---|
+| **Level 1** | `BASIC CONTROLS`, `HEADS-UP DISPLAY`, `RADAR` |
+| **Level 2** | `SUPPLY AND SPECIAL MOVES`, `RADIO ORDERS`, `ADVANCED CONTROLS` |
+| — | `BACK` |
 
-### Mission select ❔
-⚠️ **Stage select would not move**: sixteen d-pad presses never left Stage 01 ✅.
-Whether that is because only one stage was unlocked, or because the list is
-driven some other way, is unknown — worth settling early, since a scripted run
-has to get past it.
+[capture](../re/captures/menu-nav/q4-destinations.png) (middle panel)
+
+### Options ✅ (one level in)
+`GAME SETTINGS` · `CONTROL SETTINGS` · `SOUND SETTINGS` · `SCREEN SETTINGS` ·
+`BACK`, opening focused on the first ✅.
+[capture](../re/captures/menu-nav/q4-destinations.png) (right panel)
+
+❔ Still open: what is inside each of the four, what each setting ranges over, and
+whether a change needs confirming.
+
+### Extras ✅
+Three items: `MISSION SELECT` · `MOVIE THEATER` · `BACK`, opening focused on
+`MISSION SELECT` ✅. The cursor wraps here too — it is a menu rule, not a
+per-screen one ✅.
+[capture](../re/captures/title-builds/live-extras.png)
+
+❔ `MOVIE THEATER` has never been opened.
+
+### Mission select ✅ — and the "stuck cursor" is explained
+The stage list on the left (**8 rows visible of 16**, with a scrollbar), a detail
+panel showing the stage's name, a picture, `High Score` and `Best Time`, and a
+**Wide Area Space Map** on the right with the named systems on it. The chosen
+difficulty is printed top-right. Footer:
+`⊙ : Select   Ⓐ : OK   Ⓑ : Back   Ⓨ : Difficulty` ✅.
+
+⚠️ **"Stage select would not move" — sixteen d-pad presses never left Stage 01 —
+is now explained: the other fifteen stages were LOCKED** ✅. A locked row is
+drawn *dimmer than an unfocused one*: measured, the labels sit at three distinct
+brightnesses — focused **254**, unlocked **183**, locked **104** — and on a save
+with the story unlocked the same rows read 183, with the cursor able to reach
+**Stage16** at the bottom of the scrolled list.
+[the measurement](../re/menu-navigation-semantics.md#-mission-select-the-cursor-was-stuck-because-the-stages-were-locked) ·
+[locked](../re/captures/mission-select-stage01-only.png) ·
+[unlocked](../re/captures/mission-select-all-story-unlocked.png) ·
+[at Stage16](../re/captures/mission-select-ends-at-stage16.png)
+
+So: if you are scripting a run, **check what the save has unlocked** before
+concluding the list is broken. ❔ Whether the list wraps past Stage16, and
+whether a locked row is skipped or simply unreachable, is not settled.
 
 ### Briefing and Ready Room ❔
 ❔ What you read, what you choose, and what finally launches the mission.

docs/port/HANDOFF.md

@@ -23,12 +23,285 @@ There is no fourth kind. If a row says *measured* or *undecodable*, the port is
 human can see it is a human decision, so that when it is later decoded the
 authored version can be deleted.
 
+## 🔴 2026-08-29 — A KEYFRAME'S TIME COMES BEFORE ITS POSE. Change `pose_at`.
+
+**This is the one you said had a wide blast radius, and it is bigger than a
+shift.** Read
+[`ui-keyframe-record-layout.md`](../re/ui-keyframe-record-layout.md) before
+touching `screen_view.gd`.
+
+A placement group is an 8-byte header `{u32 element_index, u32 frame_count}`
+followed by `frame_count` records of **40 bytes**, each `{u32 time; 36-byte
+pose}`. The time word **precedes** the pose it belongs to. Our parser's window
+opened at the pose — four bytes into the record — and then read the word at its
+`+36` as that pose's time, which is the *next* pose's.
+
+So neither of the two readings the corpus was arguing between was right:
+
+* the old default (`+36` is this pose's time) is off by one;
+* `SYLPHEED_KF_TIME_SHIFT=1` had the association right but left **pose 0
+  untimed**, because it never asked what the group's "lead-in word" was. It is
+  pose 0's time.
+
+`SYLPHEED_KF_TIME_SHIFT` is gone. `SYLPHEED_KF_TIME_LEGACY=1` restores the old
+reading if you want to A/B.
+
+**Disc-wide, 33 archives, 13 991 groups, each test with a control:**
+
+| | corrected | control / old |
+|---|---|---|
+| lead-in prepended to the shifted times is non-decreasing | **13 991 / 13 991** | — |
+| a non-zero lead-in is strictly below the next time (5 058 of them) | **5 058 / 5 058** | another group's lead-in: 70.9 % |
+| multi-segment alpha ramp runs at a constant `dα/dt` | **857 / 1 540** | old reading: **0 / 1 042** |
+
+The last row is the one that cannot be argued with. Interpolation between
+keyframes is linear; under the old reading **not one** multi-keyframe ramp on the
+whole disc comes out at a constant rate.
+
+### What it changes for you, by the list you sent me
+
+* **`pose_at` (line ~184).** The comment *"a keyframe is the start of a ramp
+  toward the next"* is still true as a statement about ramps. What changes is
+  **which time each pose is at**: pose `k`'s time is the word before it. Every
+  screen's build-in timing moves.
+* **The final pose now has a time.** Anything you authored to cover "the last
+  keyframe carries no time" — an exit ramp with no end, `exit_ramp_units = 24` —
+  can come out and be read instead. `exit_ramp_units` is now a decodable number,
+  not an authored one.
+* **`settle_units` / `settle_time`.** `rest.t` still is not when a screen settles
+  (`5b0a6e6` stands), but its *value* moves. Re-derive it.
+* **`spin_period_units`.** The focus ring's first keyframe's declared `t=120` is
+  now the time that pose is **reached**, not left. Check which end of the ring's
+  group you were reading.
+* **The `PRESS Ⓐ` plate.** `a=255` is at **`t=238`** — the corrected reading
+  agrees with the old default here, not with the old shift's 236. Your `5b0a6e6`
+  note is unaffected.
+* **`ramp: "linear"` in `authored/timing.json` — KEEP IT.** Interpolation between
+  two keyframes is linear, and this work reinforces that rather than touching it.
+  ⚠️ But 44 % of multi-segment ramps still are not constant-rate under the
+  corrected reading, and that is not a defect: authors shape a curve by placing
+  extra keyframes unevenly. Your `_lerp_pose` is right; do not add an easing
+  function.
+
+### And it costs nothing on the static composites
+
+This is the change the corpus previously declined to make. `SYLPHEED_KF_TIME_SHIFT=1`
+moved `GP_TITLE` build 7 by 13.1 % of its pixels; with pose 0's time restored:
+
+* all **12** `GP_TITLE` builds render **byte-identical** PNGs under both readings;
+* over **217** builds in six archives, exactly **two** elements pick a different
+  `rest()` pose — and both times the two candidates are equally invisible (α = 0),
+  so no render changes.
+
+So `screen render` is still the reference you diff against, unchanged. **If your
+static screens move, that is your bug, not this change.**
+
+## ✅ 2026-08-29 — builds 0/1 and 10/11 are the LOADING SCREEN (your ask #2)
+
+**Decoded** — the authors' own element names, straight out of the declaration
+table. Every element of all four bundles is prefixed `pgloading_`: the 7-element
+pair (builds 0/1) is the plain plate, the 10-element pair (builds 10/11) adds
+`pgloading_eff00.prm`, `pgloading_loop5.rat` and `pgloading_baseeff.t32` over a
+circuit-line background. `DELTASABER / SYLPHEED A.I.` is the caption art on
+`pgloading_str.t32`, not the screen's identity.
+
+⚠️ **Do not name them `LOADING` / `LOADING2` in an asset path.** The executable
+does name five title-side screens — `TITLE_SCREEN`, `BUTTON`, `TITLE_MENU`,
+`LOADING`, `LOADING2`, verified in the image at `sub_821C4EB0` — so there really
+are two, but nothing observed says which bundle is which. 🟡 undecided.
+
+🟡 **Which member of each pair is English: the first half of the data segment.**
+All eight pairs put exactly one member in each half of `GP_TITLE.p00`, and all
+three pairs whose language is visible (4/7, 5/8, 6/9) put English in the first.
+So builds **0, 2, 4, 5, 6, 10 are English**; 1, 3, 7, 8, 9, 11 Japanese. 🟡 not
+✅ — the three pairs this is *used* for are exactly the three no capture can
+check, and nothing in the bundle bytes differs between those twins at all.
+[`ui-title-build-map.md`](../re/ui-title-build-map.md)
+
+## ✅ 2026-08-29 — the disc is back in the decoder container; the red banner that stood here is withdrawn
+
+**This supersedes the "the decoder container has no disc" banner** written at
+commit `b9aca6a` (10:42 UTC). That diagnosis was true for the container it was
+written in, and a human has since fixed it: this container's PID 1 started at
+**11:07:38 UTC**, 25 minutes later, and it has the disc mounted.
+
+Verified, not assumed:
+
+| | |
+|---|---|
+| `/disc` | a real read-only bind mount on device 2050 (`/` is device 92), **6.2 GB**, 74 entries under `dat/`, `default.xex` present |
+| `/iso/game.iso` | present, 7 835 492 352 B |
+| end-to-end | `sylpheed-cli screen list $SYLPHEED_DISC/dat/GP_TITLE.pak` returns **12 screen builds**, matching [`ui-title-build-map.md`](../re/ui-title-build-map.md) |
+
+⚠️ **`sylph-doctor` still reports "no ISO" and "no extracted disc", and it is
+wrong.** It looks only under `/work` (`find /work -maxdepth 2 -iname '*.iso'`
+and `-d /work/sylph_extract/dat`); it never consults `$SYLPHEED_DISC`. Do not
+take its two ✖/! lines as evidence about the disc — the disc is at `/disc`
+and works. Same trap for `find / -xdev`, which by definition cannot cross into
+a bind mount on another device, and which is what the withdrawn banner ran.
+
+**What that means for you:** the decoder can boot the oracle, run
+`sylpheed-cli` against a pak, run the disc-gated tests and read the executable
+again. New measurements are available; ask for them.
+
+## ✅ 2026-08-29 — the "third sub-wave" on a music bank was OUR reader, and it is fixed
+
+**You were right to refuse to choose which one to drop.** `BGM_103.slb` really
+does return three from `sound_bank_riffs` — and the third is the **bank header**,
+not a stem. Our own `to_xma_riffs` was emitting it.
+
+The cause is arithmetic, not a judgement call: the hybrid branch derives a
+leading packet stream's start as `first_riff % 2048`, which is correct only when
+the bank header is smaller than one XMA1 packet. A music bank's header is exactly
+**five** packets (10 240 B), so the modulus returned 0 and the whole header came
+back as sub-wave 0. Voice banks are unaffected — their headers really are shorter
+than a packet, which is why the branch looked right for two months.
+
+Checked before believing it, three ways:
+
+* **disc-wide** — of `sound.pak`'s 9 519 entries, **28** carry a header at offset
+  0 (ids 1001–1023, 1101–1105 — every music bank), and on **28/28** the header's
+  own declared length ends *exactly* at the first `RIFF`. **Zero** have a gap, so
+  a header and a leading packet stream never coexist on this disc, and **zero**
+  false positives among the other 9 491;
+* **decode control, same chain, same bank** — the emitted region gives **0.009 s**
+  of PCM; the same bank's real wave 0 gives **87.744 s** against a declared
+  87.75. It is also 99.1 % zero bytes;
+* **the oracle already said two** — the XMA probe at the main menu saw exactly
+  two streams, of 3 876 864 and 3 930 112 B, which are `BGM_103`'s two declared
+  wave sizes.
+
+**What you should do:** bump your `sylpheed-formats` pin to the tag below and
+delete the manifest warning's special case — `sound_bank_riffs` now returns
+**2** for every music bank, and your "count != 2" warning becomes a real
+invariant rather than a symptom. ⚠️ Do **not** apply a "drop the smallest
+sub-wave" rule; on a voice bank the leading region is genuine audio and dropping
+it is the `VOICE_D_453` bug all over again.
+
+[`structures/slb-bank-header-not-a-wave.md`](../re/structures/slb-bank-header-not-a-wave.md)
+
+## ✅ 2026-08-29 — the interactive title is reachable again, and the "emulator-blocked" banner in MISSION is withdrawn
+
+Two consecutive boots reached the interactive title **with no pad input at all**,
+passed through the attract loop in ~3.5 minutes, took Ⓐ to the main menu and Ⓑ
+back. The standing negative ("three runs, two locales, two launch paths, ~35
+minutes of emulator time, no interactive title") does not hold in this container.
+
+❔ **Why it changed is not established.** The container came up with **no Xenia
+storage root at all** — no profile, no `xconfig.settings`, no shader cache — so
+run 1 created one with canary's `--create_profile_if_none`. That is a correlation
+across two runs, not a cause, and it is written down so the next session can test
+it rather than re-derive the reachability.
+[`capture-harness-status.md`](../re/capture-harness-status.md)
+
+**What it means for you:** the oracle is live. Anything you need timed or
+observed on the five screens can now be asked for and taken, including the two
+items MISSION parks as emulator-blocked.
+
+## ✅ 2026-08-29 — three answers from one oracle session (the port's asks 1, 2 and 3)
+
+* **1 — the focus ring SPINS CONTINUOUSLY. Period 2.18 s wall-clock; author it
+  as 120 units = 60 frames = 2.00 s at 30 Hz.** It does not ramp once and stop.
+  Measured with no angle estimated anywhere — the angular estimator written for
+  this **failed its own control** (a synthetic 30° came back as 0°) and was not
+  used. What settles it instead: total annulus brightness is conserved to
+  **0.4 %** while individual angular bins swing by **24** — brightness moving
+  *around* the ring, which excludes a pulse — and the profile's autocorrelation
+  has **eight evenly spaced peaks, mean 2.177 s**, over nine revolutions.
+  ⚠️ Do not read the committed 20 s mean image as a frame: the spin averages to
+  a uniform circle, which is why it looks headless. Five single frames 4 s apart
+  show the head at five different angles.
+  [`focus-ring-spin-measured.md`](../re/focus-ring-spin-measured.md) ·
+  [frames](../re/captures/focus-ring/ring-single-frames-4s-apart.png)
+
+* ✅ **And the ring is the ONLY thing that moves on the settled main menu.**
+  Temporal std over 20 s untouched is **exactly 0.000** on every unfocused
+  button, on the labels and on the `ptmsg` footer. Static menu + spinning ring
+  draws everything that moves.
+
+* **3 — the idle timer that made your Ⓑ rule unprovable is REFUTED on the main
+  menu.** Held untouched, the menu stayed put for **≥ 60 s** (49 samples, menu
+  correlation never leaving 0.9245–0.9249), against the "~8–10 s idle returns to
+  the title" this page carried. ✅ That timer is real but belongs to the
+  **title**, not the menu — the corpus had it attached to the wrong screen.
+  🟡 Ⓑ itself: delivered (Canary logs `vk=5801`), and in both runs the only input
+  in ≥ 100 s, followed by the title. **Ordering measured, timing not** — keep
+  Ⓑ→title, now better supported than authored.
+  [`menu-idle-and-b-2026-08-29.md`](../re/menu-idle-and-b-2026-08-29.md)
+
+* **Your new #1 — the boot title shows build 4 FIRST, and the plate arrives
+  after.** It is your third option, not the first two. Green-Ⓐ glyph count on the
+  boot title went **154 → 781**, and 154 is the same reading the committed
+  `live-title-build4-no-plate.png` gives (159) while plate titles give
+  753/977/1493.
+  ✅ **So `ScreenView` does have to draw two builds at once, and your `--boot`
+  end state is NOT plate-free** — that is the structural answer you said this
+  question decides, and it is unchanged.
+  🔴 **But my INSTRUCTION was wrong and you refuted it — do not author a delay at
+  all.** I said "when build 4 has settled, wait 2.13 s, composite build 2". Build
+  2 has a group of its own, and starting that group at settle puts the plate at
+  settle + 2.13 + 3.97 s. **Correct instruction: run build 4 and build 2 on ONE
+  clock, started together, and play both groups from their own keyframes.** The
+  plate then arrives at its declared `t=238` with nothing authored.
+  🔴 **The premise that broke it is yours and it will bite again: `rest.t` is NOT
+  when a screen settles.** It is the last *hold* keyframe before the exit.
+  `ptlogo1` has `rest.t = 251` and stops moving at **`t=42`**. The title's visible
+  build-in is over at **`t≈118`**, where `pteff01`, `pteff02.prm` and
+  `ptlogoall_eff` all end their ramps together — and `238 − 118 = 120 units =
+  **2.000 s**`, which is the 2.13 s I measured. The number was on the disc.
+  ⚠️ **If you author a gap anyway, author 120 units, not my 2.13 s.** 120 units in
+  2.135 s is the game presenting at **28.06 / 28.14 fps** against a nominal 30 —
+  and the corpus had already measured the idle title at **28.5 fps**,
+  independently and before these runs. My wall-clock was this emulator's frame
+  rate baked into a game constant; a port at a true 30 Hz would be visibly late.
+  ✅ That it is presentation rate and not the game is checkable in the same two
+  runs: *first pixels → settle* is 1.643 s and 2.131 s (a 30 % spread) while
+  *settle → plate* is 2.138 s and 2.132 s. Frames are dropped during the
+  build-in, not during the hold.
+  Pulse the plate at ≈ **2.24 s** (four intervals: 2.12 / 2.19 / 2.34 / 2.31),
+  which replicates the corpus's ≈2.3 s rather than replacing it.
+  [`title-plate-delay-measured.md`](../re/title-plate-delay-measured.md) ·
+  [figure](../re/captures/ui-timing/plate-onset-two-runs.png) ·
+  [run 1](../re/data/plate-timing-run1.tsv) · [run 2](../re/data/plate-timing-run2.tsv)
+
+* 🟡 **Your black hold survives a real clock — keep 0.17–0.23 s.** Measured on
+  the Ⓐ path in both runs, the frame is pure black (surface mean 0.070) for
+  **0.14–0.30 s** and **0.14–0.27 s**. At an 0.125 s sample interval that is as
+  tight as this instrument goes, and it brackets both your authored value and
+  the file's declared 12 units (0.20 s). It is the one authored constant you
+  ship that a measurement now agrees with.
+
+* 🔴 **The Ⓐ→menu latency is STILL not a number you may have, and now I know
+  why.** Both runs contain a **frozen frame** on the Ⓐ path — 14 frames (1.53 s)
+  and 12 frames (1.39 s) held at surface mean **26.626**, agreeing between two
+  independent runs to six decimals. Run 2 had stream restarts disabled for the
+  whole window, so it is **not** the capture path: the guest starts the fade,
+  re-presents one frame for ~1.4 s, then shows the full title again and fades
+  properly. That is a **load stall**, and the Ⓑ path — nothing to load — has none.
+  So any Ⓐ→menu figure from this harness is an emulator load time. Your
+  zero-dwell sequencer is the right call; do not add one.
+
+* 🔴 **Four durations I took the same day are WITHDRAWN, including the plate
+  delay.** `screen_match.classify_array` costs **1503 ms/frame**; a probe running
+  it per frame drained an 8 fps stream at **0.64 fps**, so its frames were stale
+  and increasingly so. It manufactured "plate 24.66 s after the title art",
+  "Ⓑ→title in 15.58 s", "Ⓑ→title in 25.60 s" and "Ⓐ→menu in 20.26 s". The tell:
+  a transition, a press and a fade do not share a duration — a backlog does.
+  A backlog **preserves ordering and destroys durations**, which is exactly why
+  the sequence results above stand and the timings do not. Fixed (`fast=True`,
+  38–75 ms, re-controlled 8/8 on both paths, agreeing to ±0.005); the ring's
+  numbers are unaffected and that was checked, not assumed.
+  ✅ **One of the four is now re-taken properly** — the plate delay, above. The
+  probe that took it costs **8.7 ms/frame** (173× cheaper) and both runs sampled
+  at **7.97 / 7.98 fps against a requested 8**, so there was no backlog to
+  destroy them.
+
 ## Status
 
 | | Question | State | Answer / link |
 |---|---|---|---|
-| Q1 | keyframe time unit + ramp shape | ✅ answered, 🟡 one gap | ramp is **linear**; **2 units per rendered frame**; **`1 unit = 1/60 s` — settled**, the idle title presents at 28.5 fps so the game is 30 Hz. 🟡 **The interpolation law is settled; the group TIMELINE for multi-keyframe elements is not** — `palogo_gamearts` is still at full alpha 9 frames after its declared `a=32`, and its declared 80-frame fade-in never draws — [`ui-keyframe-time-unit.md`](../re/ui-keyframe-time-unit.md). ✅ **REPLICATED 2026-08-29 — for ANIMATION, read `+36` as the time the NEXT pose is reached.** Three elements across two screens: `palogo_gamearts` and `palogo_seta` hold full alpha for **83 frames** and `palogo_sqex` for **≥77**, where the current reading predicts **6–8** and the shifted one **80–102**. The elements that cannot discriminate (the `_eff` glows, on which the linear law was measured) fit both. ⚠️ Our decoder still defaults to the other reading (`SYLPHEED_KF_TIME_SHIFT=1` to flip) because it changes `rest()` on one element — but that is an unsound fallback guessing either way, so **static rendering is unaffected and animation timing should use the shift** |
-| Q2 | which build is which screen state | ✅ answered | `GP_TITLE` is **8 screens shipped twice, EN/JP**: 4/7 title art, 2/3 the `PRESS Ⓐ` plate, 5/8 main menu, 6/9 `EXTRAS`, 0/1 and 10/11 two unidentified `DELTASABER` plates — [`ui-title-build-map.md`](../re/ui-title-build-map.md) |
+| Q1 | keyframe time unit + ramp shape | ✅ answered | ramp is **linear**; **2 units per rendered frame**; **`1 unit = 1/60 s` — measured**, the idle title presents at 28.5 fps so the game is 30 Hz — [`ui-keyframe-time-unit.md`](../re/ui-keyframe-time-unit.md). ✅ **The group timeline is now DECODED too (2026-08-29) and the gap is closed**: a placement group is `frames` records of `{u32 time; 36-byte pose}` after an 8-byte header, so a pose's time is the word **before** it, pose 0's time is the group's lead-in word, and **every** pose is timed — including the last, which nothing could time before. Disc-wide over 13 991 groups with controls; the old reading makes **0 of 1 042** multi-segment alpha ramps constant-rate against 857 of 1 540. `SYLPHEED_KF_TIME_SHIFT` is retired (it had the association right but left pose 0 untimed, which is the whole reason it appeared to cost 13.1 % of build 7). Static renders are byte-identical — [`ui-keyframe-record-layout.md`](../re/ui-keyframe-record-layout.md) |
+| Q2 | which build is which screen state | ✅ answered | `GP_TITLE` is **8 screens shipped twice, EN/JP**: 4/7 title art, 2/3 the `PRESS Ⓐ` plate, 5/8 main menu, 6/9 `EXTRAS`, and ✅ **0/1 and 10/11 are the LOADING screen** — two variants, plain and dressed, decoded from their `pgloading_*` element names (2026-08-29). 🟡 which of the two is `LOADING` vs `LOADING2` is undecided; 🟡 the English member of a pair is the one in the first half of the data segment — [`ui-title-build-map.md`](../re/ui-title-build-map.md) |
 | Q3 | paint order for the six screens | ✅ answered, ❔ tie-break | **decoded**: a `u16` layer key at `+0x0A` of each `T8aD` sprite header, stable-sorted with declaration index; unkeyed elements get an implied key. Confirmed on 5 measured orders + `EXTRAS` vs a capture. One residual: the **tie-break** is unknown and bites on one element of the title — [`structures/ui-paint-order-key.md`](../re/structures/ui-paint-order-key.md). ⚠️ **The key does not fully order a screen**: elements sharing a key are tied, and the tie-break is ❔ **undecodable from the bundle** — declaration table, `T8aD` header (exhaustive: every offset 0x00–0x7f at u8/u16/u32, both directions, **0** fields match the measured order against **64** for the control) and the RATC child order all give the same order the game does *not* use. Your exposure is **2 overlapping tied pairs on `EXTRAS`** — [`structures/ui-paint-order-derived-check.md`](../re/structures/ui-paint-order-derived-check.md) |
 | Q4 | button → GamePart | ✅ answered | **measured** which screen all **5** buttons open — `NEW GAME` → `DIFFICULTY` → `SELECT DATA`, not a hang. The **GamePart id is still a name match**, not a measurement — [`menu-navigation-semantics.md`](../re/menu-navigation-semantics.md) |
 | Q5 | navigation semantics | ✅ answered | **measured**: initial focus varies boot to boot (2× `TUTORIAL`, 2× `NEW GAME`); ⬆⬇ one step, **wraps both ends**; ⬅➡ do nothing; Ⓑ returns to the parent **with focus restored**; Ⓑ on the main menu → title; Ⓑ on the title → nothing — [`menu-navigation-semantics.md`](../re/menu-navigation-semantics.md) |
@@ -36,7 +309,7 @@ authored version can be deleted.
 | Q7 | transitions | ✅ answered | a **fade through black**, drawn by the screen's own last-painting `.prm` quad. Fade-in ramp is **decoded** from its keyframes; the ~0.4 s fade-out is **measured** (not in the file) — [`screen-transitions.md`](../re/screen-transitions.md) |
 | Q8 | menu audio bindings | ✅ answered | cue vocabulary + bank **decoded**; event binding is a **name match** (the authors' own event names). ✅ **You CAN have the SE audio** — ⚠️ an earlier version of this row said it was "undecodable from the disc"; that was **retracted** and the row was stale. Three cues are located in `Static.slb` and **decode to PCM**: d-pad move `0x1ec0` (4 packets), Ⓑ back `0x0ec0` (2), Ⓐ confirm `0x5d6c0` (6), all mono 48 kHz. The bank is a packed run of XMA waves with no delimiter, so a wave is only (offset, packet count) — and ⚠️ the file order is **not** cue-id order, so the index cannot be counted out — [`menu-audio-cues.md`](../re/menu-audio-cues.md) |
 | Q9 | video binding + playback rules | ✅ answered | **decoded** from the movie manifest: `ADVERTISE_MOVIE`→`ADV.wmv` (boot intro *and* attract are one asset), `MS00A`→`S00A.wmv` is the new-game intro, `STAFF_ROLL`→the credits reel. ✅ **one Ⓐ skips a movie** (title at 57 s vs a 193 s baseline) — [`movie-binding.md`](../re/movie-binding.md) |
-| Q10 | music-bank sub-wave roles (intro+loop?) | ✅ answered | **two stems of one performance, played together** — sample-synchronous, equal duration, 32/32 banks. **Concatenating is wrong.** Not a seamless loop either — [`structures/bgm-two-stems.md`](../re/structures/bgm-two-stems.md) |
+| Q10 | music-bank sub-wave roles (intro+loop?) | ✅ answered | **two stems of one performance, played together** — sample-synchronous, equal duration, 32/32 banks. **Concatenating is wrong.** Not a seamless loop either — [`structures/bgm-two-stems.md`](../re/structures/bgm-two-stems.md). ⚠️ **Our reader said three until 2026-08-29** — the extra one was the **bank header**, emitted by `to_xma_riffs`; fixed, with a 28/28 disc-wide check and two regression tests — [`structures/slb-bank-header-not-a-wave.md`](../re/structures/slb-bank-header-not-a-wave.md) |
 | S1 | Ready Room go/no-go | ✅ **no-go** | it is 2D and enumerates fine (60 builds), but `GP_READY_ROOM.pak` holds **briefing/tactical-map** content, not the six-button Ready Room menu — [`ready-room-probe.md`](../re/ready-room-probe.md) |
 
 ## Already settled — the port can rely on these today
@@ -900,7 +1173,8 @@ here until 2026-08-28 and is now settled.)
 | 🟡 | **the paint-order tie-break** (Q3) | eight candidates refuted; costs one element's blend on one screen |
 | 🟡 | **GamePart ids behind the buttons** (Q4) | the *screens* are measured; the ids are a name match onto the executable's class names |
 | 🟡 | **the boot transitions in code** (Q6) | both levels decoded — phase at `this+132` (`entry→2`, `2→0`, `2→3`, `3→4`, `4→2`) and state at `this+136` inside phase 4. Phase 0 = splash (`LOGO`), phase 2 = title + `PRESS Ⓐ`, phase 4 = menu. Unknown: what the event *numbers* mean |
-| ❔ | **builds 0/1 and 10/11**, the `DELTASABER` plates (Q2) | never seen anywhere in the boot path, the title-side screens or the attract loop. A mission load is the remaining candidate and this container kills runs before one completes |
+| 🟡 | **Ⓑ leaving the main menu** (Q5) | **upgraded 2026-08-29 (later).** The idle half of this objection is **refuted**: the main menu does not self-return for **≥ 60 s** untouched, and the ~8–10 s idle belongs to the **title**. Ⓑ is delivered (Canary logs `vk=5801`) and is the only input in ≥ 100 s before the return, so the **ordering is measured**; the latency is not (a backlogged probe void). The footer point stands — the main menu is still the only screen not advertising Ⓑ — [`menu-navigation-semantics.md`](../re/menu-navigation-semantics.md#-refutation-attempt-2026-08-29--the-main-menus-own-footer-does-not-advertise-ⓑ) |
+| 🟡 | **which loading bundle is `LOADING` and which `LOADING2`** (Q2) | ✅ the pair is identified — they are the loading screen, decoded from `pgloading_*` element names, and the executable names exactly two. What is open is only the assignment, and nothing observed maps a name to a bundle. ⚠️ The old row here said the pair was *unidentified `DELTASABER` plates never seen running*; that is withdrawn — a loading screen is not supposed to appear on the title path |
 
 (An earlier version of this table called the audio items blocked on "an emulator
 whose audio path can be observed". That was wrong — this build already has
@@ -912,6 +1186,15 @@ box sitting at ~1 GB free with swap exhausted. Dynamic experiments here have to
 fit in roughly two minutes of guest time, which is why several of these residuals
 are unfinished rather than unattempted.
 
+## The player's-eye map of the menus
+
+[`docs/game/navigation.md`](../game/navigation.md) is the screen-by-screen walk
+through the game from the chair — every label, what the cursor does, what each
+footer offers. It was filled in on 2026-08-29 from the committed oracle frames,
+and it is the page to read if you want to know what a screen *looks like* rather
+than how its bundle is laid out. Every ✅ there is a capture, and what is still ❔
+is what no capture answers.
+
 ## Reference data
 
 Committed alongside the findings, so the port can be built without a disc in the

docs/port/PORT-MISSION.md

@@ -100,7 +100,7 @@ A milestone is done when its **artifact** exists, not when the code compiles.
 | **P2** | Keyframe animation | Buttons slide in. **Blocked on HANDOFF Q1** (the time unit). Do not invent it |
 | **P3** | Splash → title, with the transition | Both screens back to back, unattended |
 | **P4** | Intro video | `ADV.wmv` plays with audio (§6) |
-| **P5** | Main menu: navigation, focus states, Ⓐ into a submenu, B back | ~~A human clicks through it~~ — ✅ **GATE MET 2026-09-02.** A human walked it: *"Menu walk and navigation is fine. Video skips too. Extras open."* [`../agents/PLAYTEST-2026-09-02-menus.md`](../agents/PLAYTEST-2026-09-02-menus.md) |
+| **P5** | Main menu: navigation, focus states, Ⓐ into a submenu, B back | A human clicks through it |
 | **P6** | Audio — menu BGM and move/confirm SFX | Sound on the P5 gate. **Looping is blocked on HANDOFF Q10** |
 | **P7** | New-game intro video after NEW GAME | Plays, then returns to a defined state |
 

docs/port/f6-what-starts-the-sweep.md

@@ -1,597 +0,0 @@
-# F6 unit a — what the port currently uses to start the title sweep
-
-**Status:** ✅ answered. **No behaviour changed** — this unit exists so that when
-the Decoder says *when* the glow should start, the edit is one line.
-Port at `937f055`, 2026-09-02.
-
-## The answer, in one line
-
-`port/scripts/screen_view.gd:684`
-
-```gdscript
-var t := leaf_time_units if leaf_time_units >= 0.0 else time_units
-```
-
-**That is the whole start mechanism, and it is not a start mechanism.**
-`leaf_time_units` is set in exactly one place — `boot.gd:359`, the `--leaf-time`
-diagnostic flag — and is `-1.0` on every real boot. So the travelling glow runs
-on `view.time_units`, the title screen's own clock, which `_advance` sets to
-`0.0` when the title is raised. **Zero offset, no gate.**
-
-## 🔴 And the obvious gate does not exist
-
-The natural reading — mine, before checking — is that the parents gate it:
-`ptloop01`/`ptloop02` declare `0:0 70:0 100:255 238:255 250:0`, invisible until
-t=70. **That is not what happens**, because what reaches the screen is the LEAF,
-and `screen_view.gd` records as decoded that *"the leaf runs on its OWN timeline
-and the parent's alpha is NOT multiplied in"*. The parent ramp gates nothing.
-
-The leaves' own declarations:
-
-| leaf | alpha | x position |
-|---|---|---|
-| `pteff03` | **`0:255`** 150:128 540:255 600:255 | −639 → −39 (t=150) → 1521 (t=540) |
-| `pteff03a` | 0:0 150:128 630:255 720:255 | 1721 → 1111 (t=150) → −839 (t=630) |
-
-**`pteff03` is at full alpha from title t=0** and is travelling from t=0. It
-clears the left edge (sprite is 399 wide) at around t≈60 and is well inside the
-frame by t=150.
-
-The plate arrives at **t=214–236**. So the port starts the sweep roughly
-**150+ units ≈ 2.5 s early** — which is the size and the direction of what the
-human reported.
-
-## Corroborated on a film, not only read
-
-Filmed a real boot at 0.05 s and measured frame-to-frame change in the title art
-band `1280x420+0+90`, which **excludes the plate's own rectangle** (y 550–600) so
-the plate cannot be what registers:
-
-```
-view_units   22    54    69    86   118   134   214   341   406
-delta      31.8  39.9  30.8   9.4  12.6   0.2   0.2   0.1   0.4
-```
-
-Motion is heavy through the build-in and the band is quiet by t≈134 — consistent
-with `pteff03` having already crossed the measured band and with the coarse
-resize washing a thin glow out. **The film neither adds to nor contradicts the
-declaration; the declaration is the evidence here.**
-
-## Where the sweep actually is, computed from the leaf's own translation
-
-The port positions the leaf **from the leaf's own clock** — it does not draw the
-parent's pose and ignore the translation. Sprite 399 wide on a 1280 screen:
-
-| t | 0 | **61** | 70 | 100 | 150 | **236** | 250 |
-|---|---|---|---|---|---|---|---|
-| `pteff03` x | −639 | **−395** | −359 | −239 | −39 | **305** | 361 |
-| `pteff03a` x | 1721 | 1477 | 1436 | 1314 | 1111 | 762 | 705 |
-
-**`pteff03` enters the frame at t=61 and is mid-screen at t=305 when the plate
-reaches full alpha at t=236** — visible and travelling for ~175 units ≈ 2.9 s
-before the plate. `pteff03a` enters much later.
-
-## 🔴 The open question in this file sits exactly inside F6's window
-
-`screen_view.gd` flags its own limit on the leaf-vs-parent alpha decode:
-
-> *"Every observation behind this has parent alpha 0, so 'the leaf wins' and 'the
-> parent is ignored because it draws nothing' are NOT separated. **A capture
-> during t=100…238 would separate them.**"*
-
-The parent is non-zero exactly on `t=100…238`, and the plate arrives at 236. So
-that unresolved ambiguity is **the same interval F6 is about**, and it is
-load-bearing for the first stretch: the parent ramps 70→100, so applying it would
-hide the sweep until t=70 and dim it to t=100, while the port shows it at full
-alpha from t=61.
-
-That accounts for ~40 units of the earliness. **It does not account for the other
-~175**, which is the leaf clock starting at title t=0 with no offset.
-
-📌 **One capture in `t=100…238` would settle both** — F6's start time and the
-leaf/parent alpha rule — rather than two.
-
-## What changes when the answer lands
-
-A start time is an **offset**, and `leaf_time_units` is an absolute override —
-they are not the same field. The one-line edit at 684 becomes a subtraction, fed
-by one authored value. Nothing else moves.
-
-## What this does NOT do
-
-* **It does not choose a start time.** That is the Decoder's, and this unit was
-  scoped to exclude it deliberately.
-* It does not touch the glow. A boot looks exactly as it did.
-* It says nothing about whether the *speed* or the *path* is right — only when it
-  begins.
-
----
-
-# 🔴 Unit b, HELD: the parent-alpha refutation may be right, but its identification step cannot carry it
-
-**Status:** ⏸️ **the renderer is NOT changed.** The Decoder's
-`f6-unit2-parent-alpha-multiplies.md` refutes `screen_view.gd`'s *"the parent's
-alpha is NOT multiplied in"* using a bound. The bound's shape is sound and its
-premise checks out against this export. **The step that assigns the measurement
-to an element does not.**
-
-## The premise holds
-
-`pteff03`'s leaf declares `0:255 150:128 540:255 600:255` — **minimum 128**,
-confirmed off `export/screens/title/title.json`. A drawn alpha below 128 cannot
-come from that leaf alone. That part is right.
-
-## 🔴 But the two strips are the SAME SIZE, so size cannot say which is which
-
-The identification is stated as *"by size against the corpus's independently
-measured AABB height of 1134 px"*. Measured off this export:
-
-| sprite | dimensions | leaf alpha range | travel |
-|---|---|---|---|
-| `pteff03` | **399 × 180** | **128 … 255** | left → right (−639 → 1521) |
-| `pteff03a` | **399 × 180** | **0 … 255** | right → left (1721 → −839) |
-
-**They are byte-identical in size**, which is consistent with the two reported
-rows measuring `1.38 × 3.15` and `1.39 × 3.15` — a 0.7 % difference. Size
-separates the sweeps from everything else on the screen; it cannot separate them
-from **each other**, and that is the distinction the argument needs.
-
-## Why it matters — the assignment flips the conclusion
-
-The quoted row that reaches **8** is the one the argument leans on. But
-`pteff03a`'s leaf alpha floors at **0**, not 128, and ramps `0 → 128` across
-t=0…150. Values of 8, 24, 33, 50 … are exactly what **that leaf alone** produces.
-So if the 8-row is `pteff03a`, the bound is satisfied with no parent at all.
-
-⚠️ **And the conclusion may still be correct via the OTHER row.** The row
-reported as `16 41 67 91 116 128 129 130 131` contains values below 128 *and* a
-dense cluster at 128–131 — the signature of `pteff03`'s floor. If that row is
-`pteff03`, then 16 < 128 refutes no-multiply exactly as claimed. **The finding
-may be right and the cited row wrong.**
-
-## The discriminator is free and already in their capture
-
-The two leaves travel in **opposite directions**: `pteff03` left→right,
-`pteff03a` right→left, separated by ~1 000 px for most of their run. One frame
-pair settles it. Nothing needs re-capturing.
-
-## ✅ Resolved: the discriminator worked, and MY proposed repair was wrong
-
-The Decoder ran the travel-direction check on the capture they already had:
-
-```
-1.38x3.15  n=1140  x centre -1.690 -> +0.500   LEFT->RIGHT
-1.39x3.15  n= 614  x centre -1.685 -> +0.495   LEFT->RIGHT
-```
-
-**Both rows travel the same way, so both are `pteff03`** — the 0.7 % size
-difference is per-frame rounding splitting **one** element across two keys.
-`pteff03a` is not in the capture at all.
-
-🔴 **So my "the finding may still be correct via the OTHER row" does not apply —
-there is no other row.** The identification was broken a third way that neither
-of us named: not two elements confused for each other, but one element counted
-twice. I was right that size could not carry the assignment and wrong about what
-the assignment actually was.
-
-⚠️ And the part I could not see from here, which is the larger one: the quoted
-`8 24 33 50 58 …` were the nine **lowest distinct** values, not a series — a
-tail, presented in a shape that reads as a ramp. **14 sub-floor samples out of
-1754.** The bound survives in shape and collapses in weight: one sample below 128
-is still unexplainable by a leaf flooring at 128, but 14 of 1754 is where a
-grouping slip or a partial frame would show up.
-
-**Status: 🟡 not refuted, not established.** The next unit is a re-read of data
-already on disk — the same capture as a *series* across t=70…100, where a
-multiplying parent must ramp on nearly every frame rather than in 14 stragglers.
-That unit is the Decoder's and has not been run.
-
-## What the port does about it: nothing yet
-
-Adopting a decode whose element assignment is unresolved is how this project has
-been burned before — and the port would be changing a renderer rule on it.
-`screen_view.gd` keeps its current behaviour until the row is identified by
-travel direction. **This is not scepticism about the conclusion**, which the
-port's own flagged limit predicted would fall this way; it is about which row.
-
----
-
-# 📌 What was actually holding this up: we both picked the wrong observable
-
-The human asked what was blocking us and whether the approach needed revising.
-**It did, and the diagnosis is short: two agents spent three exchanges on ALPHA
-while the answer sat in a POSITION series neither of us compared to anything.**
-
-## The arithmetic that should have been step one
-
-The Decoder's capture reports the sweep's x-centre running `−1.690 → +0.500`.
-Read as NDC (`x_ndc = 2·x_px/W − 1`, **an assumption, stated as one**):
-
-| | ndc | centre px | implied leaf t |
-|---|---|---|---|
-| first sample | −1.690 | −441.6 | **−0.5** |
-| last sample | +0.500 | +960.0 | 349.9 |
-| **declared at leaf t=0** | **−1.687** | **−439.5** | — |
-
-**A 2 px agreement on a 2 160 px travel.** So the game's sweep begins travelling
-at leaf t≈0, from off-screen left — **the same as the port.**
-
-🔴 **That contradicts my own earlier framing on this page**, which attributed
-~135 units of the earliness to "the leaf clock starting at title t=0 with no
-offset". If the game's leaf clock also starts at 0, that is not a defect and F6
-is a **visibility** question — alpha, or draw order, or something not yet named —
-rather than a clock question. I am flagging it rather than rewriting the section:
-this rests on two numbers relayed in a message, which is exactly the thing that
-should be read from the repository instead.
-
-## Why alpha was the wrong tool, stated generally
-
-| | alpha | position |
-|---|---|---|
-| dynamic range | 8 bits, quantised | **2 160 px** |
-| shape | non-monotone, ramps and holds | **monotone** |
-| failure mode that bit us | a 14-sample tail out of 1754 looks like signal | a wrong shape raises the residual |
-| yields the clock? | no | **origin AND rate together** |
-
-**When something moves, its position carries the clock and its alpha carries
-almost nothing.** Neither of us reached for a trajectory comparison because
-neither of us had one.
-
-## So: `tools/port/fit-trajectory`
-
-Solves `x_measured(frame) ≈ declared(t0 + rate·frame)` for the pair, and reports
-the **residual**, which is the part that matters: it says whether the model was
-right at all, where a value-at-an-instant never can.
-
-Its `--selftest` runs both directions — recovers a known clock from a synthesised
-series to 0.09 px, and **rejects** a wrong-shape series at 81.9 px against a 20 px
-bar — because a fit that cannot fail is a curve-fitter, not a measurement. Wired
-into `check-all`.
-
-⚠️ It fits a **constant** rate. A stalling guest clock or uneven capture drops
-raise the residual rather than being absorbed, which is deliberate.
-
----
-
-# ❌ WITHDRAWN — Unit c: "the port draws a sweep the game does not"
-
-> 🔴 **This whole section is refuted, and the port was right.** `pteff03a` **is**
-> drawn by the game. The two strips are batched into a **single additive draw of
-> eight vertices — two quads** — and the Decoder's log reader took the first
-> vertex match per draw line and discarded the rest, so every analysis saw quad A
-> and never quad B. No new capture was needed; `pteff03a` was in the same logs
-> that were read as declaring it absent
-> (`docs/re/f6-unit11-pteff03a-IS-drawn.md`). Measured on both sides: the strips
-> travel in opposite directions with a size ratio of 1.301 against the declared
-> 800/600 = 1.333.
->
-> ✅ **Nothing in the port changed on the strength of it.** I proposed gating
-> `pteff03a` and held, because absence in one capture read by one probe is a lead
-> and not a finding, and because the check I asked for was a human's look rather
-> than another measurement. That hold is the only reason this cost nothing.
->
-> ⚠️ **And the absence claim cited the port as evidence against itself** — "the
-> port draws it, the game does not" — so a defect was inferred in my renderer
-> from a gap in a reader. Kept in place rather than deleted: the reasoning below
-> is sound given its premise, and the premise is exactly the kind that looks like
-> data.
-
-## The original section, kept for its shape
-
-## First, the correction: my refutation was right in outcome and WRONG in its reason
-
-I challenged the Decoder's by-size identification on the ground that *"both
-sweep sprites are 399×180, so size cannot separate them"*. **That was wrong.** I
-compared the source PNGs and never looked at the leaf declarations:
-
-| leaf | sprite | declared scale | **drawn height** |
-|---|---|---|---|
-| `pteff03` | 399×180 | `[100, 600]` | **1080 px** |
-| `pteff03a` | 399×180 | `[100, 800]` | **1440 px** |
-
-The *drawn* quads differ by a third, which is exactly the 3.15 vs 3.62 NDC the
-Decoder was separating by. **Size distinguishes them fine.** The hold was still
-correct and the check I asked for still found a real defect — but it found a
-different one (one element double-counted, and a set presented as a series), and
-my stated reason did not survive. Recorded because a right answer reached by a
-wrong argument is the kind that gets cited later for the wrong reason.
-
-## And it makes the real finding sharper
-
-Because size *does* separate them, the Decoder's line — *"`pteff03a` does **not**
-appear in this capture at all"* — is well-evidenced rather than incidental. They
-looked for a distinct size and found nothing.
-
-**The port draws it.** Asked directly, at three instants:
-
-```
-t=120  drew 9: ptbase2, pteff03, pteff03a, pteff04, ...
-t=180  drew 10: ptbase2, pteff03, pteff03a, pteff04, ...
-t=240  drew 10: ptbase2, pteff03, pteff03a, pteff04, ...
-```
-
-`pteff03a` is on screen in the port from t≈108 (it crosses x=1280 there) until
-t≈521, travelling **right-to-left** at 800 % vertical scale while `pteff03` runs
-left-to-right at 600 %. The capture covers that window and contains only
-`pteff03`.
-
-> ~~**So the port appears to render a second light sweep, larger and travelling
-> the opposite way, that the game does not draw during the title build-in.**~~
-> ❌ **False.** The game draws both, batched into one eight-vertex draw.
-
-⚠️ **Absence in one capture is not absence in the game**, and this is one
-capture, read by one probe, identified by size. It is a lead, not a finding. But
-it is the first thing in F6 that is *visible*, *port-side*, and *checkable by a
-person in seconds* — which is what this whole exchange has been missing.
-
-## What did NOT work, recorded so nobody repeats it
-
-I tried to isolate the two sweeps visually by differencing title frames at
-several `--time` values. **It failed and the output is not evidence**: at those
-instants the whole title is still animating — logo, effects, copyright — so the
-difference is the entire screen rather than the sweeps. Frame-differencing
-isolates motion only when everything else is still, and during a build-in nothing
-is.
-
-## The unit, and it is one question for a person
-
-> **On the real game's title screen, is there ONE light streak sweeping across,
-> or TWO travelling in opposite directions?**
-
-Pass for the port as it stands: two. If the game shows one, `pteff03a` is drawn
-here and should not be — and an extra glow arriving at t≈108 is a very good
-candidate for *"the glow starts too early"*.
-
-**Not covered:** the start time of `pteff03` itself, which is still open; and the
-parent-alpha question, still 🟡.
-
----
-
-# ❌ Unit d — the "variant link" explanation, raised and killed in one pass
-
-The Decoder's second candidate for why the game submits `ptloop01` and not
-`ptloop02` was *"a focus/variant link means only one of the pair is ever
-active"*. **That is answerable from the export, and the answer is no.**
-
-## What looked like a smoking gun
-
-`ptloop01` carries **`opt_link = "ptloop02.rat"`**, `ptloop02` carries none, and
-it is the only linked element on the title screen. The field is exported straight
-from `el.focus_link` (`crates/sylpheed-export/src/screen.rs:622`), and
-**`port/scripts/` never reads it.** An ignored variant link would have explained
-the extra sweep exactly.
-
-## ❌ And it is not a variant link
-
-Surveying `opt_link` across the whole export splits it into two populations:
-
-| target | example | is the target also a top-level element? |
-|---|---|---|
-| `*f.rat` | `ptbtn00 → ptbtn00f` | **no** — variant only |
-| everything else | `ptloop01 → ptloop02` | **yes** — both are drawn |
-
-And the second population **chains across unrelated element kinds**. On
-`main_menu`:
-
-```
-index 3   ptloop01  -> ptloop02.rat
-index 4   ptloop02  -> ptbtn01.rat
-index 10  ptbtn01   -> ptbtn01f.rat
-```
-
-**A light sweep points at a button.** A variant selector cannot do that, so
-`opt_link` is a chain pointer that happens to land on the focus variant when the
-element is a button — which is why it was exported under the name `focus_link`.
-
-> So the field does not select between `ptloop01` and `ptloop02`, and the port
-> ignoring it is not what draws the extra sweep. **Candidate eliminated.**
-
-## The smaller finding that survives
-
-**`focus_link` is carrying two different things** and the exporter names it after
-only one of them. The `*f` population is a variant; the rest is a chain. Nothing
-depends on this today — the port reads neither — but the name asserts a meaning
-the data does not support, and the next person to reach for it will reach for the
-wrong one. Worth renaming when something actually needs it; not worth a
-re-export on its own.
-
-## Where that leaves F6
-
-The lead is unchanged and unexplained: **the port draws `pteff03a`, the game's
-capture never does** — now confirmed by an exhaustive scan of every tall quad in
-1..2499 rather than a filtered subset. One of the two candidate causes is now
-eliminated from the export side, which leaves the Decoder's first: a zero-alpha
-skip suppressing the opening frames. ⚠️ That one does not obviously survive
-either — it would explain `pteff03a`'s *opening* frames, not its whole run, and
-its leaf reaches α=128 well inside the captured window.
-
-**Nothing is deleted and the renderer is unchanged**, pending one five-second
-human look: one streak, or two?
-
----
-
-# Unit e — the port draws exactly TWO travelling lights, and the human reports more
-
-The human, watching the real game: *"I think multiple, possible more than two…
-The lights move on blue lines looking like PCB board lines. And frankly I cannot
-tell if the game renders a light per line or uses a light that is shown around
-multiple, close lines."*
-
-That is a different question from the one both agents had been asking, and it is
-worth having the port's own number first.
-
-## Census of every element on the title that travels
-
-| element | x travel | note |
-|---|---|---|
-| `ptlogo1` / `ptlogo2` (×3 instances) | 300 px | the **logo** sliding in, t=34…251 — not a light |
-| **`pteff03`** (leaf of `ptloop01`) | **2 160 px** | left → right |
-| **`pteff03a`** (leaf of `ptloop02`) | **2 560 px** | right → left |
-
-Every other title element — `pteff00`, `pteff01`, `pteff02`, `pteff04`,
-`ptlogo_back2eff` and `…eff1…5`, `ptlogoall_eff`, `ptlogoall_eff2`,
-`ptcopyright`, `ptbase2` — **declares no positional travel at all.** They fade in
-and out in place.
-
-> **The port renders exactly two moving lights.** The human describes multiple,
-> possibly more than two, running along individual PCB traces.
-
-## What that reframes
-
-Both agents had been asking *when* the sweep starts. If the game's effect is a
-population of small lights on separate traces and the port's is two full-height
-streaks crossing the screen, then **the port may have the wrong effect
-altogether**, and "starts too early" is what a wrong effect looks like to someone
-who is not reading keyframes.
-
-⚠️ **And it puts a limit on the capture result.** The Decoder's scan that found
-`pteff03a` absent covered every quad **taller than 1.2 NDC**. Small per-trace
-lights are far below that, so that scan cannot count them — it is exhaustive over
-full-height streaks and silent about the population in question. `pteff03a`'s
-absence stands (it would be 3.62 NDC); *"only one travelling quad exists"* does
-not generalise beyond tall quads.
-
-## ⚠️ A limit of this census
-
-It reads **declared** keyframes. An element with a single keyframe shows as
-"visible 0…0" here and is in fact held and drawn — `ptbase2`, the background, is
-the obvious case. So the visibility column understates; **the travel column is
-the load-bearing one**, and travel is what a moving light needs.
-
-It also cannot see motion that is not positional — a scrolling UV, a texture
-animation, or a shader would move light along a trace while declaring no travel
-at all. **Nothing in this export declares such a thing**, but the port would not
-know if the game did it that way, and that is now a live possibility rather than
-a remote one.
-
-## Not covered
-
-Whether the game's lights are one-per-trace or one glow spanning several — the
-human says they cannot tell, and it is the Decoder's screenshots to settle.
-
-
----
-
-# 📌 What the withdrawal is worth, since the port lost nothing
-
-Three of my own claims rested on `pteff03a` being absent and all three fall with
-it: that the port renders a sweep the game does not, that this was "the first
-thing in F6 that is visible and port-side", and — in a report to the human — that
-"the port draws two, the game's capture has one." **The port draws two and so
-does the game.** The census on this page stands unchanged; what changed is that
-it now agrees with the capture rather than contradicting it.
-
-**The one thing that made this free was refusing to act on it.** The evidence was
-an exhaustive scan, from an agent with the oracle, corroborated by a mechanism
-and by two candidate causes. It was still an *absence*, measured once, by one
-reader — and the check I asked for was a human's look, not another measurement.
-
-⚠️ **An absence is a claim about an instrument, not about the world.** A count of
-zero says only that nothing got through the reader. Every positive result on that
-same capture — the alpha decomposition, the press-vs-control comparisons, the
-pulse ratio — is untouched, because those compare like with like on the same
-quad. Only the absence compared a count against zero, and that is precisely where
-a truncating reader is fatal.
-
-📌 The Decoder notes this is the third time this corpus has been bitten by an
-under-reading dump, and that `REFUTED.md` already recorded a draw carrying two
-rotated parallelograms — **the general fact was written down before the reader
-contradicted it.** Their cheap check is worth repeating here because it applies to
-anything the port ever reads: *read one raw record in full before trusting any
-count derived from it.* The batch size was printed on every one of those lines.
-
-## 📌 And the same error recurred, which makes it a pattern rather than a slip
-
-The withdrawn alpha bound on this page failed because nine values quoted as a
-series were `sorted(set(...))[:9]` — the lowest distinct values, a tail wearing
-the shape of a trajectory. The Decoder has since found the same thing in a second
-finding: an implied-parent range quoted as 254.0–256.9 turned out to be *the rows
-they had printed*, every twentieth frame, standing in for a population whose real
-first-cycle spread was 250.9–260.5.
-
-**Twice, and both times the output looked fine.** That is the tell: a summary
-drawn from a subset does not look like an error, it looks like a result. The
-conclusion survived on both occasions, so nothing here needs undoing — but a
-conclusion surviving is not evidence the number under it was sound, and this port
-has now inherited two numbers that were not.
-
-⚠️ **Neither was reachable by reasoning**, which is the part worth keeping. In
-both cases the argument was valid and the *inputs to the summary* were wrong. No
-amount of re-reading the claim finds that; only re-running it does. It is the
-argument for re-running over re-checking, and it is why the two findings flagged
-as unverified above were re-run rather than defended.
-
----
-
-# ❌ A refutation aimed at this renderer, measured and NOT landed
-
-The Decoder raised it and could not test it from their side: *"if your renderer
-runs both leaves on a single rate, the two strips stay locked together and drift
-from the game by ~118 units per cycle, growing without bound."* The two leaves
-declare **600** and **720** unit loops.
-
-**Pre-registered, then measured on a real boot** via `--probe-leaf`. At a raw leaf
-clock of 4873:
-
-| leaf | span | measured `leaf_t` | `fposmod(4873, span)` |
-|---|---|---|---|
-| `pteff03` | 600 | **72.6** | 73 |
-| `pteff03a` | 720 | **552.6** | 553 |
-
-The port takes each leaf's span from **its own keyframes** — `span = max(k.t)`
-over `fe.keyframes` — so the two were never locked. **17 748 probe samples, title
-clock reaching 9 745**, i.e. the sweep is still looping 162 seconds in.
-
-## 🔴 Two false alarms of my own on the way there, both from the same mistake
-
-1. **I used `--time` to ask a question about running behaviour.** It sets
-   `frozen`, which by design bypasses the `holding` clamp, so the title read as
-   *empty* past t=250 and I nearly reported the whole title vanishing. On a real
-   boot it does not: `settle_window` is `[160, 236, 198]`, the elements clamp to
-   t=198, and a filmed frame at `view_units 6733` shows the complete title.
-2. **I read a probe stopping as the feature stopping.** Two runs ended at
-   u≈236 and I took that as the sweep dying at settle. It was the run ending —
-   without `--film` the boot exits sooner. With a film attached the same probe
-   reaches 9 745.
-
-📌 Both are the frozen-sweep lesson wearing new clothes: *the diagnostic that
-pins the clock cannot answer a question about the clock running*, and *an
-instrument going quiet is not the subject going quiet*. The second is the same
-shape as the Decoder's own absence-of-a-quad bug — a count of zero says only that
-nothing reached the reader.
-
----
-
-# ✅ Out-of-sample: what the port ships was in the passing half
-
-The Decoder pre-registered six predictions and tested them on a fresh boot that
-had no hand in deriving them. **Three failed.** Audited here against what this
-port actually authors, and the answer is **nothing to change**:
-
-| their prediction | fresh boot | does the port carry it? |
-|---|---|---|
-| leaf period ratio 1.200 | 1.1753 ✅ | **yes** — this is `rate = 0.5` |
-| strip size ratio 1.333 | 1.3009 ✅ | yes, as element identity |
-| pulse / sweep loop 0.100 | 0.0963 ✅ | yes, `looping_focus_records` 120 |
-| pulse amplitude ≤3 levels | 8.73 🔴 | no |
-| `ptcopyright` ramp ratio 0.733 | 0.550 🔴 | no |
-| sweep leads plate 0.138–0.141 | **0.0996** 🔴 | **no** — grepped, absent |
-
-`authored/rendering.json` `leaf_clock` is `{start_units: null, rate: 0.5}` and
-nothing else. No separation constant exists in `authored/`, `tools/port/` or
-`port/scripts/`.
-
-📌 **That split is not luck and is worth naming.** Everything the port adopted is
-either **declared on the disc** (the parent gate, the 120-unit pulse loop, the
-600/720 leaf periods) or **corroborated by three independent legs** (the rate).
-Every failed prediction is a figure derived from *relationships between elements
-measured in a capture* — the class with no declared counterpart, which
-`check-authored-vs-declared` says out loud it cannot arbitrate. The rule "adopt
-what the disc declares, or what three unrelated things agree on" selected exactly
-the surviving half without anyone knowing which half that would be.
-
-⚠️ And the Decoder reports that `check_labels.py` — offered last iteration as the
-mechanism for capture-only labels — **fails its first independent test**: two of
-its four checks fire on a third capture, having been validated on the two that
-produced the labels. An instrument validated on its own training data. Nothing
-here depends on it, but it is not a mechanism this port should lean on either.

docs/port/menu-destinations-are-one-line-away.md

@@ -1,70 +0,0 @@
-# Four of five main-menu destinations are blocked on ONE hardcoded archive
-
-**Status:** ✅ feasibility established, nothing changed yet. 2026-09-03.
-
-## The gap, in player terms
-
-| button | destination | today |
-|---|---|---|
-| NEW GAME | `DLG_SELECT_DIFFICULTY` → SELECT DATA → video | **jumps straight to the video** |
-| LOAD GAME | `GP_SAVE_LOAD` | **dead** |
-| TUTORIAL | — | **dead** |
-| OPTIONS | `GP_OPTIONS` | **dead** |
-| EXTRAS | `extras` | works |
-
-All four are recorded in `authored/flow.json` as **measured destinations** —
-somebody drove the real game to them. They are `blocked` for one structural
-reason, stated there: *"not a GP_TITLE build, so there is no screen file to go
-to."*
-
-## The cause is one line
-
-`crates/sylpheed-export/src/main.rs` hardcodes `let archive = "dat/GP_TITLE.pak"`.
-
-## And the reader already works on the rest
-
-`examples/probe_archives.rs` runs the **existing** `ui_layout::is_build` over
-every `.pak` on the disc. It decodes nothing new:
-
-| archive | entries | builds |
-|---|---|---|
-| `GP_OPTIONS` | 26 | **14** |
-| `GP_SAVE_LOAD` | 108 | **18** |
-| `GP_DIALOG` | 140 | **105** |
-| `GP_TUTORIAL` | 2 | **2** |
-| `GP_TITLE` | 16 | 12 |
-
-**24 archives contain UI screen builds. The exporter reads one.**
-
-> So this is not blocked on the Decoder and needs no new format work. It is an
-> exporter scope limit, and the exporter is the port's.
-
-## Why this is worth doing before the queued items
-
-Measured against *"if this is wrong, what does a player experience?"* — the
-filter this port adopted after spending two rounds on a plate pulse that turned
-out not to be a defect:
-
-* **four dead menu entries** and a missing difficulty screen: a player hits them
-  immediately and three of them do nothing at all;
-* the audio mix (F2): a player notices, but the menu still works;
-* the repeat rate (F1) and the title track (F3): both blocked on measurement.
-
-## ⚠️ What this does NOT establish
-
-* **That the screens will render.** `is_build` says the record parses as a build,
-  not that its sprites resolve, its names are known, or its layout is complete.
-  `GP_HANGAR_ARSENAL` reports 390 builds and is squarely gameplay, out of scope.
-* **Which entry is the difficulty dialog.** `GP_DIALOG` has 105 builds and none
-  of them is named yet; `DLG_SELECT_DIFFICULTY` is a name from the flow, not an
-  entry index.
-* **That more screens are free.** Every screen the export gains is a screen
-  `check-all`'s comparisons iterate over, and screen names are authored per
-  archive+entry — unnamed screens need a naming decision, not just a loop bound.
-
-## Next unit
-
-Widen the exporter to **one** further archive — `GP_OPTIONS`, the smallest at 26
-entries — as data rather than a second hardcoded constant, and see what actually
-comes out. Not all four at once: 139 new screens arriving together would make any
-regression unattributable.

docs/port/options-screens.md

@@ -1,118 +0,0 @@
-# The OPTIONS menu tree exists, renders, and is named
-
-**2026-09-03.** `GP_OPTIONS` joined `export_archives` and produced 14 screen
-builds. All 14 render; all 14 are now named.
-
-## What they are
-
-| entry | name | English | | entry | name |
-|---|---|---|---|---|---|
-| 19 | **`options`** | **the root** — GAME / CONTROL / SOUND / SCREEN SETTINGS, BACK | | 21 | `options_jp` |
-| 16 | `game_settings` | Auto-Save, View Point, Radio Log, Subtitles | | 18 | `game_settings_jp` |
-| 4 | `control_settings` | Control Type, Throttle, sensitivities, Vibration | | 8 | `control_settings_jp` |
-| 3 | `sound_settings` | Music / Movie / Voice / SFX Volume | | 5 | `sound_settings_jp` |
-| 6 | `screen_settings` | Gamma Correction, R/G/B, NEXT PAGE | | 9 | `screen_settings_jp` |
-| 7 | `screen_settings_page2` | White / Black Level Adjust, PREVIOUS PAGE | | 10 | `screen_settings_page2_jp` |
-| 20 | `control_customize` | per-action key remapping | | 22 | `control_customize_jp` |
-
-A clean EN/JP pair for every screen, which is itself a check: 14 builds, 7
-pairs, no leftovers.
-
-## How they were identified, and why that is stronger than usual here
-
-**By the text the screen renders about itself.** Each was exported, drawn by the
-port at rest, and read: the titles and row labels are legible.
-
-📌 That matters because this project has been bitten three times by
-identification via **position, size or ordinal** — the sweep strips confused by
-size, the plate identified by screen position, `ptcopyright` mistaken for the
-plate. A screen that renders the words `SOUND SETTINGS` above four volume rows is
-not that kind of inference.
-
-⚠️ **What it still does not establish:** which screen the *game* navigates to
-from which. The tree above is read off content, so `control_customize` being
-"reached from CONTROL SETTINGS" is a reading of its own legend
-(`Ⓨ : Customize` on `control_settings`), not a measured transition. Wiring
-anything beyond `main_menu → options` needs the real navigation.
-
-## Not yet done
-
-* **Nothing is reachable yet.** `main_menu` `ptbtn04` still has `goto: null`.
-* **`po_pad_slider1` has no sprite** in the export and reports NOT DRAWN.
-* **All 14 are `NEVER COMPARED`** by `verify-screen` — reported, not asserted;
-  both its allowance and the reference renderer were calibrated on `GP_TITLE`.
-* The screens are static: no navigation, no focus movement, no value editing.
-
----
-
-# ✅ OPTIONS is reachable — and navigation inside it is blocked on a kind
-
-`main_menu` `ptbtn04` now has `goto: "options"`. Walked with the menu harness:
-main_menu → ⬇⬇⬇ → Ⓐ → the OPTIONS root renders. Ⓑ backs out.
-
-## ✅ RESOLVED — the rows move. `0x3003` is `0x3002` with the parent bit set
-
-The Decoder decoded it disc-wide: **bit 0 of `kind` is the PARENT FLAG**, and it
-carries no role information. Over every `.pak` in `dat/`, `kind & 1` agrees with
-"has a parent" on **15 493 elements with zero disagreements**
-(`docs/re/ui-kind-bit0-is-has-parent.md`). The OPTIONS rows are parented; the
-main-menu buttons are not. Same record class.
-
-So the detector now matches `0x3002 | 0x3003` — **two values listed, not a
-mask**. `kind & 0xFFFE == 0x3002` would also catch `0x73002`/`0x73003`, 160
-elements whose high bits nobody has decoded, silently and on screens neither
-agent has seen.
-
-**Impact measured before re-exporting, not after:** exactly two screens gain
-buttons — `options` and `options_jp`, five rows each. No existing screen changes.
-
-Verified by walking it: `main_menu` → ⬇⬇⬇ → Ⓐ → OPTIONS, then ⬇⬇ moves
-`po_menu_btn2` → `po_menu_btn3` with the focus ring rendering on the highlighted
-row.
-
-📌 **The port was right to wait.** The rejected rule — "carries a focus record ⇒
-menu item" — would have reached the same answer here by a second inference from
-structure, and would have reclassified elements on screens nobody had looked at.
-The field cost one question and needed no inference at all.
-
-## The original section, kept for the shape of the block
-
-The exporter's button detector is `kind == 0x3002 && !focused`. The OPTIONS rows
-are **`kind_raw = 0x3003`**, so `role` comes out `unknown`, the export's
-`buttons[]` is empty, and up/down move nothing.
-
-| screen | element | kind | focus record | in `buttons[]` |
-|---|---|---|---|---|
-| `main_menu` | `ptbtn01` | `0x3002` | yes | yes |
-| `extras` | `ptbtn11` | `0x3002` | yes | yes |
-| **`options`** | **`po_menu_btn1`** | **`0x3003`** | **yes** | **no** |
-
-**What `0x3003` means is not the port's to decide**, so the rule was not widened
-here. The circumstantial case is strong — five rows, each carrying a focus
-record, on a screen whose own text lists five options — and *circumstantial* is
-precisely the standard that has cost this project three separate retractions.
-Asked of the Decoder.
-
-⚠️ A tempting alternative rule is "an element with a focus record is a menu item",
-which fits both screens. It is still an inference about semantics from structure,
-and it would silently reclassify elements on every screen in the export. Not
-taken.
-
-## The workflow cost this exposed, worth knowing before repeating it
-
-**A screen name is authored data, but it only reaches the port through a full
-re-export** — which re-transcodes both movies. Renaming one screen costs the
-whole tree. Not worth fixing today; worth knowing before anyone plans a naming
-pass.
-
-## 🔴 And a genuinely dangerous mistake, recorded because it nearly cost the session
-
-Killing a background check with `pkill -f "check-all"` matched **the container's
-own entrypoint**, whose command line contains the loop prompt — and that prompt
-mentions `check-all`. `pgrep` duly reported the process as still running after it
-had stopped, and a `pkill -9` on that pattern could have killed the session
-itself.
-
-**Match a process by its actual `comm`, or list with `ps` and check, before
-sending a signal.** A pattern that appears in your own instructions is not a
-pattern that identifies a process.

docs/re/INDEX.md

@@ -136,6 +136,7 @@ files, which is how the same ground got covered twice.
 | [`structures/stage-mission-tables.md`](structures/stage-mission-tables.md) | The stage table set — phases, routes, sub-objectives and AI parameters | ✅ the table set and how the stage record reaches it, validated across; **`AIParams` disc-wide: 23 objects, one shared 34-profile roster (782 records), loader `sub_8233C368`; `Type`→field-count holds except the two `_Test` templates** |
 | [`structures/texture-color-k8888.md`](structures/texture-color-k8888.md) | Texture colour interpretation — `k_8_8_8_8` (32bpp UI/HUD textures) | — |
 | [`ui-keyframe-time-unit.md`](ui-keyframe-time-unit.md) | What a keyframe time is worth, and what shape the ramp has |  ✅ CONFIRMED from the running game's own draw stream — the ramp is **linear** (a declared 15-unit fade lands on `round(255·k/15)` for all seven samples) and the animation clock advances **2 time units per submitted frame**. 🟡 the seconds conversion (`1 unit = 1/60 s`) rests on a measured 27.6 present-frames/second |
+| [`ui-keyframe-record-layout.md`](ui-keyframe-record-layout.md) | A keyframe's time word comes **before** its pose — the placement record, decoded | ✅ CONFIRMED, **decoded**. A group is an 8-byte header then `frames` records of `{u32 time; 36-byte pose}`, so the time precedes the pose; the group's lead-in word at `header+8` is pose 0's time and **every** pose is timed. Disc-wide over 13 991 groups in 33 archives, each test with a control: lead-in prepended is non-decreasing **13 991/13 991**; a non-zero lead-in is strictly below the next time **5 058/5 058** (control 70.9 %); a multi-segment alpha ramp runs at a constant `dα/dt` **857/1 540** against **0/1 042** under the old reading. 🔴 Retires two long-standing corpus claims — *"a group's data stops 4 bytes short of its final block's time slot"* and *"the last keyframe carries no time"* — both of which were this off-by-one. Adoption is free: all 12 `GP_TITLE` builds render byte-identically, and over 217 builds only two elements pick a different `rest()` pose, both between equally invisible ones. ❔ the executable's own parser was **not** found (the 40/60 stride query is weak, not negative) |
 | [`structures/ui-composable-bundles.md`](structures/ui-composable-bundles.md) | A screen build is not the only thing `compose` can draw |  ✅ CONFIRMED by measurement over the disc, with the artifact to |
 | [`structures/ui-focus-and-effect-elements.md`](structures/ui-focus-and-effect-elements.md) | `_eff` glow layers are not focused-state records |  ✅ CONFIRMED by measurement over all 965 screen builds on the disc, |
 | [`structures/ui-paint-order-key.md`](structures/ui-paint-order-key.md) | The paint order comes from a layer key in the T8aD sprite header |  ✅ CONFIRMED on both screens whose paint order has been measured — |
@@ -147,17 +148,22 @@ files, which is how the same ground got covered twice.
 | [`structures/unit-struct-runtime.md`](structures/unit-struct-runtime.md) | Runtime `Unit` struct (craft / vessel definitions) — read from live guest memory | — |
 | [`structures/weapon-struct-runtime.md`](structures/weapon-struct-runtime.md) | Runtime `Weapon` / `Shell` structs — read from live guest memory | — |
 | [`structures/xbg7-mesh.md`](structures/xbg7-mesh.md) | XBG7 — mesh geometry (inside XPR2 model containers) | — |
+| [`capture-harness-status.md`](capture-harness-status.md) | Why the harness stops reaching the title — and the two instruments that could not see the disc |  ✅ **the disc is BACK** (2026-08-29, container replaced at 11:07:38): `/disc` is a real 6.2 GB read-only mount and `screen list` returns 12 builds. The "no disc" section is withdrawn — and its two instruments were blind either way: `find / -xdev` cannot cross into a bind mount on another device, and `sylph-doctor` only ever looks under `/work`. Earlier sections: `screenshot` costs 10.8 s under xenia (92×), and `trace_gpu_stream` is a no-op in the Release build |
 | [`title-crash-stl-tree.md`](title-crash-stl-tree.md) | The title-screen crash is an STL `map`/`set` erase on a bad iterator |  ✅ CONFIRMED — the guest throws std::out_of_range from an STL |
 | [`ui-paint-order-third-permutation.md`](ui-paint-order-third-permutation.md) | A third measured paint order — tool built and validated, screen not reached |  ✅ the reader works and is CONFIRMED against both previously |
 | [`ui-quad-class-foothold.md`](ui-quad-class-foothold.md) | The guest's UI quad class — a foothold found from the capture's vertex layout |  🟡 PROBABLE for the identification below (it is a static read, but |
-| [`menu-navigation-semantics.md`](menu-navigation-semantics.md) | The title menu — how it moves, and where each button goes |  ✅ measured: wraps both ends, Ⓑ restores focus, ⬅➡ inert; 4 of 5 destinations driven. 🟡 GamePart id is a name match, ❔ `NEW GAME` untested |
+| [`menu-navigation-semantics.md`](menu-navigation-semantics.md) | The title menu — how it moves, and where each button goes |  ✅ measured: wraps both ends, Ⓑ restores focus, ⬅➡ inert; all 5 destinations driven. 🟡 GamePart id is a name match. 🟡 **Ⓑ leaving the MAIN menu downgraded 2026-08-29** — uncited, and the main menu is the only screen whose footer omits Ⓑ (0 glyph px in frame vs 514/518 elsewhere). ✅ **MISSION SELECT's stuck cursor was a LOCKED stage list** — labels have three brightnesses, locked 104 / unfocused 183 / focused 254 |
 | [`screen-transitions.md`](screen-transitions.md) | Between two screens — a fade through black, and where its timing lives |  ✅ the fade quad's keyframe group is decoded (disc-wide: per-pak all-or-nothing; `GP_TITLE` = the 6 screens, not the 6 overlays); the ~0.4 s fade-OUT is measured, not on the disc |
 | [`menu-audio-cues.md`](menu-audio-cues.md) | Menu audio — the event vocabulary is on the disc, the binding is not |  ✅ `SE_UI_*` cue names/ids decoded and `BANK_SE`→`Static.slb` (0/322 in FILES); 🟡 event binding is a name match; ❔ `Static.slb` has no wave boundaries, so SE audio is not extractable |
 | [`boot-config-and-gamepart-registry.md`](boot-config-and-gamepart-registry.md) | What the game reads at boot — `config.ini`, and which GameParts exist |  ✅ `config.ini` selects the language (the disc's only config); ❔ its `[SYSTEM]` is empty so the boot order is not in config; 🟡 24/29 ids bind to a class, `GP_ADVERTISE_DEMO` is never registered |
 | [`movie-binding.md`](movie-binding.md) | Which movie plays where — boot intro, attract loop, new-game intro |  ✅ decoded from the movie manifest (`ADVERTISE_MOVIE`→`ADV.wmv`, `MS00A`→`S00A.wmv`); attract identity confirmed independently by frame matching; 🟡 skippability unsettled |
 | [`ready-room-probe.md`](ready-room-probe.md) | S1 — the Ready Room probe: no-go, and not for the reason expected |  ✅ it is 2D and enumerates (60 builds), but the pak is briefing/tactical-map content; and `kind == 0x3002` finds 0 buttons there |
-| [`ui-title-build-map.md`](ui-title-build-map.md) | Which `GP_TITLE` build is which screen state |  ✅ CONFIRMED for title / `PRESS Ⓐ` / main menu / `EXTRAS` against live captures; the archive is 8 screens × EN/JP, and "6/8/9 are submenus" is withdrawn |
+| [`ui-title-build-map.md`](ui-title-build-map.md) | Which `GP_TITLE` build is which screen state |  ✅ CONFIRMED for title / `PRESS Ⓐ` / main menu / `EXTRAS` against live captures; the archive is 8 screens × EN/JP, and "6/8/9 are submenus" is withdrawn  ✅ **2026-08-29: the two "unidentified `DELTASABER` plates" are the LOADING screen** — builds 0/1 the plain variant, 10/11 the dressed one, decoded from their `pgloading_*` element names, and the executable (`sub_821C4EB0`, bytes checked in the image) names exactly five title-side screens: `TITLE_SCREEN`, `BUTTON`, `TITLE_MENU`, `LOADING`, `LOADING2`. 🟡 which loading bundle takes which of the two names is undecided. 🟡 the English member of a pair is the one in the first half of `GP_TITLE.p00` — 8/8 structurally, 3/3 where a capture can check it. |
 | [`ui-title-paint-order-capture.md`](ui-title-paint-order-capture.md) | The title screen's paint order, measured from the guest's draw submissions |  ✅ CONFIRMED — the order in which the running game paints the title |
 | [`upstream-baseline.md`](upstream-baseline.md) | A stock-upstream baseline runs Stage 02 crash-free |  ✅ CONFIRMED — upstream canary_experimental + only the pad |
 | [`weapon-datasheet-runtime.md`](weapon-datasheet-runtime.md) | Weapon DATA SHEET — runtime capture (Route B) |  🟡 first dynamic capture, 2026-07-28. The Arsenal's Gallery Mode panel is a |
 | [`xpr2-colour-check.md`](xpr2-colour-check.md) | XPR2 colours: channel order ✅ confirmed against the running game | — |
+| [`focus-ring-spin-measured.md`](focus-ring-spin-measured.md) | The main menu's focus ring spins continuously — and how fast | ✅ **measured**: period **2.177 s** over 9 revolutions (8 evenly spaced autocorrelation peaks) = 120 units = 60 frames = 2.00 s at 30 Hz. A pulse is excluded — annulus total conserved to 0.4 % while per-bin brightness swings by 24. ✅ the ring is the **only** moving thing on the settled main menu (std exactly 0.000 elsewhere). 🔴 no angle is quoted: the angular estimator FAILED its own control (30° → 0°) |
+| [`structures/slb-bank-header-not-a-wave.md`](structures/slb-bank-header-not-a-wave.md) | Why a music bank read as THREE sub-waves when the census says two | ✅ **decoded**: the third is the **bank header**, emitted by our own reader. `to_xma_riffs`'s hybrid branch derives a leading packet stream's start as `first_riff % 2048`, which is right only for a header shorter than one packet; a music bank's header is exactly **5 packets (10 240 B)**, so the modulus gave 0 and the whole header came back as sub-wave 0. The header states its own length at `+0x24` in blocks. Disc-wide over 9 519 `sound.pak` entries: **28** match the header signature at offset 0 (ids 1001–1023, 1101–1105), **28/28** end exactly at the first `RIFF`, **0** have a gap, **0** false positives — so a header at offset 0 and a leading packet stream never coexist. Decode control, same chain, same bank: the emitted region gives **0.009 s** against **87.744 s** for the real wave 0. Corroborated by the runtime XMA probe, which saw exactly two streams at the main menu. Fixed + 2 regression tests; the `VOICE_D_453` recovery is untouched (10/10 green) |
+| [`title-plate-delay-measured.md`](title-plate-delay-measured.md) | How long the boot title shows build 4 before the `PRESS Ⓐ` plate | ✅ **decoded after a refutation**: build 2 and build 4 run on **one clock started together**, and the plate's own `ptbtn00` reaches `a=255` at `t=238`; the last build-in ramp ends at `t=118`, so the interval is a declared **120 units = 2.000 s**. 🔴 The instruction that shipped first — "wait 2.13 s after build 4 settles" — was **refuted by the port** with disc arithmetic and is corrected in place; 🔴 `rest.t` is **not** when a screen settles (it is the last hold keyframe before the exit: `ptlogo1` rests at `t=251` and stops moving at `t=42`). ⚠️ The wall-clock 2.13 s is 6.7 % long because Canary presents at **28.06 / 28.14 fps** against a nominal 30, matching the corpus's independent **28.5 fps**; author the 120 units. ✅ **measured**, two independent boots: **2.138 s** and **2.132 s** from the frame build 4 settles (glyph = its no-plate 154, motion → 0). Agreeing to **6 ms**. So the boot title's end state is **not** plate-free and a compositor must draw **two builds at once**. ⚠️ Measure from *settled*, not from first pixels — "first drawn → plate" is 3.78 s vs 4.26 s across the same two runs, because the build-in animation's own duration varies with emulator frame pacing. Plate pulse re-measured at 2.12/2.19/2.34/2.31 s (mean 2.24), replicating the corpus's ≈2.3 s. ✅ black hold between screens bracketed at **0.14–0.30 s**, consistent with the declared 12 units. 🔴 the Ⓐ→menu latency is still **not** available: both runs freeze one frame for ~1.4 s at surface mean **26.626** — agreeing between runs to 1e-6, and reproduced with stream restarts disabled — which is a guest **load stall**, not the capture path. Probe: 8.7 ms/frame, 7.97/7.98 fps against a requested 8, controls 9/9 + 4/4 |
+| [`menu-idle-and-b-2026-08-29.md`](menu-idle-and-b-2026-08-29.md) | The main menu does not idle back to the title — and four durations that were a pipeline | ✅ **refuted**: no self-return in **≥ 60 s** untouched; the ~8–10 s idle belongs to the **title**. 🟡 Ⓑ→title ordering measured, latency not. 🔴 `classify_array` at **1503 ms/frame** drained an 8 fps stream at 0.64 fps and manufactured four latencies (24.66 s / 15.58 s / 25.60 s / 20.26 s) — all withdrawn; a backlog preserves ordering and destroys durations |

docs/re/REFUTED.md

@@ -617,3 +617,58 @@ neighbourhood, not just the line.
   `10 144 of 10 148 references resolve`) → **withdrawn; it is on the disc.** It is
   the `GP_STAGE_CLEAR` child the same scan named `8AX`. With the name decoded the
   count is **10 148 of 10 148**. [`ratc-child-names.md`](structures/ratc-child-names.md)
+
+## UI timing (2026-08-29)
+
+* "a screen has SETTLED at its `rest.t`" → **refuted.** `rest.t` is the last
+  *hold* keyframe before the exit, not the end of motion. Build 4's `ptlogo1`
+  rests at `t=251` and stops moving at **`t=42`**; the title's visible build-in
+  ends at `t≈118`, where `pteff01`, `pteff02.prm` and `ptlogoall_eff` end their
+  ramps together. Believing `rest.t` put a port's plate 3.97 s late —
+  [`title-plate-delay-measured.md`](title-plate-delay-measured.md).
+* "the `PRESS Ⓐ` plate is composited a measured 2.13 s after the title settles,
+  and the port should author that" → **the measurement stands, the instruction
+  was refuted by the port.** Build 2 has a keyframe group of its own; both builds
+  run on **one clock started together** and the plate's declared `t=238` supplies
+  the timing, so nothing is authored. `238 − 118 = 120 units = 2.000 s`, of which
+  2.13 s was a wall-clock reading stretched by Canary presenting at ~28.1 fps.
+  ⚠️ General lesson: **a wall-clock duration off this emulator is ~6 % long**, so
+  a measured interval that lands near a round number of units probably *is* that
+  number of units.
+* "a music bank has three sub-waves" → **refuted; it was our reader.** The third
+  is the bank header, emitted because `to_xma_riffs` derived a leading packet
+  stream's start as `first_riff % 2048` — valid only for a header shorter than
+  one packet. 28/28 disc-wide —
+  [`structures/slb-bank-header-not-a-wave.md`](structures/slb-bank-header-not-a-wave.md).
+
+## The oracle harness and the container (2026-08-29)
+
+* "the decoder container has no disc" → **refuted the same day.** The container
+  was replaced and `/disc` is a real 6.2 GB read-only mount. Worse, both
+  instruments behind the claim were blind to the answer either way:
+  `find / -xdev` **cannot cross** into a bind mount on another device, and
+  `sylph-doctor` only checks `/work` and never `$SYLPHEED_DISC`. "sylph-doctor
+  agrees" was two instruments sharing one blind spot.
+  → To test for the disc, ask the variable that names it:
+  `sylpheed-cli screen list "$SYLPHEED_DISC/dat/GP_TITLE.pak"`.
+* "the main menu returns to the title on its own after ~8–10 s idle" → **refuted.**
+  The menu sat untouched for **≥ 60 s** without moving (correlation never leaving
+  0.9245–0.9249). The ~8–10 s idle is real but belongs to the **title**. This was
+  the only reason "Ⓑ leaves the main menu" was classed as authored.
+* "whole-image statistics (green / white / mean) can tell the title from the
+  attract movie" → **refuted.** A frame of `ADV.wmv` with a bright green laser
+  reads green 0.0018 / white 0.086 / mean (53,67,76) — the title's numbers. A
+  probe built on it tapped Ⓐ into the movie and waited 120 s for a menu that was
+  never coming. → Correlate against a committed capture instead, and keep movie
+  frames as the negative controls.
+* "a 360-bin angular cross-correlation can measure the focus ring's rotation
+  angle" → **refuted by its own control**: a synthetic **30°** rotation of a live
+  frame came back as **0°** (peak 0.596), while 90/180/270° came back exactly
+  (peak 1.000) — it only resolves exact pixel permutations. No angle was quoted;
+  the spin was established from brightness conservation instead.
+* "a latency read off a classified `x11grab` stream is a duration" → **refuted.**
+  At 1503 ms per classification against an 8 fps stream the consumer ran at
+  0.64 fps, so frames were stale and increasingly so. Four "durations" died with
+  it. The tell was that a screen transition, a button press and a plate fade all
+  came out at ~20–25 s. → A backlog **preserves ordering and destroys
+  durations**; check consumed-fps against requested-fps before quoting a time.

docs/re/capture-harness-status.md

@@ -1,3 +1,62 @@
+# ✅ WITHDRAWN 2026-08-29 (later the same day) — the interactive title IS reachable here, twice, with no pad input
+
+**This banner supersedes everything below it about the title being unreachable,
+and it supersedes the 🔴 "Emulator-side questions are blocked" section of
+[MISSION](../port/MISSION.md).** Everything below is kept because the harness
+defects it diagnoses were real and the fixes are in use; what it concluded about
+the *game* is now refuted by measurement.
+
+**Two consecutive boots reached the interactive title, with the `PRESS Ⓐ BUTTON`
+plate, without a single pad press before it:**
+
+| | run 1 | run 2 |
+|---|---|---|
+| plate on screen at | **205.4 s** into the probe | **218.4 s** |
+| pad input before that | **none** | **none** |
+| Ⓐ then reached the main menu | ✅ | ✅ |
+| Ⓑ then returned to the title | ✅ | ✅ |
+
+Full per-frame traces, 8 fps, 1783 and 1886 frames:
+[`data/plate-timing-run1.tsv`](data/plate-timing-run1.tsv) ·
+[`data/plate-timing-run2.tsv`](data/plate-timing-run2.tsv). The measurement they
+were taken for is [`title-plate-delay-measured.md`](title-plate-delay-measured.md).
+
+So the standing negative — "three runs, two locales, two launch paths, ~35
+minutes of emulator time, no interactive title" — does not hold in this
+container today. **The attract loop is simply passed through in ~3.5 minutes and
+the title follows.**
+
+## ❔ What changed is NOT established, and I am not going to guess it
+
+What is different about this container, stated as facts rather than as a cause:
+
+* it came up with **no Xenia storage root at all** — no
+  `~/.local/share/Xenia`, so no profile, no `xconfig.settings`, and no shader
+  cache. The earlier runs signed in a profile that already existed.
+* run 1 therefore had to create one, with canary's own
+  `--create_profile_if_none=Decoder`. Run 2 signed in the profile run 1 made
+  (`B13EBABEBABEBABE`).
+* the launch was otherwise `boot_menu.sh`'s, minus `skip_intro.sh` — this
+  measurement had to leave the title untouched, so nothing tapped Ⓐ at all.
+
+⚠️ **A cold profile is a correlation across two runs, not a cause.** It is
+written down so the next session can test it directly (delete the storage root,
+boot, compare) instead of re-deriving that the title is reachable.
+
+## 🔵 What this unblocks
+
+* the **Japanese-locale capture** that MISSION parks as "🟡 needs one more run":
+  the mechanism (`set_console_language.py ja`, `user.language` at file offset
+  `0x912`) is in place, and the reason it was parked — *the title never
+  appears* — is gone. ⚠️ Note the storage root is new, so `xconfig.settings` has
+  been recreated and the byte offset should be re-located by its three landmarks
+  rather than assumed.
+* the two items MISSION lists as emulator-blocked: the gamma control behind
+  [tone curve](structures/ui-render-tone-curve.md), and separating `8AX` from
+  `ptbase` in [8AX](structures/ui-8ax-fullres-background.md).
+
+---
+
 # 🔴 Why the boot harness stopped reaching the title — `screenshot` costs 10.8 s
 
 **Status:** ✅ **diagnosed, with a control.** Four consecutive runs on
@@ -362,3 +421,173 @@ The gamma run's flags plainly took effect — that run is where
 `VdGetCurrentDisplayGamma` was captured — while its dump showed the file's
 values. So the dump reflects the config file and cannot confirm or refute a
 command-line override.
+
+---
+
+# ✅ 2026-08-29 (later) — the disc is back, and the section below is withdrawn as CURRENT status
+
+Kept for its history, not as a live claim. The container was replaced: PID 1
+here started at **11:07:38 UTC**, 25 minutes after commit `b9aca6a` wrote the
+section below at 10:42, and the replacement has the disc mounted.
+
+| check | result |
+|---|---|
+| `/proc/mounts` | `/dev/sda2 /disc ext4 ro,relatime` — a real bind mount |
+| device | `/disc` is device **2050**; `/` is device **92** |
+| size | 6.2 GB, 74 entries under `dat/`, `default.xex` = 3 497 984 B |
+| ISO | `/iso/game.iso`, 7 835 492 352 B |
+| end to end | `sylpheed-cli screen list /disc/dat/GP_TITLE.pak` → 12 builds, element/sprite counts matching the committed build map |
+
+⚠️ **Two instruments would have said "no disc" either way, and both are still
+in place.** This is the reusable lesson, and it is worth more than the
+resolved incident:
+
+* **`find / -xdev` cannot see `/disc`.** `-xdev` refuses to cross a filesystem
+  boundary; `/disc` is on a different device from `/`. The withdrawn section's
+  headline measurement — "no ISO, no `default.xex`, no `GP_TITLE.pak` anywhere"
+  — is what that command returns **whether or not the disc is mounted**. It had
+  no reach over the question it was used to answer.
+* **`sylph-doctor` never checks `$SYLPHEED_DISC`.** Its two disc lines are
+  `find /work -maxdepth 2 -iname '*.iso'` and `[ -d /work/sylph_extract/dat ]`
+  (lines 79–82). With the disc at `/disc` it reports "no ISO under /work" and
+  "no extracted disc — Reborn disc tests will SKIP" — as it does right now,
+  against a working disc. "`sylph-doctor` agrees" was two instruments sharing
+  one blind spot, not corroboration.
+
+**To check for the disc, ask the variable that names it**: `ls "$SYLPHEED_DISC/dat"`,
+or `sylpheed-cli screen list "$SYLPHEED_DISC/dat/GP_TITLE.pak"`, which fails
+loudly and cheaply.
+
+# 🔴 2026-08-29 — the disc is not in the decoder container at all *(WITHDRAWN — see the section immediately above)*
+
+**Status:** ✅ **diagnosed, root-caused in the launcher.** This supersedes every
+"the emulator did not reach the title" entry above as the *current* reason the
+oracle is unavailable: there is no game to run.
+
+## The measurement
+
+| looked for | result |
+|---|---|
+| `find / -xdev -iname '*.iso'` | **0** |
+| `find / -xdev -iname 'default.xex'` | **0** |
+| `find / -xdev -iname 'GP_TITLE.pak'` | **0** |
+| `$SYLPHEED_DISC` | **empty** |
+| `/work/sylph_extract` | does not exist |
+| `/exchange/files` | **empty** |
+
+`sylph-doctor` agrees and says so in its own words:
+
+```
+── project ──
+  ✖ /work/xenia-canary not mounted
+  ✖ /work/Syplheed-Reborn not mounted
+  ! no ISO under /work — run-canary needs SYLPH_ISO
+  ! no extracted disc — Reborn disc tests will SKIP
+```
+
+Everything else is healthy: `xenia_canary` is built and present, display `:98`
+is up, `screenshot` works, Vulkan (llvmpipe) enumerates, cargo and the python
+stack are fine. **The emulator has no disc to boot.**
+
+## The cause — the volume migration, and a mount nobody replaced
+
+Before [`06676d3`](#) the launcher bind-mounted the human's working tree:
+
+```
+-v "$PROJECT:$PROJECT"
+-v "$PROJECT:/work"
+```
+
+The ISO and `sylph_extract/` live in that tree, so the disc arrived **incidentally
+with the repository mount**, and `run-canary`'s `find "$PROJECT_DIR" -maxdepth 2
+-iname '*.iso'` found it.
+
+`06676d3` replaced that with the agent's own clone in a named volume —
+
+```
+-v "sylpheed-decoder-repo:/work"
+```
+
+— which is the right fix for the collision class it was written for, and it
+removed the disc along with the working tree. **Nothing was added to replace
+it.** The launcher still forwards
+
+```
+[ -n "${SYLPH_ISO:-}" ] && _out+=(-e "SYLPH_ISO=$SYLPH_ISO")
+```
+
+but that is an **environment variable with no bind mount behind it** — it names a
+host path that does not exist inside the container, so it cannot help.
+
+**The port container does not have this bug.** `docker/port/sylph-port` mounts
+the disc explicitly:
+
+```
+_out+=(-v "$DISC:/disc:ro" -e "SYLPHEED_DISC=/disc")
+```
+
+So the one container that *owns* the disc and the oracle is the one container
+without them.
+
+## Reach of the negative
+
+Whole-filesystem, single pass, `-xdev` per mount, three independent names (the
+ISO, the executable, a pak the corpus names constantly). The exchange volume is
+empty, so the disc is not arriving by `share` either. This is not "I looked in
+the usual place".
+
+## What it blocks — everything disc-side and everything dynamic
+
+* the **oracle** — no boot, no capture, no `run-canary`;
+* every `sylpheed-cli` invocation that names a pak — `screen list`, `screen info`,
+  `screen render`, `pak textures`;
+* `build-reborn test` — the disc-gated tests self-skip, and per MISSION a green
+  run then means almost nothing. (`build-reborn` is *also* pointing at
+  `/work/Syplheed-Reborn`, a path the monorepo no longer has.)
+* **static RE of the executable** — the XEX is on the disc, so the whole
+  PPC-disassembly route is shut too, not just the dynamic one.
+
+## What it does not block
+
+The committed corpus. `docs/re/captures/` is 99 MB of oracle frames and
+`docs/re/data/` 2.5 MB of extracted tables, both in git — enough to re-measure
+against captures, which is what this iteration did instead.
+
+## 🔵 For the human — the one-line fix
+
+Add a disc mount to `docker/decoder/sylph-decoder`, the way `sylph-port` already
+has one:
+
+```bash
+[ -d "$DISC" ] && _out+=(-v "$DISC:/disc:ro" -e "SYLPHEED_DISC=/disc")
+[ -f "$SYLPH_ISO" ] && _out+=(-v "$SYLPH_ISO:/disc.iso:ro" -e "SYLPH_ISO=/disc.iso")
+```
+
+Recorded rather than worked around, per *do not improvise around a blocker* —
+and **not attempted**, because the launcher runs on the host and this container
+cannot restart itself.
+
+⚠️ `sylph-doctor` reports the missing ISO as `!` (a warning) rather than `✖`. For
+the decoder that is not a warning: it is the difference between having an oracle
+and not having one.
+
+### A second, smaller consequence of the same migration — no git identity
+
+`git commit` in a fresh decoder container fails with *"Author identity
+unknown"*: nothing in the image, the entrypoint or `sylph-decoder` sets
+`user.name` / `user.email`, and the old bind mount used to bring the human's
+`.git/config` along with the tree.
+
+Set locally, per iteration if the volume is recreated:
+
+```bash
+git config --local user.name  "sylph-decoder"
+git config --local user.email "fabian@diekaulbachs.de"
+```
+
+⚠️ `push-work`'s header warns at length against `git config --local`, because
+the credential helper it wrote there leaked a container-only path onto the host.
+**That warning no longer applies to identity**: `/work` is a private named
+volume now, not a shared bind mount, so nothing written to its `.git/config`
+can reach a host checkout. The credential helper is still applied per-invocation
+with `-c`, and should stay that way.

docs/re/data/kf-record-census.txt

@@ -0,0 +1,14 @@
+paks scanned            : 33
+placement groups        : 13991
+
+A. lead-in prepended to the shifted times is non-decreasing
+   13991/13991 = 100.000%
+
+B. non-zero lead-in is strictly less than the next time
+   5058/5058 = 100.000%
+   control (another group's lead-in, same bundle): 35837/50580 = 70.852%
+   gap to the next time, most common: [(10, 2076), (1, 2022), (30, 116), (40, 80), (12, 78), (90, 78), (149, 78), (20, 78)]
+
+C. constant d(alpha)/d(time) across a multi-segment ramp
+   corrected (time precedes pose): 857/1540 = 55.649%
+   old       (+36 is own time)   : 0/1042 = 0.000%

docs/re/focus-ring-spin-measured.md

@@ -0,0 +1,119 @@
+# ✅ The main menu's focus ring spins continuously — period **2.18 s**, measured
+
+**Status:** ✅ **measured** (not on the disc as a period; the disc declares the
+ramp, the running game supplies the rate). Taken 2026-08-29 against Xenia Canary
+with the disc mounted at `/disc`.
+
+**Question this closes:** the port asked whether `ptbtneff01` — the 42×46 ring on
+the focused button — is *animated* while a button sits focused, or drawn once and
+held. It had shipped the ring at 0° and marked that known-wrong.
+[`structures/ui-button-focus-record.md`](structures/ui-button-focus-record.md)
+already said "the ring SPINS" from **one** frame showing it at a large angle;
+that is consistent with a continuous spin *and* with a static draw at a fixed
+angle, so it did not answer the question asked.
+
+## What the ring actually does
+
+Five single frames from one run, 4 s apart, focus held on `TUTORIAL` throughout:
+
+![five frames](captures/focus-ring/ring-single-frames-4s-apart.png)
+
+The ring carries a bright head, and the head is at a different angular position
+in every frame. It is still moving 16 s in, so it does **not** ramp once and
+stop.
+
+⚠️ **The 20 s mean of the same run is a uniform circle**
+([`ring-20s-mean-uniform.png`](captures/focus-ring/ring-20s-mean-uniform.png)) —
+that is the spin smearing itself out, and it is why an averaged frame must never
+be read as a single frame. A human looking at the live game sees the head; the
+average does not have one.
+
+## The measurement, and why it is not an angle
+
+🔴 **No angle is estimated anywhere.** The corpus's centroid estimator fails its
+own control by up to 19.8°, and a 360-bin angular cross-correlation written for
+this measurement **also failed its control** — a synthetic 30° rotation of a live
+frame came back as 0° (peak 0.596), while 90/180/270° came back exactly (peak
+1.000), i.e. the estimator only resolves the exact pixel permutations. It was
+therefore not used.
+
+What was used needs no angle. Two observables separate *rotation* from a
+*brightness pulse*, and both were taken in the same run:
+
+| observable | rotation predicts | pulse predicts | **measured** |
+|---|---|---|---|
+| total annulus brightness | conserved | varies | **0.4 % spread over 16 s** (5 frames); **0.53 %** over 359 frames |
+| per-angular-bin brightness | varies (a travelling feature) | varies together | **per-bin sd 24.2**, max 80.3, against a per-frame angular sd of 42.2 |
+
+Brightness moves *around* the annulus while the total holds. A pulse is excluded.
+
+The temporal standard deviation over 103 frames is **an annulus** and nothing
+else — dark inside, dark outside, peaking exactly on the ring's stroke
+(radial std: r 0–4 → 1.08, r 10–13 → **36.75**, r 20–26 → 1.18):
+
+![std annulus](captures/focus-ring/ring-temporal-std-annulus.png)
+
+⚠️ A positional *jitter* would smear variation outside the stroke. It does not:
+variation falls to ~1 both inside and outside, so the ring is not moving, it is
+turning.
+
+### The period
+
+A dense 359-frame filmstrip (24 s at **15.03 fps against a requested 15 fps** —
+the consumer kept up exactly, so these timestamps are not backlogged) gives the
+annulus's 360-bin profile per frame, correlated against frame 0. A rotating ring
+returns to itself once per revolution, so the trace's period **is** the spin
+period — again with no angle estimated.
+
+Autocorrelation local maxima, in seconds:
+
+```
+2.18  4.36  6.52  8.70  10.86  13.02  15.22  17.42
+spacings: 2.18 2.16 2.18 2.16 2.16 2.20 2.20     mean 2.177 s
+```
+
+**Eight consecutive evenly-spaced peaks over nine revolutions.** A drifting
+instrument cannot produce even spacing, which is the internal check on the
+number.
+
+Raw trace committed at [`data/focus-ring-period-corr.npy`](data/focus-ring-period-corr.npy)
+(rows: t, correlation-with-frame-0, annulus mean).
+
+### What the period is in the game's own units
+
+⚠️ **2.18 s is wall-clock under this emulator, and the emulator is not running
+the game at 30 Hz.** The corpus measures 27.6–28.8 fps here. `ptbtneff01`
+declares its first keyframe at **t = 120**, and under the settled reading
+(1 unit = 1/60 s, 2 units per rendered frame) 120 units is **60 rendered
+frames** — which at 27.6–28.8 fps spans **2.08–2.17 s**. The measurement sits at
+the top of that band.
+
+**So the spin is one revolution per 120 units = 60 frames = 2.00 s at a true
+30 Hz**, and no new constant is needed to account for it. 🟡 The 2.18 s is
+consistent with the declared 120 rather than a re-derivation of it: the guest
+frame rate was not measured in this same run, so the agreement is
+consistency, not closure.
+
+## Two other things the same run measured
+
+* ✅ **The focus ring is the ONLY moving thing on the settled main menu.** Over
+  103 frames / 20 s untouched, temporal std is **exactly 0.000** on every
+  unfocused button box, on the `NEW GAME` label, and on the `ptmsg` footer. Only
+  the focused button's box moves (std 4.46 against a background noise floor of
+  0.906). A port that draws the main menu statically plus a spinning ring is
+  drawing everything that moves.
+* ✅ **The ring is `ptbtneff01`, positionally confirmed.** Its centre was located
+  from the temporal-std map at game **(520.7, 339.7)**. The declared leaf offset
+  applied to button 3's rest position (542, 322) predicts **(521, 340)**. That
+  is a sub-pixel agreement between a decoded declaration and a live measurement,
+  and it is what ties the annulus to the record rather than to "a circle near the
+  cursor".
+
+## Reach
+
+* One run, one emulator, English locale, `GP_TITLE` build 5.
+* The period is measured on **one** focused button (`OPTIONS`, button 4) and the
+  spin is shown on a second (`TUTORIAL`, button 3). Not checked on all five, and
+  not checked on `EXTRAS`.
+* Says nothing about the direction of rotation — the estimator that would give a
+  signed angle failed its control and was not used.

docs/re/menu-idle-and-b-2026-08-29.md

@@ -0,0 +1,120 @@
+# 🔴 The main menu does NOT self-return to the title — and three "latencies" were my own pipeline
+
+**Status:** one ✅ **measured** negative, one 🟡 ordering-only result, and one
+🔴 **instrument defect that voids three numbers I took the same day.** Taken
+2026-08-29.
+
+## ✅ Refuted: "an ~8–10 s idle returns to the title" does not apply to the main menu
+
+HANDOFF's residue table downgraded *Ⓑ leaves the main menu* to **authored**, on
+the grounds that "an ~8–10 s idle also returns to the title, and nobody has
+separated the two". That reason is now gone.
+
+**Measured:** the main menu was held with **no input at all** and classified every
+~1.2 s by [`screen_match.py`](../../tools/re-capture/screen_match.py):
+
+| phase | duration untouched | screens seen |
+|---|---|---|
+| period capture | 24 s | menu only |
+| idle probe | **60 s** (49 samples) | **menu only** |
+
+Correlation against the committed main-menu capture never moved outside
+**0.9245 – 0.9249** across the whole idle window — not a drift, not a fade, a
+screen sitting still. Conservatively that is **≥ 60 s of continuous idle with no
+self-return**, against a claim of 8–10 s.
+
+✅ **And the 8–10 s idle is real — it belongs to the TITLE.** Immediately after
+this run, a probe that expected to find the title still on screen found it had
+left on its own into the attract movie. So the corpus's idle timer is a property
+of the **title screen** (title → `ADV.wmv` → title), and the residue table
+attached it to the wrong screen.
+
+**What this gives the port:** the idle alternative that made Ⓑ unprovable is
+refuted *on the screen in question*. Ⓑ is no longer competing with a timer there.
+
+## 🟡 Ⓑ on the main menu: the ordering survives, the timing does not
+
+Ⓑ was **delivered** — Canary's own log records `[file-pad] keystroke vk=5801
+down` / `up` and `XamInputGetKeystrokeEx -> user=0 vk=5801`, so this is not a
+dropped press. In both runs the menu was followed by the title, and in both runs
+**Ⓑ was the only input** in a window of ≥ 100 s either side.
+
+🟡 **But it is still two observations with a confound I cannot yet exclude**, and
+the reason is the next section: the "latency" I measured is worthless, so I
+cannot say the return followed Ⓑ *promptly*. What stands is ordering plus the
+absence of any other cause:
+
+* no input for ≥ 100 s before → no transition;
+* Ⓑ delivered → transition to the title.
+
+**Classification: measured ordering, unmeasured timing.** The port should keep
+Ⓑ→title, and it is now better supported than "authored" — but it is not yet a
+timed measurement.
+
+## 🔴 The defect: an oracle that cost 1503 ms per frame produced three fake latencies
+
+`screen_match.classify_array` does a ±8 px ZNCC search over a 675×1279 surface
+against two references. **Measured: 1503 ms per frame.** A probe calling it on
+every frame of an 8 fps `x11grab` stream therefore drained the pipe at
+**0.64 frames/s** — verified from the probe's own trace, 107 samples over 166 s.
+
+The pipe backed up at ~7.4 fps, so every frame classified was **stale, and
+increasingly so**. That is not a subtle bias; it manufactured three numbers:
+
+| reported | actually |
+|---|---|
+| plate appears 24.66 s after the title art | unknown |
+| Ⓑ → title in 15.58 s (run 1) | unknown |
+| Ⓑ → title in 25.60 s (run 2) | unknown |
+| Ⓐ → menu in 20.26 s | unknown |
+
+🔴 **All four are withdrawn.** The tell was that they are all ~20–25 s: a screen
+transition, a button press and a plate fade do not share a duration, but a
+backlog does. The two Ⓑ figures *growing* 15.6 → 25.6 s across a longer run is
+the backlog accumulating, and it is the signature to remember.
+
+⚠️ **What a backlog does and does not destroy.** It delays every frame by the
+same growing amount, so it **preserves ordering** and destroys **durations**.
+That is why the ordering results above survive and every duration here does not.
+
+✅ **Fixed and re-controlled.** `screen_match` now has a `fast=True` path
+(4× decimation, ±2 decimated px) at **38–75 ms**, a 20–60× reduction, and the
+control was re-run on **both** paths: 8/8 each, with the fast path agreeing with
+the exact path to **±0.005** on every score.
+
+✅ **The ring measurements are NOT affected**, and this was checked rather than
+assumed: `ring_period.py` does a greyscale conversion and a crop per frame, and
+achieved **15.03 fps against a requested 15** — it kept up exactly, so its
+timestamps carry no backlog. Its period also has an internal check a drifting
+clock cannot pass: eight *evenly spaced* autocorrelation peaks
+([`focus-ring-spin-measured.md`](focus-ring-spin-measured.md)).
+
+## 🟡 The `PRESS Ⓐ` plate: sequence answered, duration not
+
+The port asked whether the boot title is build 4 alone, build 4 with the plate
+composited from the start, or build 4 **then** the plate after a delay.
+
+✅ **It is the third.** On the boot title the green-Ⓐ glyph count went
+**154 → 781** with the title art already matching at 0.946. The 154 is the
+decisive number: the committed no-plate capture
+`live-title-build4-no-plate.png` reads **159** with the same counter, and plate
+titles read 753 / 977 / 1493. So the title genuinely presents **without** the
+plate first, and the plate arrives afterwards.
+
+🔴 **How long afterwards is NOT measured** — that figure came from the backlogged
+probe and is withdrawn with the rest. The port needs one more run with the fast
+path to get it.
+
+## Instrument controls, now committed
+
+The negative controls for `screen_match` are **movie frames**, because that is
+the class the oracle exists to reject — a statistics-based oracle
+(green/white/mean) called a frame of `ADV.wmv` containing a bright green laser
+`title`, and a probe built on it tapped Ⓐ into the movie and then waited 120 s
+for a menu that was never coming.
+
+An earlier version of the control list pointed at two **scratch** grabs, and a
+later run of the same probe overwrote one of them — turning a negative control
+into a title frame and failing the control for the wrong reason. They are now
+committed fixtures under
+[`captures/instrument-controls/`](captures/instrument-controls/).

docs/re/menu-navigation-semantics.md

@@ -23,8 +23,8 @@ with [`tools/re-capture/menu_focus.py`](../../tools/re-capture/menu_focus.py).
 | **wrap at the bottom** | ⬇ from the last item goes to the **first** | same, panels 3→4, and 4 presses from `EXTRAS` landing on `OPTIONS` — i.e. wrapping — is what makes the count come out |
 | **left / right** | **nothing**, on the main menu | cursor unmoved across one ⬅ and one ➡ |
 | **Ⓑ on a submenu** | returns to the parent **with focus restored to the item you entered from** — `LOAD GAME`→`LOAD GAME`, `TUTORIAL`→`TUTORIAL`, `OPTIONS`→`OPTIONS`, `EXTRAS`→`EXTRAS` | 4/4 |
-| **Ⓑ on the main menu** | goes to the **title**, which re-draws `PRESS Ⓐ BUTTON` after a beat | |
-| **Ⓑ on the title** | **nothing** | |
+| **Ⓑ on the main menu** | 🟡 goes to the **title**, which re-draws `PRESS Ⓐ BUTTON` after a beat | **none** — and the main menu's own footer does not advertise Ⓑ; [downgraded below](#-refutation-attempt-2026-08-29--the-main-menus-own-footer-does-not-advertise-ⓑ) |
+| **Ⓑ on the title** | 🟡 **nothing** | **none** |
 
 Wrap holds on both screens tested — the 5-item main menu and the 3-item `EXTRAS`
 submenu — so it is a menu rule, not a per-screen table.
@@ -48,7 +48,7 @@ Measured by driving: focus the item, press Ⓐ, read the screen's own title.
 | `TUTORIAL` | the lesson list, `TUTORIAL`, Level 1 / Level 2 | same, middle | 🟡 `25 GP_TUTORIAL` |
 | `OPTIONS` | `OPTIONS` — GAME / CONTROL / SOUND / SCREEN SETTINGS / BACK | same, right | 🟡 `8 GP_OPTIONS` |
 | `EXTRAS` | **`GP_TITLE.pak` build 6** — MISSION SELECT / MOVIE THEATER / BACK | [`ui-title-build-map.md`](ui-title-build-map.md) | 🟡 `5 GP_EXTRAS` |
-| `EXTRAS ▸ MISSION SELECT` | the stage list + Wide Area Space Map | | 🟡 `7 GP_MISSION_SELECT` |
+| `EXTRAS ▸ MISSION SELECT` | the stage list + Wide Area Space Map — **8 rows visible of 16**, and rows below the first are **locked** on a fresh save ([below](#-mission-select-the-cursor-was-stuck-because-the-stages-were-locked)) | [`mission-select-stage01-only.png`](captures/mission-select-stage01-only.png) | 🟡 `7 GP_MISSION_SELECT` |
 | `EXTRAS ▸ MOVIE THEATER` | ❔ not tested | | 🟡 `6 GP_MOVIE_THEATER` |
 
 **Say which, as the gate asks.** The *screen* each button opens is **measured** —
@@ -134,3 +134,109 @@ with nothing about `NEW GAME`. 🟡 n = 1 either way; do not read it as "fixed".
 Worth recording because the first observation could easily have hardened into
 "the new-game path crashes", which is what "A on NEW GAME hangs" had already
 become once.
+
+---
+
+## 🟡 Refutation attempt 2026-08-29 — the main menu's own footer does **not** advertise Ⓑ
+
+**Attempted claim:** this page's row *"Ⓑ on the main menu goes to the title,
+which re-draws `PRESS Ⓐ BUTTON` after a beat"*.
+
+**Why this row and not another.** It is one of only **two** rows in the Q5 table
+with an **empty evidence cell** (the other is "Ⓑ on the title → nothing"); every
+row that cites a capture cites one. And it is a rule the port will build on
+directly — it is the only way out of the main menu.
+
+**The measurement** — whole-frame colour test for the pad-glyph discs, run by
+[`tools/re-capture/footer_and_locked_rows.py`](../../tools/re-capture/footer_and_locked_rows.py)
+against the committed captures:
+
+| capture | Ⓐ glyph px | Ⓑ glyph px |
+|---|---|---|
+| `live-main-menu.png` | 438 | **0** |
+| `live-main-menu-options-focused.png` | 438 | **0** |
+| `live-extras.png` | 440 | 514 |
+| `difficulty-screen.png` | 438 | 518 |
+
+**The control passes twice over.** The same detector, unchanged, finds the red Ⓑ
+on the two screens that visibly have one; and the **Ⓐ** count is 438/438/440/438
+across all four, i.e. the same glyph asset at the same size on every screen — so
+a Ⓑ of that family would have been ~450–520 px and cannot have fallen under a
+threshold. The negative is over the **whole frame**, not a guessed footer band:
+`live-main-menu.png` contains **zero** red-glyph pixels anywhere.
+
+So the main menu's legend reads `⊙ : Select   Ⓐ : OK` where every submenu reads
+`⊙ : Select   Ⓐ : OK   Ⓑ : Back`.
+
+**Verdict: the claim SURVIVES, at reduced confidence, and the row is downgraded
+to 🟡.** A legend is not behaviour — a game may accept an unadvertised Ⓑ — so an
+absent glyph cannot refute a press that was actually observed. But:
+
+* the observation has **no capture behind it**, and it is now the only Q5 row
+  contradicted by the game's own on-screen text;
+* there is a **named confound**: the title-side screens auto-return on idle, and
+  "I pressed Ⓑ and ended up at the title, which drew `PRESS Ⓐ BUTTON` after a
+  beat" is also exactly what an idle timeout looks like to an observer who does
+  not hold the two apart. The corpus documents that timeout at ~8–10 s
+  ([`boot-config-and-gamepart-registry.md`](boot-config-and-gamepart-registry.md)).
+
+**What would settle it:** press Ⓑ on the main menu and read `0x828A690C`, the
+live screen id (`1` title, `3` main menu, `4` extras) — a transition inside a
+second is a Ⓑ, one at ~8–10 s regardless of the press is the timeout. Cheap, and
+it needs no screenshots.
+
+🔴 **Not runnable here.** This container has no disc and no ISO, so there is no
+oracle at all — see
+[`capture-harness-status.md`](capture-harness-status.md#-2026-08-29--the-disc-is-not-in-the-decoder-container-at-all).
+
+**For the port:** Ⓑ from the main menu to the title is **measured, single
+observation, uncited, and unadvertised by the game**. Implement it — it is the
+only exit — but treat it as authored rather than transcribed, and do not also
+build the idle-return on the assumption that the two are distinct until someone
+has separated them.
+
+---
+
+## ✅ MISSION SELECT: the cursor was stuck because the stages were **locked**
+
+**Measured 2026-08-29 from committed captures**, no disc needed. Settles the
+⚠️ open in [`../game/navigation.md`](../game/navigation.md): *"sixteen d-pad
+presses never left Stage 01 — whether that is because only one stage was
+unlocked, or because the list is driven some other way, is unknown"*.
+
+The stage list has **three** label brightnesses, not two, and that is what
+discriminates. Sampling the label strip (x 190…320) of each of the 8 visible
+rows, 95th percentile of luminance:
+
+| capture | row 1 | rows 2–8 |
+|---|---|---|
+| `mission-select-stage01-only.png` | **254** | **104** |
+| `mission-select-all-story-unlocked.png` | **254** | **183** |
+| `mission-select-ends-at-stage16.png` | 183 | 183 ×6, then **254** on row 8 |
+
+* **254** = focused (the row carrying the spinning focus ring)
+* **183** = unlocked, not focused
+* **104** = **locked**
+
+The all-unlocked capture is the control: it holds row 1 focused at the identical
+254 while rows 2–8 move 104 → 183 as one uniform step. So the dim rows in the
+Stage01-only capture are **not** "unfocused"; unfocused is 183, and they are
+79 levels below it.
+
+**And the cursor does move when they are unlocked.** In
+`mission-select-ends-at-stage16.png` the list has scrolled to show Stage09…16,
+the scrollbar thumb is at the bottom, and the focus ring is on **Stage16** — the
+last row. Locked list: 16 presses, no movement. Unlocked list: the cursor reaches
+the end.
+
+| | |
+|---|---|
+| **rows visible at once** | **8** |
+| **list length** | **16** (`Stage01`…`Stage16`; the scrollbar bottoms out at 16) |
+| **why 16 presses did nothing** | every row below the first was locked |
+
+⚠️ **Reach.** This is a still image, so it says the cursor *reached* Stage16, not
+how it got there and not whether the list wraps — the scroll thumb bottoming out
+at row 16 is consistent with either. Whether a *locked* row is skipped or simply
+unreachable is likewise not separated: with only row 1 unlocked the two are the
+same observation.

docs/re/present-rate-instrument-failed.md

@@ -0,0 +1,115 @@
+# 🔴 I cannot measure this emulator's presentation rate — and the 2 % between two of my pages is not a disagreement about the game
+
+**Status:** one 🔴 **instrument failure** (recorded, not published as a number),
+and one ✅ **resolution of a challenge** that follows from it. 2026-08-29.
+
+## The challenge
+
+The port put two of my pages against each other. Both measure the same declared
+quantity — **120 keyframe units of wall clock during a static hold, in Canary** —
+and they differ by 2 %:
+
+| page | measured | implied presentation |
+|---|---|---|
+| [`title-plate-delay-measured.md`](title-plate-delay-measured.md), settle→plate, 2 runs | 2.138, 2.132 → **2.135 s** | 28.10 fps |
+| [`focus-ring-spin-measured.md`](focus-ring-spin-measured.md), 7 spacings | 2.16 … 2.20 → **2.177 s** | 27.56 fps |
+
+0.042 s apart — seven times the 6 ms run-to-run agreement the plate page rests
+on. Its own corroboration argument (*"the build-in is where frames are dropped;
+the static hold is not"*) is aimed at exactly this, and these are two static
+holds. Fair challenge.
+
+## ✅ The resolution: 2 % is far inside this emulator's own variation
+
+The question assumes the wall clock is stable enough for 2 % to mean something.
+It is not, and the counterexample is the same interval, in the same container, on
+the same day:
+
+| run | conditions | settle → plate |
+|---|---|---|
+| 1 | 8 fps grab | **2.138 s** |
+| 2 | 8 fps grab | **2.132 s** |
+| **3** | 8 fps grab **+ `--log_ui_draws=true`** | **2.549 s** |
+
+**A 19 % swing on the declared interval, from a logging flag.** The 2 % the two
+pages differ by is a fifth of that. They were taken in different sessions under
+different load, and nothing in either can separate "the game timed it
+differently" from "the emulator ran slower" — because both are wall clock.
+
+**So the two pages were never in conflict about the game.** They are three
+readings of one declared quantity through a clock that moves. What settles the
+quantity is the disc: `t=118 → t=238` is 120 units, and the port's own structural
+rule for the ring (two keyframes differing only by a 360° rotation, first timed
+and second untimed — 16/212 elements matched, all of them focus rings) gives the
+ring's period the same way.
+
+⚠️ **This removes the evidence that the ring is not 120 units. It does not prove
+that it is.** The disc-side rule does that, and it is the port's, not mine.
+
+## 🔴 The instrument I built to answer it properly, and why it is dead
+
+Wall clock cannot separate the two hypotheses; **frames** can. So I tried to
+measure the presentation rate.
+
+### Canary's own frame counter perturbs by a third
+
+`--log_ui_draws=true --ui_draw_capture_frames=N` logs `[UI-CAP] capture armed`
+and `[UI-CAP] done: D draws over F frames`. This is the instrument that produced
+the corpus's **28.5 fps** ([`ui-keyframe-time-unit.md`](ui-keyframe-time-unit.md)).
+
+Measured here, armed on the title with a concurrent 8 fps grab:
+
+> **300 frames in 16.567 s = 18.11 fps**, against ~28 for the same screen without
+> it.
+
+⚠️ **A frame counter that costs a third of the frame rate cannot measure the
+frame rate.** This does not overturn the 28.5 fps — that run had no concurrent
+grab — but it does mean the figure is a **lower bound taken under its own
+instrument's load**, and it should not be treated as *the* rate.
+
+### And the unperturbing replacement FAILED its own decisive control
+
+The alternative: count **distinct frames** in an oversampled crop of something
+that moves every frame (the spinning focus ring). At 60 fps against a source
+presenting at R, the fraction of consecutive samples that differ is R/60.
+
+Three controls were written before the run. It failed the one that matters:
+
+| control | result |
+|---|---|
+| a static crop must read ≈ 0 | **2.63 fps of "change"** — not clean |
+| two sampling rates must agree | 45 fps → **12.73**, 60 fps → **12.08** ✅ |
+| **must agree with the game's own counter while both run** | counter **15.88** vs `[UI-CAP]` **17.59** — **10 % low** 🔴 |
+
+The third is decisive and it is a failure: **the ring does not change on every
+presented frame**, so the counter measures the ring's animation rate, not the
+presentation rate. It also drifted 12.1 → 15.9 → 18.1 across one session, which
+a real rate estimator on a settled screen should not do.
+
+**Dead, not tuneable** — per [`METHOD.md`](METHOD.md). No rate is published from
+it. Controls preserved:
+[`data/present-rate-controls-2026-08-29.json`](data/present-rate-controls-2026-08-29.json).
+
+## What this means for the port, and for everything I hand over
+
+**Do not take a wall-clock duration off this container as a game constant.**
+Demonstrated range for one declared interval: 2.13 – 2.55 s, and the emulator's
+own rate read anywhere from 12 to 28 fps depending on what was watching it.
+
+The rule that follows: **a measured interval landing near a round number of
+declared units almost certainly IS that number of units**, and the units are what
+to ship. Wall clock is for ordering and for sanity, not for constants.
+
+## Reach
+
+* One container, one day, one machine. It says nothing about how a different host
+  runs Canary, and nothing about hardware.
+* It does **not** refute the 28.5 fps in `ui-keyframe-time-unit.md`; it reclassifies
+  it as a load-dependent lower bound.
+* ❔ **The game's true update rate is still not grounded in the disc.** "2 units
+  per submitted frame" *is* grounded — it was read off a frame-indexed draw
+  capture, so it is independent of how fast the emulator runs. What rests on the
+  emulator is only the step from *a submitted frame* to *1/30 s*, i.e. the
+  present interval. That is a constant in the executable, and reading it is
+  blocked on the missing disassembly route
+  ([`static-route-recovered.md`](static-route-recovered.md)).

docs/re/static-route-recovered.md

@@ -0,0 +1,104 @@
+# 🟡 The static PPC route was lost with the container migration — the image is back, the disassembly is not
+
+**Status:** ✅ the **image** is recovered and validated; 🔴 the **disassembly
+database** it is analysed with does not exist in this repository at all, and
+never did. 2026-08-29.
+
+## What broke
+
+Four tools in `tools/re-capture/` open a DuckDB database at
+`/work/xenia-rs/sylpheed.db` — `name_block_bases.py`, `archive_naming.py`,
+`isl_cmdtab.py` and the census work that produced most of the `sub_82xxxxxx`
+findings in [`INDEX.md`](INDEX.md). In this container:
+
+```
+$ ls /work/xenia-rs
+ls: cannot access '/work/xenia-rs': No such file or directory
+```
+
+🔴 **And nothing in the repository builds it.** A grep for `duckdb` finds only
+*consumers*; there is no disassembler, no PPC decoder vendored, and `capstone` is
+not installed (and `pip install` is refused here by PEP 668). So the static route
+is four read-only clients of a producer that is not in the tree.
+
+⚠️ **This is not a small gap.** Every finding that cites a function address —
+the GamePart registry, the challenge gate, the ISL command table, `PlayerParams`,
+the boot sequencer — is currently **unre-checkable in this container**. They are
+not wrong; they are unverifiable, which is a different and quieter problem.
+
+## `default.xex` is not a substitute
+
+The disc's executable is encrypted and LZX-compressed:
+
+```
+$ xxd -l 16 /disc/default.xex
+00000000: 5845 5832 0000 0001 0000 3000 ...  XEX2......0.
+$ strings -a /disc/default.xex | grep -c GamePart
+0
+```
+
+The header is intact — `XEX2`, media id `535107D4`, original PE name
+`default.pe` — and everything after it is noise. No decrypt/decompress exists in
+the tree either.
+
+## ✅ What is recovered, and how it is validated
+
+Xenia decrypts, decompresses and relocates the image at load, so a **running
+guest holds the flat VA image** the corpus calls the `.pe`
+(`VA = 0x82000000 + offset`). `tools/re-capture/dump_image.py` reads it straight
+out of `/dev/shm/xenia_memory_*` — no debugger, no emulator patch, no pause.
+
+```
+$ tools/re-capture/dump_image.py /sylph-home/re/sylpheed-image.pe
+wrote ... 4194304 bytes  VA 0x82000000..0x82400000
+validated: GamePart id table + D3D runtime strings; 1013/1024 non-empty 4K pages
+```
+
+**The validation is the corpus's own landmarks, not the tool's.** A mis-based or
+partial dump fails both:
+
+* `0x820A1630` holds the **GamePart id table** — 29 `.rdata` pointers resolving
+  to `GP_TITLE` (0) … `GP_TEST` (28), with `GP_CHALLENGE` at **26**, exactly as
+  [`challenge-mission-gate.md`](challenge-mission-gate.md) records;
+* the image carries the **Xbox 360 D3D runtime's own error strings**
+  (`ERR[D3D]: Unanticipated CPU_INTERRUPT`, `D3D9D.LIB`), which only the real
+  loaded executable has.
+
+So string search, table dumps and pointer chasing work again today. **What does
+not** is anything needing decoded instructions: no `mnemonic`/`operands`, so no
+xref search, no base solving, no call graphs.
+
+⚠️ It also depends on a **booted emulator**, which is a bad dependency for the
+foundation of the static corpus. Dump once and keep the file.
+
+## 🔵 For the human — what is actually needed
+
+Not the image; that is solved. What is missing is the **producer of the
+database**, and its schema, which the four consumers pin exactly:
+
+| table | columns used |
+|---|---|
+| `functions` | `address`, `end_address`, `name` |
+| `instructions` | `address`, `mnemonic`, `operands` |
+| `strings` | `address`, `content` |
+
+An XEX unpacker would also be worth having on its own, so the static route stops
+needing a running emulator to bootstrap.
+
+## What it blocks right now
+
+The one open question this iteration wanted it for: **the game's present
+interval**, i.e. the step from *one submitted frame* to *1/30 s of real time*.
+
+"2 units per submitted frame" is already grounded and emulator-independent — it
+was read off a frame-indexed draw capture
+([`ui-keyframe-time-unit.md`](ui-keyframe-time-unit.md)). The remaining link is
+`D3DPRESENT_PARAMETERS.PresentationInterval` at device creation: `_ONE` means the
+game runs at the console's 60 Hz vblank, `_TWO` at 30. That is a constant loaded
+into a register, so **finding it needs disassembly, not string search** — the
+image contains the D3D runtime but the interval is an immediate, not a string.
+
+Settling it would move Q1's seconds-per-unit from **measured** to **decoded**,
+and it is the only part of the UI clock still resting on a wall clock this
+container has now been shown to move by 19 %
+([`present-rate-instrument-failed.md`](present-rate-instrument-failed.md)).

docs/re/structures/bgm-two-stems.md

@@ -21,7 +21,16 @@ BGM_001.slb   (9 178 040 B)
 ```
 
 A bank is a 10 240-byte header and then **exactly two waves**, and the two always
-have the **same duration** — different byte sizes and different bitrates, same
+have the **same duration**
+
+⚠️ **Our own reader disagreed with this page until 2026-08-29, and the page was
+right.** `slb::to_xma_riffs` was emitting that 10 240-byte header as a third
+sub-wave, so `sound_bank_riffs("BGM_103.slb")` returned **three** — which the
+port caught while exporting the menu music. The header is not a wave (it decodes
+to 0.009 s and is 99.1 % zero); the cause was a modulus that assumes a bank
+header is shorter than one 2048-byte packet, and it is fixed with a disc-wide
+28/28 check —
+[`slb-bank-header-not-a-wave.md`](slb-bank-header-not-a-wave.md) — different byte sizes and different bitrates, same
 number of seconds. Duration is `data_size / PsuedoBytesPerSec` (the u32 at
 `RIFF+0x20`; `RIFF+0x24` is the sample rate, 48 000 Hz except `BGM_020`–`023`
 at 44 100).

docs/re/structures/slb-bank-header-not-a-wave.md

@@ -0,0 +1,121 @@
+# ✅ A music bank's "third sub-wave" is its **header**, and the bug was arithmetic
+
+**Status:** ✅ `CONFIRMED` — **decoded**, with a disc-wide check over all 9 519
+`sound.pak` entries, a decode control, and independent corroboration from the
+running game. Fixed in `sylpheed-formats` 2026-08-29.
+
+**Raised by the port**, on its P6 critical path:
+`sound_bank_riffs("BGM_103.slb")` returned **three** sub-waves against
+[`bgm-two-stems.md`](bgm-two-stems.md)'s census, which says a music bank is
+exactly two. Its exporter was summing all three, so the shipped menu music was
+the sum of three things where the corpus predicted two. It declined to choose
+which to drop, which was right — that is a decoding question.
+
+## The answer
+
+The third thing is **the bank header**. Not a stem, not an artefact of the disc:
+our own reader was emitting it.
+
+`to_xma_riffs` has a hybrid branch for banks that carry a headerless packet
+stream *before* their first `RIFF` — the fix that recovered `VOICE_D_453`'s line
+([`slb-data-offset.md`](slb-data-offset.md)). It derives that stream's start as
+
+```rust
+first_riff % XMA1_PACKET      // XMA1_PACKET = 2048
+```
+
+which is correct **only when the bank header is smaller than one packet**. It is,
+in the voice banks the branch was written for: their headers put the first `RIFF`
+at 1392, 1468, 1600 or 1728 mod 2048.
+
+A music bank's header is **exactly five packets — 10 240 bytes** — so the
+modulus returns **0**, and the branch emitted `slb[0..10240]`: the whole header,
+as sub-wave 0.
+
+The header states its own length, so nothing here needs a heuristic:
+
+```
+BGM_103.slb
+  +0x00  BE u32   1103        bank id
+  +0x18  BE u32   0x00000800  block size = 2048
+  +0x1c  BE u32   7839244     data size
+  +0x20  BE u32   1103        the id again  ← signature, with +0x18
+  +0x24  BE u32   5           HEADER LENGTH IN BLOCKS  → 5 × 2048 = 10240
+  +0x28  BE u32   0x00100002  16 bit / 2 ch
+```
+
+## The disc-wide check
+
+Over all **9 519** entries of `sound.pak`
+([`tools/re-capture/slb_segment_phase.py`](../../../tools/re-capture/slb_segment_phase.py)
+supplies the reader):
+
+| | |
+|---|---|
+| entries matching the header signature at offset 0 | **28** |
+| ...whose declared header ends **exactly** at the first `RIFF` | **28 / 28** |
+| ...with a real gap between header and first `RIFF` | **0** |
+| false positives among the 9 491 others | **0** |
+
+The 28 are exactly the music banks — ids **1001–1023** and **1101–1105**. So on
+this disc a bank header at offset 0 and a leading packet stream **never
+coexist**, and the guard is not a threshold: if a bank states a header, believe
+it, and there is nothing before the first `RIFF`.
+
+⚠️ `BGM_106`–`BGM_109` are **not** in the 28 and must not be: their pak entries
+start mid-bank, so they have no header at offset 0 and their leading region is
+real audio (the tail of the previous bank). That is the same straddle
+[`bgm-two-stems.md`](bgm-two-stems.md) already documents.
+
+## The decode control
+
+Decoding the emitted region proves it is not audio, and the control is run
+through **the same chain, on the same bank, in the same invocation**:
+
+| | bytes | PCM decoded |
+|---|---|---|
+| `BGM_103` — what we emitted as "sub-wave 0" | 10 240 | **0.009 s** |
+| `BGM_103` — its real wave 0 (control) | 3 876 864 | **87.744 s** (declared 87.75) |
+| `BGM_001` — what we emitted as "sub-wave 0" | 10 240 | **0.009 s** |
+| `BGM_001` — its real wave 0 (control) | 4 466 688 | **173.809 s** (declared 173.82) |
+
+FFmpeg `xma1`, mono/stereo taken from the bank's own `fmt `. The region is also
+**99.1 % zero bytes** (67–93 non-zero of 10 240 across the 28 banks) and its last
+non-zero byte is at 6431, so its final 1.86 packets are entirely empty.
+
+## Corroboration from the oracle, which was already in the corpus
+
+[`bgm-two-stems.md`](bgm-two-stems.md) records that at the **main menu**, with
+`--xma_param_probe=true`, the decoder was handed **two** stereo 48 kHz streams —
+of **3 876 864** and **3 930 112** bytes, byte-for-byte `BGM_103`'s two declared
+waves. A third stem would have been a third stream. The running game was already
+saying two.
+
+## The fix
+
+`slb::bank_header_len` (new, `pub`) reads the signature and returns the declared
+length; the hybrid branch uses it in preference to the modulus:
+
+```rust
+let start = bank_header_len(slb).unwrap_or_else(|| leading_data_offset(ri));
+if ri > start { /* emit the leading stream */ }
+```
+
+Two regression tests in
+[`tests/slb_leading_segment_disc.rs`](../../../crates/sylpheed-formats/tests/slb_leading_segment_disc.rs):
+the disc-wide 28/28 identity, and `BGM_103`/`BGM_001` returning exactly two
+sub-waves at their declared payload sizes. The pre-existing voice-bank tests —
+`broken_banks_recover_their_line`, `derived_offset_recovers_voice_banks_without_regressing_etc`
+— still pass, so the `VOICE_D_453` recovery is untouched. 10/10 green with
+`SYLPHEED_DISC` set.
+
+## Reach
+
+* The 28 are the only banks on the disc that state a header at offset 0. A bank
+  format elsewhere with a header ≥ 2048 B that we have not seen would have had
+  the same bug; nothing on this disc does.
+* This says nothing about **which** of the two remaining waves is which — that is
+  still 🟡 in [`bgm-two-stems.md`](bgm-two-stems.md) (surround-rear pair vs a
+  second intensity layer), and both readings predict playing them together.
+* It does not change the count for any voice bank: `VOICE_*` entries have no
+  header at offset 0, so their leading region is emitted exactly as before.

docs/re/title-plate-delay-measured.md

@@ -0,0 +1,213 @@
+# ✅ The boot title shows build 4 alone for **2.13 s**, then composites the plate
+
+**Status:** ✅ **measured** — two independent boots of the real game in Xenia
+Canary, 2026-08-29. Not on the disc as a delay: build 2 (the `PRESS Ⓐ BUTTON`
+plate) is an overlay with no fade quad of its own, and nothing in either
+bundle's keyframe group carries the gap between them.
+
+**Question this closes:** the port asked which of three things the boot title is
+— build 4 alone, build 4 with the plate composited from the start, or build 4
+**then** the plate after a delay — because the third case is the only one where
+`ScreenView` has to draw **two builds at once**, which it has never done. The
+sequence was already answered (it is the third,
+[`menu-idle-and-b-2026-08-29.md`](menu-idle-and-b-2026-08-29.md)); **the delay
+was withdrawn the same day** and is what this page supplies.
+
+## The number
+
+| | run 1 | run 2 |
+|---|---|---|
+| title art first drawn (surface leaves black) | 201.617 s | 214.130 s |
+| **title settled** — glyph counter first reads its no-plate value **154** | 203.260 s | 216.261 s |
+| **plate first counted** — glyph leaves 154 | 205.398 s | 218.393 s |
+| **settled → plate** | **2.138 s** | **2.132 s** |
+| first drawn → plate | 3.781 s | 4.263 s |
+
+**Take 2.13 s, measured from the moment build 4's own build-in animation
+finishes.** The two runs agree to **6 ms**, which is under one sample interval.
+
+⚠️ **Do not take "first drawn → plate".** It differs by 0.48 s between the two
+runs because the build-in itself ran 1.64 s and 2.13 s — the emulator's frame
+pacing during an animation is not the game's clock, and this is exactly the sort
+of number that looks like a measurement and is really the harness.
+
+![plate onset, both runs](captures/ui-timing/plate-onset-two-runs.png)
+
+Raw per-frame data, 8 fps, every frame of both runs:
+[`data/plate-timing-run1.tsv`](data/plate-timing-run1.tsv) ·
+[`data/plate-timing-run2.tsv`](data/plate-timing-run2.tsv).
+
+## Why "then the plate", and not "the plate was pulsing all along too dim to see"
+
+The plate's declared alpha never exceeds `0x50` (80/255,
+[HANDOFF](../port/HANDOFF.md)), so a glyph counter with a hard threshold could in
+principle miss its dim phase and produce a fake delay. It does not, on two
+independent observables:
+
+* the glyph count is **exactly 154** — the committed no-plate title's own value,
+  159 on `live-title-build4-no-plate.png` — for every frame of the plateau, with
+  **zero** variation, for 1.99 s (run 1) and 2.13 s (run 2). After onset the
+  same counter swings 714 ↔ 1520 continuously. A cycling plate cannot produce a
+  flat exact-154 plateau nearly one full period long;
+* the **surface mean** is flat to ±0.03 across the plateau (61.09 → 61.15) and
+  then rises. A pulsing overlay moves the frame mean; the frame mean does not
+  move until onset.
+
+## 🔴 The instruction below was WRONG, and the port refuted it — corrected 2026-08-29
+
+**What stands:** every measurement on this page. **What was wrong:** what I told
+the port to do with it.
+
+The instruction was *"when build 4 has settled, wait 2.13 s, composite build 2"*.
+The port implemented it literally, then pointed out with arithmetic off the disc
+that it cannot be right: build 2 has a **group of its own**, and playing that
+group from a start at "settle" puts the plate at settle + 2.13 + 3.97 s. The
+3.97 s is real — `ptbtn00.rat` reaches `a=255` at `t=238`, confirmed here
+independently of their message:
+
+```
+$ sylpheed-cli screen info --build 2 --geometry $SYLPHEED_DISC/dat/GP_TITLE.pak
+build [2]  1280x720  1 elements
+0  ptbtn00.t32   214: 383,560 a=0   236: 383,550 a=0
+                 238: 383,550 a=255  244: 383,550 a=255   -: a=0
+```
+
+### The reconciliation: one clock, and my landmark is `t≈118`, not `t=261`
+
+**Build 2's group runs on the same clock as build 4's, starting together.** Then
+the plate's own keyframes say when it arrives and nothing needs authoring.
+
+The port's premise that *"build 4 settles at `t=261` = 4.35 s"* is the part that
+fails, and it is worth stating plainly because it will bite elsewhere:
+🔴 **`rest.t` is not when a screen settles.** It is the last *hold* keyframe
+before the exit. `ptlogo1` has `rest.t = 251` and stops moving at **`t=42`** —
+after which it creeps 5 px over the next 209 units. The title's visible build-in
+is over at **`t≈118`**, where three elements' ramps end together (`pteff01`,
+`pteff02.prm`, `ptlogoall_eff`); the only later change is the copyright line and
+the ™.
+
+That closes the gap exactly, with no free parameter:
+
+| | units |
+|---|---|
+| last build-in ramp ends (`pteff01` / `pteff02.prm` / `ptlogoall_eff`) | `t = 118` |
+| `ptbtn00` reaches `a = 255` | `t = 238` |
+| **difference** | **120 units = 2.000 s** at 1 unit = 1/60 s |
+
+against a measured **2.138 s** and **2.132 s**. So the interval the two runs agree
+on to 6 ms is a **declared** 120 units — the number was on the disc, and I handed
+over a wall-clock reading of it.
+
+### ⚠️ And the wall-clock reading is 6.7 % long, for a reason the corpus already knew
+
+120 units in 2.135 s is **56.2 units/s**, i.e. the game presenting at **28.06 /
+28.14 fps** against its nominal 30. The corpus independently measured the idle
+title at **28.5 fps** ([`ui-keyframe-time-unit.md`](ui-keyframe-time-unit.md)) —
+1.3 % from these two runs, established before and separately from them.
+
+✅ Corroborating that it is presentation rate and not the game: within these runs
+*first pixels → settle* is **1.643 s** and **2.131 s** — a 30 % spread — while
+*settle → plate* is **2.138 s** and **2.132 s**. The build-in is where frames are
+dropped; the static hold is not. A model in which the game's own timing varied
+would have to move both.
+
+## What the port should author — nothing
+
+1. draw build 4 and build **2** on **one clock, started together**, and play both
+   groups from their own keyframes;
+2. the plate then appears at its declared `t = 238` with no authored constant;
+3. its pulse is the focus record `ptbtn00f`, measured here at **2.12 / 2.19 /
+   2.34 / 2.31 s** over four intervals, mean **2.24 s** — replicating the
+   corpus's ≈ 2.3 s rather than replacing it.
+
+⚠️ **If you do author a gap anyway, author 120 units (2.00 s at 30 Hz), not my
+2.13 s.** The 2.13 s is this emulator's presentation rate baked into a game
+constant, and a port running at a true 30 Hz would be visibly late.
+
+So yes: `ScreenView` needs two builds at once, and the boot's end state is
+**not** plate-free. That part of the answer is unchanged.
+
+### ❔ What this does not settle
+
+* **Which reading of the keyframe times** — the current one or Q1's replicated
+  shift — is right. It barely matters here (the plate's `a=255` is `t=238`
+  unshifted and `t=236` shifted, 0.03 s apart), but the two make different
+  predictions for `ptcopyright`'s fade, and my traces contain **both** a 0.4 s
+  rise and a 1.1 s creep before the plate. Not separated; Q1's 🟡 stands.
+* **My settle landmark to better than ±5 units.** At 56 units/s, 8 units is
+  0.14 s — about one sample. `t=118` is identified from the file (three ramps
+  ending together) and is *consistent with* the measurement, not pinned by it.
+
+## What is NOT measured here — the press latencies, again
+
+Both runs pressed Ⓐ on the plate and Ⓑ on the menu, and both runs contain a
+**frozen frame** on the Ⓐ path that makes the Ⓐ→menu duration meaningless:
+
+| | run 1 | run 2 |
+|---|---|---|
+| frames held at surface mean **26.626**, motion exactly 0 | 14 (1.53 s) | 12 (1.39 s) |
+
+🔴 **This is not the instrument.** Run 1's freeze straddled an x11grab restart,
+so it looked exactly like the documented stale-stream failure; run 2 was run with
+restarts **disabled** for the whole measuring window and reproduced the same
+freeze, at the **same** surface mean to six decimals, in the same place relative
+to the press. Two independent runs cannot agree to 1e-6 on a stalled buffer.
+It is the guest: after Ⓐ, the fade-out starts (mean 64.4 → 51.0 → 26.6), the
+frame is then **re-presented unchanged for ~1.4 s**, the full title reappears at
+mean 64.28, and only then does the fade run to completion. That is the shape of
+a **load stall**, and the Ⓑ path — menu → title, nothing to load — has no freeze
+at all.
+
+**So the Ⓐ→menu latency is an emulator load time, not a game beat, and the port
+must not bake it in.** The parts of the transition that are stall-free:
+
+| | run 1 | run 2 |
+|---|---|---|
+| press → first visible change (Ⓐ) | — | 0.29–0.37 s |
+| press → first visible change (Ⓑ) | — | 0.28–0.33 s |
+| **pure black between the two screens** (Ⓐ path) | 0.14–0.30 s | 0.14–0.27 s |
+| black → menu settled | ≈ 1.0 s | ≈ 1.0 s |
+| Ⓑ path: menu fade-out to black | — | 0.50 s |
+| Ⓑ path: black → title art | — | ≤ 0.27 s, and it is a **cut**, not a fade |
+
+⚠️ The two "first visible change" figures are **upper bounds that include this
+harness**: the press is a file the emulator polls (`--hid=file`), so an unknown
+poll interval sits inside them. They are quoted only because they bracket the
+black hold, and they do **not** refute
+[`screen-transitions.md`](screen-transitions.md)'s 0.07 s, which was taken a
+different way.
+
+✅ **The black hold does check the port's authored constant.** The port ships
+0.17–0.23 s; both runs put it in **0.14–0.30 s**. Consistent, at a sampling
+resolution (0.125 s) that cannot do better — so the authored value stands and is
+now bracketed by a measurement rather than only by the declared 12 units
+(0.20 s).
+
+## The instrument, and its controls
+
+[`tools/re-capture/title_timing_probe.py`](../../tools/re-capture/title_timing_probe.py),
+built because the four durations withdrawn on 2026-08-29 came from a classifier
+costing **1503 ms per frame** draining an 8 fps stream at 0.64 fps.
+
+* **8.7 ms of compute per frame** — measured, 173× cheaper. The saving is the
+  ±8 px offset search: every committed capture aligns at exactly `dy=0 dx=0`
+  ([`five-screens-acceptance.md`](five-screens-acceptance.md)), so the live path
+  decimates 4× and does one ZNCC per reference instead of 25 at full res.
+* **Both runs sampled at 7.97 and 7.98 fps against a requested 8.** A backlog
+  preserves ordering and destroys durations; there was no backlog.
+* `--control` **passed 9/9 content controls and 4/4 plate-detector controls**,
+  including the two committed movie frames that are the class this oracle exists
+  to reject.
+* an **independent one-shot grab** every 20 s, through a separate process, is
+  logged beside the stream's own frame. On the static screens the two agree to
+  **0.000 / 0.001**; the large disagreements are all inside movies, where a
+  0.3 s difference in grab time is a different picture.
+* and the plateau itself carries an internal clock check: the plate's ~2.2 s
+  pulse is visible in the same trace. A stalled stream cannot produce a periodic
+  signal.
+
+## Reach
+
+Two runs, English locale, one machine, Xenia Canary. It says nothing about the
+**attract loop's** title (which the corpus records as accepting no input at all),
+and nothing about the Japanese build 7.

docs/re/ui-keyframe-record-layout.md

@@ -0,0 +1,239 @@
+# A keyframe's time word comes **before** its pose — the placement record, decoded
+
+**Status:** ✅ `CONFIRMED`, **decoded**. The field, plus a disc-wide check
+(13 991 placement groups over 33 archives, three tests, each with a control) and
+a regression test that runs against the disc
+(`crates/sylpheed-formats/tests/ui_keyframe_record_disc.rs`).
+
+This closes the one thing [MISSION](../port/MISSION.md) **Q1** still had open —
+*"the interpolation law is settled; the group TIMELINE for multi-keyframe
+elements is not"* — and it dissolves, rather than decides, the argument in
+[`ui-keyframe-time-unit.md`](ui-keyframe-time-unit.md) about whether to adopt
+`SYLPHEED_KF_TIME_SHIFT`. Both sides of that argument were reasoning about a
+missing word that is not missing.
+
+## The record
+
+A build bundle's placement region is a run of groups, one per element. A group
+is an 8-byte header followed by `frame_count` **records of 40 bytes**:
+
+```text
+u32  element_index
+u32  frame_count
+                            ┐
+u32  time                   │  record 0   ← the time comes FIRST
+36   pose                   ┘
+u32  time                   ┐  record 1
+36   pose                   ┘
+…
+u32  time                   ┐  record n−1
+36   pose                   ┘
+```
+
+Total group size: `8 + frame_count * 40`.
+
+The 36-byte pose is what the parser already reads correctly — fade ARGB, the
+three signed rotation words, scale X/Y, tint, X, Y — at offsets 0…35 of the
+pose, i.e. 4…39 of the record.
+
+## What was wrong, and why it looked right for so long
+
+Our parser opened its 40-byte window **at the pose**, four bytes into record 0,
+and then read the word at window `+36` as that pose's time. That word is
+record `k+1`'s `time` — the time of the *next* pose. Every pose field lands
+correctly (the window is aligned to a pose, and poses are what it reads); only
+the time association slips by one.
+
+Two long-standing oddities in the corpus are that off-by-one, and nothing else:
+
+| the oddity as recorded | what it actually was |
+|---|---|
+| *"a group's data stops 4 bytes short of its final block's time slot — that word is already the next group's element index"* | the group is **not** short. `8 + frames*40` is exact. The parser was reading 4 bytes past the last pose because its window began 4 bytes early |
+| *"the last keyframe carries no time"* — `Keyframe::time` was `Option<u32>`, `None` on every group's final pose | the final pose's time is the *previous* stride's `+36` word. **Every** pose is timed |
+| the stray `time = 1869640736` (= `"ohnm"`, ASCII from the next record) that "silently corrupts the max-dwell pick in `Element::rest`" | the same over-read |
+
+The first pose's time is the group's **lead-in word** at `header + 8` — the word
+[`parse_placements`](../../crates/sylpheed-formats/src/ui_layout.rs) skipped as
+*"one lead-in word"* without asking what it was.
+
+## The disc-wide check
+
+`tools/re-capture/kf_record_census.py`, output committed at
+[`data/kf-record-census.txt`](data/kf-record-census.txt). Run it with
+
+```bash
+python3 tools/re-capture/kf_record_census.py "$SYLPHEED_DISC"/dat/*.pak
+```
+
+### A. The lead-in word takes its place in the sequence
+
+Prepending the lead-in to the shifted time series must give a non-decreasing
+sequence. **13 991 of 13 991 groups — 100.000 %.** (15 493 including
+single-pose groups, which are trivially ordered; the regression test counts
+those and also finds 0 out of order.)
+
+### B. The 5 058 non-zero lead-ins are times, not padding
+
+If the lead-in were padding, a flag, or a count, 5 058 of them would not all
+happen to fall strictly below the group's next time.
+
+| | result |
+|---|---|
+| non-zero lead-ins | 5 058 |
+| strictly less than the next time | **5 058 — 100.000 %**, none equal |
+| **control**: another group's lead-in from the same bundle | 35 837 / 50 580 = **70.9 %** |
+
+The gap to the next time piles up at **10** (2 076 groups) and **1** (2 022) —
+ramp lengths, not arbitrary numbers. And the values themselves read as times:
+`GP_DIALOG` entry 9's `pzeff02.t32` runs `167 → 197 → 217 → 232`; entry 25's
+`pznoise.rat` runs `40 → 80 → 230 → 260`.
+
+### C. A multi-keyframe ramp only runs at a constant rate under this reading
+
+Interpolation between two keyframes is linear — measured against the running
+game, in [`ui-keyframe-time-unit.md`](ui-keyframe-time-unit.md). So where an
+author chains three or more keyframes through a monotone alpha ramp, a correct
+time assignment should often make `d(alpha)/d(time)` come out constant, and a
+wrong one should scramble it.
+
+| reading | multi-segment alpha ramps at a constant rate (±6 %) |
+|---|---|
+| **corrected** — time precedes pose | **857 / 1 540 = 55.6 %** |
+| old — `+36` is the block's own time | **0 / 1 042 = 0.0 %** |
+
+**Zero.** Not one ramp on the whole disc. The 44 % that are not constant under
+the corrected reading are genuinely shaped ramps — authors do place keyframes
+unevenly — so 56 % is a floor, not a fit.
+
+A worked example, `pgloading_loop4.rat` on `GP_TITLE` build 11:
+
+| | times | alphas | rate per unit |
+|---|---|---|---|
+| corrected | 0, 4, 6, 7, 8, 32, 38 | 0, 128, 192, 224, 255, 255, 0 | **32, 32, 32, 31** — then hold, then out |
+| old | 4, 6, 7, 8, 32, 38, *(none)* | 0, 128, 192, 224, 255, 255, 0 | 64, 64, 32, 1.3 — then hold, then an **untimed** fade-out |
+
+## What it costs to adopt: nothing, on every static composite
+
+This is the change the corpus previously declined to make, because
+`SYLPHEED_KF_TIME_SHIFT=1` moved `GP_TITLE` build 7 by 13.1 % of its pixels and
+made the EN/JP twin brightness disagree (70.94 vs 76.32 against build 4's
+71.41). **That was the missing first time word, not the shift.**
+
+With the lead-in restored as pose 0's time:
+
+| check | result |
+|---|---|
+| `GP_TITLE`, all 12 builds rendered under both readings | **12 / 12 byte-identical PNGs**, build 7 included |
+| 217 builds over 6 UI archives, `rest()` pose per element | **2 builds differ**: `GP_TITLE` 7 and `GP_DIALOG` 31 |
+| what those 2 differences are | `ptlogo_eff3.t32`: `(98,42)` vs `(108,72)` — **both α = 0**, so neither paints. `pzstg14_2.t32`: one pixel of Y |
+| renders of those 2 builds | **identical** |
+
+So the build-7 luminance objection is withdrawn: it was `rest()`'s dwell
+fallback picking the 200 %-scale bloom because pose 0 had no time to be compared
+against. Given a time, the dwell rule picks an invisible pose — the same
+*visible* result the old reading produced, by a rule that is now sound.
+
+⚠️ **`Element::rest()` is unchanged and is still a heuristic.** The times feed
+it; they do not fix it. `structures/ui-resting-pose.md` stands as written.
+
+## Against the oracle
+
+The committed `log_ui_draws` capture of the developer splash
+([`captures/ui-timing/splash-build-quads.csv`](captures/ui-timing/splash-build-quads.csv))
+is the check that this is the game's reading and not merely a tidier one.
+
+`palogo_gamearts_eff.t32` — lead-in 0, `W = [15, 30, 45, –]`, alphas
+`[0, 255, 255, 0]`:
+
+| phase | corrected | old | captured |
+|---|---|---|---|
+| fade in | t 0→15 (7.5 f) | t 15→30 (7.5 f) | frames 94–101, **7 f** |
+| hold | t 15→30 (7.5 f) | t 30→45 (7.5 f) | frames 101–107, **7 f** |
+| fade out | t 30→45 (7.5 f) | **untimed** | frames 108–115, **8 f** |
+
+The glow's *durations* do not discriminate — that was already recorded — but its
+**end does**: the old reading cannot say when the fade-out finishes, and the
+capture plainly shows it finishing.
+
+`palogo_gamearts.t32` — lead-in 0, `W = [15, 30, 190, 194, 206, 210, –]`, alphas
+`[0, 0, 255, 255, 232, 32, 0]`:
+
+| | corrected | old | captured |
+|---|---|---|---|
+| fade in | t 15→30, **7.5 f**, in the same window as its own glow | t 30→190, **80 f** | already at 255 when the quad first appears (frame 116) |
+| hold at 255 | t 30→190, **80 f** | t 190→194, **2 f** | frames ≤116–198, **≥ 83 f** |
+| fade out | t 190→210, **10 f** | t 194→? , untimed end | frames 199–211, **13 f** |
+
+A logo whose bloom layer fades in over 7.5 frames while the logo itself takes 80
+is not a thing anyone authored. This replicates the 26× result already in
+[`ui-keyframe-time-unit.md`](ui-keyframe-time-unit.md) and adds the reason.
+
+⚠️ **Reach.** The capture's absolute frame numbers sit about 18 frames later than
+the glow-derived calibration `t = 2f − 171` predicts for the *logo* — the
+fade-out starts at frame 199 where the calibration says 180.5. Durations match;
+the two elements' groups do not appear to start on the same frame. That offset is
+**not explained here** and is not needed for this result, which is about which
+word is which. It is the same lateness `ui-keyframe-time-unit.md` records as
+"17 frames late" and leaves open.
+
+### And the corpus had already used this reading without noticing
+
+[`ui-title-build-map.md`](ui-title-build-map.md)'s splash timing table — written
+on 2026-08-28 against a 10 fps capture, and agreeing with it to ±0.1 s — reads
+`palogo_sqex.t32`'s declared `[15 30 235 239 251 255 –]` as
+
+| | the table says | the OLD reading actually gives | the corrected reading gives |
+|---|---|---|---|
+| hold at α=255 | `30 → 235` = **3.42 s** ✅ measured ≈3.5 s | `235 → 239` = **0.07 s** | `30 → 235` = **3.42 s** |
+| fade out | `235 → 255` = **0.33 s** ✅ measured ≈0.3 s | `239 → ?` — the α=0 pose is **untimed** | `235 → 255` = **0.33 s** |
+
+Its author paired each time with the pose that *reaches* it, by eye, because that
+is the only pairing that produces a sensible splash — and then checked it against
+a capture, which agreed. The record layout is what that pairing was.
+
+## What changed in the code
+
+[`crates/sylpheed-formats/src/ui_layout.rs`](../../crates/sylpheed-formats/src/ui_layout.rs):
+
+* `parse_placements` reads `header + 8` as pose 0's time and the previous
+  stride's `+36` as pose `k`'s. Every pose gets a time.
+* `SYLPHEED_KF_TIME_SHIFT` is gone. `SYLPHEED_KF_TIME_LEGACY=1` restores the old
+  reading for A/B work.
+* `Keyframe::time` stays `Option<u32>` only so the legacy gate still type-checks.
+  Under the default it is always `Some`.
+
+New test, disc-gated: `tests/ui_keyframe_record_disc.rs` — every pose timed and
+ordered (15 493 groups), and ≥ 45 % of multi-segment alpha ramps at a constant
+rate (the old reading scores 0 %).
+
+⚠️ `tests/ui_header_time_disc.rs` needed one line: bundles whose every group is a
+single static pose now report `max_time = 0` where before they reported no time
+at all, and 546 of them were swamping the ratio histogram's zero bucket. The
+result it guards **strengthened** — the bound `max_time ≤ header +0x08` now holds
+over **2 859** bundles instead of 2 313, still with **0** violations, and the
+newly readable times are the latest in every group.
+
+## What is NOT established
+
+❔ **The executable's own parser was not found.** Reach: queried the disassembly
+database for functions carrying a `mulli` by 40 (the record stride) and by 60
+(the declaration-entry stride) — 26 functions have the first, none have both, and
+PowerPC compilers synthesise both constants as shift-adds, so the query is weak
+rather than negative. Nothing here rests on a database row; every number above
+comes from the disc bytes or from a committed capture. Finding the interpolator
+would upgrade this from *decoded from the container's own arithmetic and a
+disc-wide census* to *decoded from the code*, and would also settle the 18-frame
+group-start offset above.
+
+## For the port
+
+The pose values you already have do not move. What moves is **when** each pose is
+reached:
+
+* pose `k`'s time is the word **before** it, not after it;
+* pose 0 has a time — usually 0, but 5 058 groups on the disc start late;
+* the **last** pose has a time, so an exit ramp now has an end. Anything you
+  authored to cover "the final keyframe has no time" can come out.
+
+Static composites are unaffected: `screen render` produces byte-identical output
+on all 12 `GP_TITLE` builds.

docs/re/ui-keyframe-time-unit.md

@@ -1,5 +1,21 @@
 # What a keyframe time is worth, and what shape the ramp has
 
+> ## ✅ 2026-08-29 — the argument on this page about WHICH BLOCK OWNS A TIME is over
+>
+> It was never a choice between two readings. A placement group is
+> `frames` records of `{u32 time; 36-byte pose}` after an 8-byte header, so the
+> time word **precedes** its pose; the group's "lead-in word" is pose 0's time,
+> and **no** time is missing. `SYLPHEED_KF_TIME_SHIFT` had the association right
+> and pose 0 untimed, which is the only reason it looked like it cost build 7
+> 13.1 % of its pixels. Decoded disc-wide, with controls, in
+> [`ui-keyframe-record-layout.md`](ui-keyframe-record-layout.md); the gate is now
+> `SYLPHEED_KF_TIME_LEGACY=1`.
+>
+> **Everything else on this page stands** — the ramp is linear, the clock advances
+> 2 units per submitted frame, and `1 unit = 1/60 s` is measured. Read the
+> sections below with that correction applied: where a table pairs a time with a
+> pose, the pairing is the corrected one.
+
 **Status:** ✅ `CONFIRMED` for the two things the port is blocked on — the ramp is
 **linear**, and the animation clock advances **2 keyframe time units per frame the
 game submits**. 🟡 the conversion to *seconds* rests on one further step: the game

docs/re/ui-title-build-map.md

@@ -2,7 +2,11 @@
 
 **Status:** ✅ `CONFIRMED` for the four screens the boot path actually shows
 (title art, `PRESS Ⓐ BUTTON`, main menu, `EXTRAS`); 🟡 `PROBABLE` for their
-Japanese twins; ❔ open for the two `DELTASABER` plates.
+Japanese twins.
+
+✅ **2026-08-29 — the two "unidentified `DELTASABER` plates" are the LOADING
+SCREEN**, and the ❔ on them is withdrawn. See
+[below](#-the-deltasaber-plates-are-the-loading-screen-and-there-are-two-of-them).
 
 Answers [MISSION Q2](../port/MISSION.md). The previous statement — *"build 4
 title, 5 main menu, 6/8/9 submenus"* — is **partly wrong** and is withdrawn:
@@ -53,7 +57,7 @@ Contact sheet of every render:
 
 | build | what it is | confirmed how |
 |---|---|---|
-| 0, 1 | a `DELTASABER / SYLPHEED A.I.` plate low-left on black, no background | ❔ **not observed running.** Never seen in the boot path, the main menu, `EXTRAS` or `MISSION SELECT` |
+| 0, 1 | ✅ **the LOADING screen**, plain — a `DELTASABER / SYLPHEED A.I.` plate low-left on black, no background. 7 elements, all named `pgloading_*` | ✅ **decoded from the declaration table**, not observed running |
 | **2**, 3 | the `PRESS Ⓐ BUTTON` plate — **an overlay build of its own**, not a state of build 4 | ✅ seen composited over build 4 on the live title, at the same rect our render puts it |
 | **4** | title art, English (`PROJECT SYLPHEED`, ™, `(C)2006,2007 SQUARE ENIX`) | ✅ [`live-title-press-a.png`](captures/title-builds/live-title-press-a.png) |
 | 7 | the same, Japanese | 🟡 renders as the JP twin of build 4; the container runs an English locale, so it was not seen |
@@ -61,7 +65,96 @@ Contact sheet of every render:
 | 8 | the same, Japanese | 🟡 as above |
 | **6** | the `EXTRAS` submenu, English: MISSION SELECT / MOVIE THEATER / BACK, footer `Ⓐ : OK  Ⓑ : Back` | ✅ [`live-extras.png`](captures/title-builds/live-extras.png) |
 | 9 | the same, Japanese | 🟡 as above |
-| 10, 11 | the same `DELTASABER` plate as build 0, over a dark circuit-line background | ❔ **not observed running** |
+| 10, 11 | ✅ **the LOADING screen**, dressed — the same plate over a dark circuit-line background. 10 elements, the same seven plus `pgloading_eff00.prm`, `pgloading_loop5.rat` and `pgloading_baseeff.t32` | ✅ **decoded from the declaration table**, not observed running |
+
+## ✅ The `DELTASABER` plates are the LOADING screen, and there are two of them
+
+**2026-08-29. Decoded — the authors' own element names, out of the declaration
+table.** No renderer, no capture, no inference. Every element of all four
+bundles is prefixed `pgloading_`:
+
+| build | entry | elements |
+|---|---|---|
+| 0, 1 | 0, 1 | `pgloading_loop1.rat` `pgloading_loop3.rat` `pgloading_str.t32` `pgloading_line.t32` `pgloading_loop4.rat` `pgloading_eff01.t32` `pgloading_eff02.t32` |
+| 10, 11 | 12, 15 | the same seven, plus `pgloading_eff00.prm` `pgloading_loop5.rat` `pgloading_baseeff.t32` |
+
+Reproduce:
+
+```bash
+sylpheed-cli screen info --build 0  "$SYLPHEED_DISC/dat/GP_TITLE.pak"
+sylpheed-cli screen info --build 10 "$SYLPHEED_DISC/dat/GP_TITLE.pak"
+```
+
+`DELTASABER / SYLPHEED A.I.` is the artwork on `pgloading_str.t32` — the loading
+screen's caption, not the screen's identity. Reading the picture named the plate;
+reading the file names the screen.
+
+⚠️ This also removes the reason the pair was open. The previous row said *"never
+seen in the boot path, the main menu, `EXTRAS` or `MISSION SELECT`… a mission
+load is the remaining candidate"*. It is a **loading** screen: it is not supposed
+to appear on any of those, and the remaining candidate was right.
+
+### 🟡 Which is `LOADING` and which is `LOADING2` — the executable names five
+
+`sub_821C4EB0` builds `GamePart_Title` and asks its table for five sub-entries in
+this order, one `bl sub_821CEDF8` each, setting an error flag on any failure:
+
+| call site | string | VA |
+|---|---|---|
+| `0x821C503C` | `TITLE_SCREEN` | `0x820A3D3C` |
+| `0x821C5068` | `BUTTON` | `0x820A339C` |
+| `0x821C5090` | `TITLE_MENU` | `0x820A3D30` |
+| `0x821C50BC` | `LOADING` | `0x820A214C` |
+| `0x821C50E4` | `LOADING2` | `0x820A3D24` |
+
+✅ **Checked against the image, not just the database** — `/image/sylpheed.pe` at
+`0x821C503C`, `0x821C5090`, `0x821C50BC`, `0x821C50E4` reads `38aa3d3c`,
+`3baa3d30`, `38aa214c`, `38aa3d24`, exactly the `addi rX, r10, <lo16>` the
+database shows, with `r10 = 0x820A0000` set two instructions earlier.
+
+That is five named title-side screens, and `BUTTON` is what the `PRESS Ⓐ BUTTON`
+overlay would be called — which the corpus had already isolated as a build of its
+own (pair B) on capture evidence alone.
+
+🟡 **Two loading screens named, two loading bundles found — but nothing observed
+maps one to the other.** `LOADING` is the 7-element plain plate and `LOADING2`
+the 10-element dressed one *if* the suffix means "the second, richer variant",
+and that is a guess about a name. The port should treat the pairing as
+**undecided** and not carry either name into an asset path.
+
+Also note the lookup is **not** by pak TOC hash: at `0x821C5118`–`0x821C512C` the
+game hashes `BASE_INFO` and `TITLE_MENU` with `sub_82455C78` (the same name-hash
+[`hash.rs`](../../crates/sylpheed-formats/src/hash.rs) implements) and splices
+the two 32-bit results into one 64-bit key. So these strings key a **sub-table
+inside the GamePart's own record**, not an archive entry — which is why
+`pak list` resolves none of `GP_TITLE`'s 16 names.
+
+## 🟡 Which member of each pair is English — the archive is packed in two halves
+
+The port asked which member of pairs A, B and H is which locale, since those
+three render byte-identically and no capture can tell them apart. The **data
+segment** can:
+
+| | entries | data offset |
+|---|---|---|
+| first half | 0, 2, 4, 5, 6, 10, 11, 12 | 0 … 507 904 |
+| second half | 1, 3, 7, 8, 9, 13, 14, 15 | 6 078 464 … 10 868 736 |
+
+Every one of the eight pairs has **exactly one member in each half**, and in all
+three pairs whose language is visible — C (4/7), D (5/8), E (6/9) — the English
+build is the one in the **first** half. `GP_TITLE.p00` is one locale's eight
+bundles followed by the other's; the TOC interleaves them only because it is
+sorted by name hash.
+
+So: **first half = English**, i.e. builds 0, 2, 4, 5, 6, 10 are English and 1, 3,
+7, 8, 9, 11 are Japanese.
+
+⚠️ 🟡 not ✅. The rule is 8/8 structurally consistent and 3/3 where it can be
+checked, but the three pairs it is *used* for are exactly the three it cannot be
+checked on. Reach of the negative: nothing in the bundle bytes themselves — the
+header, the declaration table, the element names — differs between the twins of
+pairs A, B and H at all; they render byte-identical PNGs. If a locale marker
+exists it is not in the bundle.
 
 ## ✅ The splash — the four "non-build" entries, rendered
 

tools/motion-census

@@ -1,199 +0,0 @@
-#!/usr/bin/env python3
-"""Does it ANIMATE, or does it switch? — compare a film, never two stills.
-
-    tools/motion-census <dir-of-frames> [--interval 0.05] [--rows] [--roi x,y,w,h]
-    tools/motion-census --selftest
-
-Point it at a directory of PNGs captured in order during a REAL run — the port's
-`--film`, or a capture harness's frame dump. It reports where the picture moves
-and where it is frozen, plus how many distinct states it ever took.
-
-Why this exists
----------------
-🔴 A human played the port and said *"the logos just switch, there is no
-animation at all."* Every check either agent had said the splash was correct.
-Three instruments agreed, and all three were blind in the same way:
-
-  * a **frozen sweep** — step the clock by hand, render a still per unit. That
-    proves the renderer CAN draw pose N. It never runs the animation.
-  * a **settled comparison** — correlate the resting pose against a capture. A
-    screen that is frozen 84 % of the time matches a settled reference
-    perfectly; that is what being frozen MEANS.
-  * an **achieved-fps counter** — frames DRAWN per second. Drawing the same
-    pixels 25 times a second scores identically to animating at 25 fps.
-
-The common defect: **every one measured throughput or a pose, and none measured
-CHANGE.** So this measures change and nothing else.
-
-  measured 2026-09-02 on the boot splash: moving 1.30 s of 7.95 s (16.4 %),
-  publisher frozen for 3.20 s, developer for 2.40 s, 26 distinct luma values.
-
-What the numbers mean
----------------------
-A fade is ONE LONG RUN of small non-zero deltas. A switch is isolated one-frame
-spikes with flat nothing between them. The `distinct states` count is the blunt
-version of the same question: a 45-unit ramp cannot be drawn in 26 states.
-
-⚠️ It cannot tell you the animation is CORRECT — only that something moved. A
-wrong ramp that moves every frame passes here. Pair it with a comparison against
-the oracle; this is the liveness half, which is the half that was missing.
-"""
-
-from __future__ import annotations
-
-import sys
-from pathlib import Path
-
-try:
-    from PIL import Image
-except ImportError:
-    sys.exit("motion-census: needs Pillow (pip install pillow)")
-
-# Below this, two frames are the same picture. Chosen as a floor, not tuned: PNG
-# frames of an unchanged scene differ by exactly 0.000, so anything above noise
-# works and a bigger number would only hide small fades.
-MOVED = 0.05
-
-# Downsample before comparing. A fade moves every pixel a little, so it survives
-# scaling; scaling also stops one stray cursor pixel reading as motion.
-GRID = (160, 90)
-
-
-def load(path: Path, roi=None) -> list[int]:
-    im = Image.open(path).convert("L")
-    if roi:
-        x, y, w, h = roi
-        im = im.crop((x, y, x + w, y + h))
-    return list(im.resize(GRID).getdata())
-
-
-def census(frames: list[Path], interval: float, roi=None):
-    prev, rows = None, []
-    for i, f in enumerate(frames):
-        px = load(f, roi)
-        lum = sum(px) / len(px)
-        delta = 0.0 if prev is None else sum(abs(a - b) for a, b in zip(px, prev)) / len(px)
-        rows.append((i * interval, delta, lum))
-        prev = px
-    return rows
-
-
-def segments(rows):
-    segs, cur, start = [], None, 0.0
-    for t, delta, _ in rows[1:]:
-        state = "MOVING" if delta > MOVED else "static"
-        if state != cur:
-            if cur is not None:
-                segs.append((cur, start, t))
-            cur, start = state, t
-    if cur is not None:
-        segs.append((cur, start, rows[-1][0]))
-    return segs
-
-
-def report(rows, interval: float, show_rows: bool) -> int:
-    total = rows[-1][0]
-    segs = segments(rows)
-
-    if show_rows:
-        print(f"{'t(s)':>7} {'Δ prev':>8} {'luma':>7}  bar")
-        for t, delta, lum in rows:
-            print(f"{t:>7.2f} {delta:>8.3f} {lum:>7.2f}  {'#' * min(60, int(delta * 6))}")
-        print()
-
-    print(f"{len(rows)} frames @{interval}s = {total:.2f}s\n")
-    print(f"{'state':<8} {'from':>7} {'to':>7} {'dur':>7}   luma")
-    for state, a, b in segs:
-        lums = [l for t, _, l in rows if a <= t <= b]
-        flag = "   <-- FROZEN" if state == "static" and (b - a) > 0.5 else ""
-        print(f"{state:<8} {a:>7.2f} {b:>7.2f} {b-a:>7.2f}   "
-              f"{min(lums):.2f}..{max(lums):.2f}{flag}")
-
-    moving = sum(b - a for s, a, b in segs if s == "MOVING")
-    pct = 100 * moving / total if total else 0.0
-    states = len({round(l, 2) for _, _, l in rows})
-    print(f"\nmoving  {moving:.2f}s of {total:.2f}s = {pct:.1f}%")
-    print(f"distinct luma states: {states}")
-    longest = max((b - a for s, a, b in segs if s == "static"), default=0.0)
-    print(f"longest frozen stretch: {longest:.2f}s")
-    print()
-    if pct < 50:
-        print("🔴 This is a SWITCH, not an animation. Most of the run is one still")
-        print("   picture. A frozen sweep and a settled comparison both pass on this.")
-        return 1
-    print("moves for most of its length — liveness only; correctness is a separate")
-    print("question this tool cannot answer.")
-    return 0
-
-
-def selftest() -> int:
-    """Synthetic controls, executed. A detector that cannot tell a fade from a
-    switch would report the same green line on both, and its verdict on the real
-    film would mean nothing."""
-    import tempfile
-
-    ok = 0
-    with tempfile.TemporaryDirectory() as d:
-        root = Path(d)
-
-        def write(name, values):
-            sub = root / name
-            sub.mkdir()
-            for i, v in enumerate(values):
-                Image.new("L", (320, 180), int(v)).save(sub / f"f{i:04d}.png")
-            return sorted(sub.glob("*.png"))
-
-        # A fade: every frame differs from the last.
-        fade = write("fade", [10 + i * 4 for i in range(40)])
-        rows = census(fade, 0.05)
-        pct = 100 * sum(b - a for s, a, b in segments(rows) if s == "MOVING") / rows[-1][0]
-        good = pct > 90
-        print(f"  {'a real fade reads as MOVING':<40} {pct:5.1f}%  {'✅' if good else '🔴'}")
-        ok |= 0 if good else 1
-
-        # A switch: one value, then another, held. This is the shape the port
-        # actually produced, and the case the old instruments could not see.
-        sw = write("switch", [10] * 20 + [200] * 20)
-        rows = census(sw, 0.05)
-        pct = 100 * sum(b - a for s, a, b in segments(rows) if s == "MOVING") / rows[-1][0]
-        good = pct < 20
-        print(f"  {'a switch reads as STATIC':<40} {pct:5.1f}%  {'✅' if good else '🔴'}")
-        ok |= 0 if good else 1
-
-        # Fully frozen: the degenerate case must not read as motion.
-        fr = write("frozen", [42] * 30)
-        rows = census(fr, 0.05)
-        pct = 100 * sum(b - a for s, a, b in segments(rows) if s == "MOVING") / rows[-1][0]
-        good = pct == 0
-        print(f"  {'a frozen film reads as 0% motion':<40} {pct:5.1f}%  {'✅' if good else '🔴'}")
-        ok |= 0 if good else 1
-
-    print()
-    print("the census separates a fade from a switch" if not ok
-          else "🔴 the census cannot tell a fade from a switch — it asserts nothing")
-    return ok
-
-
-def main(argv: list[str]) -> int:
-    if "--selftest" in argv:
-        return selftest()
-    args = [a for a in argv if not a.startswith("--")]
-    if not args:
-        sys.exit(__doc__.split("\n\n")[1])
-    interval = 0.05
-    roi = None
-    for i, a in enumerate(argv):
-        if a == "--interval" and i + 1 < len(argv):
-            interval = float(argv[i + 1])
-        if a == "--roi" and i + 1 < len(argv):
-            roi = tuple(int(v) for v in argv[i + 1].split(","))
-    d = Path(args[0])
-    frames = sorted(d.glob("*.png"))
-    if len(frames) < 3:
-        sys.exit(f"motion-census: {d} holds {len(frames)} PNG(s) — nothing to compare.\n"
-                 "   Exit 2: the harness is broken, not the animation.")
-    return report(census(frames, interval, roi), interval, "--rows" in argv)
-
-
-if __name__ == "__main__":
-    sys.exit(main(sys.argv[1:]))

tools/port/check-all

@@ -1,376 +0,0 @@
-#!/usr/bin/env bash
-# Run every check this port has, and say which ones assert.
-#
-#   tools/port/check-all
-#
-# There are fourteen tools under `tools/port/` (eleven when this was written --
-# the count is stated because it dates the sentence) and nothing ran them
-# together, so
-# each had to be remembered individually. That is the ninth instance of this
-# port's recurring shape -- something correct, documented and unexercised -- one
-# level up: the checks themselves were the thing nobody was running.
-#
-# ⚠️ It runs the tools that ASSERT. The exploratory ones -- `screen-strip`,
-# `which-focus`, `strip-padding`, `verify-dwell`, `check-capture`,
-# `verify-video-audio` -- produce artifacts for a person to look at and have no
-# verdict to collect. Listing them here as passes would be inventing six.
-set -euo pipefail
-cd "${PROJECT_DIR:-/work}"
-export DISPLAY="${DISPLAY:-:97}"
-OUT="${OUT:-${TMPDIR:-/tmp}/check-all}"; mkdir -p "$OUT"
-BIN="${CARGO_TARGET_DIR:-/sylph-home/port/target-container}/debug/sylpheed-export"
-fail=0
-
-step() { # name, expectation, command...
-  local name="$1" expect="$2"; shift 2
-  local log="$OUT/${name}.log" rc=0
-  "$@" >"$log" 2>&1 || rc=$?
-  case "$expect" in
-    must-pass)
-      [ $rc -eq 0 ] && printf '  %-24s ok\n' "$name" \
-        || { printf '  %-24s 🔴 FAILED (rc=%d) -- %s\n' "$name" "$rc" "$log"; fail=1; }
-      ;;
-    report-only)
-      printf '  %-24s ran (no verdict -- see below)\n' "$name"
-      ;;
-  esac
-}
-
-# 🔴 THE DISPLAY CAN BE GONE, AND EVERY GODOT STEP THEN FAILS FOR ONE REASON.
-#
-# Xvfb does not survive a container restart, and its socket does: /tmp/.X11-unix
-# keeps `X97` after the server is gone, so Godot reports
-#
-#   ERROR: X11 Display is not available
-#
-# rather than "no such display", falls back to Wayland, fails that too, and
-# exits non-zero. Every Godot-backed step below would then report red, and all of
-# it would mean one thing -- there is no display -- which is exactly the wall of
-# meaningless failures a check suite exists to avoid. Cost one run on 2026-09-01
-# before it was noticed.
-#
-# Checked with `xdpyinfo` rather than by looking for the socket, because the
-# stale socket is what makes the failure confusing in the first place.
-if ! DISPLAY="$DISPLAY" timeout 10 xdpyinfo >/dev/null 2>&1; then
-  echo "🔴 no X display on $DISPLAY -- every Godot step below would fail for that one reason."
-  echo "   Xvfb does not survive a container restart and leaves its socket behind. Start it with:"
-  echo "     rm -f /tmp/.X11-unix/X\${DISPLAY#:} /tmp/.X\${DISPLAY#:}-lock"
-  echo "     Xvfb $DISPLAY -screen 0 1280x720x24 -nolisten tcp &"
-  echo "   🔴 THE LOCK FILE IS NOT OPTIONAL and this recipe omitted it until"
-  echo "      2026-09-03. Removing only the socket leaves /tmp/.X<n>-lock behind,"
-  echo "      Xvfb exits 1 immediately, and the next command still reports no"
-  echo "      display -- which reads as the restart having failed for some deeper"
-  echo "      reason. Cost three occurrences before anyone read Xvfb's own stderr."
-  exit 3
-fi
-
-# 🔴 GODOT'S SCRIPT CLASS LIST IS A BUILD CACHE, AND IT IS GITIGNORED.
-#
-# `port/.godot/global_script_class_cache.cfg` is what resolves a `class_name`,
-# and `.gitignore` excludes `port/.godot/` -- correctly, it is derived. So a
-# checkout that MERGES a commit adding a new `class_name` keeps a cache that
-# does not list it, and every script referencing the new class fails to parse:
-#
-#   SCRIPT ERROR: Parse Error: Identifier "Gamepad" not declared in the current scope.
-#   ERROR: Failed to load script "res://scripts/boot.gd" with error "Parse error".
-#
-# The whole project then refuses to load, from `--screen` to `--boot`, and the
-# error names the symbol rather than the cache -- so it reads as a missing file
-# or a bad merge. This is exactly what merging the human's input fix did on
-# 2026-09-01: `gamepad.gd` arrived with `class_name Gamepad`, the cache in this
-# container was warm and predated it, and the port did not run at all.
-#
-# A fresh clone has no `.godot/` and Godot builds one on first run, so nobody
-# hits this until they merge into a working tree -- which is every iteration of
-# this loop. Reimporting is cheap and idempotent, so it runs unconditionally
-# rather than behind a staleness test that would itself need to be right.
-echo "godot: reimporting so class_name resolves against a fresh cache"
-DISPLAY="$DISPLAY" godot --headless --path port --import >"$OUT/godot-import.log" 2>&1 \
-  || { echo "  🔴 godot --import FAILED -- see $OUT/godot-import.log"; fail=1; }
-for c in $(grep -ho '^class_name [A-Za-z_][A-Za-z0-9_]*' port/scripts/*.gd | awk '{print $2}'); do
-  grep -q "\"$c\"" port/.godot/global_script_class_cache.cfg 2>/dev/null \
-    || { printf '  %-24s 🔴 class_name %s is not in the class cache\n' class-cache "$c"; fail=1; }
-done
-echo
-
-echo "asserting checks:"
-step format-validator must-pass "$BIN" check
-# The contract lives on a branch this checkout does not merge: HANDOFF on `main`
-# is frozen at 926 lines while the live one is 4 111. Reading 70 unread sections
-# by hand is how two days of deliveries went unread. These are the values that
-# have been reduced to a check; the rest are still read by eye, or not at all.
-step contract-values  must-pass tools/port/contract-check
-step contract-control must-pass tools/port/contract-check --control
-# 🔴 The control harness itself is asserted. Every --control run says "each check
-# fails on a perturbed contract"; none of them said "a broken control reports
-# broken". A harness that silently approves a dead check is exactly as useless as
-# a check that silently approves a dead value.
-step control-harness  must-pass tools/port/contract-check --selftest
-step modding-rules    must-pass tools/port/check-modding
-# Every `kind` in authored/ is a claim about where a value came from, and until
-# 2026-08-30 nothing checked what any of them rested on -- seven were resting on
-# a sibling `why` that argued a different claim.
-step authored-kinds   must-pass tools/port/audit-kinds
-# The classifier is asked whether it can tell grounded from ungrounded at all,
-# rather than only what it found. Exit 2 = the harness is broken.
-step kinds-harness    must-pass tools/port/audit-kinds --selftest
-# Band levels are alignment-free and carry their own known negative on every run;
-# the difference-signal half of the same tool stays report-only and asserts
-# nothing. See docs/port/DECISIONS.md -- the waveform question is still open.
-step transcode-bands  must-pass tools/port/verify-transcode-fidelity
-# Asks whether the band measurement is LIVE, not just what it found. An empty
-# band list makes every comparison read 0.0 dB and pass; that now exits 2.
-step bands-harness    must-pass tools/port/verify-transcode-fidelity --selftest
-step capture-controls must-pass tools/port/check-capture-controls
-step menu-audio       must-pass env OUT="$OUT/audio" tools/port/verify-menu-audio
-# 🔴 ADDED 2026-09-02, because `menu-audio` above SPENT WEEKS UNABLE TO FAIL. It
-# computed its verdict, printed a red line when a cue was silent, and its python
-# had no exit path -- so it returned 0 while registered `must-pass` here. Every
-# other assertion in this file has a control for exactly this reason and audio
-# was the one that did not. It costs a second set of runs and that is the price.
-step menu-audio-ctl  must-pass env OUT="$OUT/audioctl" tools/port/verify-menu-audio --control
-# 🔴 ADDED 2026-09-01 after a human found Ⓐ dead on a real controller while the
-# unattended P5 walk passed. `--script` sends `InputEventAction`, which BYPASSES
-# the input map, so every check here asserted the code BELOW the map and nothing
-# about the map -- which was missing a joypad binding for `ui_accept` and
-# `ui_cancel` entirely. The same blind spot hid a second defect: an
-# `InputEventAction` is not an analog axis, so nothing could see that a held
-# stick fired once per jitter.
-step input-map        must-pass tools/port/verify-input
-step input-control    must-pass tools/port/verify-input --control
-# 🔴 ADDED 2026-09-02 after a human found the splash frozen while THREE checks
-# here were green. The frozen sweep proved a pose could be drawn, the settled
-# comparison scored 0.01 % against the oracle (a frozen screen matches a settled
-# reference perfectly -- that is what frozen means), and the fps counter counted
-# frames drawn. All three measured throughput or a pose; none measured CHANGE.
-# Same shape as InputEventAction bypassing the input map, two rows above.
-step boot-motion      must-pass tools/port/verify-motion
-step motion-control   must-pass tools/port/verify-motion --control
-# A stale index is worse than none: it answers "is this already decided?" with a
-# confident no. That is not hypothetical -- see the entry it was built after.
-step decisions-index  must-pass tools/port/index-decisions --check
-# `audit-kinds` checks citations in `authored/`; nothing checked the PROSE, and
-# prose is where this port explains itself. A first run found 37 of 91
-# non-resolving -- 7 of them pointing at NOTHING on any ref, left behind by the
-# monorepo move and the `export/` rename. Only that class fails; a citation that
-# is merely on a peer's unmerged branch is reported, because the fix is a merge
-# and nobody in this container can make it.
-step trajectory-fit   must-pass tools/port/fit-trajectory --selftest
-step linked-records   must-pass tools/port/check-linked-records
-step linked-rec-ctl   must-pass tools/port/check-linked-records --selftest
-step authored-declared must-pass tools/port/check-authored-vs-declared
-step authored-decl-ctl must-pass tools/port/check-authored-vs-declared --selftest
-step doc-citations    must-pass tools/port/check-citations
-step citations-control must-pass tools/port/check-citations --selftest
-# A refuted claim asserted outside its correction is a lie the corpus tells a
-# reader who greps for it. Registered claims must carry an explicit `[refuted]`.
-# 🔴 The register check had NO executable control until 2026-08-31 -- every
-# "planted a revival and it failed" in DECISIONS was done by hand, once. Four
-# cases now drive it as a subprocess and read its real exit code, including an
-# EMPTY REGISTER, which used to report clean forever.
-step claims-control   must-pass tools/port/check-claims --control
-step refuted-claims   must-pass tools/port/check-claims
-echo
-echo "reported, not asserted:"
-# Not an assertion: being behind a peer's topic branch is the normal state, and a
-# red line for it would be scenery within a day. It is here so the affordance is
-# visible on every run -- reading a peer's head needs no merge and no human.
-step peer-heads       report-only tools/port/peer-head
-step oracle-captures  report-only env OUT="$OUT/oracle" tools/port/verify-capture
-sed -n '/^screen /,$p' "$OUT/oracle-captures.log" | sed 's/^/    /'
-# 🔴 `verify-capture` prints and always exits 0. Its own header is right that the
-# numbers are not a target -- the captures carry the game's tone ramp, so RMSE has
-# a floor and driving it lower is fitting the ramp. But "not a target" is not the
-# same as "not a regression detector", and nothing here would notice `title_plate`
-# moving off 0.00 %. Asserting it needs a stored baseline per row, which is a real
-# design decision about what a baseline means when the pose is fitted. NAMED, not
-# quietly skipped.
-
-echo
-echo "consistency (expected to differ, for a stated reason):"
-rc=0; env OUT="$OUT/screens" tools/port/verify-screen >"$OUT/verify-screen.log" 2>&1 || rc=$?
-differs=$(grep -c DIFFERS "$OUT/verify-screen.log" || true)
-# 🔴 THE ALLOWANCE IS DERIVED NOW, NOT LISTED, and that is strictly stronger.
-#
-# Six screens joined this set on 2026-09-01 and the cause is diagnosed for two of
-# them: the port draws some elements ADDITIVE -- transcribed from the Decoder's
-# per-draw RB_BLENDCONTROL0 log off the running game -- and the reference has no
-# additive path at all (ui_layout.rs has exactly two blend sites, both
-# alpha-over, and line 1169 records that it tried additive and refuted it from
-# its own composite metrics). So the two renderers disagree ON PURPOSE, and the
-# size of the disagreement tracks the size of the additive set: extras has 9
-# elements and a mean of 6.74, main_menu has 5 and 3.94, and the screens with
-# none sit an order of magnitude below.
-#
-# Computing the allowance from `authored/rendering.json` rather than listing it
-# means a screen is excused BECAUSE it has additive elements the reference
-# cannot draw, and a screen that differs WITHOUT them still fails -- which a
-# literal list could not express, and which keeps this from going stale against
-# the map it is derived from. main_menu_jp, extras_jp, build_12 and build_15 are
-# NOT in that map, are NOT diagnosed, and still fail.
-# docs/port/verify-screen-blend-divergence.md
-# 🔴 THIS DERIVED FROM authored/rendering.json AND I DELETED THAT KEY MYSELF.
-# The blend is decoded now and the map is gone, so the lookup silently returned
-# an EMPTY allowance -- which would have failed main_menu and extras too, six
-# rows instead of four, for no reason anyone could have read off the output. A
-# derived allowance is only as durable as the thing it derives from, and I
-# pointed this one at a file I then emptied one iteration later.
-#
-# It now derives from the EXPORT, which is what the port actually draws from: a
-# screen may differ if any of its elements -- or any nested focus/leaf element --
-# carries `blend_additive: true`, because `ui_layout.rs` has no additive path at
-# all and cannot reproduce those draws by construction.
-#
-# ⚠️ THIS ALLOWANCE IS LOOSER THAN THE ONE IT REPLACES AND THAT IS A REAL COST.
-# The old map covered 3 screens because it was a transcription of what somebody
-# had driven the game to; the bit is disc-wide, so 12 of 16 screens now qualify
-# and verify-screen goes fully green. Measured after the swap, the two sets line
-# up exactly -- all 10 screens that DIFFER have a drawn additive element, and all
-# 6 that agree have none -- so nothing is being excused that does not have the
-# cause. But a screen that starts differing for some OTHER reason will now be
-# excused if it happens to carry an additive element anywhere, and this check
-# will not say so.
-#
-# ✅ THE REAL FIX HAS LANDED -- AT A TAG, NOT YET ON `main`, WHICH IS WHY THIS
-# CLAUSE IS STILL HERE. `ui_layout::blit` draws additive as of
-# formats-pin-2026-09-01b, so the comparison is capable again and this widening
-# has lost its justification.
-#
-# Measured at that tag, in a detached worktree, with SYLPHEED_CLI pointed at it:
-# main_menu 7.26 -> 1.21, extras 6.98 -> 1.02, both JP twins likewise, and
-# build_00/build_01 go DIFFERS -> OK (over3 3422 -> 0). A 6x collapse.
-#
-# 🔴 NOT NARROWED YET, AND ON PURPOSE. This script builds the reference from the
-# WORKSPACE crate, and the additive path is not on `main`. Narrowing now would
-# turn check-all red against a reference that still cannot draw additive -- a
-# wall of failures meaning one thing, which is the defect the display guard above
-# exists to prevent.
-#
-# TRIGGER, so this does not rot: when `grep -q additive crates/sylpheed-formats/src/ui_layout.rs`
-# succeeds, delete the export-derived clause and keep only `-e title -e title_jp`.
-# The set that should then differ is measured in
-# docs/port/verify-screen-blend-divergence.md: title, title_jp, main_menu, extras,
-# main_menu_jp, extras_jp, build_12, build_15 -- and build_00/build_01 pass.
-additive_screens=$(python3 -c "
-import json, glob, os
-out = []
-for p in sorted(glob.glob('export/screens/*/*.json')):
-    d = json.load(open(p))
-    def any_add(els):
-        for e in els:
-            if e.get('blend_additive'):
-                return True
-            for k in ('focus', 'leaf'):
-                if any_add((e.get(k) or {}).get('elements', [])):
-                    return True
-        return False
-    if any_add(d.get('elements', [])):
-        out.append(os.path.basename(p)[:-5])
-print('\n'.join(out))" 2>/dev/null)
-allow_args=(-e title -e title_jp)
-for sc in $additive_screens; do allow_args+=(-e "$sc"); done
-printf '  %-24s allowing %s (additive set + 2 legacy)\n' verify-screen \
-  "$(echo $additive_screens | tr '\n' ' ')"
-unexpected=$(grep DIFFERS "$OUT/verify-screen.log" | awk '{print $1}' \
-  | grep -vx "${allow_args[@]}" || true)
-
-# 🔴 SCREENS FROM A NEWLY EXPORTED ARCHIVE HAVE NEVER BEEN COMPARED, AND THAT IS
-# NOT THE SAME AS DISAGREEING.
-#
-# `verify-screen` is renderer-vs-renderer, and BOTH its allowance and the
-# reference renderer itself were built against GP_TITLE. When the exporter gained
-# `GP_OPTIONS` (2026-09-03) its 14 screens all read DIFFERS at means of 10-60
-# against 0.02-7.3 for the calibrated set -- which says nothing yet, because
-# nobody has looked at a single one of them.
-#
-# They are REPORTED, not failed and NOT added to the allowed set. Failing would
-# put the suite red for a state nobody has investigated -- the wall of
-# meaningless failures the display guard exists to prevent. Allowing would assert
-# they are explained, and `verify-screen`'s own header is emphatic that the
-# allowed set means "measured, cause open", not "ignore this".
-#
-# The discriminator is the sprite group in the manifest path, so a screen becomes
-# assertable the moment somebody moves it into the calibrated population
-# deliberately, rather than by an export widening underneath the check.
-uncompared=$(python3 -c "
-import json
-m = json.load(open('export/manifest.json'))
-print('\n'.join(s['name'] for s in m['screens']
-                 if not s['file'].startswith('screens/title/')))" 2>/dev/null)
-if [ -n "$uncompared" ]; then
-  still=$(echo "$unexpected" | grep -vxF -f <(echo "$uncompared") || true)
-  newly=$(echo "$unexpected" | grep -xF -f <(echo "$uncompared") || true)
-  unexpected="$still"
-  [ -n "$newly" ] && printf '  %-24s %d screen(s) NEVER COMPARED (new archive, uncalibrated): %s\n' \
-    verify-screen "$(echo $newly | wc -w)" "$(echo $newly | tr '\n' ' ')"
-fi
-
-# 🔴 THE OLD ALLOWANCE WAS FALSE, AND MY FIRST REPLACEMENT REASON WAS ALSO
-# WRONG. Both are recorded because the second error is the more instructive.
-#
-# It said: "the pin is not on main, so this compares two decoder eras". I
-# replaced that with "the eras render identically -- 0 pixels different on three
-# screens". 🔴 **That measurement was void**: the two binaries I compared had the
-# same md5. I built one in a worktree at the pinned tag and one from the
-# workspace, and both commits carry the record-layout fix, so I compared a
-# binary with itself and reported the zero as evidence.
-#
-# Rebuilt properly against `origin/main`, which is the genuinely stale era
-# (`rest t=70 [12 70 80 -]` against the fixed `rest t=12 [0 12 70 80]`):
-#
-#   title      0 px      main_menu  0 px      title_jp  74 507 px
-#
-# ✅ The eras DO change pixels, and `title_jp` is one of the seven bundles where
-# they do -- reproducing the Decoder's figure exactly, under their flags and
-# mine. My "--animated masks it" hypothesis was wrong too.
-#
-# ✅ BUT THE ERA STILL CANNOT EXPLAIN THIS SCRIPT'S ROWS, for a reason I had not
-# established: BOTH SIDES OF THIS COMPARISON ARE THE FIXED ERA. The exporter is
-# pinned to `formats-pin-2026-08-30` and this reference is built from the
-# workspace, and a binary built from each has the SAME md5. There is no era
-# mismatch here to explain anything. Right answer, wrong evidence, and the wrong
-# evidence was a broken experiment.
-#
-# The real reasons are per-screen and already documented:
-#   title    -- the ptloop SWEEP PHASE residual, max 6 / over3 790, unchanged
-#               across every renderer change since P1 (DECISIONS.md).
-#   title_jp -- the `--pose=rest` sparkle handling. Adjudicated against the
-#               oracle: the port's SHIPPED pose scores r +0.9994 against the
-#               game where the reference scores +0.8727, and `--pose=rest` is
-#               what this script compares.
-#   ⚠️ title_jp is ALSO an era-sensitive bundle, so if this reference is ever
-#   built from a different era than the exporter's pin, that row's cause changes
-#   and this note stops applying. Check the md5s before trusting it again.
-#
-# So the allowance is now a NAMED SET, not a count with an excuse. A DIFFERS on
-# any other screen fails the run, which a count never could.
-# 🔴 SIX MORE SCREENS JOINED THIS SET ON 2026-09-01 AND THE SET WAS NOT WIDENED.
-# main_menu, extras, main_menu_jp, extras_jp, build_12, build_15. Measured, not
-# diagnosed: the difference is full-frame, it is EXACTLY ZERO on unblended
-# pixels (18 081 of them agree to a hundredth of a level) and gamma-shaped on
-# every blended one, so it is a blend-SPACE divergence rather than moved content.
-# Scored against the live capture the port is 16 % closer than the reference --
-# an ordering only, since both sides share this script's --pose=rest
-# contamination. Left failing on purpose: this allowance has twice been widened
-# with a reason that turned out false, and "I measured it but cannot say which
-# renderer is right" is not a reason. docs/port/verify-screen-blend-divergence.md
-if [ -n "$unexpected" ]; then
-  printf '  %-24s 🔴 DIFFERS on %s -- not in the allowed set\n' verify-screen "$(echo $unexpected | tr '\n' ' ')"
-  printf '  %-24s see docs/port/verify-screen-blend-divergence.md -- measured, cause open\n' ""
-  fail=1
-else
-  printf '  %-24s %d DIFFERS, both named and explained per screen:\n' verify-screen "$differs"
-  printf '  %-24s title = sweep phase; title_jp = rest-pose sparkles (the port is\n' ""
-  printf '  %-24s closer to the GAME there than the reference is).\n' ""
-fi
-
-# Separately, and unrelated to the rows above: revert to the path dependency when
-# the pin lands. Read from Cargo.toml so it cannot drift out of step again.
-pin=$(sed -n 's/.*tag = "\([^"]*\)".*/\1/p' crates/sylpheed-export/Cargo.toml | head -1)
-if [ -n "$pin" ] && git merge-base --is-ancestor "$pin" origin/main 2>/dev/null; then
-  printf '  %-24s ⚠️  %s has landed on main -- revert Cargo.toml to the path dep\n' pin "$pin"
-fi
-
-echo
-[ $fail -eq 0 ] && echo "every asserting check passes" || echo "🔴 a check failed"
-exit $fail

tools/re-capture/boot_timeline_probe.py

@@ -0,0 +1,234 @@
+"""Time the whole boot, and measure the PRESENTATION RATE per screen.
+
+Two jobs, one oracle session, because they need each other.
+
+1. **The boot timeline the port asked for.** Every screen-to-screen transition
+   from launch to the main menu, wall-clock, with the black holds marked. The
+   port paces its boot off `ScreenView.settle_time()` = a group's `rest.t`, and
+   `rest.t` is NOT when a screen settles (docs/re/REFUTED.md) — so every screen's
+   dwell is currently wrong by an unknown amount.
+
+2. **Frames, not seconds.** Two pages of the corpus measure the same declared
+   120 keyframe units during a static hold and disagree by 2 %: settle→plate is
+   2.135 s (28.10 fps implied) and one focus-ring revolution is 2.177 s (27.56
+   implied). Either the presentation rate differed between those sessions, or one
+   interval is not 120 units. The two were taken on DIFFERENT SCREENS, so this
+   measures the rate on each — with the game's own frame counter, not a guess
+   about what changes between grabs.
+
+`--log_ui_draws=true --ui_draw_capture_frames=N` makes Canary log
+`[UI-CAP] capture armed` and then `[UI-CAP] done: D draws over F frames`. Timing
+between those two lines in its own stdout gives frames/second directly, and it
+re-arms (the log index is `{:02d}`), so one session can measure several screens.
+
+⚠️ The instrument can perturb what it measures — writing a draw log costs the
+emulator something. Control built in: the ring period is measured both DURING a
+capture and OUTSIDE one, and a rate that is an artefact of logging would move it.
+
+    boot_timeline_probe.py --control
+    boot_timeline_probe.py --run SECONDS OUT.tsv CANARY_STDOUT [shots_dir]
+"""
+import os
+import subprocess
+import sys
+import time
+
+import numpy as np
+from PIL import Image
+
+SD = os.path.dirname(os.path.abspath(__file__))
+sys.path.insert(0, SD)
+import title_timing_probe as T  # noqa: E402  (same crop, same ZNCC, same controls)
+
+REPO = os.path.dirname(os.path.dirname(SD))
+CAP = os.path.join(REPO, "docs", "re", "captures")
+
+# The boot shows two splashes before the movie; both are committed captures.
+T.REFS["splash_pub"] = "title-builds/live-splash-publisher.png"
+T.REFS["splash_dev"] = "title-builds/live-splash-developer.png"
+T._R.clear()
+
+RATE = 8
+CAPTURE_FRAMES = int(os.environ.get("UICAP_FRAMES", "300"))
+
+
+def control():
+    """Every control title_timing_probe has, plus the two splashes."""
+    T.CONTROLS.extend([
+        (os.path.join(CAP, "title-builds/live-splash-publisher.png"), "splash_pub"),
+        (os.path.join(CAP, "title-builds/live-splash-developer.png"), "splash_dev"),
+    ])
+    return T.control()
+
+
+def _tail(path, seen):
+    """New lines appended to the emulator's stdout since the last call."""
+    try:
+        with open(path, "rb") as f:
+            f.seek(seen)
+            b = f.read()
+        return b.decode("utf-8", "replace"), seen + len(b)
+    except OSError:
+        return "", seen
+
+
+def arm_capture(log_path, seen, timeout=90.0):
+    """Press F10, then time the emulator's own armed->done lines.
+
+    Timed between the two LOG lines, not from the keypress: the arm latency is
+    then excluded rather than folded into the rate.
+    """
+    win = subprocess.run(["xdotool", "search", "--name", "Xenia-canary"],
+                         capture_output=True, text=True).stdout.split()
+    if not win:
+        return None, seen
+    w = win[-1]
+    subprocess.run(["xdotool", "windowactivate", w], capture_output=True)
+    subprocess.run(["xdotool", "key", "--window", w, "F10"], capture_output=True)
+    subprocess.run(["xdotool", "key", "F10"], capture_output=True)
+    t_armed = t_done = None
+    frames = draws = None
+    deadline = time.time() + timeout
+    while time.time() < deadline:
+        chunk, seen = _tail(log_path, seen)
+        for line in chunk.splitlines():
+            if "[UI-CAP] capture armed" in line and t_armed is None:
+                t_armed = time.time()
+            elif "[UI-CAP] done" in line and t_armed is not None:
+                t_done = time.time()
+                # "[UI-CAP] done: 1526 draws over 300 frames"
+                parts = line.replace(":", " ").split()
+                try:
+                    draws = int(parts[parts.index("done") + 1])
+                    frames = int(parts[parts.index("over") + 1])
+                except (ValueError, IndexError):
+                    pass
+        if t_done:
+            break
+        time.sleep(0.02)
+    if not (t_armed and t_done and frames):
+        return None, seen
+    dt = t_done - t_armed
+    return {"frames": frames, "draws": draws, "seconds": dt, "fps": frames / dt}, seen
+
+
+def run(limit, out_path, log_path, shots_dir):
+    os.makedirs(shots_dir, exist_ok=True)
+    n = T.W * T.H * 3
+    p = T.open_stream()
+    t0 = time.time()
+    seg = t0
+    frames = 0
+    seen = 0
+    ev = []
+    rates = {}
+    state = "boot"
+    last_label = None
+    last_gray = None
+    prev_mean = -1.0
+    fh = open(out_path, "w")
+    fh.write("#t\tglyph\tmean\tmotion\t" + "\t".join(T.REFS) + "\tlabel\n")
+
+    def mark(name, t=None):
+        t = time.time() - t0 if t is None else t
+        ev.append((name, t))
+        print(f"EVENT {name} t={t:.3f}", flush=True)
+        return t
+
+    while time.time() - t0 < limit and state != "done":
+        now = time.time()
+        # Restart only while still waiting; never across a measured interval.
+        if state == "boot" and now - seg > 30:
+            p.kill(); p = T.open_stream(); seg = now
+            fh.write(f"#restart\t{now - t0:.3f}\n")
+        buf = p.stdout.read(n)
+        if len(buf) < n:
+            p.kill(); p = T.open_stream(); seg = time.time(); continue
+        t = time.time() - t0
+        rgb = np.frombuffer(buf, np.uint8).reshape(T.H, T.W, 3)
+        g = T.gray_of(rgb)
+        gl = T.glyph(rgb)
+        sc = T.scores(g)
+        lb = T.label(sc)
+        surf = T.surface(g)
+        mn = float(surf.mean())
+        mo = float(np.abs(surf[::8, ::8] - last_gray).mean()) if last_gray is not None else -1.0
+        last_gray = surf[::8, ::8].copy()
+        frames += 1
+        fh.write(f"{t:.3f}\t{gl}\t{mn:.3f}\t{mo:.3f}\t"
+                 + "\t".join(f"{sc[k]:+.4f}" for k in T.REFS) + f"\t{lb}\n")
+
+        # Every label change and every entry/exit from pure black is a boot event.
+        blk = "black" if mn < 1.0 else lb
+        if blk != last_label:
+            mark(f"screen:{blk}", t)
+            last_label = blk
+            if blk in ("splash_pub", "splash_dev", "title_noplate", "menu"):
+                Image.fromarray(rgb).save(os.path.join(shots_dir, f"boot-{blk}.png"))
+
+        if state == "boot":
+            if lb in ("title_noplate", "title_plate") and 0 <= mo < 2.0 and gl >= 100:
+                mark("title_settled", t); state = "title"
+        elif state == "title":
+            if gl >= T.PLATE_GLYPH:
+                mark("plate", t); state = "plate_hold"; hold_from = t
+        elif state == "plate_hold":
+            if t - ev[-1][1] > 3.0:
+                fh.flush()
+                r, seen = arm_capture(log_path, seen)
+                rates["title"] = r
+                mark(f"rate_title={r and round(r['fps'], 3)}")
+                state = "press"
+        elif state == "press":
+            tp = T.tap("A") - t0
+            ev.append(("pressA", tp)); print(f"EVENT pressA t={tp:.3f}", flush=True)
+            state = "toMenu"
+        elif state == "toMenu":
+            if lb == "menu":
+                mark("menu", t); state = "menuSettle"; menu_at = t
+        elif state == "menuSettle":
+            if t - ev[-1][1] > 6.0:
+                fh.write(f"#ring_free_start\t{t:.3f}\n")
+                state = "ringFree"; ring_from = t
+        elif state == "ringFree":
+            # 12 s of ring with NOTHING else running -- the outside-capture control
+            if t - ring_from > 12.0:
+                fh.write(f"#ring_free_end\t{t:.3f}\n")
+                fh.flush()
+                r, seen = arm_capture(log_path, seen)
+                rates["menu"] = r
+                mark(f"rate_menu={r and round(r['fps'], 3)}")
+                fh.write(f"#ring_capture_end\t{time.time()-t0:.3f}\n")
+                state = "ringAfter"; after_from = time.time() - t0
+        elif state == "ringAfter":
+            if t - after_from > 12.0:
+                state = "done"
+
+    p.kill()
+    dt = time.time() - t0
+    fh.write(f"#summary\tframes={frames}\telapsed={dt:.1f}\tfps={frames/dt:.2f}\trequested={RATE}\n")
+    for k, r in rates.items():
+        if r:
+            fh.write(f"#rate\t{k}\tframes={r['frames']}\tdraws={r['draws']}"
+                     f"\tseconds={r['seconds']:.3f}\tfps={r['fps']:.4f}\n")
+        else:
+            fh.write(f"#rate\t{k}\tFAILED\n")
+    for name, t in ev:
+        fh.write(f"#event\t{name}\t{t:.3f}\n")
+    fh.close()
+    print(f"\n{frames} frames in {dt:.1f}s = {frames/dt:.2f} fps (requested {RATE})")
+    for k, r in rates.items():
+        print(f"  presentation rate on {k}: "
+              + (f"{r['fps']:.4f} fps ({r['frames']} frames in {r['seconds']:.3f} s, "
+                 f"{r['draws']} draws)" if r else "FAILED"))
+    return 0
+
+
+if __name__ == "__main__":
+    if len(sys.argv) > 1 and sys.argv[1] == "--control":
+        sys.exit(control())
+    if len(sys.argv) > 4 and sys.argv[1] == "--run":
+        sys.exit(run(float(sys.argv[2]), sys.argv[3], sys.argv[4],
+                     sys.argv[5] if len(sys.argv) > 5 else "/sylph-home/re/shots/boot-timeline"))
+    print(__doc__)
+    sys.exit(2)

tools/re-capture/dump_image.py

@@ -0,0 +1,81 @@
+#!/usr/bin/env python3
+"""Dump the guest's DECOMPRESSED executable image out of live Xenia memory.
+
+Why this exists: the static PPC route the corpus is built on ran against a
+disassembly database at `/work/xenia-rs/sylpheed.db`, and that file is **not in
+this container** — the same migration that took the Xenia storage root. Without
+it, every finding that cites a `sub_82xxxxxx` is unre-checkable.
+
+`/disc/default.xex` cannot substitute: it is encrypted and LZX-compressed. Its
+header is intact (`XEX2`, original PE name `default.pe`) and everything after is
+noise — `strings` finds **zero** occurrences of `GamePart` in it.
+
+Xenia decompresses, decrypts and relocates the image at load, so a running guest
+holds exactly the flat VA image the corpus calls the `.pe`. Dump it once and the
+static route works offline, with no emulator and no disc.
+
+Validated on write, and both checks are the corpus's own, not this tool's:
+
+  * `0x820A1630` must hold the **GamePart id table** — 29 pointers into `.rdata`
+    resolving to `GP_TITLE` … `GP_TEST`, with `GP_CHALLENGE` at id 26
+    (docs/re/challenge-mission-gate.md);
+  * the image must contain the Xbox 360 D3D runtime's own error strings, which a
+    mis-based or partial dump does not.
+
+    dump_image.py [OUT.pe]           # with Canary running
+"""
+import os
+import struct
+import sys
+
+SD = os.path.dirname(os.path.abspath(__file__))
+sys.path.insert(0, SD)
+import gmem  # noqa: E402
+
+LO, HI = 0x82000000, 0x82400000
+BASE = LO
+
+EXPECT = {0: "GP_TITLE", 3: "GP_LOAD", 11: "GP_READY_ROOM", 26: "GP_CHALLENGE", 28: "GP_TEST"}
+
+
+def validate(buf):
+    def s_at(va):
+        o = va - BASE
+        e = buf.find(b"\0", o, o + 64)
+        return buf[o:e].decode("ascii", "replace")
+
+    bad = []
+    for i, want in EXPECT.items():
+        p = struct.unpack_from(">I", buf, 0x820A1630 - BASE + 4 * i)[0]
+        got = s_at(p) if LO <= p < HI else f"<ptr {p:#x} out of range>"
+        if got != want:
+            bad.append(f"GamePart id {i}: expected {want!r}, got {got!r}")
+    if buf.count(b"ERR[D3D]") < 1:
+        bad.append("no Xbox 360 D3D runtime strings — this is not the game image")
+    return bad
+
+
+def main(out):
+    path = gmem.mem_path()
+    off = gmem.va_to_off(LO)
+    with open(path, "rb") as f:
+        f.seek(off)
+        buf = f.read(HI - LO)
+    if len(buf) < HI - LO:
+        print(f"short read: {len(buf)} of {HI - LO}", file=sys.stderr)
+        return 1
+    bad = validate(buf)
+    for b in bad:
+        print("FAIL:", b, file=sys.stderr)
+    if bad:
+        return 2
+    open(out, "wb").write(buf)
+    pages = sum(1 for i in range(0, len(buf), 4096) if any(buf[i:i + 4096]))
+    print(f"wrote {out}  {len(buf)} bytes  VA {LO:#x}..{HI:#x}")
+    print(f"validated: GamePart id table + D3D runtime strings; "
+          f"{pages}/{len(buf)//4096} non-empty 4K pages")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main(sys.argv[1] if len(sys.argv) > 1 else "/sylph-home/re/sylpheed-image.pe"))

tools/re-capture/fade_quads.py

@@ -4,8 +4,12 @@
 The screen-transition fade lives here -- see docs/re/screen-transitions.md.
 Usage: PAK=<pak> fade_quads.py [build...]   (default: GP_TITLE, builds 2 4 5 6)"""
 import struct, sys, glob, os, zlib
-sys.path.insert(0, "/work/Syplheed-Reborn/tools/re-capture")
-src = open("/work/Syplheed-Reborn/tools/re-capture/regn_decode.py").read()
+# The monorepo migration left this pointing at /work/Syplheed-Reborn, a path
+# that no longer exists -- so the command screen-transitions.md cites as its
+# evidence could not be re-run.  Resolve beside this file instead.
+_SD = os.path.dirname(os.path.abspath(__file__))
+sys.path.insert(0, _SD)
+src = open(os.path.join(_SD, "regn_decode.py")).read()
 exec(src.split("# ── POF0")[0])
 
 DECL_AT, DECL_ENTRY, KF = 0x20, 60, 40
@@ -34,7 +38,10 @@ def parse(bundle):
         groups[idx]=g; pos=end
     return names, groups
 
-pak = os.environ.get("PAK", "/work/sylph_extract/dat/GP_TITLE.pak")
+# ...and the default pak pointed at /work/sylph_extract, which the disc mount
+# replaced.  $SYLPHEED_DISC is what run-canary and sylpheed-cli both use.
+pak = os.environ.get("PAK") or os.path.join(
+    os.environ.get("SYLPHEED_DISC", "/disc"), "dat", "GP_TITLE.pak")
 E = pak_entries(pak)
 E = [b for h,b in E]
 # build index -> pak entry index, from `screen list`: 0..9 then 12, 15

tools/re-capture/focus_ring_probe.py

@@ -0,0 +1,159 @@
+#!/usr/bin/env python3
+"""Does the main menu's focus ring KEEP spinning, or is it drawn once and held?
+
+The question is not "is the ring rotated" -- one oracle frame already showed it
+at a large angle (docs/re/structures/ui-button-focus-record.md).  It is whether
+that rotation is ANIMATED while a button sits focused, which is what decides
+whether a port draws a static ring or runs a loop.
+
+Instrument: a live x11grab filmstrip and the per-pixel TEMPORAL standard
+deviation of the frames while nothing is touched.  A spinning ring makes its
+own box vary; a held one does not.  No angle is estimated anywhere -- the
+centroid estimator that would do that fails its own control by up to 19.8 deg
+(same page), so this probe measures presence-of-change instead, which is the
+question actually asked.
+
+NO FIXED PIXEL BOXES.  xenia's window has a menu bar and the game surface is
+1279x675 inside a 1280x720 root, so game coordinates do not address grab
+coordinates.  This probe saves whole-frame accumulators; `focus_ring_report.py`
+aligns them against a committed capture first and only then reads boxes.
+
+Phases: A = 20 s untouched, then d-pad DOWN, then C = 12 s untouched.
+The d-pad press is the POSITIVE CONTROL: |mean(A) - mean(C)| must fire at the
+two ring locations, or a null in phase A is a dead instrument, not a finding.
+
+Usage:  focus_ring_probe.py OUTDIR
+"""
+import os, subprocess, sys, time
+import numpy as np
+from PIL import Image
+
+W, H = 1280, 720
+SD = os.path.dirname(os.path.abspath(__file__))
+OUT = sys.argv[1] if len(sys.argv) > 1 else "/sylph-home/re/ringcap"
+os.makedirs(OUT, exist_ok=True)
+RESTART_S = 25          # a long-lived x11grab stream stalls and repeats frames
+
+
+def open_stream():
+    return subprocess.Popen(
+        ["ffmpeg", "-loglevel", "error", "-f", "x11grab", "-draw_mouse", "0",
+         "-video_size", f"{W}x{H}", "-i", ":98", "-r", "4",
+         "-f", "rawvideo", "-pix_fmt", "rgb24", "-"],
+        stdout=subprocess.PIPE, bufsize=W * H * 3 * 2)
+
+
+class Stream:
+    def __init__(self):
+        self.p = open_stream(); self.seg = time.time()
+    def read(self):
+        if time.time() - self.seg > RESTART_S:
+            self.p.kill(); self.p = open_stream(); self.seg = time.time()
+        buf = self.p.stdout.read(W * H * 3)
+        if len(buf) < W * H * 3:
+            self.p.kill(); self.p = open_stream(); self.seg = time.time()
+            return None
+        return np.frombuffer(buf, np.uint8).reshape(H, W, 3)
+    def close(self):
+        try: self.p.kill()
+        except Exception: pass
+
+
+sys.path.insert(0, SD)
+from screen_match import classify_array   # controlled: 8/8, incl. the movie
+                                          # frames that broke the old oracle
+
+
+def collect(st, secs, tag):
+    """Whole-frame temporal mean and std over `secs`, plus a PNG filmstrip."""
+    t0 = time.time(); n = 0
+    acc = acc2 = None
+    next_shot = 0.0
+    while True:
+        el = time.time() - t0
+        if el >= secs:
+            break
+        a = st.read()
+        if a is None:
+            continue
+        f = a.astype(np.float64)
+        acc = f.copy() if acc is None else acc + f
+        acc2 = f * f if acc2 is None else acc2 + f * f
+        if el >= next_shot:
+            Image.fromarray(a).save(f"{OUT}/{tag}-t{el:05.1f}.png")
+            next_shot = el + 4.0
+        n += 1
+    mean = acc / n
+    std = np.sqrt(np.maximum(acc2 / n - mean * mean, 0))
+    np.save(f"{OUT}/{tag}-mean.npy", mean.astype(np.float32))
+    np.save(f"{OUT}/{tag}-std.npy", std.astype(np.float32))
+    Image.fromarray(mean.astype(np.uint8)).save(f"{OUT}/{tag}-mean.png")
+    # a visible std map, scaled x8 and clipped -- an artefact a human can look at
+    Image.fromarray(np.clip(std * 8, 0, 255).astype(np.uint8)).save(f"{OUT}/{tag}-std8.png")
+    print(f"[{tag}] {n} frames in {secs:.0f}s = {n/secs:.2f} fps; "
+          f"whole-frame std mean {std.mean():.4f} max {std.max():.2f}", flush=True)
+    return mean, std, n
+
+
+def main():
+    st = Stream()
+    t0 = time.time(); seen = None; last = None; skipped = False
+    # ONE (A) ~45 s in skips the intro movie: measured, title at ~57 s against a
+    # ~193 s no-input baseline (HANDOFF, movie-binding.md).  HAMMERING is what
+    # breaks the boot -- 88 presses left a permanent black screen -- so exactly
+    # one, and only once.
+    while time.time() - t0 < 620:
+        a = st.read()
+        if a is None:
+            continue
+        last = a
+        el = time.time() - t0
+        if not skipped and el > 45:
+            subprocess.run(["python3", f"{SD}/pad.py", "tap", "A", "0.3"], check=False)
+            skipped = True
+            print(f"t={el:6.1f}s  one (A) to skip the intro movie", flush=True)
+            continue
+        c, sc = classify_array(a)
+        if c != seen:
+            print(f"t={el:6.1f}s screen={c}  " +
+                  "  ".join(f"{k}={v:+.3f}" for k, v in sc.items()), flush=True)
+            seen = c
+        if c == "title":
+            break
+    if seen != "title":
+        print("NEVER REACHED THE TITLE"); st.close(); return 1
+    Image.fromarray(last).save(f"{OUT}/00-title.png")
+    subprocess.run(["python3", f"{SD}/pad.py", "tap", "A", "0.3"], check=False)
+    print("(A) on the title", flush=True)
+    t1 = time.time(); got = False
+    while time.time() - t1 < 150:
+        a = st.read()
+        if a is None:
+            continue
+        c, sc = classify_array(a)
+        if c == "menu":
+            got = True; break
+    if not got:
+        print("NO MENU AFTER A"); st.close(); return 2
+    time.sleep(4)          # let the menu's ~1 s fade-in and element ramps settle
+    a = st.read()
+    if a is not None:
+        Image.fromarray(a).save(f"{OUT}/01-menu.png")
+    print("AT MAIN MENU", flush=True)
+
+    mA, sA, nA = collect(st, 20, "A")
+    subprocess.run(["python3", f"{SD}/pad.py", "dpad", "down"], check=False)
+    print(">>> d-pad DOWN pressed", flush=True)
+    time.sleep(2.0)
+    mC, sC, nC = collect(st, 12, "C")
+
+    d = np.abs(mA - mC)
+    np.save(f"{OUT}/AC-absdiff.npy", d.astype(np.float32))
+    Image.fromarray(np.clip(d * 4, 0, 255).astype(np.uint8)).save(f"{OUT}/AC-absdiff4.png")
+    print(f"[A-vs-C] absdiff mean {d.mean():.4f} max {d.max():.2f}", flush=True)
+    st.close()
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

tools/re-capture/focus_ring_report.py

@@ -0,0 +1,109 @@
+#!/usr/bin/env python3
+"""Read focus_ring_probe.py's accumulators, after ALIGNING them to game space.
+
+A grab is the whole root window; game coordinates only address it once the
+window chrome offset is measured.  This script measures that offset by
+correlating the run's own mean frame against the committed `live-main-menu.png`
+over a +/-12 px search, and refuses to report anything if the alignment is poor.
+
+Then, in game coordinates:
+  ring boxes    -- 80x80 around each button's declared rest position; the ring
+                   `ptbtneff01` is 42x46 and sits left of the label
+  static boxes  -- `ptmsg` (one untimed keyframe) and a background corner:
+                   the NEGATIVE controls, which must read sensor noise
+  positive ctrl -- |mean(A) - mean(C)| across the d-pad press must fire at the
+                   two rings that changed state, or a null in A is a dead
+                   instrument rather than a finding.
+"""
+import os, sys
+import numpy as np
+from PIL import Image
+
+OUT = sys.argv[1] if len(sys.argv) > 1 else "/sylph-home/re/ringcap"
+REPO = os.path.dirname(os.path.dirname(os.path.dirname(os.path.abspath(__file__))))
+REF = os.path.join(REPO, "docs/re/captures/title-builds/live-main-menu.png")
+
+BTN_Y = [162, 242, 322, 401, 482]
+LABEL = ["NEW GAME", "LOAD GAME", "TUTORIAL", "OPTIONS", "EXTRAS"]
+BOXES = {}
+for i, y in enumerate(BTN_Y):
+    BOXES[f"ring{i+1} ({LABEL[i]})"] = (480, y - 20, 560, y + 60)
+BOXES["ptmsg footer  [static ctl]"] = (527, 595, 773, 633)
+BOXES["bg corner     [static ctl]"] = (10, 10, 130, 130)
+BOXES["button1 label [same row]"] = (560, 142, 760, 202)
+
+
+def gray(a):
+    return (0.299 * a[..., 0] + 0.587 * a[..., 1] + 0.114 * a[..., 2]).astype(np.float32)
+
+
+def zncc(x, y):
+    x = x - x.mean(); y = y - y.mean()
+    d = np.sqrt((x * x).sum() * (y * y).sum())
+    return float((x * y).sum() / d) if d else 0.0
+
+
+def align(mean_rgb, ref_rgb):
+    """Measure (dy,dx) taking GAME coords -> GRAB coords. Returns (dy,dx,corr)."""
+    g = gray(mean_rgb); r = gray(ref_rgb)
+    rh, rw = r.shape
+    best = (None, None, -1.0)
+    for dy in range(30, 60):                       # chrome is ~45 rows
+        for dx in range(-12, 13):
+            if dy + rh > g.shape[0] or dx < 0 or dx + rw > g.shape[1]:
+                continue
+            c = zncc(g[dy:dy + rh, dx:dx + rw], r)
+            if c > best[2]:
+                best = (dy, dx, c)
+    return best
+
+
+def main():
+    mA = np.load(f"{OUT}/A-mean.npy"); sA = np.load(f"{OUT}/A-std.npy")
+    mC = np.load(f"{OUT}/C-mean.npy"); sC = np.load(f"{OUT}/C-std.npy")
+    ref = np.array(Image.open(REF).convert("RGB")).astype(np.float32)
+    dy, dx, corr = align(mA, ref)
+    print(f"alignment: game(0,0) sits at grab({dx},{dy}); ZNCC {corr:+.4f}")
+    if corr < 0.80:
+        print("ALIGNMENT TOO POOR — refusing to report boxes"); return 1
+    print(f"           (independent check: the window chrome measured 45 rows)\n")
+
+    def box(arr, b):
+        x0, y0, x1, y1 = b
+        return arr[y0 + dy:y1 + dy, x0 + dx:x1 + dx, :]
+
+    d = np.abs(mA - mC)
+    print(f"{'box':<30} {'A std':>9} {'A p99.9':>9} {'C std':>9} "
+          f"{'|A-C| mean':>11} {'|A-C| max':>10}")
+    print("-" * 84)
+    rows = {}
+    for k, b in BOXES.items():
+        a_s = box(sA, b); c_s = box(sC, b); dd = box(d, b)
+        rows[k] = (float(a_s.mean()), float(np.percentile(a_s, 99.9)),
+                   float(c_s.mean()), float(dd.mean()), float(dd.max()))
+        print(f"{k:<30} {rows[k][0]:9.3f} {rows[k][1]:9.3f} {rows[k][2]:9.3f} "
+              f"{rows[k][3]:11.3f} {rows[k][4]:10.2f}")
+
+    noise = max(rows["ptmsg footer  [static ctl]"][0],
+                rows["bg corner     [static ctl]"][0])
+    print(f"\nnegative-control noise floor (max of the two static boxes): {noise:.3f}")
+    print("A box only counts as MOVING if its phase-A std clears that floor.\n")
+    for k in BOXES:
+        if "ctl" in k:
+            continue
+        v = rows[k][0]
+        print(f"  {k:<30} A std {v:7.3f}  = {v/noise:6.2f}x the noise floor"
+              f"   {'MOVING' if v > 3*noise else 'static'}")
+
+    # visual artefacts, cropped to the game surface
+    for tag, arr, sc in (("A-std", sA, 8), ("C-std", sC, 8), ("AC-absdiff", d, 4)):
+        g = arr[dy:dy + 675, dx:dx + 1279, :]
+        Image.fromarray(np.clip(g * sc, 0, 255).astype(np.uint8)).save(f"{OUT}/{tag}-game.png")
+    Image.fromarray(mA[dy:dy + 675, dx:dx + 1279, :].astype(np.uint8)).save(f"{OUT}/A-mean-game.png")
+    Image.fromarray(mC[dy:dy + 675, dx:dx + 1279, :].astype(np.uint8)).save(f"{OUT}/C-mean-game.png")
+    print(f"\nwrote game-space artefacts to {OUT}")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

tools/re-capture/footer_and_locked_rows.py

@@ -0,0 +1,92 @@
+#!/usr/bin/env python3
+"""Re-measure two menu facts from the COMMITTED oracle captures — no disc needed.
+
+  1. Which screens advertise Ⓑ in their footer legend.
+     The pad glyphs are saturated green (Ⓐ) and red (Ⓑ) discs on a blue field,
+     so a colour test finds them without knowing where the footer is.
+
+  2. Whether a dim MISSION SELECT row is LOCKED or merely UNFOCUSED.
+     Three brightness levels discriminate; the all-unlocked capture is the
+     control that separates them.
+
+Usage:  python3 tools/re-capture/footer_and_locked_rows.py [repo-root]
+"""
+import sys
+import pathlib
+import numpy as np
+from PIL import Image
+
+ROOT = pathlib.Path(sys.argv[1] if len(sys.argv) > 1 else ".").resolve()
+CAP = ROOT / "docs/re/captures"
+
+
+def glyph_masks(rgb):
+    r, g, b = rgb[:, :, 0], rgb[:, :, 1], rgb[:, :, 2]
+    green = (g > 110) & (g > r + 45) & (g > b + 45)
+    red = (r > 110) & (r > g + 45) & (r > b + 45)
+    return green, red
+
+
+def blobs(mask, gap=20):
+    ys, xs = np.nonzero(mask)
+    if len(xs) == 0:
+        return []
+    o = np.argsort(xs)
+    xs, ys = xs[o], ys[o]
+    out, start = [], 0
+    for i in range(1, len(xs) + 1):
+        if i == len(xs) or xs[i] - xs[i - 1] > gap:
+            s = slice(start, i)
+            out.append((int(xs[s].min()), int(xs[s].max()),
+                        int(ys[s].min()), int(ys[s].max()), i - start))
+            start = i
+    return out
+
+
+def footers():
+    print("== 1. footer legends: does the screen advertise Ⓑ? ==")
+    print(f"{'capture':46} {'Ⓐ px':>7} {'Ⓑ px':>7}   verdict")
+    shots = [
+        ("title-builds/live-main-menu.png", "main menu"),
+        ("title-builds/live-main-menu-options-focused.png", "main menu (OPTIONS focused)"),
+        ("title-builds/live-extras.png", "EXTRAS"),
+        ("difficulty-screen.png", "DIFFICULTY"),
+    ]
+    for rel, _name in shots:
+        p = CAP / rel
+        if not p.exists():
+            print(f"{rel:46} MISSING")
+            continue
+        a = np.asarray(Image.open(p).convert("RGB")).astype(int)
+        g, r = glyph_masks(a)  # WHOLE frame, not a guessed band
+        verdict = "no Ⓑ anywhere in frame" if r.sum() == 0 else f"Ⓑ at {blobs(r)[0][:2]}"
+        print(f"{rel:46} {g.sum():7d} {r.sum():7d}   {verdict}")
+
+
+ROW_Y0, ROW_PITCH, ROW_X = 201, 50, (190, 320)
+
+
+def stage_rows():
+    print("\n== 2. MISSION SELECT rows: locked, or just unfocused? ==")
+    shots = [
+        ("mission-select-stage01-only.png", "save with only Stage01 cleared"),
+        ("mission-select-all-story-unlocked.png", "save with the story unlocked"),
+        ("mission-select-ends-at-stage16.png", "unlocked, scrolled to the end"),
+    ]
+    for rel, note in shots:
+        p = CAP / rel
+        if not p.exists():
+            print(f"{rel:44} MISSING")
+            continue
+        a = np.asarray(Image.open(p).convert("L")).astype(float)
+        p95 = []
+        for i in range(8):
+            y = ROW_Y0 + ROW_PITCH * i
+            p95.append(np.percentile(a[y - 14:y + 14, ROW_X[0]:ROW_X[1]], 95))
+        print(f"{rel:44} {note}")
+        print("     row p95: " + " ".join(f"{v:5.0f}" for v in p95))
+
+
+if __name__ == "__main__":
+    footers()
+    stage_rows()

tools/re-capture/kf_record_census.py

@@ -0,0 +1,214 @@
+#!/usr/bin/env python3
+"""Disc-wide test of the UI placement-group record layout.
+
+A placement group in a screen bundle is an 8-byte header `{u32 element_index,
+u32 frame_count}` followed by `frame_count` records of 40 bytes, each
+`{u32 time; 36-byte pose}`.  The time word therefore **precedes** the pose it
+belongs to.
+
+Our parser's block window starts at the pose, so under the old reading a
+block's `+36` word was taken as *its own* time — off by one, which left the
+group's final pose (the end of every fade-out) untimed and made the group look
+4 bytes short.
+
+This script tests the corrected reading against the whole disc, with controls:
+
+  A. monotonicity — prepending the lead-in word to the shifted time series must
+     give a non-decreasing sequence, for every group.
+  B. the non-zero lead-ins — a lead-in that is a *time* must be strictly less
+     than the next time.  Control: swap in another group's lead-in from the
+     same bundle.
+  C. ramp linearity — within a monotone alpha ramp of >=3 segments, is
+     d(alpha)/d(time) constant?  Keyframe interpolation is linear
+     (`docs/re/ui-keyframe-time-unit.md`), so a correct time assignment should
+     make multi-keyframe ramps come out at a constant rate far more often than
+     an incorrect one.
+
+Usage:  python3 tools/re-capture/kf_record_census.py "$SYLPHEED_DISC"/dat/*.pak
+"""
+import collections
+import os
+import random
+import struct
+import sys
+import zlib
+
+
+def be32(b, o):
+    return struct.unpack_from(">I", b, o)[0]
+
+
+def load_pak(pak_path):
+    """Entries of an IPFB archive, transparently un-Z1'd. See sylpheed-formats::pak."""
+    idx = open(pak_path, "rb").read()
+    if idx[:4] != b"IPFB":
+        return []
+    n = be32(idx, 4)
+    data = b""
+    base = os.path.splitext(pak_path)[0]
+    for i in range(100):
+        p = f"{base}.p{i:02d}"
+        if not os.path.exists(p):
+            break
+        data += open(p, "rb").read()
+    out = []
+    for k in range(n):
+        _h, off, sz = struct.unpack_from(">III", idx, 0x10 + 12 * k)
+        blob = data[off : off + sz]
+        if blob[:2] == b"Z1":
+            try:
+                blob = zlib.decompress(blob[0x0A:])
+            except Exception:
+                blob = b""
+        out.append(blob)
+    return out
+
+
+def elem_name(b, o):
+    s = b[o : o + 28]
+    z = s.find(b"\0")
+    return (s[:z] if z >= 0 else s).decode("latin1")
+
+
+def groups(bundle):
+    """(element_index, name, frames, lead_in, W, alphas) per placement group.
+
+    `W[k]` is the word at the k-th 40-byte stride's `+36`; `W[-1]` is None
+    because it lies outside the group.  Under the corrected reading the pose
+    times are `[lead_in] + W[:-1]`.
+    """
+    n = be32(bundle, 0x14)
+    names = [elem_name(bundle, 0x20 + i * 60) for i in range(n)]
+    pos = 0x20 + n * 60
+    out = []
+    for _ in range(n):
+        if pos + 8 > len(bundle):
+            break
+        idx, frames = be32(bundle, pos), be32(bundle, pos + 4)
+        if idx >= n or frames == 0 or frames > 4096:
+            break
+        lead_in = be32(bundle, pos + 8)
+        first = pos + 12
+        end = first + frames * 40 - 4
+        if end > len(bundle):
+            break
+        W, alphas = [], []
+        for k in range(frames):
+            blk = first + k * 40
+            W.append(be32(bundle, blk + 36) if blk + 40 <= end else None)
+            alphas.append(be32(bundle, blk) >> 24)
+        out.append((idx, names[idx], frames, lead_in, W, alphas))
+        pos = end
+    return out
+
+
+def is_build(raw):
+    if raw[:4] != b"RATC" or len(raw) < 0x20:
+        return False
+    n = be32(raw, 0x14)
+    return 0 < n <= 4096 and 0x20 + n * 60 <= len(raw)
+
+
+def monotone_ramps(alphas, min_segments=3):
+    out, i, n = [], 0, len(alphas)
+    while i < n - 1:
+        if alphas[i] == alphas[i + 1]:
+            i += 1
+            continue
+        d = 1 if alphas[i + 1] > alphas[i] else -1
+        j = i + 1
+        while j < n - 1 and (alphas[j + 1] - alphas[j]) * d > 0:
+            j += 1
+        if j - i >= min_segments:
+            out.append((i, j))
+        i = j
+    return out
+
+
+def constant_rate(times, alphas, a, b, tol=0.06):
+    rates = []
+    for k in range(a, b):
+        dt = times[k + 1] - times[k]
+        if dt <= 0:
+            return None
+        rates.append(abs(alphas[k + 1] - alphas[k]) / dt)
+    mean = sum(rates) / len(rates)
+    if mean == 0:
+        return None
+    return max(abs(r - mean) for r in rates) / mean <= tol
+
+
+def main(paks):
+    rnd = random.Random(20260829)
+    per_bundle = collections.defaultdict(list)
+    total = mono = 0
+    ramp_new = [0, 0]
+    ramp_old = [0, 0]
+    for p in paks:
+        for ei, raw in enumerate(load_pak(p)):
+            if not is_build(raw):
+                continue
+            try:
+                gs = groups(raw)
+            except Exception:
+                continue
+            for _idx, nm, _frames, lead_in, W, alphas in gs:
+                rest = W[:-1]
+                if not rest or any(w is None for w in rest):
+                    continue
+                total += 1
+                t_new = [lead_in] + rest
+                if all(t_new[i] <= t_new[i + 1] for i in range(len(t_new) - 1)):
+                    mono += 1
+                per_bundle[(os.path.basename(p), ei)].append((lead_in, rest, nm))
+                for a, b in monotone_ramps(alphas):
+                    r = constant_rate(t_new, alphas, a, b)
+                    if r is not None:
+                        ramp_new[1] += 1
+                        ramp_new[0] += r
+                # old reading: `+36` is the block's own time, last pose untimed
+                a_old = alphas[:-1]
+                for a, b in monotone_ramps(a_old):
+                    r = constant_rate(rest, a_old, a, b)
+                    if r is not None:
+                        ramp_old[1] += 1
+                        ramp_old[0] += r
+
+    nz = nz_ok = ctrl = ctrl_ok = 0
+    gaps = collections.Counter()
+    for rows in per_bundle.values():
+        pool = [l for l, _, _ in rows]
+        for lead_in, rest, _nm in rows:
+            if lead_in == 0:
+                continue
+            nz += 1
+            nz_ok += lead_in < rest[0]
+            gaps[rest[0] - lead_in] += 1
+            for _ in range(10):
+                ctrl += 1
+                ctrl_ok += rnd.choice(pool) < rest[0]
+
+    pct = lambda a, b: f"{100 * a / b:.3f}%" if b else "n/a"
+    print(f"paks scanned            : {len(paks)}")
+    print(f"placement groups        : {total}")
+    print()
+    print("A. lead-in prepended to the shifted times is non-decreasing")
+    print(f"   {mono}/{total} = {pct(mono, total)}")
+    print()
+    print("B. non-zero lead-in is strictly less than the next time")
+    print(f"   {nz_ok}/{nz} = {pct(nz_ok, nz)}")
+    print(f"   control (another group's lead-in, same bundle): "
+          f"{ctrl_ok}/{ctrl} = {pct(ctrl_ok, ctrl)}")
+    print(f"   gap to the next time, most common: {gaps.most_common(8)}")
+    print()
+    print("C. constant d(alpha)/d(time) across a multi-segment ramp")
+    print(f"   corrected (time precedes pose): {ramp_new[0]}/{ramp_new[1]} = "
+          f"{pct(ramp_new[0], ramp_new[1])}")
+    print(f"   old       (+36 is own time)   : {ramp_old[0]}/{ramp_old[1]} = "
+          f"{pct(ramp_old[0], ramp_old[1])}")
+
+
+if __name__ == "__main__":
+    if len(sys.argv) < 2:
+        sys.exit(__doc__)
+    main(sys.argv[1:])

tools/re-capture/menu_b_probe.py

@@ -0,0 +1,87 @@
+#!/usr/bin/env python3
+"""Does (B) leave the main menu -- and does the menu self-return to the title?
+
+HANDOFF downgraded "(B) on the main menu returns to the title" to authored,
+because the corpus also carries "an ~8-10 s idle returns to the title" and one
+unrecorded observation cannot separate the two causes.  This separates them by
+ordering: hold the menu UNTOUCHED for an idle window several times longer than
+the claimed 8-10 s and timestamp what happens, THEN press (B) and timestamp
+again.  If the idle window passes with the menu still up, the idle cause is
+gone and the (B) observation is unambiguous.
+
+Screen identity comes from screen_match.py, whose control includes the movie
+frames that broke the statistics-based oracle.
+
+Usage:  menu_b_probe.py IDLE_SECONDS AFTER_SECONDS
+"""
+import os, subprocess, sys, time
+import numpy as np
+from PIL import Image
+
+SD = os.path.dirname(os.path.abspath(__file__))
+sys.path.insert(0, SD)
+from screen_match import classify_array
+
+W, H = 1280, 720
+IDLE = float(sys.argv[1]) if len(sys.argv) > 1 else 60.0
+AFTER = float(sys.argv[2]) if len(sys.argv) > 2 else 30.0
+OUT = "/sylph-home/re/ringcap"
+
+
+def stream():
+    return subprocess.Popen(
+        ["ffmpeg", "-loglevel", "error", "-f", "x11grab", "-draw_mouse", "0",
+         "-video_size", f"{W}x{H}", "-i", ":98", "-r", "4",
+         "-f", "rawvideo", "-pix_fmt", "rgb24", "-"],
+        stdout=subprocess.PIPE, bufsize=W * H * 3 * 2)
+
+
+def main():
+    p = stream(); n = W * H * 3
+    t0 = time.time(); seg = t0; last = None; prev = None
+    phase = "IDLE"; pressed_at = None
+    log = []
+    while True:
+        el = time.time() - t0
+        if phase == "IDLE" and el >= IDLE:
+            subprocess.run(["python3", f"{SD}/pad.py", "tap", "B", "0.3"], check=False)
+            pressed_at = time.time() - t0
+            print(f"t={pressed_at:6.2f}s  >>> (B) PRESSED", flush=True)
+            phase = "AFTER"
+        if phase == "AFTER" and el >= IDLE + AFTER:
+            break
+        if time.time() - seg > 25:
+            p.kill(); p = stream(); seg = time.time()
+        b = p.stdout.read(n)
+        if len(b) < n:
+            p.kill(); p = stream(); seg = time.time(); continue
+        a = np.frombuffer(b, np.uint8).reshape(H, W, 3)
+        last = a
+        c, sc = classify_array(a)
+        log.append((el, c, sc["title"], sc["menu"]))
+        if c != prev:
+            print(f"t={el:6.2f}s  screen={c:<6} title={sc['title']:+.3f} "
+                  f"menu={sc['menu']:+.3f}", flush=True)
+            Image.fromarray(a).save(f"{OUT}/b-{el:06.2f}-{c}.png")
+            prev = c
+    p.kill()
+    with open(f"{OUT}/menu-b-trace.tsv", "w") as f:
+        f.write("t_s\tscreen\tcorr_title\tcorr_menu\n")
+        for r in log:
+            f.write(f"{r[0]:.3f}\t{r[1]}\t{r[2]:.4f}\t{r[3]:.4f}\n")
+    idle = [r for r in log if r[0] < IDLE]
+    aft = [r for r in log if pressed_at and r[0] > pressed_at + 1.0]
+    print(f"\nIDLE phase  : {len(idle)} samples over {IDLE:.0f}s, "
+          f"screens seen = {sorted(set(r[1] for r in idle))}")
+    print(f"AFTER (B)   : {len(aft)} samples, "
+          f"screens seen = {sorted(set(r[1] for r in aft))}")
+    first_title = next((r[0] for r in aft if r[1] == "title"), None)
+    if first_title:
+        print(f"  first 'title' at t={first_title:.2f}s = "
+              f"{first_title - pressed_at:.2f}s after the (B) press")
+    print(f"trace: {OUT}/menu-b-trace.tsv")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

tools/re-capture/present_rate_probe.py

@@ -0,0 +1,181 @@
+"""Measure Canary's PRESENTATION RATE without perturbing it, and time the boot.
+
+Why this exists: two pages of the corpus measure the same declared 120 keyframe
+units during a static hold and disagree by 2 % -- settle->plate 2.135 s (28.10
+fps implied) and one focus-ring revolution 2.177 s (27.56 implied). The port
+challenged it. Either the rate differed between the sessions, or one interval is
+not 120 units. Both were WALL-CLOCK, so nothing in either can tell them apart.
+
+The obvious instrument is Canary's own `[UI-CAP]` frame counter, and it is the
+one the corpus used for "28.5 fps". 🔴 **It perturbs badly.** Measured here:
+armed on the title with a concurrent 8 fps grab, 300 frames took 16.567 s =
+**18.11 fps** against the ~28 the same screen gives without it. A frame counter
+that costs a third of the frame rate cannot measure the frame rate.
+
+So: count DISTINCT FRAMES in an oversampled crop of something that moves every
+frame (the spinning focus ring). Sampling at 60 fps a source presenting at R,
+the fraction of consecutive samples that differ is R/60.
+
+Its controls, all in one session and all required to believe a number:
+  * a STATIC crop must read ~0 -- if it does not, the counter is seeing noise;
+  * two sampling rates (45 and 60) must agree -- if the estimate tracks the
+    sampler it is measuring the sampler;
+  * and the decisive one: while `[UI-CAP]` runs, this counter and the emulator's
+    own frame count must AGREE. Both are perturbed in that window, but agreeing
+    there is what licenses using this counter alone outside it.
+
+    present_rate_probe.py --run SECONDS OUT.json CANARY_STDOUT
+"""
+import json
+import os
+import subprocess
+import sys
+import time
+
+import numpy as np
+
+SD = os.path.dirname(os.path.abspath(__file__))
+sys.path.insert(0, SD)
+import title_timing_probe as T  # noqa: E402
+import boot_timeline_probe as B  # noqa: E402
+
+# The button column, from ring_period.py: game coords (480,130)-(570,530), and
+# the game surface sits at +1,+45 in the root.
+RX, RY, RW, RH = 481, 175, 90, 400
+# A crop that must NOT move: the top-left of the menu's background.
+SX, SY, SW, SH = 60, 120, 90, 120
+
+
+def crop_stream(x, y, w, h, rate):
+    return subprocess.Popen(
+        ["ffmpeg", "-loglevel", "error", "-f", "x11grab", "-draw_mouse", "0",
+         "-video_size", f"{w}x{h}", "-i", f"{T.DISPLAY}+{x},{y}", "-r", str(rate),
+         "-f", "rawvideo", "-pix_fmt", "rgb24", "-"],
+        stdout=subprocess.PIPE, bufsize=w * h * 3 * 4)
+
+
+def count_distinct(x, y, w, h, rate, secs, thresh=0.02):
+    """Sample a crop and count how many frames differ from their predecessor.
+
+    Returns (samples, distinct, seconds, implied_fps, frames_list, times_list).
+    `thresh` is a mean-abs-difference floor; a capture path with no noise makes
+    an identical frame differ by exactly 0, so this only has to reject dither.
+    """
+    p = crop_stream(x, y, w, h, rate)
+    n = w * h * 3
+    t0 = time.time()
+    prev = None
+    samples = distinct = 0
+    prof, ts = [], []
+    while time.time() - t0 < secs:
+        b = p.stdout.read(n)
+        if len(b) < n:
+            break
+        a = np.frombuffer(b, np.uint8).reshape(h, w, 3)
+        g = (0.299 * a[..., 0] + 0.587 * a[..., 1] + 0.114 * a[..., 2]).astype(np.float32)
+        samples += 1
+        if prev is not None and float(np.abs(g - prev).mean()) > thresh:
+            distinct += 1
+        prev = g
+        prof.append(float(g.mean()))
+        ts.append(time.time() - t0)
+    p.kill()
+    dt = time.time() - t0
+    return dict(samples=samples, distinct=distinct, seconds=dt,
+                sample_fps=samples / dt, implied_fps=distinct / dt), prof, ts
+
+
+def wait_for(pred, limit, rate=8):
+    """Classify a full-frame stream until `pred(label, glyph, mean)` or timeout."""
+    p = T.open_stream()
+    n = T.W * T.H * 3
+    t0 = time.time()
+    trail = []
+    while time.time() - t0 < limit:
+        buf = p.stdout.read(n)
+        if len(buf) < n:
+            p.kill(); p = T.open_stream(); continue
+        rgb = np.frombuffer(buf, np.uint8).reshape(T.H, T.W, 3)
+        g = T.gray_of(rgb)
+        lb = T.label(T.scores(g))
+        gl = T.glyph(rgb)
+        mn = float(T.surface(g).mean())
+        trail.append((round(time.time() - t0, 3), lb, gl, round(mn, 2)))
+        if pred(lb, gl, mn):
+            p.kill()
+            return time.time() - t0, trail
+    p.kill()
+    return None, trail
+
+
+def main(limit, out_path, log_path):
+    res = {}
+    t0 = time.time()
+    # --- reach the plate, then press A promptly: the title's idle window is short
+    hit, trail = wait_for(lambda lb, gl, mn: lb in ("title_plate", "title_noplate")
+                          and gl >= T.PLATE_GLYPH, limit)
+    res["trail_to_plate"] = trail[-40:]
+    if hit is None:
+        res["error"] = "never reached the plate"
+        json.dump(res, open(out_path, "w"), indent=1)
+        return 1
+    res["plate_at"] = round(hit, 3)
+    print(f"plate at {hit:.1f}s -> A", flush=True)
+    T.tap("A")
+    hit, trail = wait_for(lambda lb, gl, mn: lb == "menu", 120)
+    if hit is None:
+        res["error"] = "never reached the menu"
+        res["trail_to_menu"] = trail[-40:]
+        json.dump(res, open(out_path, "w"), indent=1)
+        return 1
+    print(f"menu at +{hit:.1f}s; settling", flush=True)
+    time.sleep(8)
+
+    # --- CONTROL 1: a crop that must not move
+    st, _, _ = count_distinct(SX, SY, SW, SH, 60, 6)
+    res["control_static"] = st
+    print(f"static control: {st['distinct']}/{st['samples']} distinct "
+          f"({st['implied_fps']:.2f} implied)", flush=True)
+
+    # --- CONTROL 2: the same ring at two sampling rates
+    for r in (45, 60):
+        d, prof, ts = count_distinct(RX, RY, RW, RH, r, 12)
+        res[f"ring_free_{r}"] = d
+        res[f"ring_profile_{r}"] = [round(v, 4) for v in prof]
+        res[f"ring_times_{r}"] = [round(v, 4) for v in ts]
+        print(f"ring @{r}fps: {d['distinct']}/{d['samples']} -> "
+              f"{d['implied_fps']:.2f} fps (sampled {d['sample_fps']:.1f})", flush=True)
+
+    # --- CONTROL 3 (the decisive one): agree with the game's own counter
+    seen = os.path.getsize(log_path) if os.path.exists(log_path) else 0
+    import threading
+    box = {}
+
+    def _arm():
+        box["uicap"], box["seen"] = B.arm_capture(log_path, seen, timeout=120)
+    th = threading.Thread(target=_arm)
+    th.start()
+    d, prof, ts = count_distinct(RX, RY, RW, RH, 60, 30)
+    th.join(timeout=60)
+    res["ring_during_capture"] = d
+    res["uicap"] = box.get("uicap")
+    print(f"during UI-CAP: distinct-frame {d['implied_fps']:.2f} fps; "
+          f"UI-CAP {box.get('uicap')}", flush=True)
+
+    # --- and back to unperturbed
+    d, prof, ts = count_distinct(RX, RY, RW, RH, 60, 12)
+    res["ring_after"] = d
+    res["ring_profile_after"] = [round(v, 4) for v in prof]
+    res["ring_times_after"] = [round(v, 4) for v in ts]
+    print(f"after: {d['implied_fps']:.2f} fps", flush=True)
+
+    res["elapsed"] = round(time.time() - t0, 2)
+    json.dump(res, open(out_path, "w"), indent=1)
+    return 0
+
+
+if __name__ == "__main__":
+    if len(sys.argv) > 4 and sys.argv[1] == "--run":
+        sys.exit(main(float(sys.argv[2]), sys.argv[3], sys.argv[4]))
+    print(__doc__)
+    sys.exit(2)

tools/re-capture/quad_rects.py

@@ -0,0 +1,191 @@
+#!/usr/bin/env python3
+"""Screen-space rectangles for every textured quad in a xenia draw log.
+
+The draw logs under docs/re/captures/ record vertex positions in NDC, printed
+to **two decimals**.  That is the whole point of this script: it converts the
+quads to screen space *and* carries the quantisation with them, so a
+measurement taken off one of these logs cannot quietly claim more precision
+than the log has.
+
+    NDC step 0.01  ->  half-step 0.005  ->  a single edge is +/- 3.2 px in X
+    and +/- 1.8 px in Y; a WIDTH or HEIGHT is a difference of two edges, so it
+    carries twice that: +/- 6.4 px and +/- 3.6 px.  Getting this wrong is not
+    academic -- at the per-edge figure the control below fails 2 of 6.
+
+Usage:
+    quad_rects.py LOG [LOG ...]          # every textured quad, per frame
+    quad_rects.py --control LOG          # check recovered sizes against
+                                         # known texture dimensions
+
+The control is not optional in spirit.  Any claim made from these numbers
+should quote the control first: four sprites of known size are recovered from
+the same log, and the residuals bound what the instrument can see.
+"""
+
+import math
+import re
+import sys
+
+# Screen is 1280x720; NDC x in [-1,1] maps to [0,1280], y in [1,-1] to [0,720].
+W, H = 1280.0, 720.0
+NDC_HALF_STEP = 0.005
+EDGE_X = NDC_HALF_STEP * W / 2.0   # 3.2 px on one edge
+EDGE_Y = NDC_HALF_STEP * H / 2.0   # 1.8 px on one edge
+SIZE_X = 2 * EDGE_X                # 6.4 px on a width  (two edges)
+SIZE_Y = 2 * EDGE_Y                # 3.6 px on a height (two edges)
+
+# Decoded texture sizes for build 4 of GP_TITLE, from
+# docs/re/ui-title-paint-order-capture.md and docs/re/ui-title-build-map.md.
+# These are the known-positives the control checks against.
+CONTROL_SIZES = {
+    "ptlogo1.t32": (919, 113),
+    "ptlogo2.t32": (992, 104),
+    "ptlogo_back2.t32": (1118, 262),
+    "ptlogo_back2eff.t32": (1133, 280),
+    "ptcopyright.t32": (694, 20),
+    "ptbtn00.t32": (513, 50),
+    "ptbtn00f.t32": (537, 76),
+}
+
+FRAME_RE = re.compile(r"--- frame (\d+) ---")
+DRAW_RE = re.compile(r"\s*(\d+) prim=(\d+) indices=(\d+)")
+TEX_RE = re.compile(r"tex\[base=(0x[0-9A-Fa-f]+) (\d+)x(\d+)")
+VERT_RE = re.compile(r"\[(-?\d+\.\d+),(-?\d+\.\d+),z=")
+
+
+def parse(path):
+    """Yield dicts: frame, draw, tex base, and the quad's screen-space rect."""
+    frame, cur = 0, None
+    for line in open(path):
+        m = FRAME_RE.match(line)
+        if m:
+            frame = int(m.group(1))
+            continue
+        m = DRAW_RE.match(line)
+        if m:
+            t = TEX_RE.search(line)
+            cur = {"frame": frame, "draw": int(m.group(1)),
+                   "tex": t.group(1) if t else None}
+            continue
+        if "v:" in line and cur is not None:
+            verts = [(float(a), float(b)) for a, b in VERT_RE.findall(line)]
+            # A draw can carry several quads; four vertices each.
+            for i in range(0, len(verts) - 3, 4):
+                q = verts[i:i + 4]
+                xs = [(x + 1.0) * W / 2.0 for x, _ in q]
+                ys = [(1.0 - y) * H / 2.0 for _, y in q]
+                # Vertex order is TL, TR, BR, BL, so edge 0->1 is the drawn
+                # width and 1->2 the drawn height.  For a ROTATED quad the
+                # bounding box is not the sprite; the edges are.
+                e0 = math.hypot(xs[1] - xs[0], ys[1] - ys[0])
+                e1 = math.hypot(xs[2] - xs[1], ys[2] - ys[1])
+                ang = math.degrees(math.atan2(ys[1] - ys[0], xs[1] - xs[0]))
+                yield {**cur,
+                       "left": min(xs), "top": min(ys),
+                       "w": max(xs) - min(xs), "h": max(ys) - min(ys),
+                       "ew": e0, "eh": e1, "rot": ang,
+                       "cx": sum(xs) / 4.0, "cy": sum(ys) / 4.0}
+            cur = None
+
+
+def dump(path):
+    print(f"# {path}")
+    print(f"# NDC printed to 2 dp -> edge +/- {EDGE_X:.1f}/{EDGE_Y:.1f} px, "
+          f"size +/- {SIZE_X:.1f}/{SIZE_Y:.1f} px (X/Y)")
+    print(f"{'frame':>5} {'draw':>5} {'tex':>12} "
+          f"{'left':>8} {'top':>8} {'bboxW':>8} {'bboxH':>8} "
+          f"{'edgeW':>8} {'edgeH':>8} {'rot':>7} {'cx':>8} {'cy':>8}")
+    for q in parse(path):
+        if q["tex"] is None:
+            continue
+        print(f"{q['frame']:>5} {q['draw']:>5} {q['tex']:>12} "
+              f"{q['left']:>8.1f} {q['top']:>8.1f} {q['w']:>8.1f} {q['h']:>8.1f} "
+              f"{q['ew']:>8.1f} {q['eh']:>8.1f} {q['rot']:>7.2f} "
+              f"{q['cx']:>8.1f} {q['cy']:>8.1f}")
+
+
+def control(path):
+    """Recover the known-positive sprites by size and report the residual."""
+    rects = [q for q in parse(path) if q["tex"] is not None]
+    print(f"# control: {path}")
+    print(f"{'sprite':<22} {'decoded':>11} {'measured':>13} "
+          f"{'dx':>6} {'dy':>6}  verdict")
+    ok = True
+    for name, (tw, th) in CONTROL_SIZES.items():
+        best = min(rects, key=lambda q: abs(q["w"] - tw) + abs(q["h"] - th))
+        dx, dy = best["w"] - tw, best["h"] - th
+        good = abs(dx) <= SIZE_X and abs(dy) <= SIZE_Y
+        ok &= good
+        print(f"{name:<22} {tw:>5}x{th:<5} {best['w']:>6.1f}x{best['h']:<6.1f} "
+              f"{dx:>6.1f} {dy:>6.1f}  {'PASS' if good else 'FAIL'}")
+    print(f"# {'CONTROL PASSES' if ok else 'CONTROL FAILS'} — "
+          f"every known size recovered inside the log's own quantisation"
+          if ok else "# CONTROL FAILS — do not measure anything with this")
+    return 0 if ok else 1
+
+
+# Every sprite the title's build-4 capture can draw, by decoded size.  The two
+# pteff03 entries are the nested ptloop leaves, whose declared vertical scales
+# are 600 % and 800 %.
+TITLE_SPRITES = {
+    (919, 113): "ptlogo1.t32",
+    (992, 104): "ptlogo2.t32",
+    (1118, 262): "ptlogo_back2.t32",
+    (1133, 280): "ptlogo_back2eff.t32",
+    (694, 20): "ptcopyright.t32",
+    (513, 50): "ptbtn00.t32",
+    (38, 18): "ptlogo_tm.t32",
+    (399, 180): "pteff03/pteff03a.t32",
+    (537, 76): "ptbtn00f.t32",        # build 2's focus plate
+}
+
+
+def scales(path):
+    """For each quad, the drawn size over the nearest decoded sprite size.
+
+    The question this answers: which elements are drawn at a scale other than
+    100 %?  Only those can say anything about what scale is anchored on.
+    """
+    print(f"# scale census: {path}")
+    print(f"{'frame':>5} {'sprite':<22} {'edgeW':>8} {'edgeH':>8} "
+          f"{'sx%':>7} {'sy%':>7} {'rot':>7}")
+    seen = set()
+    for q in parse(path):
+        if q["tex"] is None:
+            continue
+        if abs(q["ew"] - W) < SIZE_X and abs(q["eh"] - H) < SIZE_Y:
+            name, sx, sy = "full-screen layer", 1.0, 1.0
+            key = (name, 1.0, 1.0)
+            if key not in seen:
+                seen.add(key)
+                print(f"{q['frame']:>5} {name:<22} {q['ew']:>8.1f} "
+                      f"{q['eh']:>8.1f} {100.0:>7.1f} {100.0:>7.1f} "
+                      f"{q['rot']:>7.2f}")
+            continue
+        # Match on the edge lengths, allowing any uniform-ish scale factor.
+        best, bestcost = None, None
+        for (tw, th), name in TITLE_SPRITES.items():
+            sx, sy = q["ew"] / tw, q["eh"] / th
+            cost = abs(math.log(sx)) + abs(math.log(sy))
+            if bestcost is None or cost < bestcost:
+                best, bestcost = (name, tw, th, sx, sy), cost
+        name, tw, th, sx, sy = best
+        key = (name, round(sx, 2), round(sy, 2))
+        if key in seen:
+            continue
+        seen.add(key)
+        print(f"{q['frame']:>5} {name:<22} {q['ew']:>8.1f} {q['eh']:>8.1f} "
+              f"{100 * sx:>7.1f} {100 * sy:>7.1f} {q['rot']:>7.2f}")
+    return 0
+
+
+if __name__ == "__main__":
+    args = sys.argv[1:]
+    if not args:
+        sys.exit(__doc__)
+    if args[0] == "--scales":
+        sys.exit(max(scales(p) for p in args[1:]))
+    if args[0] == "--control":
+        sys.exit(max(control(p) for p in args[1:]))
+    for p in args:
+        dump(p)

tools/re-capture/ring_angular.py

@@ -0,0 +1,138 @@
+#!/usr/bin/env python3
+"""Is the focus ring ROTATING, or just pulsing in brightness?
+
+The temporal-std map of a focused button is an annulus, which both hypotheses
+predict: a travelling bright feature varies every annulus pixel, and so does a
+uniform fade.  Two observables separate them, and this script reports both.
+
+  (1) TOTAL annulus brightness per frame.  A rotation moves brightness around
+      the annulus and conserves the sum; an alpha pulse does not.
+  (2) The 360-bin ANGULAR PROFILE, cross-correlated between frames.  A rotation
+      shifts the profile by a lag; a pulse scales it in place.
+
+CONTROL FIRST.  The angular estimator is run over a known synthetic rotation of
+the run's own first frame (30/90/180/270 deg) and must recover it; the corpus
+already has a centroid estimator that fails this by up to 19.8 deg, and that is
+why one is not used here.
+
+Usage:  ring_angular.py CX CY [FRAME ...]        (CX,CY in GAME coordinates)
+"""
+import os, sys
+import numpy as np
+from PIL import Image
+
+DY, DX = 45, 1          # game(0,0) -> grab, measured by focus_ring_report.py
+R_IN, R_OUT = 8.0, 18.0  # annulus radii, in px, read off the std map
+NBINS = 360
+
+
+def ndrotate(img, deg):
+    """Bilinear rotation about the patch centre -- the control's known-positive."""
+    h, w = img.shape
+    cy, cx = (h - 1) / 2.0, (w - 1) / 2.0
+    yy, xx = np.mgrid[0:h, 0:w]
+    t = np.radians(deg)
+    ys = (yy - cy) * np.cos(t) - (xx - cx) * np.sin(t) + cy
+    xs = (yy - cy) * np.sin(t) + (xx - cx) * np.cos(t) + cx
+    y0 = np.floor(ys).astype(int); x0 = np.floor(xs).astype(int)
+    fy = ys - y0; fx = xs - x0
+    out = np.zeros_like(img)
+    for dy_, dx_, wgt in ((0, 0, (1 - fy) * (1 - fx)), (0, 1, (1 - fy) * fx),
+                          (1, 0, fy * (1 - fx)), (1, 1, fy * fx)):
+        yi = np.clip(y0 + dy_, 0, h - 1); xi = np.clip(x0 + dx_, 0, w - 1)
+        ok = (y0 + dy_ >= 0) & (y0 + dy_ < h) & (x0 + dx_ >= 0) & (x0 + dx_ < w)
+        out += np.where(ok, img[yi, xi] * wgt, 0.0)
+    return out
+
+
+def ndrotate(img, deg):
+    """Bilinear rotation about the patch centre -- the control's known-positive."""
+    h, w = img.shape
+    cy, cx = (h - 1) / 2.0, (w - 1) / 2.0
+    yy, xx = np.mgrid[0:h, 0:w]
+    t = np.radians(deg)
+    ys = (yy - cy) * np.cos(t) - (xx - cx) * np.sin(t) + cy
+    xs = (yy - cy) * np.sin(t) + (xx - cx) * np.cos(t) + cx
+    y0 = np.floor(ys).astype(int); x0 = np.floor(xs).astype(int)
+    fy = ys - y0; fx = xs - x0
+    out = np.zeros_like(img)
+    for dy_, dx_, wgt in ((0, 0, (1 - fy) * (1 - fx)), (0, 1, (1 - fy) * fx),
+                          (1, 0, fy * (1 - fx)), (1, 1, fy * fx)):
+        yi = np.clip(y0 + dy_, 0, h - 1); xi = np.clip(x0 + dx_, 0, w - 1)
+        ok = (y0 + dy_ >= 0) & (y0 + dy_ < h) & (x0 + dx_ >= 0) & (x0 + dx_ < w)
+        out += np.where(ok, img[yi, xi] * wgt, 0.0)
+    return out
+
+
+def patch(path, cx, cy, half=28):
+    a = np.array(Image.open(path).convert("RGB")).astype(np.float32)
+    g = 0.299 * a[..., 0] + 0.587 * a[..., 1] + 0.114 * a[..., 2]
+    return g[cy + DY - half:cy + DY + half, cx + DX - half:cx + DX + half]
+
+
+def polar(p):
+    """(total annulus brightness, 360-bin mean profile) of one patch."""
+    h, w = p.shape
+    yy, xx = np.mgrid[0:h, 0:w]
+    cy, cx = (h - 1) / 2.0, (w - 1) / 2.0
+    r = np.hypot(yy - cy, xx - cx)
+    m = (r >= R_IN) & (r <= R_OUT)
+    th = (np.degrees(np.arctan2(yy - cy, xx - cx)) + 360.0) % 360.0
+    idx = np.clip((th[m] / 360.0 * NBINS).astype(int), 0, NBINS - 1)
+    v = p[m]
+    prof = np.zeros(NBINS); cnt = np.zeros(NBINS)
+    np.add.at(prof, idx, v); np.add.at(cnt, idx, 1.0)
+    prof = np.where(cnt > 0, prof / np.maximum(cnt, 1), np.nan)
+    prof = np.nan_to_num(prof, nan=np.nanmean(prof))
+    return float(v.sum()), prof
+
+
+def lag(p0, p1):
+    """Circular cross-correlation lag in degrees taking p0 -> p1."""
+    a = p0 - p0.mean(); b = p1 - p1.mean()
+    c = np.fft.irfft(np.fft.rfft(b) * np.conj(np.fft.rfft(a)), NBINS)
+    k = int(np.argmax(c))
+    peak = c[k] / np.sqrt((a * a).sum() * (b * b).sum())
+    return (k if k <= 180 else k - 360), float(peak)
+
+
+def main():
+    cx, cy = int(sys.argv[1]), int(sys.argv[2])
+    frames = sys.argv[3:]
+    p0 = patch(frames[0], cx, cy)
+
+    print("=== CONTROL: recover a known synthetic rotation of frame 0 ===")
+    ok = True
+    for deg in (30, 90, 180, 270):
+        rot = ndrotate(p0, -deg)
+        _, pr = polar(rot); _, pa = polar(p0)
+        d, pk = lag(pa, pr)
+        err = ((d - deg + 180) % 360) - 180
+        flag = "ok " if abs(err) <= 3 else "FAIL"
+        if abs(err) > 3:
+            ok = False
+        print(f"  {flag} applied {deg:4d} deg -> recovered {d:5d} deg  "
+              f"(err {err:+4d}, peak {pk:.3f})")
+    # negative control: a ring-free patch of the same frame must not correlate
+    off = patch(frames[0], cx + 160, cy)
+    _, po = polar(off); _, pa = polar(p0)
+    _, pk = lag(pa, po)
+    print(f"  ring-free patch of the same frame: peak {pk:.3f} (must be low)")
+    if not ok:
+        print("\nCONTROL FAILED — the estimator cannot measure this; stopping.")
+        return 1
+    print("  CONTROL PASSED\n")
+
+    print("=== MEASUREMENT: successive live frames of the same focused ring ===")
+    print(f"{'frame':<24} {'annulus sum':>12} {'vs f0 %':>9} {'lag vs f0':>10} {'peak':>7}")
+    base_s, base_p = polar(p0)
+    for f in frames:
+        s, pr = polar(patch(f, cx, cy))
+        d, pk = lag(base_p, pr)
+        print(f"{os.path.basename(f):<24} {s:12.1f} {100*s/base_s:8.1f}% "
+              f"{d:9d}d {pk:7.3f}")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

tools/re-capture/ring_period.py

@@ -0,0 +1,105 @@
+#!/usr/bin/env python3
+"""Measure the focus ring's SPIN PERIOD from a dense live filmstrip.
+
+No absolute angle is estimated.  The corpus's centroid estimator fails its own
+control by up to 19.8 deg, and a 360-bin angular cross-correlation also FAILED
+the control written for it here (a synthetic 30 deg rotation of a live frame
+came back as 0 deg, peak 0.596), so neither is trusted.
+
+What is used instead needs no angle: the annulus's 360-bin brightness profile,
+correlated against frame 0.  A rotating ring's profile returns to itself once
+per revolution, so the correlation trace is periodic and its first return to a
+maximum IS the period.  The ring is located from the data (the peak of the
+temporal-std map over the button column), not from a declared coordinate.
+
+Usage:  ring_period.py SECONDS OUTDIR
+"""
+import os, subprocess, sys, time
+import numpy as np
+from PIL import Image
+
+W, H, DY, DX = 1280, 720, 45, 1
+R_IN, R_OUT, NB = 8.0, 18.0, 360
+SECS = float(sys.argv[1]) if len(sys.argv) > 1 else 30.0
+OUT = sys.argv[2] if len(sys.argv) > 2 else "/sylph-home/re/ringcap"
+COL = (480, 130, 570, 530)          # x0,y0,x1,y1 in GAME coords: the button column
+
+
+def grab_stream(secs):
+    p = subprocess.Popen(
+        ["ffmpeg", "-loglevel", "error", "-f", "x11grab", "-draw_mouse", "0",
+         "-video_size", f"{W}x{H}", "-i", ":98", "-r", "15",
+         "-f", "rawvideo", "-pix_fmt", "rgb24", "-"],
+        stdout=subprocess.PIPE, bufsize=W * H * 3 * 2)
+    n = W * H * 3
+    t0 = time.time(); frames = []; ts = []
+    x0, y0, x1, y1 = COL
+    while time.time() - t0 < secs:
+        b = p.stdout.read(n)
+        if len(b) < n:
+            break
+        a = np.frombuffer(b, np.uint8).reshape(H, W, 3)
+        g = (0.299 * a[..., 0] + 0.587 * a[..., 1] + 0.114 * a[..., 2]).astype(np.float32)
+        frames.append(g[y0 + DY:y1 + DY, x0 + DX:x1 + DX].copy())
+        ts.append(time.time() - t0)
+    p.kill()
+    return np.array(frames), np.array(ts)
+
+
+def annulus_profile(patch, cy, cx):
+    h, w = patch.shape
+    yy, xx = np.mgrid[0:h, 0:w]
+    r = np.hypot(yy - cy, xx - cx)
+    m = (r >= R_IN) & (r <= R_OUT)
+    th = (np.degrees(np.arctan2(yy - cy, xx - cx)) + 360) % 360
+    idx = np.clip((th[m] / 360 * NB).astype(int), 0, NB - 1)
+    v = patch[m]
+    prof = np.zeros(NB); cnt = np.zeros(NB)
+    np.add.at(prof, idx, v); np.add.at(cnt, idx, 1.0)
+    prof = np.where(cnt > 0, prof / np.maximum(cnt, 1), np.nan)
+    return np.nan_to_num(prof, nan=np.nanmean(prof)), float(v.mean())
+
+
+def main():
+    F, T = grab_stream(SECS)
+    if len(F) < 10:
+        print("too few frames"); return 1
+    fps = len(F) / (T[-1] - T[0])
+    print(f"{len(F)} frames over {T[-1]-T[0]:.1f}s = {fps:.2f} fps", flush=True)
+
+    std = F.std(0)
+    cy, cx = np.unravel_index(np.argmax(
+        np.array([[std[max(0, i-14):i+14, max(0, j-14):j+14].mean()
+                   for j in range(std.shape[1])] for i in range(std.shape[0])])), std.shape)
+    print(f"ring located from the data at patch({cx},{cy}) = "
+          f"GAME({COL[0]+cx},{COL[1]+cy}); local std {std[cy, cx]:.2f}", flush=True)
+
+    profs = []; means = []
+    for f in F:
+        p, m = annulus_profile(f, cy, cx)
+        profs.append(p); means.append(m)
+    P = np.array(profs); M = np.array(means)
+    print(f"annulus mean brightness: {M.mean():.2f} +/- {M.std():.3f} "
+          f"({100*M.std()/M.mean():.2f}% -- a PULSE would move this)", flush=True)
+
+    a = P[0] - P[0].mean()
+    corr = np.array([float(((p - p.mean()) * a).sum() /
+                           np.sqrt(((p - p.mean())**2).sum() * (a * a).sum()))
+                     for p in P])
+    np.save(f"{OUT}/period-corr.npy", np.vstack([T, corr, M]))
+    print("\n t(s)  corr-with-frame0   annulus mean")
+    for t, c, m in zip(T, corr, M):
+        bar = "#" * max(0, int((c + 1) * 25))
+        print(f"{t:6.2f}  {c:+.3f} {bar:<50} {m:7.2f}")
+
+    # first return to a local maximum after the trace has dipped
+    dip = np.argmax(corr < 0.3) if (corr < 0.3).any() else None
+    if dip:
+        after = corr[dip:]
+        k = dip + int(np.argmax(after))
+        print(f"\nfirst return to max after the dip: t = {T[k]:.2f}s (corr {corr[k]:+.3f})")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

tools/re-capture/screen_match.py

@@ -0,0 +1,151 @@
+#!/usr/bin/env python3
+"""Identify a LIVE grab by correlating it against committed oracle captures.
+
+Why not whole-image statistics (screen_id.py's green/white/mean)?  Because the
+class they have to reject is MOVIE FRAMES, and a movie frame can be anything.
+Measured 2026-08-29: a frame of `ADV.wmv` containing a bright green laser beam
+scored green=0.0018 white=0.086 mean=(53,67,76) -- numerically indistinguishable
+from the title plate, and a probe built on those features tapped (A) into the
+attract movie and then waited 120 s for a menu that was never coming.
+
+So match on CONTENT instead.  Zero-normalised correlation against the committed
+captures, over a small offset search, with the movie frames that fooled the
+statistics kept as permanent negative controls.
+
+A live grab is the whole 1280x720 root: xenia's title bar and menu bar occupy
+the top ~45 rows, and the game surface below them is 1279x675 -- the same size
+as the committed captures, which is not a coincidence.
+
+Usage:
+    screen_match.py IMAGE [IMAGE ...]     classify each
+    screen_match.py --control             run the controls and exit non-zero on failure
+"""
+import os, sys
+import numpy as np
+from PIL import Image
+
+REPO = os.path.dirname(os.path.dirname(os.path.dirname(os.path.abspath(__file__))))
+CAP = os.path.join(REPO, "docs", "re", "captures")
+REFS = {
+    "title": "title-builds/live-title-press-a.png",
+    "menu":  "title-builds/live-main-menu.png",
+}
+SURFACE_TOP = 45          # rows of xenia window chrome on a 1280x720 root
+SEARCH = 8                # +/- px offset search, as the corpus does elsewhere
+THRESH = 0.70
+FAST_DS = 4               # decimation for the live path (see below)
+
+# 🔴 The exact path costs 1503 ms PER FRAME, measured.  A probe that ran it on
+# every frame of an 8 fps x11grab drained the pipe at 0.64 fps, so the frames it
+# classified were tens of seconds stale -- and the staleness GREW, which is how
+# three "latencies" of 15.6 s, 20.3 s and 25.6 s were produced by a pipeline
+# rather than by the game.  Ordering survives a backlog; durations do not.
+# `fast=True` decimates 4x and searches +/-2 decimated px, and is controlled
+# below against the same 8 captures as the exact path.
+
+
+def load(p):
+    return np.array(Image.open(p).convert("L"), dtype=np.float32)
+
+
+def surface(a):
+    """Crop a grab to the game surface. A committed capture is passed through."""
+    h, w = a.shape
+    if h == 720 and w == 1280:
+        return a[SURFACE_TOP:, :1279]
+    return a
+
+
+def zncc(x, y):
+    x = x - x.mean(); y = y - y.mean()
+    d = np.sqrt((x * x).sum() * (y * y).sum())
+    return float((x * y).sum() / d) if d else 0.0
+
+
+def best_corr(img, ref, fast=False):
+    """Max ZNCC over a small 2-D offset search."""
+    if fast:
+        img = img[::FAST_DS, ::FAST_DS]; ref = ref[::FAST_DS, ::FAST_DS]
+        rng, step = 2, 1
+    else:
+        rng, step = SEARCH, 2
+    h = min(img.shape[0], ref.shape[0]); w = min(img.shape[1], ref.shape[1])
+    best = -1.0
+    for dy in range(-rng, rng + 1, step):
+        for dx in range(-rng, rng + 1, step):
+            ys0, ys1 = max(0, dy), min(h, h + dy)
+            yr0, yr1 = max(0, -dy), min(h, h - dy)
+            xs0, xs1 = max(0, dx), min(w, w + dx)
+            xr0, xr1 = max(0, -dx), min(w, w - dx)
+            c = zncc(img[ys0:ys1, xs0:xs1], ref[yr0:yr1, xr0:xr1])
+            if c > best:
+                best = c
+    return best
+
+
+_REF_CACHE = {}
+
+
+def refs():
+    if not _REF_CACHE:
+        for k, v in REFS.items():
+            _REF_CACHE[k] = surface(load(os.path.join(CAP, v)))
+    return _REF_CACHE
+
+
+def classify(a_gray, fast=False):
+    """Return (label, {name: corr}). label is 'title' | 'menu' | 'other'."""
+    img = surface(a_gray)
+    scores = {k: best_corr(img, r, fast) for k, r in refs().items()}
+    k = max(scores, key=scores.get)
+    return (k if scores[k] >= THRESH else "other"), scores
+
+
+def classify_array(rgb, fast=False):
+    g = (0.299 * rgb[:, :, 0] + 0.587 * rgb[:, :, 1] + 0.114 * rgb[:, :, 2]).astype(np.float32)
+    return classify(g, fast)
+
+
+CONTROLS = [
+    # (path, expected)  -- positives from the committed corpus ...
+    (os.path.join(CAP, "title-builds/live-title-press-a.png"), "title"),
+    (os.path.join(CAP, "title-screen-oracle.png"),             "title"),
+    (os.path.join(CAP, "title-builds/live-main-menu.png"),     "menu"),
+    (os.path.join(CAP, "main-menu-oracle.png"),                "menu"),
+    (os.path.join(CAP, "main-menu-reached.png"),               "menu"),
+    # ... and the NEGATIVES.  Movie frames are the class this oracle exists to
+    # reject, so they are COMMITTED fixtures, not scratch: an earlier version of
+    # this list pointed at two scratch grabs and a later run of the same probe
+    # overwrote one of them, turning a negative control into a title frame and
+    # failing the control for the wrong reason.
+    (os.path.join(CAP, "instrument-controls/movie-frame-attract-a.png"), "other"),
+    (os.path.join(CAP, "instrument-controls/movie-frame-attract-b.png"), "other"),
+    (os.path.join(CAP, "difficulty-screen.png"),               "other"),
+]
+
+
+def control():
+    import time as _t
+    bad = 0
+    for fast in (False, True):
+        print(f"--- {'FAST (live path)' if fast else 'EXACT'} ---")
+        for p, exp in CONTROLS:
+            if not os.path.exists(p):
+                print(f"  SKIP (missing) {os.path.basename(p)}"); continue
+            t = _t.time(); got, sc = classify(load(p), fast); ms = (_t.time() - t) * 1000
+            ok = "ok " if got == exp else "FAIL"
+            if got != exp:
+                bad += 1
+            print(f"  {ok} {os.path.basename(p):<34} -> {got:<6} (exp {exp:<6}) "
+                  + "  ".join(f"{k}={v:+.3f}" for k, v in sc.items())
+                  + f"  [{ms:.0f} ms]")
+    print(f"\n{'CONTROL PASSED' if not bad else f'CONTROL FAILED ({bad})'}")
+    return 1 if bad else 0
+
+
+if __name__ == "__main__":
+    if len(sys.argv) > 1 and sys.argv[1] == "--control":
+        sys.exit(control())
+    for p in sys.argv[1:]:
+        got, sc = classify(load(p))
+        print(f"{p}: {got}  " + "  ".join(f"{k}={v:+.3f}" for k, v in sc.items()))

tools/re-capture/title_plate_and_b_probe.py

@@ -0,0 +1,119 @@
+#!/usr/bin/env python3
+"""One boot, two answers: when the PRESS (A) plate appears, and what (B) does.
+
+Q(plate): the port's boot ends on GP_TITLE build 4, which carries no plate, and
+  (A) is the only way off it -- so it ships a screen that needs a press and does
+  not say so.  Builds 2/3 are the plate.  The open half is the SEQUENCE: build 4
+  alone, build 4 with the plate composited from the start, or build 4 and THEN
+  the plate after a delay.  This logs the title-art correlation and the green-(A)
+  glyph count on EVERY frame from before the title appears, so the two crossings
+  are read off one trace rather than inferred.
+
+Q(B): whether (B) leaves the main menu, timed against the idle alternative.
+
+Controls, both pre-run on committed captures:
+  * screen identity -- screen_match.py, 8/8 including the movie frames that
+    broke the statistics oracle;
+  * the plate -- green-(A) glyph count: 753/977/1493 px on plate titles, 159 on
+    `live-title-build4-no-plate.png`, 327 on the main menu.  Threshold 400.
+
+Usage:  title_plate_and_b_probe.py OUTDIR
+"""
+import os, subprocess, sys, time
+import numpy as np
+from PIL import Image
+
+SD = os.path.dirname(os.path.abspath(__file__))
+sys.path.insert(0, SD)
+from screen_match import classify_array
+
+W, H = 1280, 720
+PLATE = 400
+OUT = sys.argv[1] if len(sys.argv) > 1 else "/sylph-home/re/platecap"
+os.makedirs(OUT, exist_ok=True)
+
+
+def stream():
+    return subprocess.Popen(
+        ["ffmpeg", "-loglevel", "error", "-f", "x11grab", "-draw_mouse", "0",
+         "-video_size", f"{W}x{H}", "-i", ":98", "-r", "8",
+         "-f", "rawvideo", "-pix_fmt", "rgb24", "-"],
+        stdout=subprocess.PIPE, bufsize=W * H * 3 * 2)
+
+
+def glyph(a):
+    r, g, b = a[:, :, 0].astype(int), a[:, :, 1].astype(int), a[:, :, 2].astype(int)
+    return int(((g > 130) & (g - r > 45) & (g - b > 45)).sum())
+
+
+def main():
+    p = stream(); n = W * H * 3
+    t0 = time.time(); seg = t0; prev = None
+    skipped = False; stage = 0; marks = {}
+    rows = []
+    while time.time() - t0 < 420:
+        if time.time() - seg > 25:
+            p.kill(); p = stream(); seg = time.time()
+        b = p.stdout.read(n)
+        if len(b) < n:
+            p.kill(); p = stream(); seg = time.time(); continue
+        a = np.frombuffer(b, np.uint8).reshape(H, W, 3)
+        el = time.time() - t0
+        c, sc = classify_array(a)
+        gl = glyph(a)
+        rows.append((el, c, sc["title"], sc["menu"], gl))
+        if c != prev:
+            print(f"t={el:7.2f}s screen={c:<6} title={sc['title']:+.3f} "
+                  f"menu={sc['menu']:+.3f} glyph={gl}", flush=True)
+            prev = c
+
+        if not skipped and el > 45:
+            subprocess.run(["python3", f"{SD}/pad.py", "tap", "A", "0.3"], check=False)
+            skipped = True
+            print(f"t={el:7.2f}s  one (A) to skip the intro movie", flush=True)
+        elif stage == 0 and c == "title":
+            marks["title_art"] = el; stage = 1
+            Image.fromarray(a).save(f"{OUT}/title-first-{el:07.2f}.png")
+            print(f"t={el:7.2f}s  TITLE ART (glyph={gl}) — watching for the plate",
+                  flush=True)
+        elif stage == 1 and gl >= PLATE:
+            marks["plate"] = el; stage = 2
+            Image.fromarray(a).save(f"{OUT}/title-plate-{el:07.2f}.png")
+            print(f"t={el:7.2f}s  PLATE (glyph={gl}) — "
+                  f"{el-marks['title_art']:.2f}s after the title art", flush=True)
+        elif stage == 2 and el > marks["plate"] + 6:
+            subprocess.run(["python3", f"{SD}/pad.py", "tap", "A", "0.3"], check=False)
+            marks["A"] = el; stage = 3
+            print(f"t={el:7.2f}s  >>> (A) on the title", flush=True)
+        elif stage == 3 and c == "menu":
+            marks["menu"] = el; stage = 4
+            print(f"t={el:7.2f}s  MENU — idling 25 s before (B)", flush=True)
+        elif stage == 4 and el > marks["menu"] + 25:
+            subprocess.run(["python3", f"{SD}/pad.py", "tap", "B", "0.3"], check=False)
+            marks["B"] = el; stage = 5
+            print(f"t={el:7.2f}s  >>> (B) PRESSED", flush=True)
+        elif stage == 5 and c != "menu":
+            marks["left_menu"] = el
+            print(f"t={el:7.2f}s  LEFT THE MENU -> {c}, "
+                  f"{el-marks['B']:.2f}s after (B)", flush=True)
+            stage = 6
+        elif stage == 6 and el > marks["left_menu"] + 12:
+            break
+
+    p.kill()
+    with open(f"{OUT}/trace.tsv", "w") as f:
+        f.write("t_s\tscreen\tcorr_title\tcorr_menu\tglyph\n")
+        for r in rows:
+            f.write(f"{r[0]:.3f}\t{r[1]}\t{r[2]:.4f}\t{r[3]:.4f}\t{r[4]}\n")
+    print("\nmarks:", {k: round(v, 2) for k, v in marks.items()})
+    if "title_art" in marks and "plate" in marks:
+        print(f"PLATE DELAY: {marks['plate']-marks['title_art']:.2f}s "
+              f"after the title art first matched")
+    if "B" in marks and "left_menu" in marks:
+        print(f"(B) -> left the menu in {marks['left_menu']-marks['B']:.2f}s")
+    print(f"trace: {OUT}/trace.tsv")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

tools/re-capture/title_timing_probe.py

@@ -0,0 +1,368 @@
+#!/usr/bin/env python3
+"""Time the boot title: when the PRESS (A) plate arrives, and what a press costs.
+
+WHY THIS EXISTS.  Four durations published on 2026-08-29 were withdrawn the same
+day because `screen_match.classify_array` costs 1503 ms/frame and a probe calling
+it per frame drained an 8 fps x11grab at 0.64 fps.  A backlog PRESERVES ORDERING
+and DESTROYS DURATIONS, so every "latency" it produced was really the queue
+depth.  See docs/re/menu-idle-and-b-2026-08-29.md.
+
+So this probe is built the other way round:
+
+  * per-frame work is a few MILLISECONDS, not 1.5 s.  The cost in screen_match is
+    the +/-8 px offset search over a full-res surface (25 znccs); every committed
+    capture aligns at exactly dy=0 dx=0 (five screens, +/-2 px search,
+    five-screens-acceptance.md), so this classifier decimates 4x and does ONE
+    zncc per reference.  --control checks that shortcut against the same fixtures
+    screen_match uses, INCLUDING the movie-frame negatives.
+  * the stream is torn down and restarted every RESTART_S, because a long-lived
+    x11grab degrades and then freezes on a stale frame (fast_title_probe.py).
+  * an INDEPENDENT one-shot grab every CHECK_S is compared with the stream's own
+    latest frame.  A stalled stream cannot pass that, and the check is logged so
+    a negative result can be audited rather than believed.
+  * the loop's real sample rate is reported.  If frames/elapsed is not close to
+    the requested rate, the durations in the log are NOT trustworthy and the
+    probe says so in its own summary.
+
+Every frame is written to a TSV; the durations are computed offline from it, so
+nothing here depends on the probe having classified in real time.
+
+    title_timing_probe.py --control
+    title_timing_probe.py --run SECONDS OUT.tsv
+"""
+import os
+import subprocess
+import sys
+import time
+
+import numpy as np
+from PIL import Image
+
+REPO = os.path.dirname(os.path.dirname(os.path.dirname(os.path.abspath(__file__))))
+CAP = os.path.join(REPO, "docs", "re", "captures")
+SD = os.path.dirname(os.path.abspath(__file__))
+
+W, H = 1280, 720
+SURFACE_TOP = 45          # xenia window chrome; the game surface is 1279x675
+DS = 4                    # decimation for both live frames and references
+RATE = 8                  # requested frames/s
+RESTART_S = 30            # a long-lived x11grab freezes on a stale frame
+CHECK_S = 20              # independent one-shot grab, cross-checked against the stream
+THRESH = 0.70
+DISPLAY = os.environ.get("DISPLAY", ":98")
+
+REFS = {
+    # the interactive title WITH the plate -- what the run is waiting to see arrive
+    "title_plate":   "title-builds/live-title-press-a.png",
+    # the same screen BEFORE the plate.  This is the reference the plate delay is
+    # measured from, and it is a committed capture, not a render of ours.
+    "title_noplate": "title-builds/live-title-build4-no-plate.png",
+    "menu":          "title-builds/live-main-menu.png",
+}
+
+
+def surface(a):
+    h, w = a.shape
+    if h == H and w == W:
+        return a[SURFACE_TOP:, :1279]
+    return a
+
+
+def load_gray(p):
+    return np.asarray(Image.open(p).convert("L"), dtype=np.float32)
+
+
+_R = {}
+
+
+def refs():
+    if not _R:
+        for k, v in REFS.items():
+            r = surface(load_gray(os.path.join(CAP, v)))[::DS, ::DS]
+            _R[k] = (r - r.mean()) / (np.sqrt((r * r).sum() - r.size * r.mean() ** 2) or 1.0)
+    return _R
+
+
+def scores(gray):
+    """ZNCC of a frame against every reference, decimated, NO offset search."""
+    img = surface(gray)[::DS, ::DS]
+    out = {}
+    for k, rn in refs().items():
+        h = min(img.shape[0], rn.shape[0])
+        w = min(img.shape[1], rn.shape[1])
+        x = img[:h, :w]
+        y = rn[:h, :w]
+        xc = x - x.mean()
+        d = np.sqrt((xc * xc).sum())
+        out[k] = float((xc * y).sum() / d) if d else 0.0
+    return out
+
+
+def label(sc):
+    k = max(sc, key=sc.get)
+    return k if sc[k] >= THRESH else "other"
+
+
+def glyph(rgb):
+    """Byte-identical to is_title.py's counter."""
+    r = rgb[:, :, 0].astype(np.int16)
+    g = rgb[:, :, 1].astype(np.int16)
+    b = rgb[:, :, 2].astype(np.int16)
+    return int(((g > 130) & (g - r > 45) & (g - b > 45)).sum())
+
+
+def gray_of(rgb):
+    return (0.299 * rgb[:, :, 0] + 0.587 * rgb[:, :, 1] + 0.114 * rgb[:, :, 2]).astype(np.float32)
+
+
+# ---------------------------------------------------------------- control
+
+
+CONTROLS = [
+    (os.path.join(CAP, "title-builds/live-title-press-a.png"), "title_plate"),
+    (os.path.join(CAP, "title-screen-oracle.png"), "title_plate"),
+    (os.path.join(CAP, "title-builds/live-title-build4-no-plate.png"), "title_noplate"),
+    (os.path.join(CAP, "title-builds/live-main-menu.png"), "menu"),
+    (os.path.join(CAP, "main-menu-oracle.png"), "menu"),
+    (os.path.join(CAP, "main-menu-reached.png"), "menu"),
+    # the class this oracle exists to reject
+    (os.path.join(CAP, "instrument-controls/movie-frame-attract-a.png"), "other"),
+    (os.path.join(CAP, "instrument-controls/movie-frame-attract-b.png"), "other"),
+    (os.path.join(CAP, "difficulty-screen.png"), "other"),
+]
+
+# The plate detector is a THRESHOLD on the glyph counter, so it needs its own
+# control: the committed no-plate title reads ~159 and plate titles 753..1493.
+GLYPH_CONTROLS = [
+    (os.path.join(CAP, "title-builds/live-title-build4-no-plate.png"), "lo"),
+    (os.path.join(CAP, "title-builds/live-title-press-a.png"), "hi"),
+    (os.path.join(CAP, "instrument-controls/movie-frame-attract-a.png"), "lo"),
+    (os.path.join(CAP, "instrument-controls/movie-frame-attract-b.png"), "lo"),
+]
+PLATE_GLYPH = 400
+
+
+def control():
+    bad = 0
+    print("--- content classifier (decimated, no offset search) ---")
+    for p, exp in CONTROLS:
+        if not os.path.exists(p):
+            print(f"  SKIP (missing) {os.path.basename(p)}")
+            continue
+        t = time.time()
+        sc = scores(load_gray(p))
+        got = label(sc)
+        ms = (time.time() - t) * 1000
+        ok = got == exp
+        bad += 0 if ok else 1
+        print(f"  {'ok  ' if ok else 'FAIL'} {os.path.basename(p):<36} -> {got:<13} "
+              f"(exp {exp:<13}) " + "  ".join(f"{k}={v:+.3f}" for k, v in sc.items())
+              + f"  [{ms:.1f} ms]")
+
+    print(f"\n--- plate detector (glyph >= {PLATE_GLYPH}) ---")
+    for p, exp in GLYPH_CONTROLS:
+        if not os.path.exists(p):
+            print(f"  SKIP (missing) {os.path.basename(p)}")
+            continue
+        n = glyph(np.asarray(Image.open(p).convert("RGB")))
+        got = "hi" if n >= PLATE_GLYPH else "lo"
+        ok = got == exp
+        bad += 0 if ok else 1
+        print(f"  {'ok  ' if ok else 'FAIL'} {os.path.basename(p):<36} glyph={n:<6} -> {got} (exp {exp})")
+
+    print(f"\n{'CONTROL PASSED' if not bad else f'CONTROL FAILED ({bad})'}")
+    return 1 if bad else 0
+
+
+# ---------------------------------------------------------------- live run
+
+
+def open_stream():
+    return subprocess.Popen(
+        ["ffmpeg", "-loglevel", "error", "-f", "x11grab", "-draw_mouse", "0",
+         "-video_size", f"{W}x{H}", "-i", DISPLAY, "-r", str(RATE),
+         "-f", "rawvideo", "-pix_fmt", "rgb24", "-"],
+        stdout=subprocess.PIPE, bufsize=W * H * 3 * 2)
+
+
+def oneshot():
+    """An INDEPENDENT grab, through a fresh short-lived process."""
+    p = subprocess.run(
+        ["ffmpeg", "-loglevel", "error", "-f", "x11grab", "-draw_mouse", "0",
+         "-video_size", f"{W}x{H}", "-i", DISPLAY, "-frames:v", "1",
+         "-f", "rawvideo", "-pix_fmt", "rgb24", "-"],
+        stdout=subprocess.PIPE, timeout=20)
+    b = p.stdout
+    if len(b) < W * H * 3:
+        return None
+    return np.frombuffer(b[:W * H * 3], np.uint8).reshape(H, W, 3)
+
+
+PAD = os.environ.get("XENIA_PAD_FILE", "/tmp/xenia_pad.txt")
+
+
+def _pad_write(state):
+    tmp = PAD + ".tmp"
+    with open(tmp, "w") as f:
+        f.write(state)
+    os.replace(tmp, PAD)
+
+
+def tap(button, secs=0.25):
+    """Press INLINE and return the moment the press landed.
+
+    pad.py through subprocess.run costs a python start plus the hold before the
+    caller can timestamp anything, so run 1's press times were ~0.3 s late with
+    no way to tell how late.  Same file, same rename-into-place, no interpreter.
+    """
+    _pad_write(f"press={button}")
+    t = time.time()
+    time.sleep(secs)
+    _pad_write("")
+    return t
+
+
+def run(limit, out_path, shots_dir):
+    os.makedirs(shots_dir, exist_ok=True)
+    n = W * H * 3
+    p = open_stream()
+    t0 = time.time()
+    seg = t0
+    chk = t0
+    frames = 0
+    saved = set()
+    ev = []          # (name, t) -- ordering only; durations come from the TSV
+    state = "wait"   # wait -> title -> plate -> pressedA -> menu -> pressedB -> done
+    last_gray = None
+    prev_mean = -1.0
+    same = 0
+    longest_same = 0
+    fh = open(out_path, "w")
+    fh.write("#t\tglyph\tmean\tmotion\ttitle_plate\ttitle_noplate\tmenu\tlabel\n")
+
+    def mark(name):
+        t = time.time() - t0
+        ev.append((name, t))
+        print(f"EVENT {name} t={t:.3f}", flush=True)
+        return t
+
+    title_seen_at = None
+    while time.time() - t0 < limit and state != "done":
+        now = time.time()
+        # 🔴 Do NOT restart once the measurement is under way.  Run 1 restarted
+        # 0.25 s after the (A) press and then reported 14 byte-identical frames
+        # over 1.5 s -- a stale stream straddling exactly the interval being
+        # timed, which is how a press latency gets inflated by 1.5 s.  The
+        # degradation the restart guards against is a minutes-scale drift
+        # (fast_title_probe.py); the whole measuring window is under 30 s, so
+        # freezing the stream for it is strictly safer than restarting inside it.
+        if state == "wait" and now - seg > RESTART_S:
+            p.kill()
+            p = open_stream()
+            seg = now
+            fh.write(f"#restart\t{now - t0:.3f}\n")
+        buf = p.stdout.read(n)
+        if len(buf) < n:
+            p.kill()
+            p = open_stream()
+            seg = time.time()
+            continue
+        t = time.time() - t0
+        rgb = np.frombuffer(buf, np.uint8).reshape(H, W, 3)
+        g = gray_of(rgb)
+        gl = glyph(rgb)
+        sc = scores(g)
+        lb = label(sc)
+        surf = surface(g)
+        mn = float(surf.mean())
+        mo = float(np.abs(surf[::8, ::8] - last_gray).mean()) if last_gray is not None else -1.0
+        last_gray = surf[::8, ::8].copy()
+        frames += 1
+        if abs(mn - prev_mean) < 1e-6:
+            same += 1
+            longest_same = max(longest_same, same)
+        else:
+            same = 0
+        prev_mean = mn
+        fh.write(f"{t:.3f}\t{gl}\t{mn:.3f}\t{mo:.3f}\t{sc['title_plate']:+.4f}\t"
+                 f"{sc['title_noplate']:+.4f}\t{sc['menu']:+.4f}\t{lb}\n")
+
+        # --- independent cross-check that the stream is not stale
+        if time.time() - chk > CHECK_S:
+            chk = time.time()
+            o = oneshot()
+            if o is None:
+                fh.write(f"#check\t{t:.3f}\tONESHOT_FAILED\n")
+            else:
+                om = float(surface(gray_of(o)).mean())
+                fh.write(f"#check\t{t:.3f}\tstream={mn:.3f}\toneshot={om:.3f}\t"
+                         f"delta={abs(om - mn):.3f}\n")
+            fh.flush()
+
+        # --- the drive.  DO NOT press during a movie: a run that taps through
+        # the intro reaches a title that accepts nothing (skip_intro.sh).
+        if state == "wait":
+            if lb in ("title_noplate", "title_plate") and 0 <= mo < 2.0:
+                title_seen_at = mark("title_static")
+                if gl >= PLATE_GLYPH:
+                    mark("plate_already")     # would mean the plate is not late
+                    state = "plate"
+                else:
+                    state = "title"
+                Image.fromarray(rgb).save(os.path.join(shots_dir, "t0-title.png"))
+        elif state == "title":
+            if gl >= PLATE_GLYPH:
+                mark("plate")
+                Image.fromarray(rgb).save(os.path.join(shots_dir, "t1-plate.png"))
+                state = "plate"
+                plate_at = t
+        elif state == "plate":
+            if t - ev[-1][1] > 5.0:
+                tp = tap("A") - t0
+                ev.append(("pressA", tp))
+                print(f"EVENT pressA t={tp:.3f}", flush=True)
+                state = "pressedA"
+        elif state == "pressedA":
+            if lb == "menu":
+                mark("menu")
+                Image.fromarray(rgb).save(os.path.join(shots_dir, "t2-menu.png"))
+                state = "menu"
+        elif state == "menu":
+            if t - ev[-1][1] > 8.0:
+                tp = tap("B") - t0
+                ev.append(("pressB", tp))
+                print(f"EVENT pressB t={tp:.3f}", flush=True)
+                state = "pressedB"
+        elif state == "pressedB":
+            if lb in ("title_plate", "title_noplate"):
+                mark("back_title")
+                Image.fromarray(rgb).save(os.path.join(shots_dir, "t3-back-title.png"))
+                state = "done"
+
+    p.kill()
+    dt = time.time() - t0
+    fps = frames / dt if dt else 0
+    fh.write(f"#summary\tframes={frames}\telapsed={dt:.1f}\tfps={fps:.2f}\trequested={RATE}"
+             f"\tlongest_identical_run={longest_same}\n")
+    for name, t in ev:
+        fh.write(f"#event\t{name}\t{t:.3f}\n")
+    fh.close()
+    print(f"\n{frames} frames in {dt:.1f}s = {fps:.2f} fps (requested {RATE})")
+    print(f"longest run of byte-identical surface means: {longest_same} frames "
+          f"({longest_same / RATE:.2f} s at the requested rate)")
+    if fps < RATE * 0.75:
+        print("🔴 SAMPLE RATE FELL BELOW 75% OF REQUESTED — durations in this log "
+              "are NOT trustworthy (this is the backlog failure mode).")
+    for name, t in ev:
+        print(f"  {name:<14} {t:8.3f}")
+    return 0
+
+
+if __name__ == "__main__":
+    if len(sys.argv) > 1 and sys.argv[1] == "--control":
+        sys.exit(control())
+    if len(sys.argv) > 3 and sys.argv[1] == "--run":
+        sys.exit(run(float(sys.argv[2]), sys.argv[3],
+                     sys.argv[4] if len(sys.argv) > 4 else "/sylph-home/re/shots/title-timing"))
+    print(__doc__)
+    sys.exit(2)