v0.4.8 — the Limits bound the whole district, the nine spots really are nine, and an action points at its square

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

TODO.md

@@ -52,6 +52,14 @@ Ordered within each section by how much it is currently costing us.
       this needs re-measuring); or move the Express's freight budget into the Cargo phase, where an
       expedited train does still get a turn. **Nothing is broken** — this is a contradiction between
       two lines on one card, and the timing rule itself is behaving exactly as recorded.
+- [ ] **A DISTRICT CAN NOW ONLY WIDEN AS FAR AS ITS MAIN REACHES (v0.4.8) — worth watching in the
+      rebalance rather than acting on now.** Track stays inside the Limits at every row, so extending
+      the Running Track is the only way to buy room for sidings, and a straight laid on the sign is
+      worth more than it was. The bot barely notices — it built outside its own Limits 5 times in 100
+      games — but the bot also builds close to its Office; a human building deliberately hits this on
+      the first wide district, which is how it was reported. If territory turns out to be the real
+      constraint on freight, this is one of the two places to look (the other is the track supply,
+      below).
 - [ ] **REBALANCE, once the rules are right — deliberately deferred.** Card counts, industry counts
       and the track mix all need a pass together, and none of them should move until the rules stop
       moving. Standing distortions to account for when it happens: offices are doubled (Q12) and
@@ -623,6 +631,13 @@ target is settled and freight carries its intended share.
 - [ ] **The 5 MB replay size limit is arbitrary.** Invented, not a browser constraint. It has earned
       its place — it caught a 5.2 MB payload that turned out to be the whole grid re-serialised every
       frame — but the number itself deserves a reason.
+- [ ] **The test suite fails at random under `npm test`, and it is the runner rather than the code.**
+      `node --test test/**/*.test.ts` runs the files in parallel and three suites write and read the
+      same `dist/` — the static build, the published-replay check and "the three places a game is
+      drawn stay in step". Back-to-back full runs measured **9 failures then 0**; run one file at a
+      time and every suite passes. That is worse than a slow suite: it trains us to shrug at a red
+      run, which is exactly how a real regression gets waved through. Give the build test its own
+      output directory, or mark the trio to run serially.
 - [ ] **Curves are drawn as two straight segments meeting**, not true arcs. Fine at this size, angular
       close up.
 - [ ] **Wide boards scroll.** A 40-card district and a 13-section Division both need horizontal