Files
station-master/.gitignore
T
Jesse.MarkowitzandClaude Opus 5 7ade60e21f v0.7.9.1 — the engine was right twice; the screen was not
Gitea#22: the Division map drew every westbound train in the wrong half of
its Mainline card. `regionOfTransit` counts from the end a train entered,
which is what the collision rules ask; the map wanted "which printed box,
left to right" and used the same number, so an eastbound train came out
right by luck and a westbound one came out mirrored. It cost a collision —
Train 3 was cleared to follow T5 and ran into TX17, which the picture had
drawn ahead of T5 rather than behind it. One mirror in `view.ts`, at the
boundary the map is drawn from; the collision rules are untouched.

Gitea#21: a second tank car would not come off at a refinery, and "Blocked
— why nothing is moving" answered by describing the refinery's green box.
The real answer was Train 3's printed rule — the Express works one freight
car per location — so the refusal was correct and the panel sent the player
to spend a Freight Agent action that could not have helped. No rule
changed. The panel now names the budget, asking the reducer's own
predicate so its words cannot drift from the rule.

Both were replayed from the saves attached to the issues and verified in
the exact position each report names. The map fix is proved by mutation:
reverting the mirror fails two tests, and making the renderer ignore the
region fails a third. Every existing region test ran eastbound, where the
mirror is the identity, which is why the bug survived them.

891 tests pass, up from 884.

Closes #21
Closes #22

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E3Qk7uresKCHksdZajXCLg
2026-09-07 11:41:23 -04:00

59 lines
2.0 KiB
Plaintext

# OS
.DS_Store
Thumbs.db
# Editors
.vscode/
.idea/
*.swp
# Dependencies / build output
#
# NO TRAILING SLASH on node_modules, deliberately. `node_modules/` matches a directory and not a
# SYMLINK of that name — so one pointing at a shared install was committed in v0.4.7, and because it
# pointed at a path that does not exist, a fresh checkout had no TypeScript: `npm run typecheck` said
# "tsc: not found" and 20 tests failed for a reason that had nothing to do with the code.
node_modules
dist/
dist-test/
build/
target/
__pycache__/
*.pyc
# Claude Code's own state — session checkpoints and the git worktrees it works in.
#
# NOT ignored until now, so `git add -A` in the repo root would have staged
# `.claude/worktrees/`: a whole second checkout of this repository, committed into itself. Nothing
# in here is a source file and none of it should travel with the package.
.claude/
# Env
.env
.env.local
# Logs
*.log
# Generated replays — ANCHORED to the repo root on purpose.
#
# Unanchored, `replay*.html` also matched `src/web/replays.html`, which is a SOURCE file: the
# website's replay viewer. It was therefore never committed, and a fresh clone was missing a page
# the build copies unconditionally. Only the throwaway files this directory collects are ignored.
/replay*.html
# Playtest saves — somebody's game, attached to a bug report.
#
# ANCHORED, and with the README exempted: the directory has to exist and say what it is for, while
# nothing that lands in it is ever committed. A save is a seed plus the moves made, it belongs to
# whoever sent it, and it goes stale the moment the rules move. `public/replays/` is the place for
# one that is worth publishing.
/playtests/*
!/playtests/README.md
# The Jitsi harness is NOT scrubbed — four of its files carry a real domain and real
# participant names (workspace AGENTS.local.md). Ignored so that a `git add -A` cannot sweep it
# into a history that would be permanently exposed if this repo is ever made public. When it is
# promoted in Phase 1, scrub it FIRST, then `git add -f tools/`.
tools/