The table, the hall, the rules and the guide: three boards drawn in Gygax's colours, a drake to play, the article in full, and the pages that walk a player in

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CCLa2PaEeCj8njQZSWGqHx

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

@@ -7,7 +7,7 @@ description: The weekly Wyrm operations pulse — game server health, errors, th
 
 One command on the droplet prints everything; read it as a short report.
 
-    ssh root@__IP__ wyrm-pulse.sh
+    ssh root@159.203.115.252 wyrm-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/wyrm-reports/SKILL.md

@@ -7,7 +7,7 @@ description: Work the Wyrm reports desk — fetch players' bug reports, show the
 
 Players file reports from the Report button in a room's masthead (seated
 or from the gallery). Each lands in `/var/lib/wyrm/feedback.jsonl`
-on the droplet (__IP__) 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@__IP__:/var/lib/wyrm/rooms/<roomId>.jsonl <scratchpad>/`
+1. **Replay to the pin.** `scp root@159.203.115.252:/var/lib/wyrm/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 __IP__`.
-5. **Reply.** `bash deploy/report-reply.sh __IP__ <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/wyrm-visitors/SKILL.md

@@ -10,7 +10,7 @@ host glancing over the hall.
 
 ## Gather
 
-    ssh root@__IP__ wyrm-visitors.sh [YYYY-MM-DD]
+    ssh root@159.203.115.252 wyrm-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.