Verified by killing rojo and confirming the guard restored it with 34872
owned by 'rojo'. Guard refuses to start if the port is held by anything
else (sshd tunnel) rather than masking that bug.
Two real failures diagnosed 2026-08-06:
- a leftover 'ssh -N -R 34872' reverse tunnel made port 34872 answer as sshd
while serving the LINUX tree; /api/rojo looked healthy the whole time
- ServerPackages is gitignored, so the windows clone had no wally deps and
rojo exited on startup, which presents as 'rojo will not connect'
CLAUDE.md covers tool operation; this covers what the game IS, where it
sits in the roadmap, and where reference assets actually live.
Also fixes a stale NAS path in README (RX-7 reference dir is
001-original-images/001-1993-Mazda-RX-7, not a top-level spaced name).