re: the splash confirmed against the running game, and timed

Closing the amber I raised last iteration: the splash renders had no
framebuffer capture to diff against. Recording the boot from the moment
the window appears, at 2 fps, catches it before the movie.

Both halves match their own render at zero shift, each with the OTHER
half as a negative control: publisher frame 0.9146 against entry 10 and
0.027 against entry 11; developer frame 0.9792 against entry 11 and
-0.033 against entry 10. The EN/JP twins score 0.876 and 0.966, so the
test tells a screen from a different screen but cannot tell a pair apart,
and I have said so rather than implying it discriminates.

The recording also times the front of the boot, which Q6 and Q7 only had
from the title onward: SQUARE ENIX from about 0.5 to 4.0 s, black,
developer logos from about 5.0 to 7.5 s, black, then ADV.wmv from about
9.5 s.

One trap avoided and written into METHOD. The frames around 9.5 to 12.5 s
show SQUARE ENIX again in cyan, and read from the capture alone that is a
third logo screen. It is not -- it is the intro movie's own opening,
which the milestone-2 notes describe as white SQUARE ENIX plus cyan glow
plus red diamonds. A logo appearing twice may be two different things.

docs/re/METHOD.md

@@ -244,3 +244,8 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
   stating it "cannot be rendered at all". It renders fine under `--all`. When two
   pages disagree about whether something exists, run the tool both ways before
   believing either.
+* **A logo that appears twice may be two different things.** The boot shows
+  `SQUARE ENIX` at ~2 s and again at ~10 s; the first is the splash screen, the
+  second is the intro movie's own opening frame. Reading the capture alone gives
+  "three logo screens". Cross-check a repeat against what is *supposed* to be
+  playing at that moment before counting it as its own screen.