re: first audit of INDEX against the pages it links -- 3 of 8 rows were stale

INDEX is read every iteration and is the first thing a new reader meets, and I had
admitted three times to never auditing it. Found by accident: I was about to spend
a boot measuring whether A skips a movie because INDEX said 🟡, when movie-binding.md
had it settled since 2026-08-28 with a three-boot baseline and a delivery counter,
and HANDOFF carried it correctly. The staleness was in the index alone.

Three stale rows fixed: movie skippability, SE audio extractability, and B leaving
the main menu. Five other hits read and left alone -- index and page were talking
about different clauses.

One of the three should have been caught by check_refuted.py: REFUTED holds the
same dead claim with a different second clause, and the register matches exact
wording. Its docstring documents that weakness; this is the first live instance.

Also flags a within-page contradiction not fixed here: menu-audio-cues.md line 81
still heads a section saying SE audio is not extractable, which its own line 189
refutes.

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

docs/re/data/index-vs-pages-audit.txt

@@ -0,0 +1,58 @@
+# Does INDEX.md agree with the pages it links? -- 2026-08-30. FIRST AUDIT.
+#
+# INDEX.md is read every iteration by both agents and is the first thing a new
+# reader meets. sylpheed-port's phrase is the right one: an index is an
+# AMPLIFIER -- a status wrong there is wrong everywhere it is quoted from. It is
+# also a file I have admitted three times I had never audited.
+#
+# FOUND BY ACCIDENT, which is why the audit happened: I was about to spend a boot
+# measuring whether Ⓐ skips a movie, because the port's BLOCKED.md lists it 🟡 and
+# so did INDEX. `movie-binding.md` has had it ✅ SETTLED since 2026-08-28 -- with a
+# three-boot baseline and a delivery counter -- and HANDOFF carries it correctly.
+# The staleness was in the index alone, and it nearly cost a run.
+#
+# TOOL: tools/re-capture/index_vs_pages.py. It prints a LISTING, NOT A VERDICT:
+# 8 rows where the index is 🟡/❔ while the linked page has a "✅ settled/decoded"
+# heading. A row can legitimately be unsure about one clause while its page is
+# sure about another, so every hit is a prompt to read. I read all 8.
+#
+# ✅ 5 ARE LEGITIMATE -- index and page are talking about different clauses:
+#   77  flight-speed-law        "🟡 for the unit scale"           -- still true
+#   127 isl-builtins            "🟡 28 ..."                        -- still true
+#   132 mcol-collision          "🟡 OPENED ..."                    -- a status word
+#   159 boot-config-registry    "❔ [SYSTEM] is empty ..."          -- still true
+#   162 ui-title-build-map      "🟡 which loading bundle takes which name" -- open
+#
+# 🔴 3 WERE STALE, all three contradicted by the page they link:
+#
+#   160 movie-binding      "🟡 skippability unsettled"
+#       -> page: ✅ settled 2026-08-28. One Ⓐ skips: title at 57 s against a
+#          193/196/193 s three-boot baseline, press proved singular by Canary's
+#          own delivery counter going 3→4, skipped-to title fully functional.
+#
+#   158 menu-audio-cues    "❔ Static.slb has no wave boundaries, so SE audio is
+#                           not extractable"
+#       -> page line 189: "both waves are located in Static.slb. The port can
+#          have the audio." The waves are at move 0x1ec0, confirm 0x5d6c0,
+#          back 0x0ec0.
+#       ⚠️ AND THE PAGE CONTRADICTS ITSELF: its line 81 still heads a section
+#          "❔ And a new negative: an individual SE's audio is not extractable
+#          yet", which its own line 189 refutes. Not fixed here -- flagged.
+#
+#   156 menu-navigation     "🟡 Ⓑ leaving the MAIN menu downgraded 2026-08-29 --
+#                            uncited"
+#       -> page line 27: ✅ measured 2026-08-30, delivery-confirmed, ≤0.4 s, no
+#          loading screen, plate re-drawn ~7 s later, three captures cited.
+#
+# 🔴 AND ONE OF THE THREE SHOULD HAVE BEEN CAUGHT BY MY OWN REGISTER.
+# REFUTED.md holds "`Static.slb` has no wave boundaries, so its layout is
+# unknown". INDEX said "...so SE audio is not extractable". Same dead claim,
+# different second clause -- and check_refuted.py matches EXACT wording, so it
+# saw nothing. That weakness is documented in the tool's own docstring ("a clean
+# run means no VERBATIM revival"); this is the first LIVE instance of it, and it
+# survived in the index for days.
+#
+# ⚠️ REACH: this compares an index row's emoji against the presence of a ✅
+# heading on the linked page. It cannot see a row that is confidently WRONG
+# (no 🟡 to trip on), a row whose page has no status heading, or anything in
+# HANDOFF.md or BLOCKED.md. 3 of 8 hits were real; the other 5 cost one read each.