5be071f9cf
verify-transcode-fidelity --selftest closes my list. It had three controls running every time -- identity, a 4-pole top-end loss, an unrelated movie -- and none asked whether the measurement itself was live. With an empty band list every comparison reads 0.0 dB: identity passes, the real pair passes, and only the unrelated-movie control fails, reporting exit 1 for a broken instrument. Same shape as the empty register in check-claims, same fix: exit 2. The self-test drives the script as a subprocess over a short window -- normal 0, bands emptied 2. All four tools now assert their own harnesses. Top-item sweep from the DIFFICULTY finding: one site, MenuFlow.initial_focus's buttons[0], already documented as a repair. Every other [0] in the tree is unrelated indexing. Nothing to fix, recorded so the sweep is known to have run. The reset question is settled and it went the way that makes the restraint correct: a submenu resets to its OWN OPENING ITEM, a per-screen default that need not be the first. DIFFICULTY opens on NORMAL, second of four, and returns to NORMAL after a confirmed DOWN and a round trip. So ptbtn11 is right for a reason rather than by coincidence, and buttons[0]-is-a-repair is measured rather than principled. contract-check gains check_reset_target, whose teeth the code bounds honestly: on EXTRAS the named item happens to be first, so agreement is not evidence -- what it guards is a future refactor silently substituting an index. Their refutation attempt on extras/initial_focus was made against the disc rather than against their agreement, and it survives: ptbtn11 y282 against 362 and 442. Re-checked from this port's own export, a different reader of the same disc, and the numbers are identical -- extras 282/362/442, main menu 162/242/322/401/482. Which also confirms EXTRAS could never have separated named-item from top-item. Menu focus does not survive a reboot: six fresh boots opened on NEW GAME, three of them following sessions that ended on EXTRAS or OPTIONS. So the authored value is a fresh-start value. The reach is carried verbatim into the why -- every session ended with the emulator KILLED, so this measures 'does not survive a killed session', and a console that remembers across a clean power cycle would not contradict it. Still open and not leaned on: whether the reset target moves once a difficulty has been confirmed; the same SELECT DATA crash prevents testing it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
514 lines
36 KiB
JSON
514 lines
36 KiB
JSON
{
|
|
"format": "sylpheed.flow/1",
|
|
"_": [
|
|
"The boot sequence. AUTHORED, and it has to be: HANDOFF Q6 closed this with a",
|
|
"negative -- the order is in none of the four places it could have been. It is",
|
|
"not in config.ini's empty [SYSTEM], not in the movie manifest (which carries",
|
|
"assets, not transitions), not in a persistent GamePart field (the requested id",
|
|
"lives only as a stack argument in flight), and `GP_ADVERTISE_DEMO` has zero",
|
|
"xrefs of any kind. A transition is a call with a name argument, chosen by code.",
|
|
"",
|
|
"So this file REPRODUCES AN OBSERVATION. The sequence below is what the RE",
|
|
"agent watched the game do, not what any file on the disc says it does. Nothing",
|
|
"here may be presented as decoded."
|
|
],
|
|
"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."
|
|
},
|
|
{
|
|
"screen": "developer_logos",
|
|
"why": "GAME ARTS / SETA / studio anima, after the publisher wordmark. HANDOFF Q2."
|
|
},
|
|
{
|
|
"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."
|
|
},
|
|
{
|
|
"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=238. `clock: \"shared\"` is that, spelled out rather than implied by the absence of a delay field.",
|
|
"arithmetic_why": "Why one clock reproduces the measurement, checked against this export rather than taken on trust: build 4's visible build-in ends at t=118, where `pteff01`, `pteff02` and `ptlogoall_eff` finish together; `ptbtn00` reaches alpha 255 at t=238; the difference is 120 units = 2.000 s at 60 units/s. The oracle measured 2.138 s and 2.132 s. The gap is presentation rate: 120 units in 2.135 s is 56.2 units/s, i.e. the emulator presenting at 28.1 fps against a nominal 30, and the corpus had independently measured the idle title at 28.5 fps before these runs.",
|
|
"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. `ptlogo1` has rest.t=251 and stops MOVING at t=42, then creeps 5 px and 31 alpha steps over the next 209 units. Reading rest.t 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.",
|
|
"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.",
|
|
"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."
|
|
},
|
|
"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."
|
|
}
|
|
],
|
|
"dwell": {
|
|
"_": [
|
|
"NOT SET -- because the dwell is DECLARED, and the port already plays it.",
|
|
"",
|
|
"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'.",
|
|
"🔴 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.",
|
|
"",
|
|
"🔴 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."
|
|
]
|
|
},
|
|
"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).",
|
|
"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.",
|
|
"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.",
|
|
"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)."
|
|
},
|
|
"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.",
|
|
"",
|
|
"🔴 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."
|
|
},
|
|
"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.",
|
|
"",
|
|
"🔴 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.",
|
|
"",
|
|
"⚠️ 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.",
|
|
"",
|
|
"🔴 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.",
|
|
"",
|
|
"❔ The Decoder is measuring EXTRAS re-entry now. Do not build on the",
|
|
"non-persistence half until it returns."
|
|
],
|
|
"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.",
|
|
"",
|
|
"🔴 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.",
|
|
"",
|
|
"✅ 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.",
|
|
"",
|
|
"⚠️ 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.",
|
|
"",
|
|
"⚠️ 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) ✅ 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) ⚠️ 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.",
|
|
"",
|
|
"🔴 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": "DIFFICULTY",
|
|
"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 `DIFFICULTY` 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.",
|
|
"",
|
|
"🔴 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": "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.",
|
|
"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.",
|
|
"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.",
|
|
"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.",
|
|
"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.",
|
|
"",
|
|
"🔴 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": null,
|
|
"goto_name": null,
|
|
"blocked": "The settings menu is GP_OPTIONS, not in this export. Destination MEASURED."
|
|
},
|
|
"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.",
|
|
"",
|
|
"🔴 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.",
|
|
"",
|
|
"📌 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.",
|
|
"",
|
|
"🔴 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.",
|
|
"",
|
|
"⚠️ 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.",
|
|
"",
|
|
"",
|
|
"✅ 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.",
|
|
"",
|
|
"✅ 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.",
|
|
"",
|
|
"❔ 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.",
|
|
"",
|
|
"",
|
|
"🔴 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) ⚠️ 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) 🔴 If EXTRAS turns out to persist, this becomes history and the kind must",
|
|
" (was) change with it.",
|
|
"",
|
|
"✅ CHECKED AGAINST THE BYTES 2026-08-31, by both agents independently. The",
|
|
"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.",
|
|
"",
|
|
"🔴 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.",
|
|
"",
|
|
"🔴 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.",
|
|
"",
|
|
"🔴 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."
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|