Wiz-War's host follows the hall's shared layout: its own Caddy site file, its own access log, a memory cap for a shared box

The host's Caddyfile gathers each game's site from /etc/caddy/sites/;
Wiz-War's is rendered from deploy/Caddyfile.tmpl and logs to
wizwar-access.log, which the rollup and the pulse read. The server's memory
cap drops from 700M to 350M (it runs in about 125M), so a runaway cannot
starve other games sharing the box. Applied on the live droplet with its
logs renamed in place.

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

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

@@ -57,7 +57,7 @@ quiet, say so in one line before the details.
      lists
    - Unanswered feedback count from /var/lib/wizwar/feedback.jsonl —
      if any, offer to run the reports desk (`/wizwar-reports`)
-   - Access-log pulse: `wc -l /var/lib/caddy/access.log` and a count of
+   - Access-log pulse: `wc -l /var/lib/caddy/wizwar-access.log` and a count of
      distinct `client_ip`s in the last day, for the growth line
 
 ## Report
@@ -77,7 +77,7 @@ action, or "nothing needs you."
   stale and leaves the rest asleep, so a deploy costs no memory spike.
 - Unattended-upgrades reboots the box at 09:30 UTC when a kernel patch
   requires it; a reboot there is maintenance, not an outage.
-- Caddy access logs live at /var/lib/caddy/access.log (self-rotating,
+- Caddy access logs live at /var/lib/caddy/wizwar-access.log (self-rotating,
   10MiB × 30); the systemd sandbox denies /var/log/caddy.
 - Per-address limits (2026-09-03): 12 new rooms and 6 reports per
   address per hour, in packages/server/src/ratelimit.ts. A player who