Docs: the StartOS package is the only place the game is served

The static site on the File Browser host was retired with the 0.4.9
line on 2026-09-29. README, TODO and the structure plan no longer
describe a site deploy as the release step or the zero-dependency rule
as what keeps the site a static upload.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019rwKTmug58sEsJ72AuWsEi

TODO.md

@@ -54,9 +54,11 @@ Not items. Things that are true of every change, and that have gone wrong when s
 - **Commits and tags are GPG-signed and I cannot make them.** Stage the work, write the message to
   a file, hand over a `!` command. Tags must be `git tag -s` — a bare `git tag` makes a lightweight
   tag and `git push --follow-tags` skips it *without any error*.
-- **There is one line now.** The 0.4.9 playtest line was retired on 2026-09-29 (Jesse: "no longer
-  being maintained"), so `npm run deploy:web` from this directory is the deploy. The public site
-  serves the last 0.4.9h build until that is run once from `main`.
+- **There is one line and one place the game is served.** The 0.4.9 playtest line was retired on
+  2026-09-29 (Jesse: "no longer being maintained"), and the static site on the File Browser host
+  with it: "the game is served on the StartOS service for station master." Releasing is the wrapper
+  bump and `make install`; there is no site deploy. `npm run deploy:web` stays in the repo only in
+  case a static host ever returns, and nothing depends on it.
 - **The save check is the LAST thing before the tag, not a thing done during the work.** 0.8.2
   replayed every server save, wrote "three resume, ten refuse" into its notes, and then put a card
   into the deck — and shipped with zero of thirteen resuming. Replay the server's saves against the