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

deploy/wizwar-rollup.sh

@@ -43,7 +43,7 @@ paths = collections.Counter(); status = collections.Counter(); refs = collection
 # Where a visit came from, when the link itself says so: ?ref=<name> on a
 # link Eric posted, a Facebook click's fbclid, or a utm_source.
 campaigns = collections.Counter(); seen_campaign = set()
-for f in sorted(glob.glob("/var/lib/caddy/access*.log*")):
+for f in sorted(glob.glob("/var/lib/caddy/wizwar-access*.log*")):
     if os.path.getmtime(f) < t0: continue
     opener = gzip.open if f.endswith(".gz") else open
     with opener(f, "rt", errors="ignore") as fh: