handoff+method: land the ordinal retraction where the claims live

Marks the two void splash rows in the capture-comparison data file, withdraws the
three claims in HANDOFF, and corrects the METHOD entry -- whose 'a gradient across
buckets is not a mechanism' near-miss was itself resolved by a counter-example
taken with the wrong index.

General form recorded: an index that silently means something else produces
well-formed output for the wrong object, and this project has now been bitten
twice from opposite directions with 'everything still validates' both times.

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

docs/re/data/settle-vs-rest-against-captures.txt

@@ -1,3 +1,13 @@
+# 🔴 THE TWO SPLASH ROWS BELOW ARE VOID (retracted 2026-08-30).
+# They used `screen render --build 10/11`, which takes a BUILD ORDINAL:
+# `screen list` says [10] entry 12, [11] entry 15. Those are the LOADING
+# screens. The rows scored loading-screen renders against SPLASH captures.
+# I discarded them at the time for a railed gamma fit; the real reason is
+# that they were the wrong screens, and the railing was that mismatch
+# surfacing in the only place the instrument could report it.
+# The `title` row is unaffected -- ordinal 4 is entry 4.
+# See splash-settle-window-retraction.txt.
+#
 # Does UiBuild::settle_time() itself beat rest() against the GAME?
 #
 # The port ran my PROPOSAL against captures and favoured it 3/3, but tested