re: fix two stale rows -- NEW GAME's destination, and my own repeat claim

No emulator-requiring state/approved item was open this iteration (issues
#1, #3, #5 all landed and moved to state/needs-human; #25 still awaits
approval). Used the gap for corpus consistency instead of idling, per the
same "a correction that never reaches the row someone reads" failure this
project keeps naming.

1. menu-navigation-semantics.md's own Q4 table still said NEW GAME was
   "not tested" and its own prose said it was "deliberately not pressed"
   and hangs the emulator -- both refuted BY THIS SAME PAGE on 2026-08-28,
   34 lines further down ("NEW GAME -- measured ... it is not a hang. It
   opens DIFFICULTY then SELECT DATA"). The correction never propagated
   backward into the table or the status line above it, so a reader
   stopping at either would come away with the wrong (and already-refuted)
   answer. Fixed in place, struck rather than deleted, with the actual
   destination and an honest note that DIFFICULTY has no id-table name
   match (already refuted separately) while SELECT DATA plausibly matches
   GP_SELECT_STORAGE as a fresh, low-confidence guess.

2. Found the identical failure mode in my own recent work: HANDOFF.md's
   original Q1-Q10 summary table (near the top of a 6600+ line file) still
   quoted the 2026-08-30 "no auto-repeat" finding as current, three commits
   after this same session measured 12 frames delay / 4 frames interval
   through a repeat-capable driver and explained why the earlier negative
   was a driver limitation, not a game fact. A reader who only sees the
   summary table -- which is exactly what a long file trains a reader to
   rely on -- would get the withdrawn answer. Fixed with an explicit note
   pointing at the current entries rather than silently editing the number
   in place, so the correction itself stays visible.

Refutation-shaped either way: two claims ("NEW GAME untested", "no
auto-repeat") checked against this corpus's own newer evidence and found
not to survive, recorded rather than left to be rediscovered.

docs/re/menu-navigation-semantics.md

@@ -1,9 +1,10 @@
 # The title menu — how it moves, and where each button goes
 
 **Status:** ✅ `CONFIRMED` (**measured**, by driving the running game) for the
-movement rules and for four of the five main-menu destinations. 🟡 the GamePart
-*id* behind each destination is a **name match onto the decoded id table**, not a
-measurement. ❔ `NEW GAME` deliberately untested.
+movement rules and for all **five** main-menu destinations, `NEW GAME`
+included (→ `DIFFICULTY` → `SELECT DATA`, not a hang — corrected 2026-09-12,
+see the Q4 table). 🟡 the GamePart *id* behind each destination is a **name
+match onto the decoded id table**, not a measurement.
 
 Answers [MISSION Q5](../port/MISSION.md) and most of Q4. Nothing here is on the
 disc in any form found so far — the port is **authoring** these rules from this
@@ -244,7 +245,7 @@ Measured by driving: focus the item, press Ⓐ, read the screen's own title.
 
 | button | screen it opens | evidence | GamePart id |
 |---|---|---|---|
-| `NEW GAME` | ❔ **not tested** | — | — |
+| `NEW GAME` | 🔴 **stale row, corrected 2026-09-12** — measured 2026-08-28: `DIFFICULTY` (`EASY`/`NORMAL`/`HARD`/`BACK`) → `SELECT DATA` → guest crash (unrelated cache-manager bug, not a menu fault). The "`NEW GAME` — measured" section further down this same page had the answer already and this table was never updated to match it | [captures](captures/newgame-path/) | `DIFFICULTY`: **no id-table name match** — already tried and refuted (`boot-config-and-gamepart-registry.md`: neither `DIFFICULTY` nor `EXTRA_MENU` survive as call-site strings). `SELECT DATA`: 🟡 `2 GP_SELECT_STORAGE`, a fresh name-guess, same low confidence as every other row here |
 | `LOAD GAME` | the save-slot list, `LOAD GAME` / `Current Storage` | [`q4-destinations.png`](captures/menu-nav/q4-destinations.png) left | 🟡 `3 GP_LOAD` |
 | `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` |
@@ -262,10 +263,15 @@ it is a name match I made by eye. The port should treat these ids as authored.
 Worth noting that the ids and the paks are not one-to-one: `GP_EXTRAS` is id 5
 with **no pak of its own** — its artwork is a build inside `GP_TITLE.pak`.
 
-**❔ `NEW GAME` was deliberately not pressed.** Ⓐ on it leads to a standing
-black-screen hang that ends the run
+~~**❔ `NEW GAME` was deliberately not pressed.**~~ **Withdrawn — stale, fixed
+2026-09-12.** This line said Ⓐ on it hangs the emulator
 ([`ui-paint-order-third-permutation.md`](ui-paint-order-third-permutation.md)),
-and this iteration needed the session. It is the one destination still unmeasured.
+which the very next section of this same page already refuted on
+2026-08-28: it does not hang, it opens `DIFFICULTY` then `SELECT DATA` before
+an unrelated crash. Kept struck rather than deleted — this is the exact
+failure this corpus keeps naming, a correction that landed lower in the
+same document than the claim it corrected and never caught up to the table
+above.
 
 ### 🔴 The "cheap way to finish this" was a dead route — WITHDRAWN 2026-08-29