Files
OrbitTv/docs/VERIFICATION-0.99.0.md
pauljdandClaude Opus 5.5 e0d600bc3d
pauljd/davidson-ci: Davidson CI / quality (push) Failing after 1m45s
pauljd/davidson-ci: Davidson CI / ai-review (push) Failing after 1m27s
0.99.0: Ring X weeknight flagships are appointments, so they start near 18:00
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-04 01:00:29 +00:00

2.4 KiB

Orbit TV 0.99.0: Ring X weeknight flagships start on time

This is the first of the isolated editorial corrections, approved as the next task by Paul on 4 November 2026 at 00:55. The change is to scheduling only, for Ring X (401) only.

What's in it

The six weeknight blocks (Monday to Saturday, 18:00 to 23:00) are now appointments (onTime = true in RingXDayParts). This is the mechanism PPV Sunday has used since 0.94.0:

  • In the 90 minutes before 18:00, the vault programmes are picked, in their normal turn where possible, so one ends at the appointment or within its first 20 minutes.
  • Nothing is cut, no gap is left, and nothing extra is added.

Unchanged:

  • the weeknight line-ups and their presentation keys and idents
  • PPV Sunday
  • the daytime vault and Late blocks
  • equal-turns rotation with finish-together, since Ring X isn't weighted
  • every other channel

Checks before install

  • 400 unit tests pass. Lint has no errors.
  • New RingXWeeknightsTest:
    • The six weeknights are on time, with PPV Sunday still on time and once a night, and no everyday block changed.
    • On a pool with awkward episode lengths, every weeknight over two weeks starts 0 to 20 minutes after 18:00, with no gaps.
  • Four-week replay on Ring X's real pool, from box copies taken at 00:40 (docs/replays/editorial-corrections-2026-11-04.txt, EditorialCorrectionsAuditTest). It covers 19 weeknights booked after the committed plan, with every channel booking together:
Median late Worst Within 10 min Gaps
0.98.0 34 min 105 min 6 of 19 0
0.99.0 8 min 37 min 12 of 19 0

The two worst nights (Saturday 37 minutes, Monday 30 minutes) are when no vault programme in its turn fits the run-in. The grace of the existing rule then lets the night start late rather than cut anything.

  • Fingerprints (docs/replays/replay-fingerprints-0.99.0.txt): a four-week replay of all 30 channels on 0.98.0 and 0.99.0.
    • Every committed fingerprint is identical.
    • Only 401 differs.
    • The presentation replay is unchanged (83 transitions, committedKeptExactly=true), and Ring X's weeknight idents still mark their nights.

Known limits

  • Ring X's committed plan runs to about 10 November, so new bookings follow this rule from then, in line with Paul's plan for one coordinated cutover later.
  • Tested here as scheduling logic only.

Rollback

Install 0.98.0. No saved data changes.