incidents/2026-10-14-omniroute-node-connection-refused-storm.md was at exactly 21d and
would have tripped the threshold on the next run. Its residual claim ("omniroute-1
answers again") was re-probed live and still holds: TCP connect to 100.78.63.20:20128
succeeds (no Errno 111), the Tailscale peer reads Online:true, and a keyed
POST /v1/chat/completions returns HTTP 200. Page re-verified (updated/verified_on ->
2026-11-06, review_after -> 2026-12-06) with the probe recorded on the page.
New trap recorded on the page and in systems/scheduled-tasks.md: on omniroute-1 the
RAW model id deepseek/deepseek-v4-flash returns HTTP 401 "No active credentials for
provider: deepseek", while the fleet's deepseek-paid-smart alias returns HTTP 200 and
resolves to that same model. The 401 is an alias-routing artefact, not an outage - probe
the alias the fleet pins, never the raw model id. (A first probe using the wrong
key_env also produced a 401; omni-101's key env is HERMES_CUSTOM_100_78_63_20_20128_API_KEY.)
Freshness re-run after the edits: 0 stale / 124 fresh / 3 no-date of 127 pages.
Quartz rebuilt and redeployed. Vault mirror synced to both conventions (sha-verified).
Ran wiki-maintain.sh (repo script). skills-index regenerated -> 302 skills / 68 categories.
Freshness audit at the 21-day threshold -> 0 stale / 124 fresh / 3 no-date of 127 pages.
Quartz rebuilt (761 files) and deployed to public/; hermes-wiki-serve.service restarted.
Live-vs-page drift diff (age scan alone missed all of this):
- infrastructure/tailscale.md: 1 state transition + 8 offline-age drifts + 2 dead Serve
routes. anthonys-mac-mini came back online (peer record Online:true, tailscale ping ->
pong via DERP(syd)). Offline ages refreshed +1d each (cloudreve 104d, elementsynapse
107d, freshrss-new 80d, octoagent 4d, octop 2d, omarchybook 15d, omarchymac 4d,
openmausbot 15d). Every peer IP still matches the live JSON; no peer missing, no
orphan row. /agent-estate->8769 and /synergy-prep->9123 are DEAD (no listener) while
still present in `tailscale serve status` - both now marked DEAD, matching
network-map.md. All other Serve targets have live listeners.
- infrastructure/docker-services.md: the 2026-11-05 "the seeder does not exist on any
host" finding was FALSE - a point-in-time sampling artefact. The worldmonitor-seeder-*
containers are transient and systemd-timer driven on CT200 (worldmonitor-seed.timer
4h -> seeder-scheduled; worldmonitor-seed-fast.timer 15min -> seeder-fast), visible
only while a run is in flight. Both present at 2026-11-06 03:1x; neither at
2026-11-05 05:1x. The "no cron job" claim was also wrong (systemd timers, not cron) and
the "rename" narrative was wrong (one script, two container names). Corrected on the
page with strikethrough + dated correction. CT200's 61-container running set still
matches live set-wise. CT333 container renamed again: flamboyant_mahavira ->
nostalgic_keldysh.
- systems/scheduled-tasks.md: no drift. Live jobs.json reads 29 jobs / 26 enabled /
3 disabled, 1 non-clean last_status - exactly as recorded.
- current-state.md / index.md: false seeder claim and "every state matching" claim
marked superseded with dated corrections (SCHEMA rule 9), not silently rewritten.
- infrastructure/network-map.md: dates bumped, dead routes re-confirmed, peer recheck
note refreshed.
- log.md: appended (append-only) with the full stocktake record.
No secrets, tokens or keys written or quoted.