Roadmap: Orbit 1.0 as the stability milestone
release-gate / verify (push) Successful in 15m49s
pauljd/davidson-ci: Davidson CI / quality (push) Failing after 13m4s
pauljd/davidson-ci: Davidson CI / ai-review (push) Failing after 1m48s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-13 00:07:24 +00:00
co-authored by Claude Opus 5.5
parent 20ccf6a1c1
commit 161a2ffa7f
+16
View File
@@ -269,6 +269,22 @@ The first-day baseline was healthy (docs/VPS-DEPLOYMENT.md). Paul agrees to loos
conservatively: never flood the server, and size the limits for the whole household, since the upstairs TV joins once
the living room is settled. Measure again after the scan first.
## Orbit 1.0: the stability milestone (Paul, 13 November 2026)
1.0 is about making what exists dependable, not more features. It's ready when:
- A new user can connect their media and start watching without confusion.
- Channels build reliably, whatever the library's size.
- The Director's Chair makes customisation straightforward.
- Remote navigation and accessibility behave the same everywhere.
- Orbit respects each server's limits.
- Backups, updates and recovery can be trusted.
- The TV experience feels polished in every layout.
Known gaps going in (13 November 2026): a re-filed episode still skips (films are found again); the Drive-In keeps fixed
timings; Back to TV and the new Settings untested on a box with no channels; the upstairs TV is three builds behind; the
capacity test and household-sized limits wait for the VPS's first scan.
## Future polish ideas
Paul's ideas, 1 November 2026. Not fixes and not scheduled.