handoff: the menu BGM loop is attempted and not captured; the route left

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

docs/port/HANDOFF.md

@@ -2529,6 +2529,28 @@ whatever it returns — the same reason a truncated log and a t=0 render both lo
 fine from inside. Template matching against the exported cue with a bed-only
 control has no such knob, which is the right fix rather than a better threshold.
 
+## 🟡 2026-08-30 — the menu BGM loop point: attempted, NOT captured
+
+Your 87.8 s restart and 3.4 s near-silent seam still stand alone. I tried to
+measure what the game does at `BGM_103`'s loop and **failed on the rig, not the
+question** — recorded so nobody repeats it.
+
+Audio needs the ALSA tee; seeing the title needs video, so `--gpu=null` was off the
+table. That combination runs the guest at **~0.20× real time** — 76.5 s of audio in
+378 s of wall clock — and never reached the menu in 300 s even after tapping Ⓐ to
+skip the movie. The tee's slave ended in a broken pipe. ⚠️ Not a crash: memory was
+fine and the kill was my own cleanup.
+
+✅ **The route left** (written down, not attempted): drop video and use the **XMA
+probe log as the screen oracle**. Sitting on the menu decodes exactly `BGM_103`'s
+two waves — 3 876 864 and 3 930 112 B — so those appearing *is* the menu, which
+frees `--gpu=null` and its clean 0.31 %-silence capture. Better provenance for an
+audio question than a screenshot, too.
+
+⚠️ **This is not "the menu is unreachable"** — Ⓐ into the menu is measured and works
+(the A/B's leg B ends at glyph 327). One recording configuration failed.
+[`menu-bgm-loop-not-yet-captured.md`](../re/structures/menu-bgm-loop-not-yet-captured.md)
+
 ## ✅ 2026-08-30 — the resolver is FIXED, and there is a new pin: `formats-pin-2026-08-30`
 
 **Cause:** the start filter carried a second condition, `end - s < 1_500_000`