re: break the EXTRAS n=1 cap -- which I had wrongly called structural

I recorded EXTRAS as able to supply only one gap measurement because "its sole
exit is (B) to the menu", and called that n=1 STRUCTURAL -- a word that retires a
question. The disc refutes it in one command: build 6 declares three buttons,
ptbtn11/ptbtn12/ptbtn13, all kind 0x3002. The cap was an unverified assertion I
had already written into HANDOFF twice.

Measured EXTRAS -> a screen outside GP_TITLE via (A): outgoing quad rises across
frames 36-40 (4-5 frames, matching build 6's declared 10-unit close), then THREE
empty frames at 42, 43, 44, then a different archive builds (23-28 draws/frame
against GP_TITLE's 11-14). Gap = 3.

So EXTRAS as outgoing gives {2, 3}, and seven transitions now group as:
menu {0,1,1} n=3, EXTRAS {2,3} n=2, title {3,3,3} n=3.

A pairwise control that holds the destination class constant: menu -> another
archive gives 1, EXTRAS -> another archive gives 3. Same kind of destination, gap
differs by outgoing screen. That is the strongest support yet for the
outgoing-screen dependence because it removes the destination as the variable.

But the clean ordering is GONE: EXTRAS {2,3} and title {3,3,3} overlap at 3, so
"menu < EXTRAS < title" no longer separates them. What survives is weaker -- the
outgoing screen constrains the gap to a ~2-wide band and the bands are not
disjoint.

METHOD: a structural limit is a claim and needs checking like any other.
"Structural" and "impossible" are the two words most worth distrusting in your own
notes, because they retire a question rather than answering it and nothing later
re-opens them.

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

docs/re/METHOD.md

@@ -552,6 +552,16 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
   discipline as "state what the number is a number of", applied to scope rather
   than to units.
 
+* ⚠️ **A structural limit is a claim, and it needs checking like any other.** I
+  recorded that `EXTRAS` could supply only one measurement because *"its sole exit
+  is Ⓑ to the menu"*, and called the resulting `n=1` **structural** — a word that
+  closes a question. The disc refutes it: build 6 declares **three buttons**
+  (`ptbtn11/12/13`, kind `0x3002`), so Ⓐ leaves by another route entirely.
+  📌 **"Structural" and "impossible" are the two words most worth distrusting in
+  your own notes**, because they retire a question rather than answering it, and
+  nothing later re-opens them. The check here cost one `screen info` invocation
+  against a claim I had already written into `HANDOFF.md` twice.
+
 ## Runtime / emulator
 
 * **Look at the PNG** — and check its dimensions.