Generate forward and reverse record tables from authoritative AXFRs
while preserving handwritten Markdown outside per-zone markers. Run the
generator in CI and link the reference from the relevant docs.
Place physical hardware inventories and VPS resource allocations near
the top of each box page, while leaving broader platform details in
their topical sections.
Document the home network's out-of-band devices that aren't managed by
this flake:
- `home-aps.md` — the two dumb APs (`vibe` MikroTik cAP ax, `wave` Cudy
AX3000 on OpenWrt): shared VLAN-trunk design (`hi`/`lo` are both
trusted client VLANs differing only by MTU), SSIDs, per-AP management
addressing, roaming (802.11k/v), and the OpenWrt flash + on-device
config for `wave` (incl. the `mtk_eth_soc` eth0 2026-byte MTU cap that
keeps it off the jumbo `hi` VLAN, wpad-mbedtls swap, HE160).
- `home-switches.md` — the hand-configured switches (`jim`/`dave`
MikroTik, `brian` UniFi) topology, VLAN map, and ONT/WAN path.
Add the `home-aps.md` pointer to AGENTS.md alongside the existing
switches reference.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Note `CLAUDE.md` is a symlink to `AGENTS.md` (edit the real file).
- Policy: prefer recording durable guidance here over agent memory.
- Add the "Home switches" section (`jim`/`dave`/`brian`, access,
confirm-before-apply) pointing at `home-switches.md`.
- Document `deploy --boot` for staging a config without live-switching.
- Note the `ssh-agent` hang workaround for outbound SSH (`ssh-machine`/`deploy`).
- Add a comment convention: comment where useful, not for trivial code, and
describe general purpose rather than the one-off reason for a change.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
fmt reindents non-canonically-formatted files wholesale, burying logical
changes in whitespace churn. Note to match surrounding style by hand.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Capture what this session surfaced: the routing-common indexed-module
active/backup pattern, VRRP VIPs for gateway+DNS, the wan-online.target
convention, the networkd helper locations, and the "boxes not fleet"
terminology. Also note the fish login shell caveat for ssh scripting.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
`check-system` evaluates a NixOS config without building it; `ssh-machine`
SSHs to a system or home by name, resolving the target and ssh options
from its `deploy-rs` node. Document both in `AGENTS.md`.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
jackos1998