- 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)
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.
Ran wiki-maintain.sh (skills-index regenerated: 302 skills / 69 categories,
unchanged; freshness report 0 stale / 109 fresh / 3 no-date of 112 pages;
Quartz rebuilt and deployed).
Freshness is not accuracy. A live-vs-page diff found real drift on five pages.
All corrections verified against live sources first.
- infrastructure/tailscale: node table rebuilt from tailscale status --json.
50 non-funnel nodes (49 IPv4 peers + hermes), not 54. 2 IP changes, 4 peers
expired out of the tailnet. Zero IP mismatches, zero missing/extra rows on
re-verification. m93p records online (peer record chronically stale, third
occurrence -- ping + SSH confirm). CT460 :443 route set (12 paths) and
CT201 :443/:8443 tables re-probed and match.
- systems/scheduled-tasks: fleet is 29 jobs (25 enabled / 4 disabled), not
28/25/3. Mnemosyne Health Monitor ea79a2107e36 was auto-paused 2026-10-30
01:04:22 after its 00:01:08 slot closed "unknown" on a gateway-connection
failure. Non-clean last_status is 4, not 3. "Failing (delivery only)" is 2.
Seven job rows carried stale error claims for jobs since cleared to ok --
each marked superseded with a dated correction, not rewritten (SCHEMA rule 9).
- NEW incidents/2026-10-30-mnemosyne-health-monitor-paused: the job's own
failure notice was never delivered (deliveries.db has zero rows for
2026-10-30), so the incident row is the only trace. Job not re-enabled and
gateway not restarted by this run; root cause recorded as unverified.
- infrastructure/hosts: CT201 LAN is 192.168.178.77 (was .166); CT450 Hermes
is v0.22.5 / bf0203a794a0, same build as CT460 (page said v0.22.3 /
5b147ab036d6); cron count 29/25/4; orphaned "omni" peer has expired out of
the tailnet entirely. Skills count of 302 left alone -- it is correct.
- systems/homepage-dashboard: live app count is 123 (was 114); grid is a
responsive repeat(auto-fill, minmax(230px, 1fr)), not a fixed 5-column grid;
tab bar is built from the service groups (renderTabs iterates state.groups),
so the settings.yaml layout block and its tab:/columns: keys are inert --
there is no "Overview" tab; saved theme is Boarding Pass / light, not dark
amber; manager.py runs inside the homepage-manager container; and the "no
Traefik container" evidence was wrong -- the container exists but is
stopped (Exited (255) 2 months ago). The conclusion that Traefik does not
occupy 443 stands. Same evidence error corrected in tailscale.md.
Also corrected two of my own first-pass errors before committing: the
homepage tab list (groups vs tabs) and the CT450 version (a stale root-level
/usr/local/bin/hermes reports v0.19.0; the live agent is the hermes-user
install at v0.22.5).
No secrets written -- provider names, key names and HTTP status codes only.
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>
wiki-maintain.sh ran clean (302 skills indexed, Quartz rebuilt, 634 files emitted,
service restarted). The freshness report listed 8 stale pages; each was diffed
against live state and corrected only where reality could be verified. A second
script run rewrote the same-day report with 0 stale / 103 fresh / 4 no-date,
so the committed report matches the tree it ships with.
- infrastructure/hosts.md: CT600 is LIVE (not retired); CT601 does not exist on
either hypervisor; CT333 verified running; both hypervisors verified; config
33->51; skills 66->302; cron 25->28 (25 enabled / 3 disabled); Xvfb :102->:99;
providers split into Omniroute:20128 (CT600) and omni-101 (CT101, default).
- agents/hermes-production.md: Tailscale IP 100.96.100.82 -> 100.118.5.51 (the
old value is the PVE hypervisor); v0.21.5 -> v0.22.3; dead 8082 claim removed;
fallback chain rewritten from live config (first entry is the dead nous
credential); all 8 auxiliary slots now no-think/freeapi/auto; cron 30->28.
- agents/hermes-chaos.md: v0.22.3 (same build as CT460); "3 commits behind" ->
0 behind origin/master; default model smart-route on custom:omni-101; cron
"11 paused" -> 25 jobs (13 enabled / 12 disabled), 9 names shared with CT460.
- infrastructure/tailscale.md: node table rebuilt from status --json; octoagent
and omarchymac-1 were missing entirely (52 -> 54 non-funnel nodes); m93p now
online; every offline age refreshed; omni row corrected to "CT601 removed
from both hypervisors"; Serve tables re-probed per host.
- systems/memory-backend.md: re-verified against live config; coverage 1899/2350
(80.8%), working 96.8%, episodic 99.4% — above the 95% reindex threshold.
- runbooks/provider-health.md: the step-3 OmniRoute snippet raised IndexError
(provider renamed omniroute -> Omniroute:20128; key moved to key_env) — fixed;
new step 3b documents the omni-101 /v1/models false-failure quirk.
- runbooks/update-hermes-safely.md: added managed-runtime dependency re-assert
step; clarified --branch vs stable channel (v0.22.5 available).
- incidents/2026-10-03-ct450-hermes-update.md + incidents/2026-10-03-mnemosyne-vector-recall-fts-only.md:
Current-state sections recording current versions and embedding coverage.
All 9 corrected pages verified 200 at http://127.0.0.1:9120/<path>.
Vault mirror at /home/hermes/wiki synced for all touched files (22 copies,
sha256-verified) and committed locally; the vault is local-only and is not pushed.
No secrets written — IDs, URLs, key env var names, counts and timestamps only.