The keeper can bring back a seat a browser lost: a reseat line on the ledger gives that wizard's seat a new token and the old one opens nothing after, wizwar-reseat.sh on the host asks for it through a keeper door that listens on the loopback alone and opens only to a key the deploy makes once, and the link it prints carries the seat in the fragment, which leaves the address bar at once and is kept only when no seat held in this browser still opens and the server takes it; a gallery watching a game in play is told both ways back, the front page asks before forgetting a game not yet finished, and the server's tests now run with the rest

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MbtUPJ24P6vc6tE1x6RS3m

deploy/README.md

@@ -52,4 +52,15 @@ longer replays becomes unreachable after restart, so this is not optional.
   `setup-droplet.sh` does NOT install it — on a fresh droplet, copy the
   script, configure rclone (the script refuses to run while the config still
   holds its CHANGE_ME placeholder), and add the cron entry by hand.
+- A player whose browser lost their seat (Safari's seven days, an app's own
+  browser, cleared data) writes to the keeper. On the droplet,
+  `wizwar-reseat.sh ROOM` lists who sits at the table and when each last
+  moved or spoke; `wizwar-reseat.sh ROOM NAME` gives that wizard's seat a new
+  token and prints a link carrying it in the fragment. The old token opens
+  nothing after. The script answers through the game server's keeper door,
+  a listener of its own on 127.0.0.1:9787 that Caddy never reaches, which
+  opens only to the key in /etc/wizwar/keeper.key (root and the wizwar user
+  alone can read it, so the other services on the host cannot use the door).
+  The first deploy makes the key, and every deploy installs the script at
+  /usr/local/bin.
 - One-off backup: `scp -r root@<ip>:/var/lib/wizwar/rooms ./rooms-backup`