re: the blend mode IS on the disc -- T8aD +0x04 bit 0x02, DECODED

Reverses two of my own pages. t32-blend-mode-not-on-disc.md said the mode is not
on the disc; ui-blend-mode-measured.md classified it measured and told the port
that which field selects it was unknown. Both were honest and neither is current.

Bit 0x02 of +0x04 set means the game draws that sprite ADDITIVE
(RB_BLENDCONTROL0 = 0x01010101); clear means premultiplied alpha-over.

Fit: 35 elements over three screens, 16 set/additive and 19 clear/alpha-over,
zero errors, every label read out of the guest command stream rather than off a
render.

Control: of every bit of the first twelve header words, exactly one separates
those 35 without error. Nothing ties with it -- which is precisely what the
+0x08 = 0x8050 candidate failed.

Within-pair: ptbtn00 0x0110 alpha-over against ptbtn00f 0x0112 additive, same
screen, same bundle, adjacent draws, one bit apart. And other f variants are
bit-clear and alpha-over, so it is not 'focused variants are additive'.

Out of sample: a prediction committed at bbd85e9, before its capture, on a
different archive -- GP_OPTIONS entry 19, 3 additive of 16, falsified if any
other element drew additive. The game drew exactly po_menu_eff01/02/03 additive
and nothing else.

This revives a claim REFUTED.md killed. The refutation said blending those
sprites additively worsens every measure against the capture -- a claim about
our renderer, made while that renderer had a stale keyframe association, no leaf
geometry and no rotation. Recorded as a revival with its evidence;
check_refuted.py passes with 0 unmarked assertions.

Two other readings of the same bit stay refuted and are explicitly not revived:
'the name contains eff' and 'premultiplied storage'. Those were the bit's
meaning; this is its effect.

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

docs/re/REFUTED.md

@@ -83,8 +83,28 @@ neighbourhood, not just the line.
 * "the plate-free title capture (t ≈ 4.0 s) may be too early to be settled" →
   **mine, and refuted.** The swoosh band correlates 0.7342 at t = 4.0 s and
   0.7353 at t = 21.5 s — identical to 0.001 over 17.5 s.
-* "`T8aD +0x04` bit `0x02` selects an additive blend" → **mine, and refuted.**
-  Blending those sprites additively worsens every measure against the capture.
+* ~~"`T8aD +0x04` bit `0x02` selects an additive blend" → **mine, and refuted.**
+  Blending those sprites additively worsens every measure against the capture.~~
+  🔴 **REVIVED AND ESTABLISHED 2026-08-31 — the refutation was wrong, and it was
+  wrong in a way this corpus has a rule for.** *"Blending them additively worsens
+  every measure against the capture"* is a claim about **our renderer**, which the
+  protocol calls a hypothesis under test; at the time it had a stale keyframe
+  association, no leaf geometry and no rotation. The claim was never tested
+  against the game.
+  ✅ It is now: the blend is read per draw out of `RB_BLENDCONTROL0`, and the bit
+  partitions **35 elements over three screens with zero errors** — and of every
+  bit of the first twelve header words, **exactly one** does so, with no tie.
+  ✅ The within-pair case: `ptbtn00` `0x0110` alpha-over, `ptbtn00f` `0x0112`
+  **additive** — same screen, same bundle, adjacent draws, one bit apart.
+  ✅ And an **out-of-sample prediction committed before its capture** held on a
+  different archive: `GP_OPTIONS` entry 19 was predicted 3 additive of 16, and
+  the game drew exactly `po_menu_eff01/02/03` additive and nothing else.
+  → [`structures/ui-blend-mode-decoded.md`](structures/ui-blend-mode-decoded.md)
+  ⚠️ Two *other* readings of this same bit stay refuted, and are not revived by
+  this: "the bit means the name contains `eff`" (fails on 2 657 of 4 995 disc-wide)
+  and "the bit selects premultiplied alpha" (the flagged group violates `RGB ≤ A`
+  *more* than the unflagged one). Those were readings of the bit's **meaning**;
+  what is established here is its **effect**.
   [`ui-title-build-map.md`](ui-title-build-map.md)
 * "the title logo elements' wrong pivots (off by up to 59 px, authored against the
   other language's sprite) explain the swoosh rendering too thick" → **mine, and