0.7.8:0 — bundle Station Master v0.7.8

Submodule pinned to v0.7.8 (193800a). current.ts bumped in place at
0.7.8:0 — no new version file, no migration: the change is which screen
a solitaire visit lands on, plus the splash footer's wording. Both are
client-side, and a solitaire save lives in the browser rather than on
this server, so nothing here is involved either way.

0.7.5 skipped the setup screen whenever the browser held a save, and any
browser that has ever played solitaire holds one — so the door could
never reach the screen again. The door outranks a save now; a bare
reload still resumes; #ss-resume keeps the game in progress reachable
since Deal clears it.

Verified on phoenix.local against what the server returns: the door
carries ?solitaire, play.html carries #ss-resume and #ss-saved-note, the
footer names both ways to play, and the build tag is 0.7.8-mtfaojtv.
Migration 0.7.7:0 -> 0.7.8:0 ran empty and both multiplayer games in
progress (WHISTLE-4086, COAL-7370) resumed with their same intent counts.

The behaviour itself is covered by four new tests upstream that
reproduce the reported state (door + existing save) rather than by
reading served output — which is what the two previous attempts did, and
why they were reported as verified while still being wrong.

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

instructions.md

@@ -35,6 +35,13 @@ watches the table — there is nothing else to open.
 Solitaire runs entirely in your own browser and needs nothing from the server, so it works here
 exactly as it does on the public Station Master site.
 
+**What changed in 0.7.8.** The solitaire setup screen now appears for everyone. It was being skipped
+whenever your browser held a saved solitaire game — and any browser that has ever played holds one —
+so most players never saw it at all. Clicking **Play solitaire** now always asks how you want the
+game set up. **Your game in progress is safe:** the screen offers **Continue saved game**, and says
+plainly that dealing a new one replaces it. Simply reopening the page still picks up where you left
+off, exactly as before. The homepage footer now names both ways to play, too.
+
 **What changed in 0.7.7.** Updates to this service now actually reach your browser. Until now every
 release published its files under the same cache name and the server never told browsers when to
 look again, so returning players kept running whatever version their browser had already stored —