re(ui): measure the paint-order hedge -- exact on 4 of 5, and bound the rest

`compose` claimed the derived paint order "reproduces both measured
orders up to ties". That sentence was never measured and was stale by
one: there are three measured orders, not two. examples/paint_order_audit.rs
checks it.

  main menu (entries 5, 8)      derived == measured   0 inverted pairs
  developer splash (11, 14)     derived == measured   0 inverted pairs
  title (entry 4)               DIFFERS               8, all same-key ties

So the claim holds and the exception is entirely ties -- but two of those
ties are total occlusions, not near-misses. The tied family is the five
ptlogo_back2eff glows (key 32899); back2eff5 is 1133x280 and FULLY
CONTAINS back2eff3 (82,824 px^2 = 100% of the smaller) and back2eff4
(152,047 px^2 = 100%). Derived paints it on top of two glows it entirely
covers; the game paints it underneath. A tie-break by declaration index
can therefore be wrong by a whole layer. The title itself is unaffected --
it has a measured order.

The port's actual exposure, per screen: title, main menu and developer
splash all use MEASURED orders; the publisher splash is derived but has
ZERO ties, so it is fully determined; EXTRAS is derived with 15 tied
pairs of which only 2 OVERLAP. Two element pairs on one screen is the
whole risk, and that is what HANDOFF now says -- not the raw 15, which
would have overstated it 7x.

Reach stated: this compares the derived order against orders measured
from the game, not an independent derivation, so where no measured order
exists only the tie exposure can be checked. Overlap uses pivot*2 as the
element size at its resting placement.

Stale comment in compose corrected. METHOD: a hedge in a code comment is
an unmeasured claim; and count the cases that can bite, not the ones that
match the pattern.

docs/re/METHOD.md

@@ -551,3 +551,16 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
   within 2 % — so the negative arrives with its own evidence that the frames were
   live. Building the cross-check into the tool costs a few lines and is what
   separates a measurement from a silence.
+* **A hedge in a code comment is an unmeasured claim.** `compose` said the
+  derived paint order "reproduces both measured orders up to ties" — a sentence
+  that sounds like a result and was neither measured nor kept current: there were
+  three measured orders by then, not two. Measuring it took one example program
+  and turned a hedge into a bounded number (exact on 4 of 5 bundles; the 5th off
+  by 8 pairs, all ties). Grep your own comments for "up to", "roughly",
+  "essentially" — each one is a claim nobody has checked.
+* **Count the cases that can actually bite, not the cases that match the
+  pattern.** `EXTRAS` has 15 tied pairs in its derived paint order, which reads
+  alarming. Only **2** of them overlap, and a tie between non-overlapping
+  elements paints identically either way. Reporting 15 would have overstated the
+  risk by 7×; the useful number is the one filtered by whether the difference can
+  reach a pixel.