OrbitTv/VERIFICATION-0.39.0.md

Orbit TV 0.39.0 verification

Smart Channels Phase A, Paradox only. Full report for Paul: https://claude.ai/artifact/N5QipynfmMu3uUtaXouaAg

Changed

• A shared scheduling engine (ChannelSchedule.kt) with channel configuration. Paradox is the only channel configured.
• Whole series read in bounded pages, cached. Seven days planned ahead, appended to and never rewritten.
• Three versioned files in no_backup/schedule: episodes, schedule and aired progress. Atomic writes, validation, last good copy. catalogue.db isn't touched.
• The channel falls back to its existing loop outside its plan, or when switched off.
• The guide reaches seven days ahead, for every channel.

Checked on the box, 2 November 2026

• 688 episodes read in 12 requests and 3.07 s. First plan 276 ms, 231 programmes. Extension from 5.5 to 7 days 585 ms, 0 requests. 78,119 bytes stored, plus backup copies.
• Tuning: 338 to 512 ms for the provider, then 1.4 to 2.3 s to ready, 4 timed tunes. One earlier tune was still waiting at 25 s, not reproduced, cause unknown.
• Schedule file fingerprint unchanged across restarts. catalogue.db fingerprint unchanged (b630828b...).
• Extension kept every committed programme and continued the sequence.
• Damaged and deleted schedule files recovered from the saved place with no provider requests.
• An unavailable programme showed a message, and the next programme played by itself.
• The guide reached Mon 9 Nov 01:57.

Unit tests

• assembleDebug, testDebugUnitTest and lintDebug pass; 174 tests, 0 failures, 23 new.

Not checked

• Join-in-progress on Paradox by eye. A unit test covers it, and the seek code is unchanged.
• Emby offline on the box, and a daylight saving change on the box. Unit tests cover keeping a plan with no provider.
• A show finishing and restarting on air. Unit test only.
• Several days of real running, including hourly top-ups.
• Memory has no pre-engine baseline.