0.7.6:0 — bundle Station Master v0.7.6

Submodule pinned to v0.7.6 (b4f09f0). current.ts bumped in place at
0.7.6:0 — no new version file, no migration: fixes a client-side
routing bug in the solitaire door that v0.7.5 introduced (a browser
that had ever held a multiplayer seat could not reach the new setup
screen at all), so every game in progress carries over without
exception.

Verified: npm run check clean, prettier clean, make x86 packs as
v0.7.6:0, installed on phoenix.local — logs show the empty migration
running and both games in progress (WHISTLE-4086, COAL-7370) resuming
with their same intent counts, and the served index.html confirmed to
link the solitaire door to ./play.html?solitaire.

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

README.md

@@ -13,10 +13,16 @@ Station Master is a railroad operations board game with an authoritative multipl
 solitaire needs no server and is not what this package is for. This package runs that server —
 the browser client, the lobby, and the intent/SSE API — as a single StartOS service.
 
-**Bundled version: 0.7.5.** A client-side flow change: a genuinely fresh visit to the solitaire page
-now opens a setup screen and asks for the game's options before dealing, the same question the
-multiplayer lobby has asked before a game starts since 0.6.0. No rule the server enforces changed,
-so this update carries every game in progress, on the server and in a browser, without exception.
+**Bundled version: 0.7.6.** Fixes the solitaire door 0.7.5 introduced: a browser that had ever held a
+multiplayer seat could not reach the new setup screen at all — a bare page load could not tell
+"clicked Play solitaire" apart from "reloaded mid multiplayer game", so the door lost to whatever
+game or lobby that browser last touched. The door now marks its intent explicitly (`?solitaire`), the
+same fix `?lobby` already carries for the door on the other side. Client-side only; every game in
+progress carries over.
+
+**0.7.5 was a client-side flow change**: a genuinely fresh visit to the solitaire page opens a setup
+screen and asks for the game's options before dealing, the same question the multiplayer lobby has
+asked before a game starts since 0.6.0.
 
 **0.7.4 bundled three rules corrections** off the tracker (Gitea#13, #5, #19), all of them places
 where the code and the cards disagreed.