v0.1.0 — undo, the crew's reach on the board, workers on the card, and four engine bugs

Fifteen items from two playtest sessions. Three that read as drawing faults were engine
bugs: cars could be added to a train that was not being made up (50 offers in 8 games),
the make-up panel merged two trains and could couple a car to the wrong one, and an
Office upgrade silently deleted what a Modifier had added. A fourth was a sentinel
inside a coordinate's own value range — a Mainline placement travelling as row -1, which
is an ordinary district row.

Trains are now drawn the way they stand: west on the left, nose toward the way the engine
faces, on both the district card and the Division chip. Undo steps back through the game
by replaying the save without its last intent. The switching walk keeps its rejections, so
the board can say why a square is not offered. Laborers and Porters are on the card, and
the rule that a district only grows outwards is finally written down.

Versions start here: third digit for fixes, second for a feature set, 1.0 for a release.

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

README.md

@@ -10,15 +10,23 @@ train into an occupied Subdivision. Get that wrong and two trains meet at speed.
 
 ## Status
 
-Design complete, implementation just begun.
+**v0.1.0 — solitaire is playable in a browser.** The whole game runs client-side: the engine is pure,
+imports nothing outside itself, and never touches `Math.random`, so a static host is all it needs.
 
 - **Rules** — fully specified. Ten gaps in the original prototype rules found and resolved.
 - **Card faces** — every card's printed values specified.
 - **Architecture** — six documents, including a 20-component build plan.
-- **Code** — build step 1 of 12 complete: card catalogue, state model, seeded RNG.
+- **Code** — the engine, the bot, the balance harness, the replay viewer and the playable page. A
+  game can be saved, shared, replayed and stepped back through.
+- **Not built** — multiplayer (the engine runs 2–5 player games and the bot plays them, but there is
+  no server, no turn submission and no per-player view), the 22 opponent-directed cards, and real
+  audio.
 
-The MVP target is **solitaire, one Office, a fixed number of Days**, with a server talking to a
-single browser.
+Balance is *not* where it should be: the developer bot averages 1.4 Revenue against a target of 20.
+`TODO.md` says why, and says which of it is the bot and which is the deck.
+
+Versions follow the convention at the top of [`CHANGELOG.md`](CHANGELOG.md): third digit for fixes,
+second for a set of features, 1.0 for the first release that deserves the name.
 
 ## Layout