Steady starts, fair checks: a head start behind live, a settings pane, a strip that holds still #119

Merged
cmoriarty merged 1 commit from feature/steady-starts into develop 2026-11-08 12:24:21 -05:00
Owner

Milestone 39, "Steady starts, fair checks": #114, #115 and #117, from the owner's live test on 2026-11-08 (Liverpool and the Bengals).

#115: fair checks

  • The bug: Liverpool's standby search took the one read slot every round from 15:23 to 15:38, while Falcons vs. Bengals, followed and live, got no check at all.
  • The order: a followed live game with no stream is now read before a played game's second standby.
  • Taking turns: a standby read that finds nothing owes the next round to a waiting check; the search resumes the round after with the links it hasn't tried.
  • The Now table: it plays the round order forward. next names the standby search when that is what comes, the ETAs count the reads ahead, and the queue chips are checks only, each game once.

#114: a wait strip that holds still

  • Scale: fixed at twice the late line, so the dashed line stays at mid-height.
  • Long waits: a longer wait is drawn full height with a cap mark.
  • Axis: three labels, 0, the line and the top.
  • Why 4.3 s waits passed a 4 s line without failing: the failure clock also restarts when a segment finishes downloading. The waits are now timed on that same clock (Health.quiet_longest), so a bar at the line means the check fails. The help and the line's title say so.

#117: a head start and a settings pane

  • The setting: playback.head_start, 0–30 s, default 15 (the owner's choice), changed through PUT /api/settings/playback.
    • Its starting value comes from CHANNEL_HEAD_START_SECONDS.
    • The cap is 30, not the ticket's 60, because the channel keeps 20 segments in memory.
  • A background channel nobody watches holds its clock until the head start is in hand.
    • That hold doesn't count as stalling.
    • When a viewer arrives, the clock resumes on time and the served rate counts from then.
  • A viewer's cold tune reads the source's window first. If the window holds less than the head start, the "Starting behind live" loading card plays for the shortfall before the game. The owner decided a cold tune always waits for the full head start, and the card isn't counted as trouble.
  • A first poll is never answered with an empty playlist.
  • The pane: a gear in the Admin top bar opens it.
    • The background channels move there from the flame's popover; the flame is now a readout that opens the pane.
    • Playback's "Start behind live" is a stepper in 5 s steps.
  • The buffer gauge shows level against target ("14 s / 16 s"), amber under half.
  • The lanes run with a head start of 0, so existing timings hold. The head start has its own tests.

Design notes are in openspec/changes/steady-starts/design.md.

Lanes (run locally; ci.yml is manual)

  • make test (frontend built first): 1150 passed, 1 skipped
  • npm --prefix frontend test: 245 passed (18 files)
  • make e2e: passed (click-to-play, failure, recording, replay, channel)
  • The settings pane was also checked by hand in a local run: the stepper saved 20 s and offered the way back to 15 s.

Closes #114, #115, #117

🤖 Generated with Claude Code

Milestone 39, "Steady starts, fair checks": #114, #115 and #117, from the owner's live test on 2026-11-08 (Liverpool and the Bengals). ## #115: fair checks - **The bug:** Liverpool's standby search took the one read slot every round from 15:23 to 15:38, while Falcons vs. Bengals, followed and live, got no check at all. - **The order:** a followed live game with no stream is now read before a played game's second standby. - **Taking turns:** a standby read that finds nothing owes the next round to a waiting check; the search resumes the round after with the links it hasn't tried. - **The Now table:** it plays the round order forward. `next` names the standby search when that is what comes, the ETAs count the reads ahead, and the queue chips are checks only, each game once. ## #114: a wait strip that holds still - **Scale:** fixed at twice the late line, so the dashed line stays at mid-height. - **Long waits:** a longer wait is drawn full height with a cap mark. - **Axis:** three labels, 0, the line and the top. - **Why 4.3 s waits passed a 4 s line without failing:** the failure clock also restarts when a segment finishes downloading. The waits are now timed on that same clock (`Health.quiet_longest`), so a bar at the line means the check fails. The help and the line's title say so. ## #117: a head start and a settings pane - **The setting:** `playback.head_start`, 0–30 s, default 15 (the owner's choice), changed through `PUT /api/settings/playback`. - Its starting value comes from `CHANNEL_HEAD_START_SECONDS`. - The cap is 30, not the ticket's 60, because the channel keeps 20 segments in memory. - **A background channel nobody watches** holds its clock until the head start is in hand. - That hold doesn't count as stalling. - When a viewer arrives, the clock resumes on time and the served rate counts from then. - **A viewer's cold tune** reads the source's window first. If the window holds less than the head start, the "Starting behind live" loading card plays for the shortfall before the game. The owner decided a cold tune always waits for the full head start, and the card isn't counted as trouble. - **A first poll** is never answered with an empty playlist. - **The pane:** a gear in the Admin top bar opens it. - The background channels move there from the flame's popover; the flame is now a readout that opens the pane. - Playback's "Start behind live" is a stepper in 5 s steps. - **The buffer gauge** shows level against target ("14 s / 16 s"), amber under half. - **The lanes** run with a head start of 0, so existing timings hold. The head start has its own tests. Design notes are in `openspec/changes/steady-starts/design.md`. ## Lanes (run locally; ci.yml is manual) - `make test` (frontend built first): 1150 passed, 1 skipped - `npm --prefix frontend test`: 245 passed (18 files) - `make e2e`: passed (click-to-play, failure, recording, replay, channel) - The settings pane was also checked by hand in a local run: the stepper saved 20 s and offered the way back to 15 s. Closes #114, #115, #117 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Milestone 39, from the owner's live test on 2026-11-08 (Liverpool, the
Bengals).

#115, fair checks: a watched game's standby search took the one read
slot every round, and a followed live game waited 18 minutes for its
first check. A live game with no stream now comes before a played
game's second standby, and a standby read that finds nothing owes the
next round to a waiting check. The Now table plays the round order
forward: next names the standby search when that is what comes, ETAs
count the reads ahead, and the queue chips are checks, each game once.

#114, the waits strip: a fixed scale at twice the late line, a cap
mark on longer waits, a 0 / line / top axis. The waits are timed on the
failure rule's own clock (a finished download restarts it too), so a
bar at the line means the check fails; the help says so.

#117, the head start: playback.head_start in settings.json (0-30 s,
default 15, CHANNEL_HEAD_START_SECONDS), PUT /api/settings/playback.
The depth holds it in the stream's own segments; a background channel
nobody watches holds its clock until it is in hand (not judged
stalling; the served rate counts from the viewer); a viewer's cold tune
reads the window first and plays the "Starting behind live" card for
the shortfall (not counted as trouble); a first poll is never empty.
The lanes run at 0. A gear in the Admin top bar opens a settings pane
with the background channels (moved from the flame's popover) and the
head start; the buffer gauge shows level against target.

OpenSpec change steady-starts. Lanes: make test 1150 passed (1
skipped), frontend 245 passed, make e2e passed.

Closes #114, #115, #117

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cmoriarty merged commit 73f86a30b2 into develop 2026-11-08 12:24:21 -05:00
Sign in to join this conversation.
No reviewers
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/sports-breaker!119
No description provided.