More bug fixes. Show the timetable, and stop the arrival message contradicting itself. Fixed division point in labels. And highlighted discard as targets.

src/web/game.ts

@@ -91,6 +91,14 @@ export type Game = {
    * would be guesswork from a rendered frame.
    */
   cues: string[];
+  /**
+   * The timetable slot the last batch of events filled, or null.
+   *
+   * Playing a train card rolls 1D12 for a Stage and the answer landed nowhere the player could see.
+   * Carrying the slot lets the timetable flash the one that just changed — the roll becomes
+   * something you watch land rather than something you are told about afterwards.
+   */
+  scheduled: number | null;
 };
 
 /** How each intent kind is introduced in the action list, in the order they should appear. */
@@ -125,7 +133,7 @@ export const SOLO_PLAYER = 'Solitaire';
 
 export function newGame(seed: number, config: GameConfig = SOLO_CONFIG): Game {
   const state = createGame({ id: `web-${seed}`, seed, config, playerNames: [SOLO_PLAYER] });
-  const game: Game = { state, seed, history: [], log: [], mustPlayCard: false, cues: [] };
+  const game: Game = { state, seed, history: [], log: [], mustPlayCard: false, cues: [], scheduled: null };
   // A history that opens mid-Stage reads as though something was missed. Say what the game IS
   // first, then let the clock take over.
   game.log.push({ text: 'Game Begins', tone: 'start' });
@@ -603,6 +611,9 @@ function record(game: Game, events: GameEvent[], actor: PlayerIndex | null = nul
 
   }
   game.cues.push(...cuesFor(events));
+  // Which timetable slot the die just filled, so the panel can flash it. Last one wins: a batch can
+  // schedule more than one train, and the most recent is the one the eye should be sent to.
+  for (const e of events) if (e.type === 'trainScheduled') game.scheduled = e.slot;
   // Keep the log bounded; the full history lives in `history` and can be replayed.
   if (game.log.length > 400) game.log.splice(0, game.log.length - 400);
 }