re: the phase transitions -- and withdrawing yesterday's refutation

because the test probed the wrong state

Nine stores to the phase field this+132, control-gated on the 136 query
returning at least the 18 known ones. Attributed to the handler each
lives in, they give the phase graph: entry -> 2, then 2 -> 0 (splash),
2 -> 3, 3 -> 4, and 4 -> 2 on event 0.

That last edge is the problem with what I did last iteration. The event-0
block sets TWO fields one instruction apart -- stw r28,136(r30) for state
0 and stw r11,132(r30) with r11 = 2 for phase 2. So B from the menu lands
in PHASE 2, the same phase as the boot title, and the test I ran
believing it probed phase 4 state 0 probed nothing of the kind.

So the refutation is withdrawn. Worse for me and better for the idea: A
working on the B-returned title is exactly what the hypothesis predicts,
since phase 2 is the phase that references BUTTON. The hypothesis is back
to untested, now consistent with two observations rather than one, and
what it still needs is the attract-returned title's phase -- which no
test so far has read.

The measurement from that iteration stands, because it does not depend on
the phase: the B-returned title accepts A, so only the ATTRACT-returned
title is inert. I have said so explicitly in the page rather than letting
the withdrawal take the good half down with it.

METHOD gets the lesson: before testing "state X behaves like this", check
your route actually reaches state X. When a transition writes more than
one field, read the whole block and not just the store you were looking
for.

docs/re/REFUTED.md

@@ -35,9 +35,12 @@ neighbourhood, not just the line.
 
 ## Screens, classes and RTTI
 
-* "the boot title is phase 2 and the attract title is phase 4 state 0, and only
-  phase 2 handles Ⓐ" → **mine, and refuted the next iteration.** Ⓑ from the menu
-  is the decoded edge `4 → 0`, and Ⓐ on that returned title opens the menu.
+* ~~"the boot title is phase 2 and the attract title is phase 4 state 0, and only
+  phase 2 handles Ⓐ" → refuted~~ — **the REFUTATION is withdrawn.** The test
+  assumed Ⓑ lands in phase 4 state 0; the event-0 block actually sets
+  **phase = 2** and state = 0 together, so it probed phase 2. The hypothesis is
+  untested, not dead.
+  [`boot-config-and-gamepart-registry.md`](boot-config-and-gamepart-registry.md)
 * "any title after the first one refuses input" → too broad. The **Ⓑ-returned
   title accepts Ⓐ**; only the **attract**-returned title is inert.
   [`canary-scripted-input-traps.md`](canary-scripted-input-traps.md)