Two changes, both measured, neither invented.
1. LEAF CLOCK. authored/rendering.json leaf_clock.title = {start_units 40,
rate 0.514}, from the Decoder's f6-unit8, both numbers off ONE capture. The
title's own rate is measured rather than assumed there (ptcopyright ramps
0->255 over 22 declared units across 22 frames = 1.000 units/frame), which was
the assumption their unit 4 had flagged. Supersedes their earlier 0.463, which
divided by the end of MOTION -- the declared track is stationary from t=540 to
600, so that denominator was short; 0.514 anchors on the loop wrap.
Corroborated independently: the human reported the port looks FASTER than the
game, offered as an impression. 1.0x against 0.514x is exactly twice too fast.
2. A LEAF OUTLIVES ITS PARENT. _draw skipped any element whose PARENT posed
transparent, before _draw_leaf was reached, so ptloop01 expiring at t=250 took
the sweep with it -- while this file's own decode says the leaf runs on its own
timeline and the parent's alpha is not multiplied in. The two were inconsistent
and the silent gate won. The capture settles it: the game submits the sweep
across frames 746..1913 while the parent expires at 956, so it keeps drawing
~950 frames after the parent is gone.
VERIFIED by probing the running renderer at two PRE-REGISTERED instants:
title u=400 -> leaf t=185.0, pteff03 centre 301 (predicted 301),
pteff03a centre 1169 (predicted 1168)
title u=800 -> leaf t=390.6, pteff03 centre 1124 (predicted 1124),
pteff03a centre 333 (predicted 332)
All within 1 px.
Effect at the plate's arrival (title t=236): the sweep's centre moves from 505 --
halfway across the screen -- to -36, just entering at the left edge. The human's
report is that the game's glow begins when the plate appears.
d7e4a7167e