stocktake: re-verify Tailscale table, correct falsified cliprox/terra claim, regenerate skills-index
Wiki maintenance (wiki-maintain.sh, exit 0) + live-vs-page drift audit.
Script:
- systems/skills-index.md regenerated from the live skill tree: 302 skills in 69
categories; 45 archived skills under ~/.hermes/skills/.archive/ now excluded and
noted. (303 SKILL.md files exist outside .archive/, but
productivity/obsidian-git-sync/obsidian-git-sync is a nested alias duplicate,
so 302 unique is correct.)
- Freshness report raw/stocktake/freshness-20261029.txt: 2 stale / 105 fresh /
3 no-date. After the corrections below and a second script run: 0 stale /
107 fresh / 3 no-date.
- Quartz rebuilt (110 pages -> 644 files) and deployed to public/.
Drift corrections (live-verified):
- infrastructure/tailscale.md: State column rebuilt from tailscale status --json,
11 rows changed. Two were state transitions, not age drift:
* sftpgo (CT299, pve) is back online - tailscale ping pong in 0s,
systemctl is-active sftpgo -> active, tailscale ip -4 inside the guest.
* m93p is online despite a stale peer record (Online: false in the JSON) -
tailscale ping pong in 1ms, SSH over the tailnet returned up 11 days.
Second occurrence of this pattern after 2026-10-26.
The other 9 rows were offline-age drift of exactly +1 day. Node count unchanged
at 54 (53 live IPv4 peers + hermes); 76 peers total, 23 IPv6-only funnel
ingress. No missing peers, no IP mismatches. Container identity re-confirmed
from inside all 34 guests via pct exec tailscale ip -4 on both hypervisors;
CT601 still absent from both.
- incidents/2026-10-01-cliproxy-connection-auth-expired.md: the residual claim
"the connection credential itself was never re-authenticated" is falsified.
Live POST /v1/chat/completions for cliprox/terra against custom:Omniroute:20128
(CT600) returns HTTP 200 - the connection has since been re-authenticated. The
same pin on custom:omni-101 (CT101) still returns HTTP 401, so the nodes carry
separate credentials. Claim marked superseded, not deleted (SCHEMA rule 9); the
remediation was never reversed and remains correct.
- incidents/2026-10-05-dead-model-pin-repin.md: every claim re-probed. All 7 jobs
still on custom:omni-101 with routing aliases; both aliases HTTP 200;
ollama-cloud/qwen3.5:397b still HTTP 410; nvidia/deepseek-v4-flash still
HTTP 400; command-code/gpt-5.6-terra now HTTP 401 rather than the original 403
- still dead, different failure signature.
- systems/scheduled-tasks.md: the Known-Issues entry repeating the
"never re-authenticated" claim now carries the correction. Fleet figures
re-checked against live jobs.json and remain accurate (29 jobs / 26 enabled /
3 disabled, 5 non-clean last_status).
- log.md / index.md: stocktake entry appended and index last-updated refreshed.
Verified correct, no change: systems/homepage-dashboard (CT201 has 8084 and 8085
listening, no 8082, Homarr on 8102); CT201 Serve routes (/ -> 8085, /mgr -> 8084
on both :443 and :8443, Steel routes still gone); CT460 Serve routes (12 paths
on :443, plus :8443/webhook Funnel and :9443).
Noted for a human, not performed: vault mirror at /home/hermes/wiki/agent-estate-wiki
has drifted on both conventions (top-level 35 match / 3 stale / 72 missing;
wiki/ 41 match / 53 stale / 16 missing). A full mirror pass is larger than a
stocktake's mandate.
This commit is contained in:
@@ -1530,3 +1530,16 @@ not pushed.
|
||||
- **Corrects the 2026-10-29 00:3x audit entry**, which described Steel as merely "not reachable / endpoint dark". It is **removed**, not down. Per SCHEMA rule 9 the superseded claims are marked, not deleted.
|
||||
- **Removed/archived:** none. **Secrets written:** none (variable names only; no key or URL values).
|
||||
- **Unresolved:** the obsolete CT333 line in Nanobot's Obsidian vault (`Areas/Homelab/architecture.md`, "Steel Browser | Clawtest | http://localhost:3000") still stands — that vault is outside this wiki and was not modified. Also noted, unrelated to Steel: `Browser Use viewing unavailable: unsupported Hermes browser resolver` has logged in the gateway since 2026-10-11.
|
||||
|
||||
## [2026-10-29] stocktake | General Agent Estate Wiki maintenance — Tailscale table re-verified, and a 23-day-old "never re-authenticated" claim turned out to be false
|
||||
|
||||
- **Script:** `wiki-maintain.sh` ran clean (exit 0). `systems/skills-index.md` regenerated from the live skill tree — **302 skills in 69 categories**, with a new note that **45 skills** are parked under `~/.hermes/skills/.archive/` and excluded from the count. (303 `SKILL.md` files exist outside `.archive/`, but `productivity/obsidian-git-sync/obsidian-git-sync/SKILL.md` is a nested alias duplicate of `productivity/obsidian-git-sync/SKILL.md`, so **302 unique skills** is the correct figure.) Freshness report written to `raw/stocktake/freshness-20261029.txt`; Quartz rebuilt (110 pages → 644 files) and deployed to `public/`.
|
||||
- **Freshness report:** **2 stale / 105 fresh / 3 no-date** of 110 pages. The 2 stale were `incidents/2026-10-01-cliproxy-connection-auth-expired.md` and `incidents/2026-10-05-dead-model-pin-repin.md`, both at **23d**.
|
||||
- **Updated [[infrastructure/tailscale]]** — State column rebuilt from `tailscale status --json`; **11 rows changed**. Two were **state transitions**: **`sftpgo` (CT299, pve) is back online** (the 2026-10-28 audit had recorded it `offline <1d`; `tailscale ping` → pong in 0s, `systemctl is-active sftpgo` → `active`, `tailscale ip -4` inside the guest → `100.88.223.70`), and **`m93p` is online despite a stale peer record** (`Online: false` in the JSON, but `tailscale ping` → pong in 1ms and SSH over the tailnet returned `m93p / up 11 days`) — the **second** occurrence of that pattern after 2026-10-26. The other 9 rows were offline-age drift of exactly +1 day. Node count unchanged at **54** (53 live IPv4 peers + `hermes`); JSON reports **76 peers — 53 with a `100.` IPv4, 23 IPv6-only funnel ingress**. **No missing peers, no IP mismatches, CT601 still absent from both hypervisors.** Container identity re-confirmed from **inside** all 34 guests via `pct exec <vmid> -- tailscale ip -4` on both hypervisors; the 3 stopped guests (CT209/CT255/CT555) and the 3 running-but-unconnected guests (CT105/CT1264/CT100) confirmed.
|
||||
- **Updated [[incidents/2026-10-01-cliproxy-connection-auth-expired]]** — the residual claim *"the connection credential itself was never re-authenticated"* is **falsified**. A live `POST /v1/chat/completions` for `cliprox/terra` against `custom:Omniroute:20128` (CT600) returns **HTTP 200** — the connection has since been re-authenticated, independently of the incident's remediation. The same pin on `custom:omni-101` (CT101) still returns **HTTP 401** (`No active credentials for provider: cliprox.`), so the two nodes carry separate credentials. Claim marked superseded rather than deleted (SCHEMA rule 9); the remediation itself (moving 3 jobs off the pin) was never reversed and remains correct.
|
||||
- **Updated [[incidents/2026-10-05-dead-model-pin-repin]]** — every claim re-probed live: all 7 jobs are still on `custom:omni-101` with routing aliases (`free-stack` ×6, `smart-route` ×1) ✔; both aliases return **HTTP 200** ✔; `ollama-cloud/qwen3.5:397b` still **HTTP 410** (retired 2026-09-25) ✔; `nvidia/deepseek-v4-flash` still **HTTP 400** (absent from the live catalog) ✔; `command-code/gpt-5.6-terra` now returns **HTTP 401** (credential) rather than the original **403** (plan-gated) — the pin is still dead, only the failure signature changed. Frontmatter `updated`/`verified_on` bumped to 2026-10-29 with `created` left at 2026-10-06 as the data period.
|
||||
- **Updated [[systems/scheduled-tasks]]** — the Known-Issues entry repeating the "never re-authenticated" claim now carries the correction. The page's fleet figures were re-checked against live `jobs.json` and remain accurate: **29 jobs / 26 enabled / 3 disabled**, 5 non-clean `last_status`.
|
||||
- **Verified, no change needed:** [[systems/homepage-dashboard]] (CT201 `ss -ltn` shows 8084 and 8085 listening, **no 8082** listener, Homarr on 8102 — all as the page claims); CT201 Serve routes (`/` → 8085, `/mgr` → 8084 on **both** `:443` and `:8443`, exactly as documented, Steel routes still gone); CT460 Serve routes (12 paths on `:443` + `:8443/webhook` Funnel + `:9443`, matching the page).
|
||||
- **Not changed, flagged for a human:** the vault mirror at `/home/hermes/wiki/agent-estate-wiki/` has drifted on **both** conventions — top-level **35 match / 3 stale / 72 missing**, `wiki/` **41 match / 53 stale / 16 missing**. A full mirror pass is larger than a stocktake's mandate, so it is recorded here rather than performed.
|
||||
- **Removed/archived:** none. **Secrets written:** none (credential names and HTTP status codes only — no key or token values).
|
||||
- **Unresolved:** `cliprox/terra` remains **401 on CT101** — the CT101-side connection still needs a dashboard reconnect if anything is ever to target that pin from that node.
|
||||
|
||||
Reference in New Issue
Block a user