The Decoder censused rest()'s dwell fallback from the file side: 2305 elements
have no plateau, 1697 of those get a visible pose, and in GP_TITLE all four
visible fires are on the splash screens this port ships. Confirmed in my export.
Refinement to their description: they named the [0:a0 15:a255 30:a212 45:a0]
shape, but palogo_gamearts_eff and palogo_seta_eff hold 255 through t=30, so
their fallback lands on the flash PEAK rather than its decay. Same defect, worse
pose.
The port ships the right frame and there is now a number for it. Publisher splash
against the committed oracle capture: timeline (shipped) RMSE 2.17 / 0.01%
differing; --pose=rest 9.05 / 0.75% -- 75x the differing area on a screen I ship.
So the rule added to verify-screen's header after the title_jp mistake
generalises, and is demonstrated against an oracle rather than argued.
What did need fixing: ScreenView logged '(transparent at rest)' for every skipped
element whatever instant it posed, so it said that about palogo_sqex_eff, whose
resting alpha is 212. That is the same rest-versus-posed-instant confusion that
cost a wrong conclusion, pre-printed in the log. It now names the instant.
Controlled both ways: timeline says 'at t=6' and skips the flash, --pose=rest
still says 'at rest' and draws it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
955f5b0c02