re: the initial-focus 🟡 is contradicted by two other records, and I could not settle it

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

docs/re/menu-navigation-semantics.md

@@ -30,6 +30,21 @@ with [`tools/re-capture/menu_focus.py`](../../tools/re-capture/menu_focus.py).
 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.
 
+⚠️ **2026-08-30 — and the sources DISAGREE, which nothing here had noticed.**
+`boot_menu.sh`'s own closing line says *"AT MAIN MENU (cursor on NEW GAME)"*, and
+[`menu-state-in-memory.md`](menu-state-in-memory.md)'s run reaches `EXTRAS` in
+**four** downs, which only counts from `NEW GAME`. Two sources say `NEW GAME`;
+this table says `TUTORIAL` 2/2. `skip_intro.sh` presses Ⓐ once and no d-pad, so
+the harness is not moving the cursor and that does not explain it.
+
+🔴 **I tried to settle it and could not: the boot never reached the menu**, twice —
+the title gate cannot fire on this title
+([harness-title-gate-assumes-a-static-title](harness-title-gate-assumes-a-static-title.md)).
+So the disagreement stands, and the round trip that would answer the persistence
+question — menu → Ⓑ → title → Ⓐ → menu, is focus where you left it or reset? — has
+still never been run. `tools/re-capture/focus_persistence.sh` is written and ready
+for a harness that can reach the menu.
+
 **🟡 Initial focus is reproducible but not established as invariant.** Both of my
 boots opened on `TUTORIAL`, and both used `boot_menu.sh`. The run recorded in
 [`menu-state-in-memory.md`](menu-state-in-memory.md) reached `EXTRAS` with *four*