diff --git a/TODO.md b/TODO.md index d1b0c2a..cab1f9d 100644 --- a/TODO.md +++ b/TODO.md @@ -1511,6 +1511,26 @@ What is on the screen and where. Split out of Other 2026-08-22; the rules are el Doesn't fit the above. +- [ ] **THE 0.4.9 PLAYTEST LINE IS BEHIND ON A RULES RULING, and that was checked rather than + assumed.** Recorded 2026-08-23, when Jesse asked whether any of v0.7.0 needed porting to the + `playtest` branch. Almost none of it does — that line has no lobby and no server, and the + `undo()` config fix is inert there because its `GameConfig` carries no victory dials, so + `configWith` only ever varies the house rules the save already restores. + + **But one v0.5.0 ruling is a CODE difference the testers do not have.** §A.4, the Local's + coach: `main`'s `apply.ts` reads `if (dropRules.coachStaysOnStationTrack && cut.some(coach) && + !atOffice)`, and `playtest`'s is the same line **without `&& !atOffice`** — so on that build a + coach still may not be set out at the Office. The other two questions the 0.4.9 README calls + open are documentation-only there (Poling is already at 0 copies; Heavy Grade behaves + identically and even deals the Mainline deck without replacement, so the correction applies + word for word). + + **Jesse's call, 2026-08-23: do not port it now.** A settled rules change is not a playtest bug + fix, and pushing one into the build people are mid-playtest on would invalidate the feedback + that build exists to collect. Recorded so the divergence is a decision rather than a surprise — + and so the 0.4.9 README is not "corrected" to match `main`'s wording, which would then describe + behaviour that build does not have. + - [ ] **Documentation generated from the implementation, not written alongside it.** Raised by Jesse 2026-08-22, immediately after Gitea#7 changed the coach counts on four train cards and the answer to "where do we keep track of that?" turned out to be **five places of three different