Steady streaming

The batch planned 2026-10-30, after Wizards vs. Hornets froze 18 times in five minutes: one branch, one merge to develop, one deploy (when nobody is mid-game), as four OpenSpec changes.

  1. Keep pace (#56): segments downloaded in parallel, polls on a schedule, a deliberate jump to the live edge when far behind, lag and skips counted. Touches channel.py's puller.
  2. Health from the viewer's side (#57): a watchdog on the playout clock, filler even while a download is in flight, health from stalls and the served rate, and the channel's own lag fixed before any swap. Uses change 1's lag counters. Touches channel.py, trouble.py and the Admin card.
  3. Splices keep the stream's shape (#39): decided 2026-10-30, a stream of another shape is re-encoded to the channel's shape while it plays (see the issue). Touches the segment path.
  4. Who's watching (#58): each Emby and Jellyfin session on the channel, and other readers, on the card. Mostly its own module.

Changes 1, 2 and 3 all edit channel.py, so they go in that order. Change 4 can run beside change 1; its card changes land after change 2's.

No due date
100% Completed
Steady streaming, first live run: a full backlog is not a frozen source, lag alone degrades nothing, 429 means one at a time
All checks were successful
ci / Unit tests, type check, bundle (pull_request) Successful in 47s
ci / One container, e2e click-to-play inside the image (pull_request) Successful in 1m36s
#61 by cmoriarty was merged 2026-10-31 00:54:32 -04:00
Steady streaming: keep pace, judge by the viewer, one video shape, and who's watching
All checks were successful
ci / Unit tests, type check, bundle (pull_request) Successful in 47s
ci / One container, e2e click-to-play inside the image (pull_request) Successful in 1m46s
#60 by cmoriarty was merged 2026-10-31 00:38:59 -04:00