Hnefatafl moves to the shared hall host

The new kit setup, its own Caddy site file and access log, and the
host's address everywhere. The old droplet forwards to hall until the
A record moves.

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

.claude/skills/hnefatafl-pulse/SKILL.md

@@ -7,7 +7,7 @@ description: The weekly Hnefatafl operations pulse — game server health, error
 
 One command on the droplet prints everything; read it as a short report.
 
-    ssh root@209.97.148.244 hnefatafl-pulse.sh
+    ssh root@159.203.115.252 hnefatafl-pulse.sh
 
 - **game server**: whether the service and Caddy are up, restarts and
   journal errors in the last seven days with the last three error lines.

.claude/skills/hnefatafl-reports/SKILL.md

@@ -7,7 +7,7 @@ description: Work the Hnefatafl reports desk — fetch players' bug reports, sho
 
 Players file reports from the Report button in a room's masthead (seated
 or from the gallery). Each lands in `/var/lib/hnefatafl/feedback.jsonl`
-on the droplet (209.97.148.244) pinned with `roomId`, `turn` (the turn
+on the droplet (159.203.115.252) pinned with `roomId`, `turn` (the turn
 being written when it was filed) and `seq` (the ledger's length then),
 enough to replay the game to the moment. Replies live in the same file
 and appear under the report in the player's hall. This desk fetches,
@@ -48,7 +48,7 @@ to hear his players' voices; never compress their words into a table.
 
 ## c) Process an unanswered report
 
-1. **Replay to the pin.** `scp root@209.97.148.244:/var/lib/hnefatafl/rooms/<roomId>.jsonl <scratchpad>/`
+1. **Replay to the pin.** `scp root@159.203.115.252:/var/lib/hnefatafl/rooms/<roomId>.jsonl <scratchpad>/`
    and replay it with the engine as `deploy/replay-ledgers.ts` does:
    `game.create(names, start.seed, start.rules, room.options)` then
    `game.resolve(state, line.inputs)` per turn line, printing the state
@@ -72,8 +72,8 @@ to hear his players' voices; never compress their words into a table.
      passing `rules` to `createGame`). Old ledgers then replay as their
      players saw them; new games get the fix.
    Either way add a test in `src/lib/game/*.test.ts` pinning the
-   corrected behaviour. Deploy with `deploy/deploy.sh 209.97.148.244`.
-5. **Reply.** `bash deploy/report-reply.sh 209.97.148.244 <reportId> <status> "text"`.
+   corrected behaviour. Deploy with `deploy/deploy.sh 159.203.115.252`.
+5. **Reply.** `bash deploy/report-reply.sh 159.203.115.252 <reportId> <status> "text"`.
    Pass the id as ONE clean argument. Write to the PLAYER: name what you
    replayed, cite the rule, and say plainly what was wrong or why nothing
    was. The desk's voice is warm and specific.

.claude/skills/hnefatafl-visitors/SKILL.md

@@ -10,7 +10,7 @@ host glancing over the hall.
 
 ## Gather
 
-    ssh root@209.97.148.244 hnefatafl-visitors.sh [YYYY-MM-DD]
+    ssh root@159.203.115.252 hnefatafl-visitors.sh [YYYY-MM-DD]
 
 Default is today, UTC; Eric is in US Eastern, so an evening at his desk
 spills into the next UTC day. Run yesterday too when the hour is early.