5f3d8f86a4
did not work I set out to do for the title what worked for the splash: measure the build-in and check it against the declared keyframes. That part failed, and I am recording the failure rather than the number. It failed for two reasons, both mine. The title was reached by skipping the movie with A, which cuts to black and brings the title up on a path that may not be the normal one. And the visible rise, about 2.7 s, is a luminance curve -- which screen-transitions.md already establishes is not the fade quad's ramp. So 2.7 s neither confirms nor contradicts build 4's declared 16 -> 261, four point oh eight seconds. They are not measuring the same thing, and I have said so instead of reporting a discrepancy. What the recording did establish is worth having anyway: the title never settles. Over 22 s the mean luminance oscillates continuously, peaks at 5.6, 7.8, 10.0, 12.7, 15.2, 17.1, 19.2 and 21.3 s, mean interval 2.24 s. Marked as about 2.2 s plus or minus 0.4 rather than a precise period, because peak-picking a low-amplitude signal is coarse. The mechanism was already decoded and I did not re-derive it: build 4 declares ptloop01.rat and ptloop02.rat, and loop*.rat is a looping sprite animation rather than a composition. What is new is the period, and that it runs forever. For the port that matters -- drawing the resting pose and stopping will look wrong. Not confirmed, and flagged: that 2.2 s is the loop's OWN declared cycle. screen info prints the element's placement keyframes but not the frame count inside the .rat, and I did not open it.