TODO: the release follow-ups, and the wrapper bump is waiting on a v0.7.2 tag

TODO.md

@@ -164,25 +164,35 @@ pass as 19-21 and 24 above, and all three are answered by Gitea#18 rather than f
 Queued 2026-08-25, from releasing 0.7.1 / 0.4.9g. **Both are blocked on the two commits being made
 and pushed** — they were still uncommitted when the session ended.
 
-30. **Close the Gitea issues by hand, each with a comment naming the commit that fixed it.** Raised
-    by Jesse 2026-08-25. `Closes #<n>` is in the main commit message and will auto-close #2, #8, #9
-    and #10 when it reaches the default branch, but auto-closing leaves the issue with no record of
-    WHICH commit or WHICH release answered it — and #9 supersedes #6, which nothing on #6 will ever
-    say. So each issue wants a comment of its own: the commit SHA on both lines, the version each
-    shipped in (0.7.1 and 0.4.9g), and for #2 and #9 the ruling that decided it, since neither was
-    fixed the way the report implies. #6 wants a comment too, pointing at #9. The token and the API
-    calls are in the workspace's `AGENTS.local.md`.
+30. ~~**Close the Gitea issues by hand, each with a comment naming the commit that fixed it.**~~ —
+    done, and done again for v0.7.2 / v0.4.9h (2026-08-26). #2, #6, #8, #9 and #10 carry their
+    comments from the v0.7.1 release, including the pointer on #6 saying #9 superseded it. #3, #14,
+    #15, #17 and #18 now carry theirs, each naming `2ab25e3` and `e9683cc` and the version each
+    shipped in — and, where the fix was not what the report implied, the ruling that decided it:
+    #15 was REVERSED on review (the placement is legal; what was confirmed is that no train crosses
+    the gap), and #14's comment lists the ten unbuilt cards that are held out, so they do not vanish
+    along with the issue.
 
-31. **Bump the StartOS wrapper to 0.7.1.** `station-master-startos` is clean, on `master`, pinned to
-    `v0.7.0` and versioned `0.7.0:3`. Once v0.7.1 is tagged: move the submodule pin to the tag, set
-    `startos/versions/current.ts` to **`0.7.1:0`** (a new upstream tag resets the downstream digit —
-    `UPDATING.md`), and write release notes in all five locales. **No new version FILE and no
-    migration** — `current.ts`'s `migrations.up` is empty, so nothing is carried from 0.7.0, and a
-    0.7.0 save replays under 0.7.1 unchanged (its intents cannot contain a Timetabled discard,
-    because that was illegal when they were recorded). `instructions.md` and `README.md` both name
-    0.7.0 and both need the three user-visible changes: the Day-end dialog, the Timetabled discard
-    and its New Game checkbox, and the reasons a blocked platform now gives. Remember the branch
-    trap: the game pushes to `main`, the wrapper to `master`.
+    **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
+    clean, on `master`, pinned to `v0.7.1` and versioned `0.7.1:0`.
+
+    **BLOCKED ON A `v0.7.2` TAG, which does not exist yet.** `origin` carries v0.7.0 and v0.7.1 only,
+    and the wrapper pins a TAG rather than a SHA. Jesse tags and pushes; a bare `git tag` plus
+    `--follow-tags` fails silently, so the tag needs pushing explicitly.
+
+    Then: move the submodule pin to the tag, set `startos/versions/current.ts` to **`0.7.2:0`** (a new
+    upstream tag resets the downstream digit — `UPDATING.md`), and write release notes in all five
+    locales. **No new version FILE and no migration** — `current.ts`'s `migrations.up` is empty, and
+    a 0.7.1 save replays under 0.7.2 unchanged.
+
+    `instructions.md` and `README.md` both name 0.7.1 and both need the user-visible changes from
+    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`.
 
 ---