- Wire host-scoped Gitea credential (git credential approve); origin was HTTPS with no userinfo
- Strip 1.76GB checkpoints/ from the unpushed range via git filter-repo --partial (fast-forward preserved)
- Untrack checkpoints/ at the tip; push set ~2GB -> 264.8MB
- Rewrite backup.sh: exit non-zero on failure, stamp .last_backup_ok only after remote verification,
decide push by remote-vs-local, guard ls-remote with || true, GitHub orphan snapshot via commit-tree,
honest AgentMail/Telegram delivery reporting
- Verified live: exit 0, origin/main == local HEAD, 0 unpushed, Gitea + GitHub APIs confirmed
- Incident page -> status: resolved; backups.md -> RESOLVED; scheduled-tasks job row updated
- Also commits the uncommitted stocktake edits (the 03:00 stocktake cron failed with
'lost its durable fire claim ownership' and left the tree dirty)
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.
ROOT CAUSE FIXED - systems/skills-index.md had TWO WRITERS:
the repo wiki-maintain.sh (302 skills / 68 categories) and the stale
~/.hermes/scripts/wiki-maintain.sh (mtime 2026-08-17, 349 skills / 26
categories - it used Path.rglob() and counted the parked .archive/ tree) were
different scripts with different generators, and wiki-maintenance/SKILL.md
line 569 pointed the 23:59 nightly audit at the stale path while the 03:00
stocktake ran the repo path. Each job overwrote the other's page; neither
raised an error. The stale copy is now a delegating wrapper with no generator
logic, and the repo script gained --no-build so the wrapper honours the old
interface without a second generator. Verified by execution.
Live-probe corrections:
- infrastructure/docker-services.md: CT200 61 running / 68 total (was 62);
worldmonitor-seeder-scheduled does not exist on ANY host (zero 'seeder'
matches across CT200/201/333/460); CT333 first container renamed again
(nostalgic_leavitt -> flamboyant_mahavira); CT201 20/26, CT460 1/1,
CT1001 1/9.
- infrastructure/tailscale.md: node table verified programmatically - 52 rows
vs 52 live IPv4 peers, no live peer missing, no orphan row, every
online/offline state matching. conduit 59d->60d, ubuntu-server-xfce
75d->76d. Serve table still matches tailscale serve status exactly.
- infrastructure/hosts.md: skills figure corrected to 302 / 68 categories.
- index.md: skills-index bullet refreshed to the 2026-11-05 figures.
New incident: incidents/2026-11-05-skills-index-generator-divergence.md
(closes the still-open item on the 2026-08-15 skills-index drift incident).
Freshness: 0 stale / 123 fresh / 3 no-date of 126 pages.
BUILD FIX — the stocktake script was failing at step 3/3 with an opaque esbuild panic.
Root cause: incidents/2026-10-31-conduit-voice-local-mode-not-applying.md had an
unquoted YAML title containing ": " (from "voice mode: local"), which YAML parsed as a
mapping entry and Quartz rejected with "bad indentation of a mapping entry (2:27)".
A scan of all 117 pages found exactly one such line; it is now properly quoted.
Quartz now builds cleanly: 690 files emitted and deployed.
RESOLVED — incidents/2026-10-09-memory-recall-relevance.md (was the only stale page).
The page claimed the recall-ranking fix "was not present in live config" and that
conflict 152 was "the only open conflict". Both claims were false:
- The weights ARE persisted, in ~/.hermes/mnemosyne/config.yaml (vec_weight 0.5,
fts_weight 0.3, importance_weight 0.3) plus MNEMOSYNE_IMPORTANCE_WEIGHT=0.3 —
not in ~/.hermes/config.yaml's memory.mnemosyne block, which is what the
2026-10-10 probe read. The page was the reason the incident looked open for 3 weeks.
- The original regression test now passes: "mnemosyne recall 'Are you up to date'"
returns only substantive current-state facts (scores 0.174/0.130/0.123); the stale
Uber Eats episode no longer outranks anything.
- Conflict 152 was auto-resolved 2026-10-29 23:53:47Z as extraction noise.
All three open items closed; page moved to status: resolved.
LIVE DRIFT CORRECTED (all verified against live systems on 2026-11-01):
- infrastructure/tailscale.md: omarchymac went offline (genuine transition, ping
times out); m93p peer record reads false for the 4th consecutive time while the
host pongs and SSH returns up 1d12h, so the row stays online; 5 offline ages
refreshed; no IP changes, no missing peers.
- infrastructure/docker-services.md: CT201's Tailscale IP was wrong
(100.116.116.116 -> 100.96.244.39); 3 misspelled overchat-* entries and 1 stale
worldmonitor-seeder-fast entry removed from the CT200 list, which is now
regenerated verbatim from live docker ps; CT333's adoring_jemison renamed to
thirsty_payne.
- infrastructure/proxmox.md: storage percentages refreshed on both hosts from live
pvesm status; pct/qm lists re-confirmed (no CT601 anywhere); m93p uptime and an
elevated load average recorded.
- systems/mnemosyne.md, systems/omniroute.md, systems/messaging-integrations.md:
re-probed and verified_on bumped.
- systems/skills-index.md: regenerated — 301 unique skills in 68 categories,
46 archived. (301 is the unique (category, skill_name) count; find returns 302
files due to the known nested obsidian-git-sync alias duplicate.)
Freshness report: 0 stale / 114 fresh / 3 no-date of 117 pages.
Root cause of the long-standing cloud_provider: steel residue: the 2026-07-30
rollback disabled the browser-steel plugin and set browser.engine: camofox but
left browser.cloud_provider: steel in config.yaml. The split config was
inert-but-wrong, so it survived ~3 months of audits unnoticed.
Corrects pages that still described Steel as present, running or configured:
- systems/browser-backend.md (incl. gateway-restart env-var note)
- comparisons/steel-vs-camoufox.md, comparisons/camoufox-vs-chrome.md
- decisions/rollback-steel-to-camofox.md, decisions/index.md
- infrastructure/docker-services.md, infrastructure/tailscale.md, infrastructure/hosts.md
- systems/homepage-dashboard.md, systems/scheduled-tasks.md
- concepts/browser-automation.md, runbooks/recover-docker-service.md
- current-state.md, index.md, agents/nanobot.md
- log.md (dated entry; supersedes the 00:3x audit's 'endpoint dark' wording)
Also restores the Ignis compose row in infrastructure/docker-services.md, which
the 2026-10-11 revision dropped (verified: /home/hermes/docker/ignis/docker-compose.yml
exists and the ignis container is Up on CT460).
Co-Authored-By: Hermes <hermes@local>
Drift found and corrected against live sources (not guessed):
- OmniRoute: CT600 omniroute is RUNNING and serving :20128 (combo API live);
CT601 omni is STOPPED with onboot=0 (peer offline 54d). Wiki had these inverted.
Hermes custom:omni resolves to omniroute -> CT600, not CT601.
- Third OmniRoute node discovered: omniroute-1 at 100.78.63.20:20128, live (401),
registered as custom provider omni-101 (5384 models, default smart-route,
carries skills_hub/free-stack). Not in pct list; identity unconfirmed.
- Ignis: TWO live instances. CT460 ignis (:8080, vault wiki/agent-estate-wiki) and
CT200 ignis-ignis-1 (image ignis-server:latest, host 8092, vault /opt/ignis/vaults).
Both return HTTP 200. Page now distinguishes them.
- Tailscale: /agent-estate targets bare 127.0.0.1:8769 (was .../8769/agent-estate-role-dashboard.html);
undocumented tailnet-only :9443 -> 127.0.0.1:5173 added; CT201 routes corrected
(8085 targets + /steel 5173 + /steel-api 3000, replacing the wrong :8443 -> :8082 row).
- Proxmox: rebuilt from live pct list + qm list. Added CT475 agentzero and VM110 omarchy
(both previously missing); 282 ubuntu-server-xfce corrected to stopped; dead rows removed.
VM403 open-claw and VM401 hermes-old absent from qm list - flagged unconfirmed, not deleted.
- Nanobot: gateway nanobot-gateway (PID 2259048) alive on 8765/8766. It is NOT systemd
nanobot.service/gateway.service (both return inactive - wrong unit names). Port 8900
no longer listening; "Serve API" claim flagged unverified.
- Docker: old "runtime not available" was a CT460 socket artifact (root:docker srw-rw----,
hermes not in group docker, no passwordless sudo in cron). Documented CT200 (~50 containers),
CT333 (9 containers), CT460 via sudo.
- Mattermost CT255 confirmed stopped; matches Tailscale peer offline 21d.
Flagged, not investigated (no root cause):
- mycompose-db-1 on CT200 is in Restarting (1) - crash-looping.
62 pages remain >21d stale and were NOT rewritten this pass (concepts, decisions,
comparisons, most runbooks) - not probed against a live source, so reported not faked.
Quartz rebuild step still inert (no quartz.config.ts) - public/ not refreshed.
Artifacts: systems/skills-index.md regenerated, raw/stocktake/freshness-20261011.txt.