re: menu focus does not survive a reboot -- six fresh boots, three following a session that ended elsewhere

No new boot was spent: six runs had already captured the first menu entry of a
fresh boot, and all six read NEW GAME. Three of them follow a session that ended
with the cursor on EXTRAS or OPTIONS, which is what makes it a test of persistence
rather than a repeated observation.

Reach stated rather than implied: every session ends with the emulator KILLED, so a
game that writes menu state on a clean shutdown would never get the chance. This
measures 'does not survive a killed session'.

Refutation attempt on the port's extras/initial_focus: ptbtn11 -- it SURVIVES.
ptbtn11 is the top button on the EXTRAS build, with the main menu as a control
where ptbtn01 is top and is known to be NEW GAME.

Incidentally corrects ring_row.py's stated calibration. It cited capture_y = 49.5 +
1.060*design_y, fitted against menu_focus.py's row centres, which are NOT the
disc's button rows -- the disc says 162/242/322/401/482, spacing 80, and
menu_focus.py drifts up to 17 px against them. Re-fitted: 64.82 + 0.9919*design_y,
residuals under 0.7 px. No item assignment changes.

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

crates/sylpheed-formats/examples/extras_button_order.rs

@@ -0,0 +1,44 @@
+//! Is `ptbtn11` the TOP item of the `EXTRAS` screen?
+//!
+//! `sylpheed-port` authors `extras/initial_focus: ptbtn11` and states it is
+//! correct under the surviving reading — "a submenu resets to the item it opens
+//! on". The oracle shows EXTRAS opening on `MISSION SELECT`, the first of
+//! MISSION SELECT / MOVIE THEATER / BACK. So their value is right only if
+//! `ptbtn11` is that first item. This checks it against the disc.
+//!
+//! CONTROL: the same read on the MAIN MENU build, whose five buttons have a known
+//! top-to-bottom order (NEW GAME first). If the ordering rule cannot reproduce a
+//! known screen it cannot be trusted on an unknown one.
+//!
+//!     cargo run -p sylpheed-formats --example extras_button_order
+use sylpheed_formats::{pak::PakArchive, ui_layout};
+use std::path::PathBuf;
+
+fn report(ar: &PakArchive, entry: usize, what: &str) {
+    let Ok(by) = ar.read(&ar.entries()[entry]) else { return };
+    let Some(b) = ui_layout::parse_build(&by) else { return };
+    let mut rows: Vec<(i32, String, u32)> = b
+        .elements
+        .iter()
+        .filter(|e| e.name.starts_with("ptbtn") && !e.name.contains('f'))
+        .map(|e| {
+            let y = e.rest().map(|k| k.y).unwrap_or(e.pivot_y as i32);
+            (y, e.name.clone(), e.kind)
+        })
+        .collect();
+    rows.sort_by_key(|r| r.0);
+    println!("\n{what} (entry {entry}) — buttons top to bottom:");
+    for (y, n, k) in &rows {
+        println!("   y {y:5}  {n:14} kind 0x{k:04x}");
+    }
+    if let Some((_, first, _)) = rows.first() {
+        println!("   => TOP item is {first}");
+    }
+}
+
+fn main() {
+    let root = PathBuf::from(std::env::var("SYLPHEED_DISC").expect("SYLPHEED_DISC"));
+    let ar = PakArchive::open(root.join("dat/GP_TITLE.pak")).expect("GP_TITLE.pak");
+    report(&ar, 5, "CONTROL: main menu (NEW GAME must be top)");
+    report(&ar, 6, "EXTRAS");
+}