port: place the last unused capture; its residual is oracle-to-oracle, not the port's

live-attract-title-press-a-band.png is 1279x120 and the harness could not compare
a band. Placed by sliding: y=520, a 25x drop over five pixels, and it fits at
t=236-238, the plate's own window.

Its 0.354% is not the port's error. The port reproduces the same band of
live-title-press-a EXACTLY (0.000%), and the two captures differ from each other
by 0.301% -- two thin strips, 248x5 and 206x1, the shape of a sub-pixel edge
difference. The row's job is to stay near the oracle-to-oracle gap, not reach
zero, and it says so.

I had begun writing that the attract-returned title differs from the boot title.
It is two hairlines. The connected-component breakdown stopped it.

All eight live captures are now used. The three that were idle were each blocked
by the harness, not the capture.

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

docs/port/DECISIONS.md

@@ -6104,3 +6104,60 @@ having to withdraw.
 ⚠️ Still unused: `live-attract-title-press-a-band.png`, a 1279×**120** strip
 rather than a full frame. It needs a banded comparison the harness does not do,
 so it is named here rather than quietly left out.
+
+## The last unused capture, placed — and its residual is the oracle's, not the port's
+
+`live-attract-title-press-a-band.png` was the one live capture nothing consumed.
+Following last iteration's rule — *an unused capture is a signal about the
+harness* — it turned out the same way as the previous two: nothing about the
+capture was unusable, the harness simply could not compare a **band**. It is
+1279×**120**, not a full frame.
+
+### Placing it
+
+Sliding it down the render, structural difference against the port:
+
+| y | differing |
+|---|---|
+| 300 | 51.99 % |
+| 500 | 19.61 % |
+| 515 | 9.14 % |
+| **520** | **0.354 %** |
+| 525 | 8.87 % |
+| 555 | 24.02 % |
+
+**y = 520**, a 25× drop over five pixels. Measured, not guessed. Sweeping the
+instant at that offset puts it at **t = 236–238** — the plate's own opaque
+window, the same instant the full-frame `title_plate` row fits.
+
+### 🔴 The 0.354 % is not the port's error
+
+Three comparisons separate it:
+
+| | differing |
+|---|---|
+| port's band vs `live-title-press-a`'s same band | **0.000 %** |
+| `live-title-press-a`'s band vs the attract band *(oracle vs oracle)* | **0.301 %** |
+| port's band vs the attract band | 0.354 % |
+
+The port reproduces one capture's band **exactly**. The two captures differ from
+*each other* by 0.301 %, which is nearly the whole residual.
+
+And that oracle-to-oracle difference is two thin horizontal strips — **248×5 px**
+and **206×1 px** — which is the shape of a sub-pixel edge difference or capture
+noise, not of a state difference.
+
+⚠️ I had started writing that the *attract-returned* title differs from the boot
+title, which would have been a finding about the game inferred from 0.3 % of a
+band. It is two hairlines. The connected-component breakdown is what stopped it,
+and I would not have run it if the number alone had looked small enough to
+dismiss or large enough to report — it was in the range where you have to look.
+
+So `title_band` joins the harness at 0.35 %, and its job is to **stay near the
+oracle-to-oracle gap**, not to reach zero. A row whose target is not zero has to
+say so, or the next person tunes toward it.
+
+✅ **All eight live captures in the corpus are now used.** Three were sitting idle
+and all three were blocked by the harness, not by the capture: an overlay posed at
+t=9 that drew nothing, a `--focus=` overwritten on every menu entry, and a banded
+comparison that did not exist.