# Does the GAME draw the sweep leaves on a SETTLED title? 2026-08-30.
# tools/re-capture/title_draw_capture.sh -> log_ui_draws, 150 frames.
# Gated on the plate pulse (glyph in [500,2500] held 12 samples); fired at 325.3 s.
# Exactly ONE emulator, verified by count through ensure_single_emulator.sh.
#
# The question came from a tension in ui-resting-pose.md: two renders one
# plateau-phase apart differ by RMSE 11.9 inside the adjudication box, while two
# captures of a (JP) title from different sessions differ by 0.32 there. I
# hypothesised the game might not draw these leaves at rest.
#
# ANSWER: IT DOES, AND THEY FREE-RUN. Two quads TALLER THAN THE SCREEN, present
# in every frame of 132, sweeping in OPPOSITE directions:
#
#   strip A  h=1134  ROT  132 appearances  x  -109 -> +518   step +6..7 px/frame
#   strip B  h=1303  ROT  112 appearances  x  +486 -> -154   step -6..7 px/frame
#
#   x over frames, strip A: 1:-109 2:-109 3:-102 4:-102 6:-90 7:-90 8:-90 9:-83
#                           10:-77 11:-70 12:-64 13:-58 ...
#   x over frames, strip B: 1:486 2:480 3:480 4:474 6:467 8:461 9:454 12:442
#                           13:435 14:429 15:422 18:410 ...
#
# ✅ THE RATE MATCHES THE DISC. The declared x track is -639..1521 = 2160 px over
# a 600-unit cycle = 3.6 px/unit, and Q1 gives 2 units per rendered frame, so
# 7.2 px/frame predicted against 6-7 measured.
#
# ⚠️ Both are flagged ROT -- rotated, which is why their axis-aligned bounding
# boxes come out ~885 and ~1300 px wide where the declared quad is 400. Consistent
# with ui-keyframe-rotation.md placing rotation in leaf records, and with
# `screen render` being axis-aligned only.
#
# 🔴 SO MY OWN HYPOTHESIS IS REFUTED by the oracle, and sylpheed-port's reading of
# their `title` curve -- that the sweep is PRESENT in a title capture -- is
# confirmed.
