v0.4.7 — the switching game: track order, the cut on your own card, and four rules

Eight play reports and one design that had been written up and not built. The
through-line is switching: what a card can hold, which end of a train a cut comes
off, which way a train meets cars standing on the line, and what the board and the
log say about all of it.

TRACK ORDER FOR STANDING CARS, AND THE CUT ON YOUR OWN CARD

Two reports turned out to be one root cause. `TrackCard.standing` claimed "in track
order (§A.3)" and had no defined orientation at all, while `CrewTray.consist` does
(nose first, relative to facing) — so every transfer between them was a conversion
nothing performed. §A.3 says what it should be: cars occupy the track "in the same
order they originally held, left-to-right". Left-to-right is west-to-east, and that
is now the defined orientation of `standing` and of an industry track through
`carsOn`. It is the board's orientation, not the train's, so it does not change when
a different train touches the card.

  - Setting out is batch-invariant. Four cars at once, four singles and two pairs
    parked three different orders, one of them physically impossible. Successive
    cuts off the same end stack up towards the engine, so the insertion point is the
    train's own place in the row.
  - Approaching a cut from either end now mirrors. `couples` is built nearest-first
    along the direction of travel and reverses onto the nose, so the farthest car met
    ends up nose-most — which is what makes a run-around worth its Move.
  - A train no longer drives through its own cut. The walk began at the neighbour of
    the start square and never read the start card, so a crew could set cars out and
    pull straight away from them. Coupling is mandatory (§A.4) and your own square is
    no exception; the cut counts against the four-car limit. Setting out off the end
    you are not leaving by still works.

`CrewTray.standingWest` records where a train stands among the cars on its card — a
train may set out off both ends on one square, so which side a cut is on is not
recoverable from the array alone.

On the board, the cut is drawn split at the train — west cars left, east cars right,
engine in the gap — and each car's tooltip says whether it stands ahead of or behind
the engine. The history says which end a cut came off, and a move's button separates
"takes your own boxcar back off this card" from cars found standing on the line.

Decided: taking your own cut back on the square you are standing on is UNDOING the
drop. It is exempt from trains 3/4's per-location freight budget, X13's "drop but not
pick up" and X22's "empties only", and it refunds the budget the drop spent.
Otherwise a legal-looking drop becomes silently one-way.

Measured, 200 paired seeds, developer bot: -0.55 revenue (t = -3.63), freight revenue
1.11 -> 0.56. That cost is the bot's, not the rule's — its trains run engine-first,
so at a stub industry it sets a car out between itself and the only way out, and the
correct play is §A.5's facing-point move, which is the cross-turn planning TODO.md
already records as out of reach of any bot. Filtering self-recoupling moves out of its
options took recoupling from 625 of 1,029 set-outs to 101 of 677, and all 101 that
remain are that case. Read the number as a bot measurement, not a balance one.

THE SUPERINTENDENT'S RULING NAMES THE TRAINS IT IS ABOUT

Reported: the Superintendent could not tell which train he was clearing. The heading
asks the question now — "may Train 6 follow Train 4 onto the same Mainline card?" —
and the trains moved to the FRONT of each button, because the button splits its label
at the first em-dash and showed only the head.

AN INDUSTRY TRACK HOLDS FOUR CARS, LIKE EVERY OTHER CARD

Reported at undo 188: "we wanted to drop two cars, but were only allowed to drop one."
An industry track was built as long as its box count, so a one-box industry had room
for one car. Box count is how much WORK an industry can hold, not how much RAIL it
has. Ordinary track was the other exception, unbounded; both are gone and every card
holds four.

THE FREIGHT AGENT MAY STAGE A LOAD BEFORE THE CAR IS THERE

§6.3 asks nothing of the industry track — the empty car belongs to §9.3's Load the
car, which is the Laborer's action. The gate now lives only there, so cargo can wait
on the dock while the car to ship it in is still being switched in. Nothing can jam:
a load in a green box is waiting, not stuck.

THE TRUCK DOCK UNLOADS, AND BRINGS NOBODY

+1 inbound, no Laborer. It printed +1 outbound and +1 Laborer, which made it a
longer-host-list copy of Forklifts. Beside Packing Sheds it now does nothing at all,
and the hand tooltip says so before it is played.

Also in this release, from the days before: Mainline card tooltips computed from the
crossing rule; an Extra starts from the Division Point its number sends it to; a
modifier's suppressed grant comes back when a Whistle Post is upgraded; the Oil
Refinery and the Grocer's Warehouse ship as well as receive, per the card reference;
and the dormant defences name the attack they answer. `.claude/` is now gitignored —
it holds Claude Code's worktrees, i.e. a second checkout of this repository.

570 tests, typecheck clean. The three published replays were re-recorded twice —
legality changed, so bot play changed. Full detail in CHANGELOG.md.

TODO.md

@@ -9,6 +9,20 @@ Ordered within each section by how much it is currently costing us.
 
 ## Next
 
+- [ ] **THE BOT CANNOT SPOT A CAR AT A STUB INDUSTRY, and the cut-ordering rules made that visible.**
+      Coupling is mandatory on your own square now (v0.4.7), so a crew that sets a car out *between
+      itself and the only way out* picks it straight back up. At a stub industry that is every
+      set-out the bot makes: its trains run engine-first with all four cars behind, so the tail cut
+      always lands on the exit side. The correct play is §A.5's **facing point** move — couple the car
+      onto the nose, shove it into the stub, set out off the nose, back away — which is the same
+      cross-turn planning already recorded as out of reach of any bot two items below.
+
+      Measured over 200 paired seeds: **-0.55 revenue** (t = -3.63) and freight revenue 1.11 → 0.56.
+      Filtering self-recoupling moves out of the bot's options took recoupling from **625 of 1,029
+      set-outs in 60 games to 101 of 677**, and all 101 that remain are this case. Nothing is broken —
+      the game models the difficulty correctly and the bot cannot yet play it — but **every revenue
+      figure in this file measured before v0.4.7 is now low by roughly half a point** and the rebalance
+      pass should not read the drop as a deck problem.
 - [ ] **WHERE THE LOCAL'S COACH STANDS WHILE ITS ENGINE WORKS (§A.4) — now hit in play, still open.**
       Trains 7/8 print "coach must remain on station track if switching", read as "the coach is never
       set out". A cut comes off an OUTER end, so a coach on one outer end with the engine on the
@@ -345,7 +359,24 @@ and what went wrong on the way are in `CHANGELOG.md`.
       are wired but dormant in solitaire; **Overpass alone has no code path at all**. The shipped
       tooltip briefly told players four working cards did nothing, which is worse than the bare label
       it replaced — `enhancements.test.ts` had passing tests for all four the whole time.
-- [x] **A modifier's grant can land on a direction its host cannot use, and nothing says so.**
+- [ ] **THE INDUSTRY TABLE STILL DISAGREES WITH THE CARD REFERENCE — two items left, Jesse's call.**
+      v0.4.7 corrected the DIRECTIONS: the Grocer's Warehouse and the Oil Refinery are `flow: 'both'`,
+      as `card-reference.md` always said, which is what let an Ice House finally give a Grocer's its
+      outbound slot. Two discrepancies remain and both are deliberate for now.
+      **(a) Base capacities.** The reference prints Grocer's 2/2 with 2 Laborers and the Refinery 2/2
+      with 3; the engine gives every industry 1 per direction it allows, Mine Tipple included. Raising
+      one alone would be a balance change rather than a correction.
+      **(b) The Freight House card.** The reference is explicit — "'Freight House' is not a card. It is
+      the collective term for a freight facility that loads *and* unloads" — and the engine deals 6
+      copies of one. Removing them is a deck-composition change worth measuring, not a quiet delete.
+- [x] **~~A modifier's grant can land on a direction its host cannot use, and nothing says so.~~
+      THE "NO BUG" VERDICT BELOW WAS WRONG, and v0.4.7 corrected it.** The reasoning was that a
+      Grocer's Warehouse is inbound-only. It is not — the card reference says "Both" — so the grant
+      was being dropped on a direction the facility should have had. Reported again in play as
+      "grocer's warehouse didn't get extra outbound slot for truck dock". The suppression machinery
+      itself was right and is kept: it still fires for a passenger Modifier beside a Whistle Post,
+      which is not a Passenger Facility — and v0.4.7 gives that grant BACK when the Office is
+      upgraded, which it never used to. Original note follows.
       Reported as "Ice House added the laborer but not the outbound slot" — **checked, and there is no
       bug**: Ice House prints +1 *outbound*, a Grocer's Warehouse is `flow: 'inbound'` so
       `allows.outbound` is false, and the capacity was raised on a direction that can never render or