0.7.7:0 — bundle Station Master v0.7.7

Submodule pinned to v0.7.7 (af68aac). current.ts bumped in place at
0.7.7:0 — no new version file, no migration: the change is to how the
built client is cached, not to what it does.

Every packaged build until now published ?v=nogit as its cache key (the
.s9pk Dockerfile copies the tree in without .git, so git rev-parse
fails), and serveStatic sent no Cache-Control at all — so 0.7.5's
solitaire setup screen and 0.7.6's fix to it were both installed here
correctly and neither ever reached a browser.

Verified on phoenix.local against what the server actually returns, not
just what was packed: build tag is 0.7.7-mtf7hyxc (not nogit) and the
module graph's inner imports carry the same tag; play.html is no-cache;
a ?v=-tagged module is immutable for a year; an untagged one is
no-cache. Migration 0.7.6:0 -> 0.7.7:0 ran empty and both games in
progress (WHISTLE-4086, COAL-7370) resumed with their same intent counts.

README.md records that a hard reload is NOT a sufficient check for this
class of bug — confirmed in the field on 0.7.6, where only a fresh
private window showed the new build.

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.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 —
+the 0.7.5 solitaire setup screen and its 0.7.6 fix were both installed correctly here and neither
+was ever seen. If a past update seemed to do nothing, this is why, and opening the page in a private
+window was the only way to see it. That should not be necessary again.
+
 **What changed in 0.7.6.** The **Play solitaire** door on the front page now reliably reaches
 solitaire. If this browser had ever taken a seat at a multiplayer table, the door used to lose to
 that game or lobby instead — a plain page load couldn't tell "I clicked Play solitaire" apart from