re: the title's build-in measured in the guest's draw stream -- the flashes are real

The settle-time decode was confirmed only against a SETTLED frame, which shows
the end state is right and says nothing about whether the five flashes ever
happen. This runs the oracle: a draw capture armed before the title exists,
so the window contains the frames in which the screen is built.

The flashes fire in a six-frame window and are absent from all 155 other
sampled frames. `ptlogo_back2eff1` is drawn in exactly two frames at t = 54.0
against a decoded peak of t54-56; `ptlogo1` first appears at t = 42.2 against
a decoded t42. Units-per-frame was taken from the GLOW's period alone, a
different element, so the timings are not circular. The two holders are
continuous from frame 134.

The plate glow's quad carries a per-vertex colour whose alpha IS the element's
fade alpha, so the ramp is read straight out of the guest: observed range
0..80 against a decoded peak of 80, exact and unfitted; period 51.158
presented frames over 20 cycle starts. Fitting the decoded ramp gives RMS
13.16 alpha levels against 38.18 for the same ramp REVERSED -- if the shape
carried no information those would be equal, so the asymmetry is real and
correctly directed. Further controls: symmetric triangle 15.73, flat 31.13.

`ptlogo_back2eff3` was never drawn, and that is expected rather than a miss: a
2-unit flash peak is 0.85 of a presented frame, so catching one is a matter of
phase. A port drawing all five every time shows more sweep than the console.

METHOD.md gains the trap this cost: a 2D draw's identity is its vertex
geometry, not its bound texture. These sprites sample shared pages, and
matching texture dimensions produced a false negative (no flash is ever drawn)
and a false positive (the intro movie's 640x360 YUV planes read as `ptbase2`)
in the same pass.

Also records the top-level restriction on the settle window, which the port
raised and which is verified here: top-level [160,236] width 76, including the
`ptloop` leaves [269,540] width 271 -- an instant past the end of every
top-level element's timeline.

Evidence committed as a derived per-frame series, not the 7 MB raw log.

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

docs/re/METHOD.md

@@ -1059,3 +1059,24 @@ The general trap: **an aggregate computed per-element is not a state of the
 system.** Ask what instant a composite claims to depict, and check that every
 element was asked the same question. See
 [`structures/ui-settle-time.md`](structures/ui-settle-time.md).
+
+## A 2D draw's identity is its geometry, not its bound texture
+
+The title's sprites **sample large shared texture pages**, so the texture bound to
+a draw identifies a page and not an element. Matching a bound texture's dimensions
+against a decoded sprite's fails silently in both directions, and one pass here
+did both at once:
+
+* **false negative** — "none of the five flash sprites is ever drawn". They are
+  drawn; they simply never appear as their own texture.
+* **false positive** — "`ptbase2` (640×360) and `pteff04` (1280×720) are drawn in
+  frames 75–105". Those frames are the **intro movie**, whose YUV planes and
+  target happen to be 640×360 and 1280×720.
+
+Re-run against the **quad's vertex rect** in design space and every element
+appears where the disc says it should. Canary's own capture code already carries
+this warning in a comment, and the corpus had already recorded that the settled
+title binds only 1280×768 pages — both were there to be read first.
+
+The general shape: **a coincidence of size is not an identification.** Before
+matching on one attribute, ask what else in the frame shares it.