Files
hyperframes/.github
Miguel Ángel 480ac61067 test(studio): the playback gate counts on CI's Chrome and cannot miss a pause
Review findings on the playback gate:
- Ceilings are recorded on Chrome 153, the runner's browser. The script
  now stops with a clear message when it runs another Chrome major.
- Frames were read from the first renderer main thread in the trace; on
  Chrome 153 that is not the page's, so no frames came out. The thread
  producing frames is used now, and zero frames fail loudly instead of
  passing the CPU check with a NaN median.
- Play goes through Studio's Space shortcut and pause through the
  runtime's player, which both builds share, so a stopped film or a
  renamed control cannot throw before the JSON is written.
- Every timeline seek is counted, silent ones included (3 per frame on
  main), and the layer count is named for when it is read (paused).
- Rounds alternate which build goes first, and a failed base build no
  longer skips the timeline gate; playback is then counted, not timed.
2026-09-27 03:57:32 -04:00
..