audit(2026-11-11): log the vault sync, the re-measured drift and the 2026-11-12 freshness report
This commit is contained in:
@@ -2477,3 +2477,6 @@ ledger activity remains the 2026-11-05T12:36:17 closures), so **nothing alerted*
|
|||||||
- **Deliveries checked at the destination:** 2026-11-11 = **7 rows, 7 / 7 `delivered`, 0 `for_failure`** (07:11:42, 07:31:01, 08:03:47, 08:34:36, 12:19:38, 14:34:55, 18:45:58); 2026-11-10's late row (22:18:48) is the one `for_failure: 1`. 2026-11-12 so far: 5 rows, 4 `completed` / 1 `running`.
|
- **Deliveries checked at the destination:** 2026-11-11 = **7 rows, 7 / 7 `delivered`, 0 `for_failure`** (07:11:42, 07:31:01, 08:03:47, 08:34:36, 12:19:38, 14:34:55, 18:45:58); 2026-11-10's late row (22:18:48) is the one `for_failure: 1`. 2026-11-12 so far: 5 rows, 4 `completed` / 1 `running`.
|
||||||
- **Providers unchanged; symptoms worse.** `config.yaml` mtime still **2026-11-09 22:58:07** — nothing repaired this window. The expired `opencode-zen` key at `fallback_providers[1]` produced **7 x HTTP 401 `api_key_expired`** on 11-11 (07:01:13 -> 19:19:39), each **immediately after** nous returned **14 x 404 `insufficient_credits_for_paid_model`** (07:01:11 -> last 19:19:38, all from the still-open desktop session `20261031_190813_95fbde`). **Two consecutive dead hops on one chain** — [[systems/opencode-go]] updated from "latent risk" to observed failure; [[incidents/2026-10-22-nous-portal-refresh-token-invalid]] gained the 11-11 escalation block. `auxiliary.pulse_memory` remains the **only slot with no `fallback_chain`** and logged **19 lines / 11 refusals** on 11-11.
|
- **Providers unchanged; symptoms worse.** `config.yaml` mtime still **2026-11-09 22:58:07** — nothing repaired this window. The expired `opencode-zen` key at `fallback_providers[1]` produced **7 x HTTP 401 `api_key_expired`** on 11-11 (07:01:13 -> 19:19:39), each **immediately after** nous returned **14 x 404 `insufficient_credits_for_paid_model`** (07:01:11 -> last 19:19:38, all from the still-open desktop session `20261031_190813_95fbde`). **Two consecutive dead hops on one chain** — [[systems/opencode-go]] updated from "latent risk" to observed failure; [[incidents/2026-10-22-nous-portal-refresh-token-invalid]] gained the 11-11 escalation block. `auxiliary.pulse_memory` remains the **only slot with no `fallback_chain`** and logged **19 lines / 11 refusals** on 11-11.
|
||||||
- **Pages written:** 1 new incident; 2 incidents -> `resolved`; 2 system pages + `current-state.md` + `index.md` updated; `systems/scheduled-tasks.md` gained the 2026-11-11 count/state normalisation. `~/.hermes/logs/errors.log` is now **6,179 lines** through **2026-11-12 00:10:11**. **No page deleted, no decision reversed, no secrets written** — no credential value appears in any page; the opencode key is recorded by *state*, never by value.
|
- **Pages written:** 1 new incident; 2 incidents -> `resolved`; 2 system pages + `current-state.md` + `index.md` updated; `systems/scheduled-tasks.md` gained the 2026-11-11 count/state normalisation. `~/.hermes/logs/errors.log` is now **6,179 lines** through **2026-11-12 00:10:11**. **No page deleted, no decision reversed, no secrets written** — no credential value appears in any page; the opencode key is recorded by *state*, never by value.
|
||||||
|
- **Post-audit housekeeping (00:2x AWST 2026-11-12), vault sync.** Touched files copied to **both** vault conventions — `…/agent-estate-wiki/<rel>` and `…/agent-estate-wiki/wiki/<rel>` — with `sha256sum` confirmed equal across all three copies; vault committed locally in `/home/hermes/wiki` (`master`, **no remote — never pushed**), explicit paths only, so the unrelated `reports/uber-eats/*` dirt stayed out. Before copying, each vault file was compared against the **pre-edit** authoring blob (`c108eb1`): every difference was a *stale-but-clean* older version (vault `index.md`/`skills-index.md` still 11-10/11-09, `log.md` still missing the 11-11 stocktake entry, the nous incident page still 2026-10-26 at 48 lines vs 96) — **no direct-to-vault edits to preserve**, so forward-sync was safe. The 2026-10-22 nous incident page was **created** in vault B's `incidents/` (it had never been mirrored); the new 11-10 audit page went into **both** `incidents/` dirs.
|
||||||
|
- **Vault drift re-measured (hash sweep over all 133 authoring pages, this run's 10 touched files excluded):** **Vault A — 13 stale / 56 missing / 64 in sync. Vault B — 58 stale / 8 missing / 67 in sync.** Unchanged in character from the 2026-10-19 measurement (the copy bridge still only syncs what an audit touches), so the missing-page backlog is recorded here and **left to an explicit request** rather than silently swept — a 133-page mirror pass is bigger than a nightly audit's mandate. ⚠ This is now a two-night-old gap: because the 2026-11-10 audit died at 00:12, **nothing was mirrored for that window either.**
|
||||||
|
- **Freshness report:** `raw/stocktake/freshness-20261112.txt` (this run, 6,325 B) — **1 stale / 129 fresh / 3 no-date of 133** pages (was 132; **+1 = the new incident page**). The single stale entry is **`log.md` itself**, which carries no frontmatter `updated:` — expected, not a finding. `systems/skills-index.md` regenerates identically at **299 skills / 67 categories**. Quartz rebuilt and `hermes-wiki-serve.service` restarted; the new page returns **200** at the served site with its body content present.
|
||||||
|
|||||||
Reference in New Issue
Block a user