fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

re: initial focus is TUTORIAL x3 / NEW GAME x3, and never anything else

Browse Source 
Two more data points for the Q5 instability, from today s drives. A run that
pressed A with no d-pad movement ended in a tutorial mission, correlating +0.960
with the committed capture, so that boot opened on TUTORIAL. A later boot read
NEW GAME from a focus detector on the first menu frame.

Six boots on the same harness now: TUTORIAL three times, NEW GAME three times,
and no other item ever observed. The distribution is not uniform over the five
buttons -- only these two occur -- which is a real constraint on whatever selects
initial focus and something an explanation will have to account for.

Also records in METHOD a bug that cost a seven-minute driven boot: a value was
clamped for readability BEFORE the comparison that used it. A focus detector
printed a degenerate margin, so it was capped at 999; the cap ran before the
vote-sorting step, two different votes compared equal, the stable sort kept the
wrong one, and a correct NEW GAME became an out-of-range index and a refusal. The
measurement was right throughout -- a cosmetic fix changed a decision. Clamp at
the point of display, never upstream of a comparison.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QsEPXWVaEpyfudtR6re1Pd
This commit is contained in:
sylph-decoder
2026-08-29 17:42:03 +00:00
parent 8b4dcccb67
commit c5fe6a460c
3 changed files with 31 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/re/menu-navigation-semantics.md
View File

@@ -130,12 +130,24 @@ So Q4's last row closes as **measured**:
and `3 GP_LOAD` / `2 GP_SELECT_STORAGE` are name-match candidates and nothing
more.
### Initial focus — a fourth data point, and it still varies
### Initial focus — six data points now, and it still varies
This boot opened the main menu on **`NEW GAME`**. Running tally across four
boots of the same harness: `TUTORIAL`, `TUTORIAL`, `NEW GAME`, `NEW GAME`.
Unchanged conclusion: **do not hardcode it.**
✅ **Two more, 2026-08-29, and the split is now even.** A drive that pressed Ⓐ
with no d-pad movement ended in a **tutorial mission** (+0.960 against
`tutorial-mission-reached-then-crash.png`), so that boot opened on `TUTORIAL`. A
later boot read **`NEW GAME`** from a focus detector on the first menu frame.
**Tally: `TUTORIAL` ×3, `NEW GAME` ×3.** Six boots, same harness, no other item
ever seen. ⚠️ It is *not* uniform across the five buttons — only these two occur —
which is a constraint on whatever selects it, and something a future explanation
has to account for. Still **do not hardcode it**, and note that
`newgame_path.sh`'s "NEW GAME is the first item so no d-pad is needed" is wrong
half the time — see [`s00a-drive-blocked-by-focus.md`](s00a-drive-blocked-by-focus.md).
### The `NEW GAME` path completes — the `SELECT DATA` crash is state, not path
A second run of the same path, 2026-08-28, **did not crash**: