re: B on the main menu goes to the TITLE -- measured, filling an empty evidence cell

menu-navigation-semantics.md had this row at yellow with an EMPTY evidence cell,
and it is what the port still authors as on_cancel.

Delivery-confirmed via [RE-INPUT] (B is kXInputPadB = 0x5801), change detected
rather than timed. B delivered at 331.2 s; the glyph leaves 327 by 331.6 and
73.5 % of pixels differ. Both captures name themselves: PROJECT SYLPHEED with the
(C)2006,2007 SQUARE ENIX line.

Three things measured:
  * B on the main menu goes to the title;
  * latency <= 0.4 s at a 4 Hz sample rate, where the corpus previously had this
    as 'not measured (a backlogged probe void)';
  * NO loading screen in between -- the disc carries four pgloading_* bundles and
    none appears on this path.

What the run CANNOT say, recorded in the table rather than glossed: 'B on the
title -> nothing' is still unevidenced. The second B was delivered during the
title's build-in, so the glyph 0 -> 154 change after it is the build-in
completing, not a response. A run that answers that row must wait for the title
to settle before pressing.

The 're-draws PRESS A after a beat' half of the first row is also still
unevidenced -- the run ended with the plate absent.

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

docs/re/data/b-on-main-menu.txt

@@ -0,0 +1,63 @@
+# What Ⓑ does on the MAIN MENU -- measured 2026-08-30.
+#
+# menu-navigation-semantics.md had this row at 🟡 with an EMPTY evidence cell,
+# and it is what the port still authors as on_cancel.
+#
+# Harness: tools/re-capture/b_from_menu.py -- the plate-pulse title detector,
+# the glyph-327 menu detector, delivery confirmed from [RE-INPUT] rather than
+# from the pad, and change detected rather than timed. B is kXInputPadB =
+# 0x5801 (ui/virtual_key.h:323).
+#
+#   [321.7s] TITLE (glyph 959)
+#   [322.7s] A delivered (attempt 1)
+#   [327.7s] MENU (glyph 327) -- pressing B
+#   [331.2s] B delivered (attempt 1)
+#   [335.0s] screen changed: 73.5 % of pixels differ, glyph 0
+#   [341.3s] glyph 154
+#
+# THE SERIES ACROSS THE PRESS (t : glyph):
+#   326.2 : 0
+#   326.5 : 327
+#   326.7 : 327
+#   326.9 : 327
+#   327.2 : 327
+#   327.4 : 327
+#   327.7 : 327
+#   331.2 : 327
+#   331.6 : 0
+#   332.4 : 0
+#   332.8 : 0
+#   333.3 : 0
+#   333.8 : 0
+#   334.1 : 0
+#   334.5 : 0
+#   335.0 : 0
+#   340.2 : 0
+#   340.5 : 54
+#   340.7 : 154
+#   340.8 : 154
+#   340.9 : 154
+#   341.0 : 154
+#   341.1 : 154
+#   341.2 : 154
+#   341.3 : 154
+#
+# READING: B on the main menu goes to the TITLE. Both captures name
+# themselves -- PROJECT SYLPHEED with the (C)2006,2007 SQUARE ENIX line.
+#   2-after-B-on-menu.png  the title MID-BUILD-IN: wordmark drawn, the green
+#                          copyright line not yet -- which is why glyph is 0
+#                          while 78.0 % of the surface is inked
+#   3-after-B-again.png    copyright drawn, glyph 154 = the plate-absent floor
+#
+# ✅ NO LOADING SCREEN between. The disc carries four pgloading_* bundles and
+# none appears on this path.
+#
+# ✅ LATENCY <= 0.4 s: B delivered at 331.2, glyph leaves 327 by 331.6, at a
+# 4 Hz sample rate. The corpus previously had this as 'not measured (a
+# backlogged probe void)'.
+#
+# 🔴 WHAT THIS RUN CANNOT SAY: 'B on the title -> nothing'. The second B was
+# delivered at 340.2, DURING the title's build-in, so the glyph 0 -> 154
+# change that follows is the build-in completing and not a response. That row
+# stays 🟡 with no evidence, and a run that answers it must wait for the title
+# to SETTLE before pressing.

docs/re/menu-navigation-semantics.md

@@ -23,8 +23,8 @@ with [`tools/re-capture/menu_focus.py`](../../tools/re-capture/menu_focus.py).
 | **wrap at the bottom** | ⬇ from the last item goes to the **first** | same, panels 3→4, and 4 presses from `EXTRAS` landing on `OPTIONS` — i.e. wrapping — is what makes the count come out |
 | **left / right** | **nothing**, on the main menu | cursor unmoved across one ⬅ and one ➡ |
 | **Ⓑ on a submenu** | returns to the parent **with focus restored to the item you entered from** — `LOAD GAME`→`LOAD GAME`, `TUTORIAL`→`TUTORIAL`, `OPTIONS`→`OPTIONS`, `EXTRAS`→`EXTRAS` | 4/4 |
-| **Ⓑ on the main menu** | 🟡 goes to the **title**, which re-draws `PRESS Ⓐ BUTTON` after a beat | **none** — and the main menu's own footer does not advertise Ⓑ; [downgraded below](#-refutation-attempt-2026-08-29--the-main-menus-own-footer-does-not-advertise-ⓑ) |
-| **Ⓑ on the title** | 🟡 **nothing** | **none** |
+| **Ⓑ on the main menu** | ✅ goes to the **title** — measured 2026-08-30, delivery-confirmed, **≤ 0.4 s**, and with **no loading screen** in between. ⚠️ the *"re-draws `PRESS Ⓐ` after a beat"* half is still unevidenced: the run ended with the plate still absent | **1 run** — [`../re/data/b-on-main-menu.txt`](data/b-on-main-menu.txt) · [mid-build-in](captures/title-builds/live-b-on-menu-title-buildin.png) · [settled](captures/title-builds/live-b-on-menu-title-settled.png). The footer point below still stands |
+| **Ⓑ on the title** | 🟡 **nothing** | **none** — ⚠️ and the 2026-08-30 run **cannot** be counted here: its second Ⓑ was delivered *during* the title's build-in, so the glyph 0 → 154 that followed is the build-in completing, not a response. A run that answers this must wait for the title to **settle** first |
 
 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.