TODO: the wrapper is on 0.7.2, and the playtesters need telling their saves are dead

TODO.md

@@ -176,23 +176,25 @@ and pushed** — they were still uncommitted when the session ended.
     **Keep doing this.** Auto-closing leaves an issue with no record of which commit or which release
     answered it. The token and the API calls are in the workspace's `AGENTS.local.md`.
 
-31. **Bump the StartOS wrapper to 0.7.2.** The 0.7.1 bump is DONE — `station-master-startos` is
+31. ~~**Bump the StartOS wrapper to 0.7.2.**~~ — done 2026-08-26 (`1bfea8d`). Submodule pinned to
-    clean, on `master`, pinned to `v0.7.1` and versioned `0.7.1:0`.
+    `v0.7.2`, `current.ts` at `0.7.2:0`, release notes rewritten in all five locales, `README.md` and
+    `instructions.md` updated. No new version file and no migration. Verified: `npm run check` clean
+    and `make x86` packs as `v0.7.2:0`.
 
-    **BLOCKED ON A `v0.7.2` TAG, which does not exist yet.** `origin` carries v0.7.0 and v0.7.1 only,
+    **This is the first release that does NOT carry games in progress**, and the release notes lead
-    and the wrapper pins a TAG rather than a SHA. Jesse tags and pushes; a bare `git tag` plus
+    with it in every locale. A save is a seed plus the moves played; the deck going from 206 cards to
-    `--follow-tags` fails silently, so the tag needs pushing explicitly.
+    121 means a card id recorded under 0.7.1 refers to a different card or to none, so a save stops
+    replaying at its first `card.play`. There is nothing to migrate — those moves were made against a
+    deck that no longer exists — and it fails safe: `src/server/index.ts` refuses to resume a save the
+    rules reject, names the move it stopped at, and leaves the file untouched, so an operator can put
+    0.7.1 back on to finish a game that matters.
 
-    Then: move the submodule pin to the tag, set `startos/versions/current.ts` to **`0.7.2:0`** (a new
+32. **Tell the 0.4.9 playtesters their saves are dead, before they find out.** The same deck change
-    upstream tag resets the downstream digit — `UPDATING.md`), and write release notes in all five
+    shipped as v0.4.9h, so every save filed before it — including the ones attached to Gitea#15 and
-    locales. **No new version FILE and no migration** — `current.ts`'s `migrations.up` is empty, and
+    #17 — stops replaying at its first `card.play`, and any game a tester has in progress will be
-    a 0.7.1 save replays under 0.7.2 unchanged.
+    declined on restart. They fail safe and the files are kept, but nobody has been told. Worth a
-
+    line wherever the tester build is announced, and worth knowing when the next bug report arrives
-    `instructions.md` and `README.md` both name 0.7.1 and both need the user-visible changes from
+    with a save that will not load.
-    this release: crossing a Mainline card is regions rather than printed speeds (most trains cross
-    faster, and Fast/Slow now matters only on Hilly), the deck is the published card counts, and the
-    Division map is one row you read left to right. Remember the branch trap: the game pushes to
-    `main`, the wrapper to `master`.
 
 ---