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

re: EXTRAS resets to MISSION SELECT while the main menu persists -- no menu-wide rule

Browse Source 
Ring at 347.5 on entry, 427.5 after one confirmed DOWN, 347.5 on re-entry with the
frame 0.0 % different from the first entry. sylpheed-port asserted non-persistence
when nothing had measured it; the assertion was right and is now measured.

MISSION SELECT is therefore a genuine initial focus, because this screen resets --
unlike the main menu, where a single-entry reading measures history.

Every control here exists because run 1 failed without it: absolute row checks
after every navigation press (a constant offset passes a differential control),
screen identity against an in-run reference frame (main menu 327, EXTRAS 324 and
OPTIONS 317 all sit in the same glyph window), and raw ring rows inside the
submenu so no three-item geometry is assumed. The screen was also confirmed by eye.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
This commit is contained in:
sylph-decoder
2026-08-30 22:07:24 +00:00
parent e35c56a5ed
commit df4fcd3c3b
3 changed files with 123 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -30,6 +30,38 @@ 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 — EXTRAS **resets**; the main menu **persists**. They differ.
**measured** — [`data/extras-focus-resets.txt`](data/extras-focus-resets.txt),
`tools/re-capture/extras_focus_persistence.py`.
| | ring y | item |
|---|---|---|
| EXTRAS opened on | 347.5 | `MISSION SELECT` |
| after 1 delivery-confirmed DOWN | 427.5 (+80.0) | `MOVIE THEATER` |
| after Ⓑ → main menu → Ⓐ → EXTRAS | **347.5** | **`MISSION SELECT`** |
Re-entry is **0.0 %** different from the first entry. So:
* ✅ **EXTRAS resets.** `sylpheed-port` asserted this in their contract-check when
nothing had measured it, and I flagged the assertion as an absence of evidence
encoded as a positive claim. **They were right, and it is now measured.**
* ✅ **`MISSION SELECT` is a genuine INITIAL focus**, precisely because this screen
resets — unlike the main menu, where a reading not taken on a fresh boot's first
entry measures history.
* 🔴 **The two screens behave differently, so there is no menu-wide rule.** The
main menu persists; EXTRAS does not. A generalisation in *either* direction
would be wrong, which is why wrap (measured on two screens) generalises and this
does not.
* ✅ The screen was confirmed **by eye** — `E1.png` is EXTRAS, MISSION SELECT /
MOVIE THEATER / BACK — because the previous run was fooled about which screen it
was on. And the 80.0 px step independently matches the main menu's separately
calibrated 79.25.
⚠️ Reach: one run, one round trip, one submenu. `OPTIONS`, `LOAD GAME` and
`TUTORIAL` are untested, as is whether the reset is to `MISSION SELECT` or simply
to the top item — those coincide here.
## 🔴 2026-08-30 (later) — the item NAMES below were wrong, and initial focus is NEW GAME
**The reader was broken and my control could not see it.** `menu_focus.py`'s row