Wiz-War lives on the shared hall host: its scripts, skills and docs name it

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

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

@@ -6,7 +6,7 @@ description: Work the Wiz-War player-feedback desk — fetch new bug reports, sh
 # The Wiz-War reports desk
 
 Players file surprise reports from the in-game 🐞 button. Each lands in
-`/var/lib/wizwar/feedback.jsonl` on the droplet (104.236.96.198) pinned
+`/var/lib/wizwar/feedback.jsonl` on the droplet (159.203.115.252) pinned
 with `roomId`, `seq`, `round`, and `deckRev` — enough to replay the game
 to the exact moment. Replies live in the same file and appear under the
 report in the player's lobby ledger. This desk fetches, displays, and
@@ -32,7 +32,7 @@ One JSONL line per entry:
   screenshot; the file is `/var/lib/wizwar/feedback-images/<id>.<ext>`.
   `scp` it to the scratchpad and Read it: it is usually the whole story.
 
-Fetch: `ssh root@104.236.96.198 'cat /var/lib/wizwar/feedback.jsonl'`
+Fetch: `ssh root@159.203.115.252 'cat /var/lib/wizwar/feedback.jsonl'`
 
 ## a) Fetch and b) display
 
@@ -49,7 +49,7 @@ players' voices — never compress their words, or your replies, into a table.
 For each unanswered report, in order:
 
 1. **Replay to the pin.** Fetch the ledger
-   (`scp root@104.236.96.198:/var/lib/wizwar/rooms/<roomId>.jsonl <scratchpad>/`)
+   (`scp root@159.203.115.252:/var/lib/wizwar/rooms/<roomId>.jsonl <scratchpad>/`)
    and replay it to the report's `seq` with the engine
    (`createGame` + `applyCommand` per command line, printing the events
    around the pinned moment). CRITICAL replay details:
@@ -80,10 +80,10 @@ For each unanswered report, in order:
    - Chronicle-only changes (event names, humanize lines) ship ungated.
    - Before deploying: full engine suite passes AND
      `bash deploy/verify-ledgers.sh` replays every production ledger
-     clean. Deploy with `bash deploy/deploy.sh 104.236.96.198` from the
+     clean. Deploy with `bash deploy/deploy.sh 159.203.115.252` from the
      repo root. The deploy restarts the server; live games survive.
 5. **Reply.** From the repo root:
-   `bash deploy/feedback-reply.sh 104.236.96.198 <reportId> <status> "text"`
+   `bash deploy/feedback-reply.sh 159.203.115.252 <reportId> <status> "text"`
    - `<reportId>` is the report's `id`, or its `at` timestamp for
      legacy reports. Pass it as ONE clean argument — a stray newline in
      the id silently orphans the reply (it happened; the bad line had