Eric WagonerandClaude Fable 5.1
6e49fc9020
Engine: pit-rim exits live in one helper (pitRimExits) shared by the resolver and the automaton; chargeReach names the six-stride cap; dust sight is inDust + dustAtEnd; PushPending is exported once; the force-field counter builds its events in one list; drawUnderSlowDeath says what it draws under. Test groups are named for the rule they pin, not the revision that introduced it. Client: one smoothstep; one edgeScar per battle-scarred edge; one board-zone rule (which also seats the caption strip on phones); the compass names live in SIDE_NAMES; net.flash() is the one toast; MediaQuery replaces two hand-rolled matchMedia listeners; sprites carry their sizes as plain numbers and their CSS in one rule each; canvas helpers are formatted like the rest of the tree. Comments that told how a cel or a fallback used to look now say what it draws. The actions-over notice no longer blames a pickup when slime ended the turn. Server and ops: dataRoot() is the one data directory; headlineOf builds its deeds without a cast; the rollup and skills read the same way the code behaves. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jm2auWk6RP71CjaAb4FMoG
86 lines
4.6 KiB
Markdown
86 lines
4.6 KiB
Markdown
---
|
||
name: wizwar-pulse
|
||
description: The weekly Wiz-War operations pulse — droplet health, error and traffic signals, backup status, and who has been playing. Use when Eric asks how the server is doing, wants an ops check, or says "run the pulse".
|
||
---
|
||
|
||
# The Wiz-War ops pulse
|
||
|
||
One invocation, one screen: how the table is doing. Gather everything,
|
||
then report in five short sections. Lead with anything ALARMING (service
|
||
down, memory near the cap, failed backup, new Sentry issues); if all is
|
||
quiet, say so in one line before the details.
|
||
|
||
## Gather
|
||
|
||
1. **Box health** (one ssh to root@104.236.96.198):
|
||
- `systemctl is-active wizwar caddy` — both must be active
|
||
- `systemctl status wizwar` Memory line — the cap is 700M; worry
|
||
past ~500M steady-state
|
||
- `free -m`, `df -h /`, `uptime` — swap in heavy use, disk past
|
||
~70%, or load near 1.0 (single vCPU) are the resize triggers
|
||
- `journalctl -u wizwar --since "-7 days" | grep -ci "unhandled
|
||
protocol error"` — anything nonzero deserves a look (Sentry has
|
||
the stack traces)
|
||
2. **Sentry** (MCP connector, org `locallygrownnet`, project `wizwar`):
|
||
- `search_issues` for `is:unresolved` — new issues are the headline
|
||
- `get_monitor_details` for cron monitor slug `new-monitor` (named
|
||
wizwar-backup) — last check-in must be ok and recent; the uptime
|
||
monitor alerts on its own but note any incidents
|
||
- New-project caveat: results can lag ingest by minutes; the
|
||
connector reads fine but 403s on create operations
|
||
3. **Backups**: `tail -3 /var/log/wizwar/backup.log` (or its rotation)
|
||
for the last run, plus the cron monitor above for missed runs
|
||
4. **Trends** (`/var/lib/wizwar/rollup.jsonl`, one JSON line per UTC day
|
||
written at 00:10 by /usr/local/bin/wizwar-rollup.sh; counts only, no
|
||
addresses): the last 7 rows give requests, human vs bot addresses,
|
||
socket connects, path mix (/, /clips, /watch, /ws), external
|
||
referrers, new rooms, human seats and names, reports/replies,
|
||
and vitals (memMB, memPeakMB, diskPct, load1, protocolErrors,
|
||
serviceStarts, ledgerMB). Report day-over-day direction, not raw
|
||
rows. Its Sentry cron monitor is slug `wizwar-rollup` (a missed
|
||
check-in there means the rollup itself is broken). Re-roll a day by
|
||
hand: `wizwar-rollup.sh YYYY-MM-DD`. `campaigns` counts visitors
|
||
(one per address per day) whose link carried a tag the rollup header
|
||
names (`?ref=<name>`, a utm_source, Facebook's fbclid); referrers
|
||
alone can't attribute Reddit or BGG, which send none.
|
||
**Right now** (on request): `wizwar-visitors.sh` prints it — live
|
||
sockets, rooms touched in the last hour, and today's partial row —
|
||
see /wizwar-visitors.
|
||
5. **The table itself**:
|
||
- Room count and growth: `ls /var/lib/wizwar/rooms/*.jsonl | wc -l`
|
||
- New human names this week: the rollup rows' `humanNames` (host and
|
||
joiners alike, bots excluded) minus the regulars the visitors skill
|
||
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
|
||
distinct `client_ip`s in the last day, for the growth line
|
||
|
||
## Report
|
||
|
||
Six sections, tight: **Verdict** (one line), **Box**, **Errors &
|
||
monitors**, **Backups**, **Trends** (the week's direction from the
|
||
rollup), **The table** (games, new faces, feedback).
|
||
Numbers with their thresholds, not raw dumps. End with any recommended
|
||
action, or "nothing needs you."
|
||
|
||
## Standing knowledge
|
||
|
||
- The service restarts cleanly (ledgers replay); restarts in the journal
|
||
during deploys are normal, not incidents.
|
||
- Room memory is evicted after idle (finished 30 min, others 24 h), each
|
||
sleeper leaving a stub on disk; a boot replays only rooms whose stub is
|
||
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,
|
||
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
|
||
hits one sees "try again in an hour"; a pulse showing many refused
|
||
creates from one address is a script, not a friend.
|
||
- Restore drill (2026-09-01): a Spaces snapshot booted 56/56 rooms
|
||
clean. The path: `rclone copy spaces:kestrel-wizwar-backups/wizwar/
|
||
snapshots/<date> ...` on the droplet, then run a local server with
|
||
WIZWAR_DATA_DIR pointed at its rooms dir. Re-drill quarterly-ish.
|