stocktake(2026-11-01): fix the Quartz build (YAML title), close the "unfixed memory ranking" incident, and correct live drift in tailscale/docker/proxmox

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.
This commit is contained in:
Tony0410
2026-11-01 04:48:30 +08:00
parent c69681dc16
commit a0b3734c95
14 changed files with 596 additions and 111 deletions
+66
View File
@@ -1744,3 +1744,69 @@ recorded wrong.**
`infrastructure/tailscale.md`, `systems/messaging-integrations.md`, `systems/omniroute.md`,
`systems/skills-index.md`) and untracked `raw/stocktake/freshness-20261031.txt` — the mirror convention is
*"(authoring COMMIT_SHA)"*, so uncommitted content stays out until the stocktake's own commit lands.
## [2026-11-01] stocktake | General Agent Estate Wiki maintenance — Quartz build was broken by a YAML title; the "unfixed memory ranking" incident turns out to have been fixed three weeks ago
- **BUILD FAILURE FOUND AND FIXED (this was blocking the whole stocktake).** `wiki-maintain.sh` exited **1** at
step 3/3 with an esbuild panic. Root cause was **not** esbuild: `incidents/2026-10-31-conduit-voice-local-mode-not-applying.md`
had an **unquoted YAML `title:`** containing the substring `: ` (from `"voice mode: local"`), so YAML parsed it as a
mapping entry and Quartz aborted with `bad indentation of a mapping entry (2:27)`. A scan of all **117** pages
found **exactly one** offending frontmatter line; the title is now double-quoted with escaped inner quotes.
**This is a latent trap worth remembering:** any future page title containing `": "` or `":` unquoted will
silently break the entire Quartz build, and the failure surfaces as an opaque esbuild goroutine dump rather
than a YAML error.
- **STALE PAGE — `incidents/2026-10-09-memory-recall-relevance.md` (23d) — RESOLVED, not stale.** The page's
central claim was that the recall-ranking fix *"was reported saved and is **not** present in live config"*, and
that conflict `152` was *"the only open conflict"*. **Both claims are false, and the page was the reason the
incident looked open for three weeks.** Live `~/.hermes/mnemosyne/config.yaml` reads `vec_weight: 0.5`,
`fts_weight: 0.3`, `importance_weight: 0.3` (plus `MNEMOSYNE_IMPORTANCE_WEIGHT=0.3` in the environment) —
**the weights live in Mnemosyne's own config file, not in `~/.hermes/config.yaml`'s `memory.mnemosyne` block
that the 2026-10-10 probe read.** The 2026-10-10 verification probed the wrong file and concluded "not applied".
**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) and the stale Uber Eats / Sonos episode
(`id 32f469aae09d56dc`, still in the DB) **no longer outranks anything**. Conflict `152` was auto-resolved
**2026-10-29 23:53:47Z** ("low-confidence LLM extraction noise") — it has not been open since. All three open
items closed; page moved to `status: resolved`. Live tier counts at 2026-11-01: working **941**, episodic
**1,124**, canonical **90**, conflicts **175** with **11 open** (ids 165–175, all one-batch extraction noise
sharing a single `fact_a_id`), working embeddings **927/941 (98.5 %)**, episodic **1,124/1,124 (100 %)** — both
above the 95 % floor, no `reindex` needed.
- **UPDATED — `systems/mnemosyne.md`:** stale 2026-10-09 tier-count block marked superseded and a live 2026-11-01
block added, including the weights' actual home and the resolved-incident pointer.
- **UPDATED — `infrastructure/tailscale.md`:** table rebuilt from live `tailscale status --json` — **1 state
transition and 5 offline-age drifts, no IP changes, no missing peers**. `omarchymac` (100.126.173.115) went
**offline** (`Online: false`, `LastSeen 2026-10-31 13:20Z`, `tailscale ping` times out — a genuine transition;
the JSON `OS` field reads `linux`). `m93p`'s peer record reads `Online: false` **again** — the **4th
consecutive** stale record — while `tailscale ping` → `pong` and SSH returned `up 1 day, 12:02`, so the row stays
**online**. Ages refreshed: cloudreve 98→**99d**, freshrss-new 74→**75d**, omarchybook 9→**10d**, openmausbot
9→**10d**, ubuntu-server-xfce 71→**72d**; `conduit` (55d) and `elementsynapse` (102d) were already correct.
- **UPDATED — `infrastructure/docker-services.md`:** **CT201's Tailscale IP was wrong** — the page read
`100.116.116.116`; live `pct exec 201 -- tailscale ip -4` returns **`100.96.244.39`** (which
`[[infrastructure/hosts]]` already had right). The CT200 inventory had **three misspelled `overtchat-*`
entries** (written `overchat-*`) and **one stale entry**, `worldmonitor-seeder-fast`, which is not running —
the list is now regenerated verbatim from live `docker ps`. **CT333's first container was renamed**:
`adoring_jemison` → **`thirsty_payne`**. Counts re-verified: CT200 **61**, CT201 **20**, CT333 **8**,
CT1001 **1** (`sshwifty`), CT460 `ignis` running.
- **UPDATED — `infrastructure/proxmox.md`:** storage percentages refreshed against live `pvesm status` on **both**
hosts (`pve` `fred-qnap` 82.45→**82.77 %**, `SSD1` 63.80→**64.32 %**, `local-lvm` 13.60→**13.75 %**; `m93p`
`nfs-proxmox-*` 82.45→**82.78 %**, `omb-internal` 58.00→**57.92 %**). `pct list` / `qm list` on both hosts
re-confirmed — **no CT601 on either hypervisor**, CT255 still `running`, VM 103 `cachyos-m93p` stopped, VM 106
`openmausbot-vm` running. `m93p` uptime recorded as **up 1 day, 12:02** with a **load average of
7.66 / 12.80 / 11.32** — elevated, worth watching.
- **UPDATED — `systems/omniroute.md` / `systems/messaging-integrations.md`:** re-probed today — both OmniRoute
nodes answer **401** on `/v1/models` (alive, auth required), CT600 and CT101 both `running`; Mattermost's
`systemctl is-active` → `active`, `LISTEN *:8065`, `/api/v4/system/ping` → **HTTP 200**. Frontmatter
`verified_on` bumped to 2026-11-01.
- **REGENERATED — `systems/skills-index.md`:** **301 unique skills** in 68 categories, **46 archived**. The count
is *unique `(category, skill_name)`* pairs, not `SKILL.md` file count — live `find` returns **302** files, and
the one difference is the known nested alias duplicate
`productivity/obsidian-git-sync/obsidian-git-sync/SKILL.md` vs `productivity/obsidian-git-sync/SKILL.md`.
**301 is correct — do not "fix" it to 302.** One skill was archived since the last run:
`hermes-runtime-worker-diagnostics` (46 archived, up from 45).
- **FRESHNESS:** the 2026-11-01 report lists **1 stale / 113 fresh / 3 no-date** of 117 pages. The single stale
page (the memory-recall incident) has been corrected and re-verified above; the report was regenerated after
the fixes, per the script → fix → re-run → commit order.
- **Probes (context, not findings):** `m93p` SSH over the tailnet timed out on the first two attempts and
succeeded on the third — a flaky path, not a host outage (`tailscale ping` → pong throughout). `homarr` on
CT201:8102 returns **307 → 200** on `/board`, so the dashboard page's "live, 200" claim still holds. CT201's
`:8443/` root returns **502** (upstream 8082 has no listener) and `:8443/mgr` returns **200** — both still as
the homepage-dashboard page records. No secrets, tokens, passwords or keys written.