re: the 2.3 s pulse is the PRESS (A) plate, not the title

Closing the residual I left explicitly unidentified last iteration, and
correcting my own claim twice over in the process.

The cheap test first: is the oscillation global? No -- the bottom-right
corner is flat at sd 0.003 and uncorrelated with the whole frame. So a
per-tile amplitude map over an 8x6 grid, which localises it hard: sd 7.65
in the band x 318..954, y 560..672 at lag 2.3 s, against 0.06 on the
wordmark. That band is the PRESS (A) BUTTON plate's rest position.

Decoding ptbtn00f.rat, the plate's highlight variant, gives the pulse
itself: alpha 0x00 -> 0x06 -> 0x4a -> 0x50, held, then back down through
0x4a to 0x06 across t=6..105. A glow that fades in and out, which is
exactly what a press-start prompt does.

So "the title screen loops at 2.2 s" was wrong in both halves. The title
ART is near-static apart from the two decoded sweeps at 7.5 s and 9.5 s;
what pulses is the PLATE, and the plate is build 2, not build 4. REFUTED
carries it under my own name.

Still amber, and said so rather than rounded off: the cycle LENGTH is not
readable. The keyframe group's last block has no time -- that slot
belongs to the next group -- so the declared span is at least 105 units,
1.75 s, against a measured 2.3 s. Consistent with a final block
extending the tail. Not confirmed.

docs/re/REFUTED.md

@@ -35,6 +35,11 @@ neighbourhood, not just the line.
 
 ## Screens, classes and RTTI
 
+* "the title screen loops at ≈ 2.2 s" → **mine, and doubly wrong.** The title
+  *art* is near-static (wordmark sd 0.06); the 2.3 s pulse is the
+  **`PRESS Ⓐ BUTTON` plate**, which is a *different build* (2, not 4). Localised
+  by a per-tile amplitude map and decoded in `ptbtn00f.rat`.
+  [`ui-title-build-map.md`](ui-title-build-map.md)
 * ~~"a `.rat` leaf record's keyframes use the build's 40-byte layout" → they do
   not~~ — **withdrawn.** They do. The scan that "found nothing" required 29
   increasing times; the records hold **three**. Decoded in