adminandClaude Opus 5.5
f296f427ef
e2e 34 "the pause holds the stream" was red in CI tasks 712, 719 and 721. The pause was not at fault. Right before it the step forces a full garbage collection for its memory check. On the CI runner that held the page for seconds, and the player ran dry before the pause was even clicked: 0.02 s and 0.05 s were left ahead in 719 and 721, against about 2 s in the green CI runs and 4 s on melektaus-atx. - The worklet counts a late sample only once it arrives and reports every 4800 samples read. So the underrun from the collection showed up after the resume and looked like samples the pause had lost. - The pause is now measured first, on a stream held at least a second ahead, with half a second for the worklet to report. The collection and the renderer's size follow while the game still plays. - The check judges what the pause adds: as many skipped samples after the resume as before the pause. Tests: - e2e 34 on melektaus-atx with a 5 s busy loop on the page where the collection was: 12375 samples skipped before the pause, the same after it. The old condition, none skipped, fails on these values. The new one passes. ALL PASSED, 148 checks - Lint and Prettier on the module are clean Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>