port: the title's sweeps loop, the black hold is 9 units, and one claim refuted

THREE THINGS FROM THE DECODER, one of which I am not taking.

REFUTED: "the developer splash is one composited quad, the bounding box of the
three logos". The observed quad is 525x259 at (378,155). The three logos'
bounding box is 500x421 at (390,164) -- a 259-tall quad CANNOT contain them, and
palogo_anima alone starts at y=449, thirty-five pixels below that quad's bottom
edge. The observed quad matches the union of gamearts_eff and seta_eff, 521x261
at (379,154), to about four pixels in every dimension -- and both of those are
TRANSIENTS my own census flagged, dark by t=45, so a frame containing that quad
is a build-in frame rather than the settled screen. I cannot see their draw
stream, so I sent the arithmetic rather than a verdict, and the port keeps
drawing three: I will not stop drawing an element on a claim whose stated
identification excludes that element from its own bounding box.

THE BLACK HOLD IS 9 UNITS, NOT 12. I authored 12 from Q7's luminance plateau of
0.17-0.23 s, supported by the menus' transition quad. The Decoder counted
SUBMITTED QUADS instead -- luminance cannot separate the outgoing fade's tail
from true black. Four frames with no sprite quad at all, at 2.284 units/frame
derived from the disc as its own clock, gives 9.1 units = 0.152 s (6.9-11.4).
That overlaps the luminance figure only at the top, and the true black is SHORTER
still since both boundary frames carry picture. My 12 was supported by analogy --
a different screen's quad on a different path -- and a number that fits by
analogy loses to one measured in place. verify-dwell's bound moved with it; both
screens still agree.

THE TITLE'S SWEEPS LOOP. The oracle shows the quad oscillating over its whole x
range and resetting hard, one reset in the first title dwell and two in the
second. The loop-length field could NOT have settled it, correcting a hope I had
stated: both records declare exactly their last keyframe time, slack zero, and
"loops at 600" and "runs once for 600 and stops" write the identical header.
Verified on the two sweeps' LCM, since their periods differ: 600 and 720 realign
at 3600 units, mean diff 0, against 0.438 at half that.

Scoped to the title. The menus declare the same lengths but the oracle
measurement is of the title, and my own weak evidence points the other way there
-- best match with the sweeps off-screen, three times worse mid-screen, against a
73% on-screen duty cycle if they looped. Two weak signals in opposite directions
is a reason to scope, not to pick.

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

authored/rendering.json

@@ -48,5 +48,39 @@
   "",
   "What deletes this list: a decode covering those cases, or an oracle capture",
   "of title_jp."
+ ],
+ "loop_leaf_on_screens": [
+  "title"
+ ],
+ "loop_leaf_why": [
+  "WHICH screens replay a leaf's group instead of letting it run once and park.",
+  "MEASURED on the title, UNRESOLVED on the menus, so it is scoped to the title.",
+  "",
+  "The disc gives one pass: ptloop01's leaf runs t=0..600 and ptloop02's t=0..720,",
+  "each ending parked off-screen at x=1521 / -839. The port ran them once.",
+  "",
+  "THE ORACLE SAYS THEY LOOP ON THE TITLE. Across two title dwells the sweep quad",
+  "oscillates over its whole x range and resets hard to the same start value --",
+  "one reset inside the first dwell, two inside the second. A run-once-and-park",
+  "shows one traverse and then a constant x.",
+  "",
+  "🔴 THE LOOP-LENGTH FIELD CANNOT SETTLE THIS, and I had hoped it would.",
+  "`ptloop01` declares 600 with keyframes to exactly 600; `ptloop02` declares 720",
+  "to 720. SLACK ZERO -- and 'loops at 600' and 'runs once for 600 and stops'",
+  "write the identical header. 92.3% of records on the disc are in that state, so",
+  "the field discriminates loop length only where there IS slack, as the plate's",
+  "105-in-120 had.",
+  "",
+  "⚠️ THE MENUS ARE NOT COVERED, on purpose. Both declare the same 600/720, so",
+  "nothing on the disc distinguishes them -- but the oracle measurement is of the",
+  "title, and my own weak evidence points the other way for the menu: sweeping the",
+  "phase against live-main-menu.png, the port matches best with the sweeps",
+  "OFF-SCREEN (0.061%) and three times worse mid-screen (0.183%). If they looped",
+  "with a 600-unit period the sweep is on screen for roughly 73% of the cycle, so",
+  "a capture showing none is not nothing -- but it is one capture, and 'best",
+  "match' is a weak instrument for an absence. Two weak signals in opposite",
+  "directions is a reason to scope, not to pick.",
+  "",
+  "What settles the menu: a direct capture of it, which the Decoder has offered."
  ]
 }