9d32852724
The port found ptmsg, the main menu's footer, at alpha 127.5 at that screen's settle instant. Verified: build 5's window is [44,56] = 12 units and screen render --settle already prints 'narrow -- this bundle may never settle'. Disc-wide, elements caught mid-ramp at their screen's settle instant: 25.5 % overall, 40.9 % on windows under 10 units, 45.1 % on 10-19, falling to 11.7 % and 15.0 % on wide ones. The obvious reading of that table -- narrow window means the settle pose is bad -- is REFUTED by the screens that motivated the proposal, and I nearly published it. The two splashes have an 8-unit window, narrower than the main menu's 12, and the settle pose beats rest() there by 75x and 33x. Width does not predict quality. The predictor is the port's own statement: the settle pose wins decisively where rest() lands on a transient's peak, and loses slightly where rest() is already sound and an element arrives after the window closes. And my own rest_vs_settle filter was wrong in both directions: dropping bundles under 10 units admitted the 10-19 bucket, the worst at 45.1 %, and excluded both splashes at width 8 -- the strongest evidence FOR the proposal. A threshold taken from a documented rule of thumb and applied without checking which screens it admitted and which it threw away. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
2.5 KiB
2.5 KiB