re: full suite green, and correcting the route I recommended last

iteration

Two loose ends, both on my own work.

The disc-gated suite finally completed: all six binaries, 131 passed,
0 failed, one pre-existing ignored. So the rest() fix and the T8adImage
flags field are fully verified rather than verified-on-three-binaries.
The reason earlier attempts produced empty logs was that the tool
timeout's SIGTERM reached the whole process group; setsid nohup survives
it, which is now a METHOD line.

And a correction that matters more. Last iteration I closed the swoosh as
undecodable from the disc and named a per-draw GPU capture as the next
route, "because it reads the actual blend state". It does not. Reading
command_processor.cc, each captured draw records primitive type, index
count, index-buffer address, VS and PS ucode hashes, the pixel shader's
texture bindings, and vertex attribute 0 of binding 0. There is no
RB_BLENDCONTROL dump.

So the route splits, and I have said so rather than leaving the wrong
version standing: the capture can test a per-draw VERTEX COLOUR today
with no code change, which would explain white-versus-pink directly, and
getting the blend mode itself needs a Canary change to dump the blend
registers. Either way it is instrumentation rather than another field.

The general lesson goes in METHOD too: validate a recommendation before
leaving it as advice. A named next step is a claim like any other, and I
made it without checking.

docs/port/HANDOFF.md

@@ -115,8 +115,10 @@ authored version can be deleted.
   capture-not-settled (the band is identical from t = 4.0 s to t = 21.5 s). The
   residual is stable and modest: band mean **+1.83**, edge-corr **0.70** vs ≈ 0.92
   frame-wide. A next attempt should use a **per-draw GPU capture** of the running
-  guest, which reads the actual blend state instead of inferring it — not another
-  field. ✅ And the plate-free capture is sound; use it.
+  guest — not another field — but ⚠️ that capture records prim/indices/shader
+  hashes/**texture bindings**/**vertex attributes** and **no blend state**, so it
+  can test a per-draw *vertex colour* today and would need a Canary change to dump
+  `RB_BLENDCONTROL`. ✅ And the plate-free capture is sound; use it.
   🔴 **Refuted:** it is *not* that our dim covers the whole frame instead of
   sitting beneath the UI — the logo reads +2.36 against a background of −0.74, so
   the paint order is being honoured.