v0.8.2 — every district opens on a Depot, and the docs are pages now

A second-digit bump for a playtest read back against the save file. Nine questions
were asked of one three-Day game; three were bugs, three were the rules working
and undocumented, three were decisions. Every save on the test server was replayed
against this build BEFORE release, which is how the cost of each rule was known
before it was chosen rather than discovered after.

EVERY DISTRICT OPENS ON A DEPOT. A Whistle Post has one A/D track and is not a
Passenger Facility, so the opening of every game was spent unable to work a
passenger and one arrival away from a collision. Two A/D tracks and passengers
from Stage 1 now; "Players start with Whistle Posts, not Depots" is the harder
game, set when the game is created. The deck follows the choice — starting on
Depots the four Depot upgrade cards are left out, because an upgrade must be to
the next tier and a Depot card at a table of Depots is a dead draw. How much
easier it is showed up as a test failure rather than an argument: the cue-coverage
pool needed widening from 24 seeded games to 60 before it held one collision.

NO SAVE WAS STRANDED BY IT, which took care. This is the one house rule that
changes how a game is DEALT rather than how it plays, so replaying a save under
the wrong opening is a different railroad from intent one — silently, with no
error. `withSavedOpening` fills it on the replay paths ONLY. Putting it in the
resolver instead made a fresh Cutthroat game deal Whistle Posts and read as
Custom, which is how the distinction was found.

THREE BUGS, ALL REPORTED FROM ONE GAME AND ALL CONFIRMED ON ITS SAVE.

An Office held TWO TRAINS ON ONE A/D TRACK. The capacity test passed with nothing
standing, the train the Interlocking had been holding at the Limits was moved into
the free slot, and the arriving train was pushed in after it without anyone asking
again whether there was room — so the collision §8.3 calls for never happened. The
held train keeps priority; the newcomer now takes the consequence it would have
met had the held train arrived first.

THE HISTORY FROZE, permanently, and the log cap was not really the cause. Each
seat's "what have I sent you" bookmark was an INDEX into an array the game trims,
so once a seat's bookmark reached the limit the slice returned nothing for the
rest of the game — at a different moment per seat, because each holds its own.
That game's log ended at exactly the cap. Lines carry a sequence number now, which
survives trimming; proven by pushing twice the cap through a simulated seat.

§8.1 ASKED THE WRONG QUESTION TWICE. "Trains may pass" returned `clear` before the
Subdivision was looked at, so a train entering a Double Track was released however
busy the rest of it was — that, not anything about Control Points, is what let
Train 8 out with no ruling. And a train standing at an Office was invisible to the
scan, so one about to re-enter the very Subdivision being entered counted for
nothing. Capacity is the test, not presence: a Depot with a track free is not in
the way; a Whistle Post with its one track taken is.

THINGS THAT HAPPENED SILENTLY NOW SAY SO — a train held against a facing one, a
train released from the Limits (a side effect of somebody else's arrival, so it
simply appeared at the Office), and the train an Interlocking is holding, whose
explanatory tooltip has existed since #99 with NO renderer ever reading the flag.

WHERE A MOVE IS REFUSED, AND WHY. `exploreMoves` decides where the rails go and the
pick-up restrictions are enforced afterwards in `check`, so a square the rails
reached and the card forbade was reachable, un-offered, and absent from the block
list with nothing said. Those squares are blocked with the rule that blocks them
now, and the reasons are got by ASKING `check` rather than re-deriving: a second
implementation of the rules is exactly the failure the block list exists to avoid.
A train may also always recover its own caboose — X13 prints "may drop but not
pick up anything", and a train needs its caboose to be made up, so one that parted
with it could never legally leave again.

RULES DECIDED IN SEPTEMBER AND APPLIED HERE. A Modifier must sit square against its
host, no diagonals. A passenger Modifier may not be played at a Whistle Post. Both
were built, measured, held back for a fortnight so a playtest could finish, and
applied now. A Second Section costs its card: `SECOND_SECTION` was declared in
content.ts and never dealt, so the action was free and the bot ordered 26
accidental ones in a measured round. The card is dealt and spent — gating on a card
the deck never holds would have deleted the mechanic rather than fixed it.

THE DOCUMENTATION IS A SET OF PAGES, not five text files served as text/plain — a
card reference is mostly tables, and as plain text a table is rows of pipes.
Markdown is still the one copy; the build renders it, and publishes the .md beside
each page. No Markdown library: this project has no runtime dependencies and one
would be a poor first. The pages add what Markdown cannot carry without drifting —
a nav across the set, a contents list built from the headings actually rendered,
an anchor on every heading, a 70-character measure, and tables that are tables.
They print as ink on paper.

The references caught up with the rules, checked rather than assumed: two
statements had gone from stale to misleading (the Quickstart told a new player to
"get a Depot down as soon as one appears"), and four rules nobody could look up
are written down — the Office tier table, §8.1 in practice, what the Circus Train
pays for, and that a Realignment can be a card with no legal target.

Adding one card to the deck reshuffles every seeded deal, which broke five
fixtures. Each was a seed meaning "a game like this" — TODO #84, exactly — so
seeds moved and pools widened rather than assertions weakening, and the clearance
fixture pins its terrain the way `enhancements.test.ts` already does. The three
published replays were re-recorded.

Closes TODO #40, #42a, #108, #109 and #110.

1046 fast tests and 35 sim tests pass.

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

TODO.md

@@ -24,6 +24,29 @@ at all. One item per place now.
 
 Not items. Things that are true of every change, and that have gone wrong when skipped.
 
+- **Update the documentation set in the same change.** `docs/quickstart.md`, `rules.md`,
+  `home-deck.md`, `mainline-deck.md` and `components.md` describe the game as built, and every
+  release restamps them — `**Version x.y.z** · date` is the second line of each. **The wrapper's
+  `instructions.md` is part of the set**: it is what a StartOS operator reads, so a change to how
+  the service is set up, run or recovered belongs there in the same commit. If a change alters what
+  a player does, sees or may rely on, the affected document changes with it. Four rules govern what
+  goes in them:
+  - **Version at the top**, before anything else on the page.
+  - **No history and no rationale.** No "this used to", no "corrected in v0.8.x", no ruling dates,
+    no TODO numbers. The documents say what the rules ARE. The reasoning belongs in `CHANGELOG.md`
+    and the argument in this file.
+  - **`instructions.md` is a manual, not a changelog.** It accumulated twenty "What changed in …"
+    blocks — 380 of its 469 lines — before they were deleted in 0.8.2. What changed in a release
+    goes in the wrapper's `releaseNotes`, which is what StartOS actually shows on update; the
+    instructions say how to run the service as it is now.
+  - **Card tables are generated, never typed.** `npm run build:cards` writes them into `home-deck.md`
+    and `mainline-deck.md` between `<!-- BEGIN CARDS: … -->` markers, and
+    `test/card-reference.test.ts` fails if a checked-in table disagrees with `content.ts`.
+  - **The Markdown is the source; the pages are built.** `scripts/build-web.ts` renders each
+    document to `<name>.html` through `scripts/markdown.ts`. Never edit a published page — and if a
+    document needs a construct the renderer does not cover, extend the renderer and test it rather
+    than writing HTML into the Markdown.
+
 - **Ask Jesse what the version bump should be.** Third digit is a bug fix, second is a new set of
   features, 1.0 is the first release worth the name — but which one a batch deserves is a judgment
   about how finished it feels, and it is his. The number lives only in `package.json`;
@@ -214,14 +237,13 @@ right — most of this release's defects were legible-but-wrong rather than brok
       laptop, are unanswered. **Needs a `days: 1` game — the timetable does not run out in five
       Days, so extended play fired in 0/10 measured games.** See **Reference · #35**.
 
-- [ ] **#42a** — **Nobody has clicked through the solitaire setup screen's own fields** and confirmed
-      the dealt game matches what was chosen. It took three attempts to become reachable at all —
-      reachable is not the same as correct. See **Reference · #42a**.
+- [x] **#42a** — **CONFIRMED at a table, 2026-09-23.** The solitaire setup screen's own fields were
+      clicked through and the dealt game matched what was chosen.
 
-- [ ] **#40** — **An older save may not replay, and players are not told so anywhere they will see
-      it.** Not a v0.7.4 fact and not a bug: a save is re-played through the current rules, so any
-      narrowing of what is legal can stop one. The rule is written down now (`README.md` § Design
-      notes); what is still owed is a line **wherever a build is announced**. See **Reference · #40**.
+- [x] **#40** — **DONE, 2026-09-23.** One sentence, in the four places a player meets a save: the
+      Quickstart's reporting section, a Rules FAQ entry ("Will an old save still replay?"), the
+      replay viewer's own page, and a tooltip on the **replays** link in the game — which had no
+      tooltip at all before. Also in the package's `instructions.md`.
 
 ---
 
@@ -424,7 +446,9 @@ need RAR or Jesse rather than code.**
       to back" depends on which way the train points and the board has reversed east-facing consists
       since v0.8.0. Each says `MADE UP, ready to leave` or `HELD at the Office: <why>`.
 
-- [ ] **#108** — **The coach ratchet: every coach ends up in the Classification Yard and never comes
+- [x] **#108** — **RULED AND CLOSED, 2026-09-23.** It stands: further table evidence supports
+      it, and part of the mid-game is players deliberately adding cars to clear the Division Yard so
+      the Classification refresh can happen. Originally: **The coach ratchet: every coach ends up in the Classification Yard and never comes
       back.** RULED 2026-09-17 — *the rule stands, the game says so loudly* — and recorded here
       because the ruling was made on one game's evidence and the balance question behind it is open.
 
@@ -582,28 +606,6 @@ What the project says about itself, and what it ships alongside the code.
 - [ ] **#88** — `card-reference.md`'s industry table may still be stale beyond Grocer's Warehouse and
       the Oil Refinery. See **Reference · #88**.
 
-- [ ] **#109** — **Render the published references instead of serving them as plain text.**
-      v0.8.0.17 publishes all five documents plus `rules/as-built.md`, links them from the splash
-      page and from the This Game card inside a running game, and serves them as `text/plain` — so a
-      tester reads their tables as rows of pipes and their links do not click. That was the
-      deliberate short version, to get the references in front of testers for this round rather than
-      leave them without any.
-
-      **Now SIX documents rather than one**, which raises the value and the cost together: the
-      Quickstart's §8 is a table of links, and a reader following one lands on another wall of
-      pipes.
-
-      **Copy the document, do not re-write it.** A hand-written HTML twin drifts from the Markdown on
-      the first edit, which is the whole argument of #15a. The step is a small Markdown-to-HTML
-      converter in `scripts/build-web.ts` writing `quickstart.html` beside the game, styled like the
-      splash page — headings, lists, tables, links and code spans are the whole of what the guide
-      uses. The `.md` MIME entry in `src/server/http.ts` and the two assertions in
-      `test/web.test.ts` (`the Quickstart guide reaches the site`) move to the rendered file with it.
-
-      **Cost:** an afternoon, most of it in the converter's table and list handling. No dependency —
-      a Markdown library would be the only runtime dependency this project has, and the guide uses a
-      small enough subset that it is not worth becoming the first.
-
 ---
 
 ## Reference — measurements, rulings and rejected approaches