audit(2026-11-12): the estate's last incident closed itself; a past-0.9.42 hq-push install was refused by the plugin scan (fix parked in PR #2)
- 429 row cbfe43_ed01845310d8 closed resolved 2026-11-12T00:25:36 on the next clean slot; 0 of 137 unclosed - 11-12: 176 rows / 175 completed / 0 failed / 1 running; 11-11: 172/172/0; deliveries 9/9 and 7/7 delivered - NEW incidents/2026-11-12-hq-push-upgrade-blocked-by-plugin-scan.md (dangerous verdict, one critical in the plugin's own tile skill; --force cannot override; no per-verdict override exists) - systems/hermes-hq-push.md corrected live (0.9.27 -> 0.9.42, tree mtime 2026-11-08 02:19, config line 13226) - current-state / scheduled-tasks / index / log updated; skills-index regenerated; freshness 2026-11-13 (0 stale)
This commit is contained in:
@@ -2495,3 +2495,55 @@ ledger activity remains the 2026-11-05T12:36:17 closures), so **nothing alerted*
|
||||
- **Order of operations:** script → page corrections → **re-run script** → log/index → commit. `wiki-maintain.sh` re-run after every page edit; Quartz rebuilt and `hermes-wiki-serve.service` restarted.
|
||||
- **No page deleted, no decision reversed, no secrets written.** No credential value appears in any page; the OmniRoute probe used the `key_env` name, never the value.
|
||||
- **Correction to the entry above (2026-11-12 00:1x AWST audit), verified live rather than inherited:** that entry states *"The single stale entry is **`log.md` itself**, which carries no frontmatter `updated:` — expected, not a finding."* **That is wrong.** The committed `raw/stocktake/freshness-20261112.txt` from that run (sha256 `da5f9e2e…`, byte-identical to this run's pre-fix output) reads **`- [ 22d] incidents/2026-09-02-sftpgo-outage.md (updated 2026-10-21)`** as its single `## STALE (1)` line — the real page, which this stocktake has now re-verified and cleared. `log.md` sits in the `## NO updated DATE` bucket, as always (pattern 13). The stale page was therefore **left unflagged in prose for one cycle while sitting stale in the tree** — the exact "fresh-looking prose, stale content" failure the report exists to prevent.
|
||||
|
||||
## 2026-11-12 23:5x – 2026-11-13 00:4x AWST — Nightly audit (window 2026-11-11 23:59 → 2026-11-12 23:59)
|
||||
|
||||
**Clean day, incident-clean estate — and an upgrade the security scan would not allow.**
|
||||
|
||||
- **The estate's last open incident closed itself.** `cbfe43_ed01845310d8` (the 2026-11-10 audit's 429)
|
||||
went `closed_at: 2026-11-12T00:25:36.133387+08:00`, `state: resolved`, when the **next slot of the same
|
||||
job ran clean** — `cbfe434a3b5e` 2026-11-11T23:59:54.486572 → 2026-11-12T00:25:36.133387 = **25 m 42 s**,
|
||||
`completed`, delivery carrying both windows. **`cron_incidents`: 0 unclosed of 137.** No config produced
|
||||
it; the pool reset at ≈ 06:36:57 on 11-11 did. The 429 page's `status: open` was **stale** — corrected to
|
||||
`resolved` with a new *Resolution* section, and its "only open row" wording superseded.
|
||||
→ [[incidents/2026-11-10-wiki-audit-429-all-targets-skipped]]
|
||||
- **Ledger, live from `executions.db`:** 2026-11-11 **172 / 172 `completed` / 0 `failed`**; 2026-11-12
|
||||
**176 rows — 175 `completed` / 0 `failed` / 1 `running`** (this audit, 23:59:54); 2026-11-13 so far
|
||||
7 / 7. **Second consecutive zero-`failed` day.** Deliveries **11-11: 7 / 7; 11-12: 9 / 9 `delivered`**,
|
||||
0 `for_failure`. Fleet **29 (26 / 3)** — seventh window unchanged. Retention floor `2026-11-07T00:00:42`,
|
||||
1,001 rows.
|
||||
- **NEW PAGE — [[incidents/2026-11-12-hq-push-upgrade-blocked-by-plugin-scan]].** On 2026-11-12
|
||||
(~17:38–18:29) `hermes plugins install … --enable --force` for `hermes-hq-push` was refused:
|
||||
*"Blocked (dangerous verdict, 1 critical of 39 findings (echo_pipe_exec))"*, *"--force does not override a
|
||||
dangerous verdict."* **Verified in source rather than assumed:** the block is one unconditional branch
|
||||
(`tools/plugin_guard.py:406-418`); `--force` lifts `caution` only; **there is no per-verdict override,
|
||||
env var, plugin trusted-source list or allowlist** — the only key is `plugins.scan_on_install` (default
|
||||
`true`, currently unset), and setting it `false` disables scanning for *every* future install. The
|
||||
`trust_level` machinery exists in `tools/skills_guard.py` (skills path) and is **not read** by
|
||||
`plugin_guard.py:398`, which hardcodes `trust_level="community"`. Installed **v0.9.42 untouched,
|
||||
`enabled`, still delivering**. **Fix = PR #2** on `mrcharlesiv/hermes-hq-plugins` (author `Tony0410`,
|
||||
`fix/tile-skill-heredoc`, **OPEN / MERGEABLE**, `mergedAt: null`, +7/−2 in one file) — pushed from a fork
|
||||
because `gh` here is authenticated as `Tony0410` with **read-only** access upstream; local clone
|
||||
`/home/hermes/workspace/hq-plugins-fix` (`90c9d28`).
|
||||
- **`systems/hermes-hq-push.md` corrected against live probes:** version **0.9.27 → 0.9.42** in the
|
||||
*Verified state* table (which still carried the 2026-11-04 reading), tree mtime **2026-11-07 06:42 →
|
||||
2026-11-08 02:19** (measured), the config claim's **line 7556 → 13226** (block opens line 13210 — noted
|
||||
as drifting), plus a new *2026-11-12 — refused upgrade* section and two new *Open* items.
|
||||
- **The "stored hold-and-ask instruction" was never stored.** Recursive sweep of `~/.hermes`
|
||||
(**184,716 files**; generated/venv/browser-profile/SQLite trees excluded) for `wait for my answer`,
|
||||
`show me what it found`, `security scan flags`, `security-scan` → **zero matches in any editable text
|
||||
file**; the sentence exists only in `state.db` **conversation history** (58 rows). **Nothing removed, no
|
||||
policy reverted** — there was nothing persisted to revert. Walkthrough recorded as the new skill
|
||||
`stored-instruction-search-and-removal`; installed skills **299 → 300** (`skills-index.md` regenerated
|
||||
by `wiki-maintain.sh`).
|
||||
- **Config: no drift.** Live `~/.hermes/config.yaml` is **byte-identical to the 2026-11-12 18:14:52
|
||||
snapshot** (565,433 B). The only delta since the **11-09** snapshot is the **model catalogue block**
|
||||
(lines 1916-1941): 6 entries removed, 9 added. Nothing unrelated moved.
|
||||
- **Still open, unchanged and re-confirmed:** the *"all targets were skipped by pre-dispatch filters"*
|
||||
signature recurred on a **second job and a second pin** (2026-11-12 03:00 stocktake), and every
|
||||
model-calling job still rides `custom:omni-101` with no failover for the free-tier cohort
|
||||
→ [[incidents/2026-10-21-omniroute-pre-dispatch-filter-skip]].
|
||||
- **Pages touched:** `incidents/2026-11-12-hq-push-upgrade-blocked-by-plugin-scan.md` (new),
|
||||
`incidents/2026-11-10-wiki-audit-429-all-targets-skipped.md`, `systems/hermes-hq-push.md`,
|
||||
`systems/scheduled-tasks.md`, `current-state.md`, `index.md`, `log.md`, `systems/skills-index.md`
|
||||
(regenerated). **No page deleted, no decision reversed, no secret written.**
|
||||
|
||||
Reference in New Issue
Block a user