stocktake 2026-11-20: re-verify 9-page 2026-10-29 stale cohort live; correct nanobot docker/cron drift, camofox host/port claims, dead-pin residual; freshness 0 stale/136 fresh
This commit is contained in:
@@ -1877,3 +1877,16 @@ recorded here so the next audit does not re-litigate it.
|
||||
- **Mnemosyne consolidation is still zero-item:** newest `consolidation_log` row **`2026-11-19T16:20:14+00:00`** (= 2026-11-20 00:20 AWST, ~31 min cadence) with `items_consolidated: 0` and `summary_preview: "No-op consolidation cycle — timestamp updated for watchdog"`; **199 of the last 200 cycles are zero-item** (was **120** on the 11-17 read). The zero-item-streak threshold remains **proposed, not applied**.
|
||||
- **Freshness at publish time** (`raw/stocktake/freshness-20261120.txt`): **9 stale / 127 fresh / 3 no-date of 139 pages**. All nine carry the *same* `updated: 2026-10-29` — one 22-day bulk cohort, not nine findings: `agents/nanobot.md`, `comparisons/camoufox-vs-chrome.md`, `comparisons/steel-vs-camoufox.md`, `concepts/browser-automation.md`, `decisions/index.md`, `decisions/rollback-steel-to-camofox.md`, `incidents/2026-10-01-cliproxy-connection-auth-expired.md`, `incidents/2026-10-05-dead-model-pin-repin.md`, `runbooks/recover-docker-service.md`. **Not re-verified by this audit** — the live-vs-page re-verification sweep belongs to the 03:00 stocktake (pattern 23), so the cohort is recorded here rather than silently inherited. Five further pages sit at exactly 21d and become the 11-21 stale list: `incidents/2026-10-27-job-radar-budget-exhausted.md`, `incidents/2026-10-28-job-radar-stage1-iteration-cap.md`, `incidents/2026-10-29-conduit-voice-silence.md`, `incidents/2026-10-30-m93p-nfs-mount-loss-lxc-boot-failure.md`, `systems/homepage-dashboard.md`.
|
||||
- **Published (patterns 13/30):** `wiki-maintain.sh` regenerated `systems/skills-index.md` (**299 skills / 67 categories**) and rebuilt Quartz — 139 pages parsed, 867 files emitted to `public/`, `hermes-wiki-serve.service` restarted (`systemctl --user is-active` → `active`, listener on `:9120`). Live check after the rebuild: `index`, `current-state`, `systems/mnemosyne`, `systems/scheduled-tasks`, `systems/skills-index` and all three incident pages return **200** on `http://127.0.0.1:9120/<path>`. Both vault conventions synced from the authoring tree with per-file `sha256` matches (8 files × 2 conventions; freshness report included), committed locally — the vault repo has no remote.
|
||||
|
||||
## 2026-11-20 03:0x — Stocktake (cron 1a8e90ea2271): 9-page stale cohort re-verified live
|
||||
|
||||
- Ran `wiki-maintain.sh` (repo script): skills-index regenerated (**299 skills / 67 categories**), freshness report `raw/stocktake/freshness-20261120.txt` → **9 stale / 127 fresh / 3 no-date of 139**. All nine stale pages were the single 2026-10-29 cohort (22d) flagged by the 01:13 audit — treated as one verification sweep (pattern 23), not nine investigations.
|
||||
- **Live probes:** `~/.hermes/config.yaml` browser block; `ss -ltnp` + process list + `cua-driver --version` on CT460; `camofox-browser.service` (`systemctl --user` → active) + `:9377/health` → ok; CT333 via PVE (`ss`, `ps`, `docker ps -a`, `tailscale ip -4`, gateway `/health`, `workspace/cron/jobs.json`); CT201 via PVE (`docker ps -a`, images, Serve status, `_archived-steel/`, `:8085` probe); OmniRoute chat-completions on both nodes (`cliprox/terra`, `free-stack`, `smart-route`); `command-code/gpt-5.6-terra`; `jobs.json` fleet read.
|
||||
- **All 9 pages re-verified** (`updated`/`verified_on` → 2026-11-20) with dated notes: `agents/nanobot.md`, `comparisons/camoufox-vs-chrome.md`, `comparisons/steel-vs-camoufox.md`, `concepts/browser-automation.md`, `decisions/index.md`, `decisions/rollback-steel-to-camofox.md`, `incidents/2026-10-01-cliproxy-connection-auth-expired.md`, `incidents/2026-10-05-dead-model-pin-repin.md`, `runbooks/recover-docker-service.md`.
|
||||
- **Corrections (claims disproved or drifted):**
|
||||
- `agents/nanobot.md`: Docker list drifted — `tender_brattain` → `ecstatic_swartz` (random-name rename class), `quirky_darwin` removed (absent with `-a`), stopped `qdrant` present. Gateway PID now 1256104 (v0.4.1, `/health` ok). **Cron section rewritten from live scheduler**: 11 jobs / 8 enabled; `morning-quota-report`, `daily-agent-briefing`, `evening-quota-report` disabled; `rss-check-proxmox-selfhst` gone; new `nightly-skills-export-sync` (04:00) and `morning-news-podcast` (07:00). Quota pair 07:30/19:00 remains enabled. Scheduler file is `workspace/cron/jobs.json` (the `~/.nanobot/cron/` dir is empty).
|
||||
- `comparisons/camoufox-vs-chrome.md`: struck the stale "9377 not listening on CT460 / service on CT450" claim — `:9377` **is** listening on CT460 (local `camofox-browser.service`, active); ws-server also on `:9222`.
|
||||
- `decisions/rollback-steel-to-camofox.md`: Rationale's "(CT450)" host attribution corrected to **CT460** with strikethrough.
|
||||
- `incidents/2026-10-05-dead-model-pin-repin.md`: residual "four jobs still carry pre-repin error status" has **cleared** — all seven now `last_status: ok`, streak 0. `command-code/gpt-5.6-terra` error class drifted **again**: now 403 `error code: 1010` (Cloudflare) vs 401 on 10-29 vs 403 MODEL_NOT_IN_PLAN originally — pin still dead, rejection layer differs. Fleet now 29 jobs / 26 enabled (was 30/27).
|
||||
- **Claims that held:** Steel fully removed (CT201 + CT333: no containers/images/routes; `_archived-steel/` intact); `cliprox/terra` 200 on CT600 / 401 on CT101 (per-node credentials, unchanged since 10-29); zero jobs on `cliprox`; `free-stack`/`smart-route` 200 on both nodes; docker.sock permission-denied for `hermes` on CT460; CT201 homepage `:8085` still 502 (degradation persists).
|
||||
- Not re-probed: the five pages at exactly 21d (job-radar ×2, conduit-voice, m93p-nfs, homepage-dashboard) — they become the 11-21 stale list; homepage's core claim was incidentally re-confirmed (502 persists) but the page itself was left for its own cycle. Pre-existing dangling wikilinks in `agents/nanobot.md` (`systems/gitea`, `systems/chromadb`, `incidents/nanobot-degraded-2026-08-07`, `runbooks/nanobot-restart`) confirmed present before this edit — flagged, not introduced.
|
||||
|
||||
Reference in New Issue
Block a user