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:
+44
-5
@@ -3,16 +3,55 @@ title: Current State
|
||||
type: concept
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
review_after: 2026-11-12
|
||||
updated: 2026-11-13
|
||||
verified_on: 2026-11-13
|
||||
review_after: 2026-11-13
|
||||
confidence: high
|
||||
tags: [system]
|
||||
sources: [live-cron-list, live-sqlite-cron-executions, live-sqlite-sessions, live-probe, live-executions-db, live-cron-incidents, live-deliveries-db, live-sessions-db]
|
||||
---
|
||||
|
||||
# Current State
|
||||
Updated: 2026-11-11
|
||||
Updated: 2026-11-13
|
||||
|
||||
## Recent Changes (2026-11-12, nightly audit; live probes 2026-11-12 23:59 – 2026-11-13 00:4x AWST)
|
||||
|
||||
**Clean day. The estate is incident-clean, and the only open item is an upgrade that cannot be installed.**
|
||||
|
||||
- **The last open incident closed itself.** `cbfe43_ed01845310d8` (the 2026-11-10 audit's 429,
|
||||
[[incidents/2026-11-10-wiki-audit-429-all-targets-skipped]]) 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 configuration produced this; the pool's
|
||||
reset at ≈ 06:36:57 on 11-11 did, and the 07:0x cohort confirmed it.
|
||||
- **State reads:** fleet **29 (26 enabled / 3 disabled)** — unchanged for a seventh window.
|
||||
Ledger — **2026-11-11: 172 rows, 172 `completed` / 0 `failed`**; **2026-11-12: 176 rows, 175 `completed`
|
||||
/ 0 `failed` / 1 `running`** (this audit); **2026-11-13 so far: 7 / 7 `completed`**. **Deliveries 11-11:
|
||||
7 / 7 `delivered`; 11-12: 9 / 9 `delivered`, 0 `for_failure`.** Executions retention floor
|
||||
`2026-11-07T00:00:42`, max `2026-11-13T00:30:55`, **1,001 rows** in the table.
|
||||
- **New open item — a refused upgrade, not a failure.** The attempt to take **`hermes-hq-push`** past its
|
||||
installed **0.9.42** was **blocked by the pre-install plugin security scan**:
|
||||
*"Blocked (dangerous verdict, 1 critical of 39 findings (echo_pipe_exec))"*, and *"--force does not
|
||||
override a dangerous verdict."* The critical is the plugin's **own** `skills/dashboard-tile/SKILL.md`
|
||||
one-liner (`echo '<json>' | python3 …` = obfuscation). Verified in source: **there is no per-verdict
|
||||
override anywhere** — `plugins.scan_on_install: false` disables scanning for *every* future install, and
|
||||
the plugin guard hardcodes `trust_level="community"` (the skills-side allowlist machinery is not read by
|
||||
it). Installed copy 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` is **read-only** upstream.
|
||||
→ [[incidents/2026-11-12-hq-push-upgrade-blocked-by-plugin-scan]]
|
||||
- **Config untouched and consistent.** Live `config.yaml` is **byte-identical to the
|
||||
2026-11-12 18:14:52 snapshot** (565,433 B). The only drift since **11-09** is the **model catalogue
|
||||
block** (lines 1916-1941): 6 models removed, 9 added. No unrelated settings moved.
|
||||
- **The "stored hold-and-ask instruction" is not stored.** The alleged standing rule about plugin
|
||||
security-scan warnings was hunted exhaustively — a recursive sweep of `~/.hermes` (**184,716 files**,
|
||||
generated/venv/browser-profile trees excluded) found **zero matches in any editable text file**; the
|
||||
sentence exists only in `state.db` **conversation history** (58 rows). **Nothing was removed, nothing
|
||||
was reverted** — there was no persisted policy to undo. Procedure recorded as the skill
|
||||
`stored-instruction-search-and-removal`; installed skills **299 → 300**.
|
||||
- **The recurring pre-dispatch-filter signature was re-confirmed** on a *second* job and a *second* pin by
|
||||
the 2026-11-12 03:00 stocktake — still no failover for the free-tier cohort
|
||||
([[incidents/2026-10-21-omniroute-pre-dispatch-filter-skip]]).
|
||||
|
||||
## Recent Changes (2026-11-11, nightly audit; live probes 2026-11-11 23:59 – 2026-11-12 00:1x AWST)
|
||||
|
||||
@@ -24,7 +63,7 @@ Updated: 2026-11-11
|
||||
`RuntimeError: HTTP 429: Service temporarily unavailable: all targets were skipped by pre-dispatch
|
||||
filters (credits 100% conn:3021bab6) reset after 6h 24m 31s` — **6 candidates, `attempted 0`**, tenant
|
||||
`tn-5ud77abtl1` quota exceeded. Row `cbfe43_ed01845310d8` (`rate_limit`) was raised at 00:12:28 but
|
||||
**`alerted_at: NULL`, `closed_at: NULL` — it is the estate's only open incident row**. Pool reset
|
||||
**`alerted_at: NULL` — it was the estate's only open incident row; it has since closed `resolved` at 2026-11-12T00:25:36 (0 of 137 unclosed)**. Pool reset
|
||||
≈ **06:36:57**; the 07:0x cohort ran clean.
|
||||
⇒ **The 2026-11-10 window was never audited.** This audit covers two windows.
|
||||
- **State reads:** fleet **29 (26 enabled / 3 disabled)**; **non-clean `last_status` 2** (was 1) —
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: Wiki Audit — Nightly Died on Its Own 429 — the 2026-11-10 Window Was Never Audited
|
||||
type: incident
|
||||
status: open
|
||||
status: resolved
|
||||
created: 2026-11-11
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
updated: 2026-11-12
|
||||
verified_on: 2026-11-12
|
||||
review_after: 2026-12-11
|
||||
confidence: high
|
||||
tags: [cron, incident, omniroute, rate-limit, audit]
|
||||
@@ -43,18 +43,36 @@ The three log lines from the run's own session `local-1000c1a3…` show the shap
|
||||
- The **same tenant** (`tn-5ud77abtl1`) appears in the `quota exceeded` line, so this is an
|
||||
account-level quota fault on the router, not a single-model lockout.
|
||||
|
||||
## Incident row — raised, never alerted, still open
|
||||
## Incident row — raised, never alerted, closed `resolved` 2026-11-12T00:25:36
|
||||
|
||||
`cbfe43_ed01845310d8` — `job_id cbfe434a3b5e`, `failure_type: rate_limit`, state **`detected`**,
|
||||
`alerted_at: NULL`, `acked_at: NULL`, `closed_at: NULL`, opened **2026-11-11T00:12:28.578435+08:00**
|
||||
(`first_seen_at` = `last_seen_at` = that instant — seen exactly once).
|
||||
|
||||
- It is the **only open row** in `cron_incidents` — the table held **135** rows at audit time and **137**
|
||||
- It **was** the only open row in `cron_incidents` — the table held **135** rows at audit time and **137**
|
||||
by the end of this run. `acked_at` is **NULL** as well as `alerted_at`, so nothing was told and
|
||||
nothing was acknowledged. The previous open item,
|
||||
`5fc292_773822455856`, closed `resolved` at **2026-11-11T08:03:47.644226**.
|
||||
- So the estate's single outstanding incident is **the audit's own failure**, and nothing was told
|
||||
about it.
|
||||
- So the estate's single outstanding incident **was** the audit's own failure, and nothing was told
|
||||
about it. ⚠ **Superseded 2026-11-12** — the row closed `resolved` at **2026-11-12T00:25:36.133387+08:00**;
|
||||
*cron_incidents* now holds **0 unclosed of 137**. See *Resolution* below.
|
||||
|
||||
## Resolution — 2026-11-12T00:25:36, self-cleared
|
||||
|
||||
The row closed **`resolved`** at **2026-11-12T00:25:36.133387+08:00**, at the end of the **next** slot of
|
||||
the same job: `cbfe434a3b5e` ran **2026-11-11T23:59:54.486572 → 2026-11-12T00:25:36.133387 = 25 m 42 s**
|
||||
and completed. Its delivery carried **both windows**, so 2026-11-10's day was reconciled a day late
|
||||
rather than never (the recovery record is the `audit(2026-11-11)` commit series at 2026-11-12 00:1x-00:24).
|
||||
|
||||
Nothing was repaired to make this happen: the pool's own reset at ≈ **2026-11-11 06:36:57** restored the
|
||||
dispatch path, exactly as the `reset after 6h 24m 31s` field predicted, and the 07:0x cohort ran clean.
|
||||
`cron_incidents` now reads **0 unclosed of 137** rows — the estate is incident-clean as of 2026-11-12.
|
||||
|
||||
**The recurrence risk is unchanged.** The same *"all targets were skipped by pre-dispatch filters"*
|
||||
signature was found again on a **second job and a second pin** by the 2026-11-12 03:00 stocktake
|
||||
([[incidents/2026-10-21-omniroute-pre-dispatch-filter-skip]]), and every model-calling job still rides
|
||||
`custom:omni-101` with no failover for the free-tier cohort. Closing this row proves the guard
|
||||
self-heals; it is not evidence the guard is gone.
|
||||
|
||||
## Impact
|
||||
|
||||
@@ -79,7 +97,8 @@ The three log lines from the run's own session `local-1000c1a3…` show the shap
|
||||
## Fix Applied
|
||||
|
||||
**None — this is a detection-and-verification record.** No configuration changed this window. The run's
|
||||
own recovery was the pool reset at ≈ 06:36:57 on 2026-11-11.
|
||||
own recovery was the pool reset at ≈ 06:36:57 on 2026-11-11, and the incident row closed on the next
|
||||
slot's clean completion (2026-11-12T00:25:36).
|
||||
|
||||
## Prevention
|
||||
|
||||
|
||||
@@ -0,0 +1,98 @@
|
||||
---
|
||||
title: hermes-hq-push 0.9.47+ — Upgrade Refused by the Plugin Security Scan (dangerous verdict)
|
||||
type: incident
|
||||
status: open
|
||||
created: 2026-11-13
|
||||
updated: 2026-11-13
|
||||
verified_on: 2026-11-13
|
||||
review_after: 2026-12-13
|
||||
confidence: high
|
||||
tags: [plugins, security-scan, hq-push, plugin-guard, install, incident]
|
||||
sources: [live-hermes-plugins-list, live-plugin-manifest, live-config, live-plugin-guard-source, live-gh-pr, live-state-db]
|
||||
---
|
||||
|
||||
# hermes-hq-push 0.9.47+ — Upgrade Refused by the Plugin Security Scan (2026-11-12)
|
||||
|
||||
**The scan did its job and there is no way to overrule it.** On 2026-11-12 (~17:38–18:29 AWST) the
|
||||
attempt to take [[systems/hermes-hq-push]] past its installed **0.9.42** was refused before any file
|
||||
was written, by the pre-install plugin security scan. The installed copy is untouched, still `enabled`,
|
||||
and still delivering. The blocking finding is in the plugin's **own** `dashboard-tile` skill, and the
|
||||
fix is sitting in an open pull request.
|
||||
|
||||
## What happened
|
||||
|
||||
| Field | Value |
|
||||
|---|---|
|
||||
| Attempted | `hermes plugins install mrcharlesiv/hermes-hq-plugins/hermes-hq-push --enable --force` |
|
||||
| Refusal | `Blocked: Security scan blocked plugin install: Blocked (dangerous verdict, 1 critical of 39 findings (echo_pipe_exec)). --force does not override a dangerous verdict.` |
|
||||
| Findings | **39 total — 1 critical**, the rest low/medium |
|
||||
| Sole critical | `hermes-hq-push/skills/dashboard-tile/SKILL.md:41` — category *obfuscation*: the `echo '<json>' \| python3 …` one-liner |
|
||||
| Verdict logic | **any** critical ⇒ `dangerous` = hard block; medium/low alone ⇒ `caution` (installable, warned) |
|
||||
| Installed after | **unchanged** — `v0.9.42`, tree mtime **2026-11-08 02:19**, `enabled`, state `user` |
|
||||
|
||||
## Why no override was available (verified in source, not assumed)
|
||||
|
||||
- **The only config key is `plugins.scan_on_install`** (default `true`; currently **not set** in
|
||||
`~/.hermes/config.yaml`, so scanning is on). Setting it `false` disables the scan for **every** future
|
||||
install — it does not overrule a verdict, it blinds the check. That is the wrong lever.
|
||||
- **`--force` lifts `caution` only.** Its own refusal text says so, and the code agrees. `--allow-removed`
|
||||
is unrelated — it is the blocklist for catalogue removals.
|
||||
- **No env var, no trusted-source list, no allowlist, no `INSTALL_POLICY`/`trust_level` for plugins.**
|
||||
Those mechanisms exist only in `tools/skills_guard.py`, reachable from the *skills* path
|
||||
(`skills.guard_agent_created`). `tools/plugin_guard.py:398` hardcodes `trust_level="community"` and
|
||||
`should_allow_plugin_install` never reads it.
|
||||
- **The block is a single unconditional branch** at `tools/plugin_guard.py:406-418`: any verdict outside
|
||||
`safe`/`caution` returns `False, "Blocked (dangerous verdict, …)"`.
|
||||
|
||||
## The fix, and why it is not merged
|
||||
|
||||
The critical is a *pattern* match, not a defect: the tile skill embedded its JSON payload in a shell
|
||||
one-liner, which the scanner reads as obfuscation however benign the intent.
|
||||
|
||||
| Field | Value |
|
||||
|---|---|
|
||||
| Repo / PR | `mrcharlesiv/hermes-hq-plugins` **#2** — the repo's **only** open PR |
|
||||
| Author | `Tony0410` (Anthony) |
|
||||
| Head | fork `Tony0410/hermes-hq-plugins`, branch `fix/tile-skill-heredoc` → base `main` |
|
||||
| State | **OPEN**, `mergedAt: null`, `mergeable: MERGEABLE`, created 2026-11-12T10:00:01Z (updated 10:01:57Z) |
|
||||
| Diff | **+7 / −2 in one file** — `hermes-hq-push/skills/dashboard-tile/SKILL.md` (the one-liner becomes a heredoc) |
|
||||
| Local clone | `/home/hermes/workspace/hq-plugins-fix` (commit `90c9d28`, branch checked out, clean) |
|
||||
|
||||
The `gh` CLI on this host is authenticated as **`Tony0410` with read-only access** to
|
||||
`mrcharlesiv/hermes-hq-plugins`, so the change had to travel fork → PR rather than as a branch push.
|
||||
|
||||
## Impact
|
||||
|
||||
- **The upgrade path to 0.9.47+ is blocked** until PR #2 merges upstream and the plugin is re-installed.
|
||||
Nothing else in the estate is affected.
|
||||
- **No app-side impact:** the installed 0.9.42 keeps delivering to the Hermes HQ iPhone app; the refusal
|
||||
happened before any file was replaced, so there is no half-installed state to clean up.
|
||||
- The block is **fail-safe by design** — the failure mode is "cannot upgrade", not "installed something
|
||||
unchecked".
|
||||
|
||||
## Related finding — the "stored hold-and-ask instruction" was never stored
|
||||
|
||||
The same evening, the alleged standing instruction to *hold and ask before acting on* plugin
|
||||
security-scan warnings was searched for exhaustively: a recursive sweep of `~/.hermes`
|
||||
(**184,716 files**, generated/venv/browser-profile/SQLite trees excluded) for the phrases
|
||||
`wait for my answer`, `show me what it found`, `security scan flags` and `security-scan` found **zero
|
||||
matches in any editable text file**. The sentence exists only in `state.db` **conversation history**
|
||||
(58 rows). **Nothing was removed and no policy was reverted**, because no such policy was ever
|
||||
persisted. Procedure recorded as the skill `stored-instruction-search-and-removal`.
|
||||
|
||||
## Prevention / how this closes
|
||||
|
||||
- **Merge PR #2**, then re-run the install. That is the whole fix.
|
||||
- If a standing exception is ever genuinely wanted, **add an explicit trusted-source or allowlist path to
|
||||
`tools/plugin_guard.py`** — do **not** set `plugins.scan_on_install: false`. Turning the scan off is
|
||||
not "allowing this plugin"; it is removing the check from every future install, including the ones
|
||||
nobody is looking at.
|
||||
- Expect the same class of false positive again: any plugin shipping a shell one-liner that pipes JSON
|
||||
into an interpreter will read as *obfuscation*. Author the pattern as a heredoc or a script file.
|
||||
|
||||
## Related
|
||||
|
||||
- [[systems/hermes-hq-push]]
|
||||
- [[systems/hermes-agent]]
|
||||
- [[systems/scheduled-tasks]]
|
||||
- [[log]]
|
||||
@@ -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.**
|
||||
|
||||
@@ -0,0 +1,147 @@
|
||||
# Wiki freshness audit — 2026-11-13
|
||||
Threshold: >21 days since `updated`
|
||||
|
||||
## STALE (0)
|
||||
|
||||
|
||||
## FRESH (131)
|
||||
|
||||
- [ 2d] CONTRIBUTING.md
|
||||
- [ 5d] agents/hermes-chaos.md
|
||||
- [ 5d] agents/hermes-production.md
|
||||
- [ 2d] agents/index.md
|
||||
- [ 15d] agents/nanobot.md
|
||||
- [ 2d] agents/open-claw.md
|
||||
- [ 9d] agents/qwenpaw.md
|
||||
- [ 2d] agents/zeroclaw.md
|
||||
- [ 15d] comparisons/camoufox-vs-chrome.md
|
||||
- [ 2d] comparisons/hermes-vs-nanobot.md
|
||||
- [ 2d] comparisons/memory-backends.md
|
||||
- [ 2d] comparisons/model-routers.md
|
||||
- [ 15d] comparisons/steel-vs-camoufox.md
|
||||
- [ 2d] concepts/agent-memory.md
|
||||
- [ 15d] concepts/browser-automation.md
|
||||
- [ 2d] concepts/model-routing.md
|
||||
- [ 2d] concepts/persistent-shells.md
|
||||
- [ 2d] concepts/tool-calling.md
|
||||
- [ 0d] current-state.md
|
||||
- [ 15d] decisions/index.md
|
||||
- [ 2d] decisions/keep-openrouter-as-fallback.md
|
||||
- [ 2d] decisions/persistent-shell-enabled.md
|
||||
- [ 15d] decisions/rollback-steel-to-camofox.md
|
||||
- [ 2d] experiments/index.md
|
||||
- [ 1d] incidents/2026-07-29-mnemosyne-relay.md
|
||||
- [ 2d] incidents/2026-08-01-mnemosyne-capture-failure.md
|
||||
- [ 1d] incidents/2026-08-04-omniroute-free-deepseek-silent-stops.md
|
||||
- [ 6d] incidents/2026-08-08-gitea-config-backup-push-dead.md
|
||||
- [ 8d] incidents/2026-08-15-skills-index-drift.md
|
||||
- [ 9d] incidents/2026-08-18-mnemosyne-capture-pipeline.md
|
||||
- [ 1d] incidents/2026-08-26-work-outlook-basic-auth-disabled.md
|
||||
- [ 2d] incidents/2026-08-29-gmail-read-state.md
|
||||
- [ 1d] incidents/2026-09-02-sftpgo-outage.md
|
||||
- [ 9d] incidents/2026-09-28-hermes-managed-runtime-deps.md
|
||||
- [ 15d] incidents/2026-10-01-cliproxy-connection-auth-expired.md
|
||||
- [ 18d] incidents/2026-10-03-ct450-hermes-update.md
|
||||
- [ 18d] incidents/2026-10-03-mnemosyne-vector-recall-fts-only.md
|
||||
- [ 15d] incidents/2026-10-05-dead-model-pin-repin.md
|
||||
- [ 20d] incidents/2026-10-09-cron-provider-timeout-storm.md
|
||||
- [ 12d] incidents/2026-10-09-memory-recall-relevance.md
|
||||
- [ 7d] incidents/2026-10-14-omniroute-node-connection-refused-storm.md
|
||||
- [ 17d] incidents/2026-10-16-omniroute-503-resource-pressure.md
|
||||
- [ 3d] incidents/2026-10-18-degenerate-stream-canned-substitute.md
|
||||
- [ 17d] incidents/2026-10-20-gateway-unclean-exit-orphaned-run.md
|
||||
- [ 1d] incidents/2026-10-21-omniroute-pre-dispatch-filter-skip.md
|
||||
- [ 19d] incidents/2026-10-22-conduit-memory-start-timeout.md
|
||||
- [ 2d] incidents/2026-10-22-nous-portal-refresh-token-invalid.md
|
||||
- [ 18d] incidents/2026-10-24-conduit-call-request-refused.md
|
||||
- [ 18d] incidents/2026-10-25-gmail-digest-runaway-and-refire.md
|
||||
- [ 16d] incidents/2026-10-26-planned-restart-orphaned-cron-run.md
|
||||
- [ 14d] incidents/2026-10-27-job-radar-budget-exhausted.md
|
||||
- [ 14d] incidents/2026-10-28-job-radar-stage1-iteration-cap.md
|
||||
- [ 14d] incidents/2026-10-29-conduit-voice-silence.md
|
||||
- [ 13d] incidents/2026-10-30-ct460-host-outage-scheduler-gap.md
|
||||
- [ 14d] incidents/2026-10-30-m93p-nfs-mount-loss-lxc-boot-failure.md
|
||||
- [ 13d] incidents/2026-10-30-mnemosyne-health-monitor-paused.md
|
||||
- [ 12d] incidents/2026-10-31-asana-access-failures.md
|
||||
- [ 12d] incidents/2026-10-31-conduit-voice-local-mode-not-applying.md
|
||||
- [ 12d] incidents/2026-10-31-gateway-reload-force-drain-orphaned-run.md
|
||||
- [ 11d] incidents/2026-11-01-cron-worker-sigterm-orphaned-claims.md
|
||||
- [ 10d] incidents/2026-11-01-weekly-review-lost-to-gateway-handoff-failure.md
|
||||
- [ 9d] incidents/2026-11-02-job-radar-stage1-iteration-cap-recurrence.md
|
||||
- [ 7d] incidents/2026-11-03-job-radar-stream-active-timeout.md
|
||||
- [ 7d] incidents/2026-11-04-upstream-stream-failure-0700-cohort.md
|
||||
- [ 8d] incidents/2026-11-04-vzdump-freeze-ct299-sftpgo-outage.md
|
||||
- [ 4d] incidents/2026-11-05-secrets-at-rest-in-mnemosyne-and-cron-prompts.md
|
||||
- [ 8d] incidents/2026-11-05-skills-index-generator-divergence.md
|
||||
- [ 6d] incidents/2026-11-06-job-radar-concurrent-fire-claim-discard.md
|
||||
- [ 4d] incidents/2026-11-07-cron-claim-loss-in-gateway-restart-drain.md
|
||||
- [ 4d] incidents/2026-11-08-pre-tool-call-hook-timeout-cascade.md
|
||||
- [ 2d] incidents/2026-11-09-job-radar-stage1-stall-silent-noop.md
|
||||
- [ 2d] incidents/2026-11-09-stocktake-completes-with-zero-edits.md
|
||||
- [ 1d] incidents/2026-11-10-wiki-audit-429-all-targets-skipped.md
|
||||
- [ 0d] incidents/2026-11-12-hq-push-upgrade-blocked-by-plugin-scan.md
|
||||
- [ 1d] index.md
|
||||
- [ 6d] infrastructure/backups.md
|
||||
- [ 2d] infrastructure/credentials-map.md
|
||||
- [ 6d] infrastructure/docker-services.md
|
||||
- [ 2d] infrastructure/domains-and-tunnels.md
|
||||
- [ 6d] infrastructure/hosts.md
|
||||
- [ 6d] infrastructure/network-map.md
|
||||
- [ 6d] infrastructure/proxmox.md
|
||||
- [ 1d] infrastructure/tailscale.md
|
||||
- [ 9d] queries/retained-research-answers.md
|
||||
- [ 19d] reports/communities-wa-social-media-audit-2026.md
|
||||
- [ 12d] reports/uber-eats/2026-07.md
|
||||
- [ 12d] reports/uber-eats/2026-08.md
|
||||
- [ 12d] reports/uber-eats/2026-09.md
|
||||
- [ 12d] reports/uber-eats/2026-10.md
|
||||
- [ 12d] reports/uber-eats/index.md
|
||||
- [ 2d] runbooks/backup-wiki.md
|
||||
- [ 2d] runbooks/diagnose-docker.md
|
||||
- [ 2d] runbooks/gateway-resource-resilience.md
|
||||
- [ 6d] runbooks/job-radar.md
|
||||
- [ 2d] runbooks/multiplexer-setup.md
|
||||
- [ 18d] runbooks/provider-health.md
|
||||
- [ 15d] runbooks/recover-docker-service.md
|
||||
- [ 2d] runbooks/restart-browser.md
|
||||
- [ 2d] runbooks/restart-hermes.md
|
||||
- [ 2d] runbooks/restore-openrouter.md
|
||||
- [ 2d] runbooks/test-openrouter.md
|
||||
- [ 2d] runbooks/troubleshoot-tool-loop.md
|
||||
- [ 18d] runbooks/update-hermes-safely.md
|
||||
- [ 5d] systems/browser-backend.md
|
||||
- [ 2d] systems/cloudflare-tunnel.md
|
||||
- [ 4d] systems/conduit.md
|
||||
- [ 18d] systems/current-profile.md
|
||||
- [ 2d] systems/guanaco.md
|
||||
- [ 2d] systems/headless-server.md
|
||||
- [ 4d] systems/hermes-agent.md
|
||||
- [ 0d] systems/hermes-hq-push.md
|
||||
- [ 2d] systems/hermes-ui.md
|
||||
- [ 9d] systems/home-assistant.md
|
||||
- [ 14d] systems/homepage-dashboard.md
|
||||
- [ 9d] systems/ignis.md
|
||||
- [ 18d] systems/memory-backend.md
|
||||
- [ 11d] systems/messaging-integrations.md
|
||||
- [ 4d] systems/mnemosyne.md
|
||||
- [ 18d] systems/model-providers.md
|
||||
- [ 9d] systems/nanobot.md
|
||||
- [ 2d] systems/nextcloud.md
|
||||
- [ 2d] systems/obsidian.md
|
||||
- [ 3d] systems/omniroute.md
|
||||
- [ 2d] systems/opencode-go.md
|
||||
- [ 2d] systems/openrouter.md
|
||||
- [ 9d] systems/paseo.md
|
||||
- [ 3d] systems/push-notifications.md
|
||||
- [ 0d] systems/scheduled-tasks.md
|
||||
- [ 0d] systems/skills-index.md
|
||||
- [ 2d] systems/terminal-backend.md
|
||||
- [ 2d] systems/tool-search.md
|
||||
|
||||
## NO updated DATE (3)
|
||||
|
||||
- SCHEMA.md
|
||||
- experiments/active/example.md
|
||||
- log.md
|
||||
|
||||
TOTAL: 0 stale, 131 fresh, 3 no-date of 134 pages
|
||||
@@ -3,9 +3,9 @@ title: hermes-hq-push (Hermes HQ iPhone app plugin)
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-11-04
|
||||
updated: 2026-11-08
|
||||
verified_on: 2026-11-08
|
||||
review_after: 2026-12-08
|
||||
updated: 2026-11-13
|
||||
verified_on: 2026-11-13
|
||||
review_after: 2026-12-13
|
||||
confidence: medium
|
||||
tags: [push, notifications, plugins, ios, desktop, device-access]
|
||||
sources: [live-hermes-plugins-list, live-plugin-manifest, live-config]
|
||||
@@ -16,18 +16,18 @@ sources: [live-hermes-plugins-list, live-plugin-manifest, live-config]
|
||||
## What it is
|
||||
|
||||
`hermes-hq-push` is a **standalone Hermes plugin** (`kind: standalone`, **v0.9.42**, author *Hermes HQ*)
|
||||
living at `~/.hermes/plugins/hermes-hq-push/` (tree mtime **2026-11-07 06:42**, reinstalled 0.9.27 → 0.9.42). It is the host-side half
|
||||
living at `~/.hermes/plugins/hermes-hq-push/` (tree mtime **2026-11-08 02:19**, reinstalled 0.9.27 → 0.9.42). It is the host-side half
|
||||
of the **Hermes HQ iPhone app**: Apple push, phone device access, the desktop-app theme, the app's Terminal
|
||||
page, and Grok Live voice token minting.
|
||||
|
||||
Its own manifest states it **replaces `dispatch-push`**, and that *"its registered phones carry over."*
|
||||
|
||||
## Verified state (2026-11-04)
|
||||
## Verified state (2026-11-13)
|
||||
|
||||
| Check | Result |
|
||||
|---|---|
|
||||
| `hermes plugins list` | `hermes-hq-push` — **enabled**, `0.9.27`, state `user` |
|
||||
| `config.yaml` → `plugins.enabled` | line **7556**: `- hermes-hq-push` |
|
||||
| `hermes plugins list` | `hermes-hq-push` — **enabled**, `0.9.42`, state `user` |
|
||||
| `config.yaml` → `plugins.enabled` | line **13226** (block opens line 13210; the number drifts with every catalogue write): `- hermes-hq-push` |
|
||||
| `~/.hermes/plugins/dispatch-push/` | **absent** — and no `dispatch-push` reference survives in `config.yaml` |
|
||||
| live tree | `~/.hermes/plugins/hermes-hq-push/` (module files + `dashboard/` subdir + its own test suite) |
|
||||
| README | none — the manifest `description` is the only prose |
|
||||
@@ -111,8 +111,37 @@ No key material is recorded on this page and none appears in the manifest — th
|
||||
- No app-side fault was recorded on 2026-11-07. Push delivery, device access and Grok Live minting were not
|
||||
re-exercised end-to-end by this audit — the version/route claim is the verified part.
|
||||
|
||||
## 2026-11-12 — the upgrade past 0.9.42 was refused by the security scan
|
||||
|
||||
An attempt to install a later build (`… --enable --force`) never wrote a file: the **pre-install plugin
|
||||
security scan** returned
|
||||
|
||||
> `Blocked: Security scan blocked plugin install: Blocked (dangerous verdict, 1 critical of 39 findings (echo_pipe_exec)). --force does not override a dangerous verdict.`
|
||||
|
||||
- The **sole critical** is this plugin's own `skills/dashboard-tile/SKILL.md:41` — the
|
||||
`echo '<json>' | python3 …` one-liner, flagged as *obfuscation*. The other **38 findings are
|
||||
low/medium** and would have been installable as `caution`.
|
||||
- **`--force` cannot help.** It lifts `caution` only; a `dangerous` verdict is an unconditional block
|
||||
(`tools/plugin_guard.py:406-418`). And **no per-verdict override exists** — the only config key is
|
||||
`plugins.scan_on_install` (default `true`, currently unset), which switches scanning off for **every**
|
||||
future install rather than allowing this one. There is no plugin trusted-source list; the
|
||||
`trust_level`/allowlist machinery lives in `tools/skills_guard.py` (the *skills* path) and is not read
|
||||
by `plugin_guard.py`.
|
||||
- **Installed state is unchanged and healthy:** `v0.9.42`, `enabled`, still delivering.
|
||||
- **The fix is PR #2** on `mrcharlesiv/hermes-hq-plugins` (author `Tony0410`, branch
|
||||
`fix/tile-skill-heredoc` → `main`, **OPEN / MERGEABLE**, `mergedAt: null`, **+7 / −2 in one file**),
|
||||
pushed from a fork because this host's `gh` account has **read-only** access to that repo. The
|
||||
diff rewrites the one-liner as a heredoc. A local clone with the commit lives at
|
||||
`/home/hermes/workspace/hq-plugins-fix`.
|
||||
|
||||
Full record: [[incidents/2026-11-12-hq-push-upgrade-blocked-by-plugin-scan]].
|
||||
|
||||
## Open
|
||||
|
||||
- **Blocked upgrade (2026-11-12):** past-0.9.42 installs are refused by the security scan until PR #2
|
||||
merges upstream and the plugin is reinstalled. Workaround is *not* to disable the scan.
|
||||
- The plugin's own skill files must avoid shell one-liners that pipe into an interpreter (`echo … |
|
||||
python3`) — that pattern alone trips the scanner's obfuscation rule.
|
||||
- `~/.hermes/hq-logs` retention is not documented anywhere yet — check its growth before it becomes a disk
|
||||
item.
|
||||
- The plugin carries a very large surface under one name; if it misbehaves the manifest `description` is the
|
||||
|
||||
@@ -3,9 +3,9 @@ title: Scheduled Tasks
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
review_after: 2026-11-12
|
||||
updated: 2026-11-13
|
||||
verified_on: 2026-11-13
|
||||
review_after: 2026-11-13
|
||||
confidence: high
|
||||
tags: [cron, scheduled, automation]
|
||||
sources: [live-cron-list, live-jobs-json, cron-executions-db, live-executions-db, live-deliveries-db, live-sessions-db]
|
||||
@@ -14,6 +14,18 @@ sources: [live-cron-list, live-jobs-json, cron-executions-db, live-executions-db
|
||||
# Scheduled Tasks
|
||||
|
||||
## Count
|
||||
- **Current as of 2026-11-12 (window 2026-11-11 23:59 → 2026-11-12 23:59; nightly audit).** **A clean day
|
||||
— and an upgrade that could not happen.** Fleet **29 (26 enabled / 3 disabled)**, a seventh consecutive
|
||||
window at the same count. Ledger — **2026-11-11: 172 rows, 172 `completed` / 0 `failed`**;
|
||||
**2026-11-12: 176 rows, 175 `completed` / **0 `failed`** / 1 `running`** (this audit, started
|
||||
23:59:54) — the **second consecutive zero-`failed` day**. **Deliveries 11-11: 7 rows, 7 / 7 `delivered`;
|
||||
11-12: 9 rows, 9 / 9 `delivered`, 0 `for_failure`.** **Unclosed incident rows: 0 of 137** — the 429 row
|
||||
that had been the estate's only open incident ([[incidents/2026-11-10-wiki-audit-429-all-targets-skipped]])
|
||||
closed **`resolved` at 2026-11-12T00:25:36** on the next slot's clean completion. The window's one new
|
||||
open item is not a job at all: the `hermes-hq-push` upgrade was refused by the plugin security scan
|
||||
([[incidents/2026-11-12-hq-push-upgrade-blocked-by-plugin-scan]]). `config.yaml` is **byte-identical to
|
||||
its 2026-11-12 18:14:52 backup** (565,433 B); the only drift since the 11-09 snapshot is the **model
|
||||
catalogue block** (lines 1916-1941 — 6 entries removed, 9 added).
|
||||
- **Current as of 2026-11-11 (window 2026-11-10 23:59 → 2026-11-11 23:59; nightly audit).**
|
||||
**Fleet 29 (26 enabled / 3 disabled)** — unchanged for a sixth window. Three states moved, and the
|
||||
observer itself is the story. **`cbfe434a3b5e` (Wiki Audit — Nightly) failed on its own 429** —
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Installed Skills
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-11-12
|
||||
verified_on: 2026-11-12
|
||||
updated: 2026-11-13
|
||||
verified_on: 2026-11-13
|
||||
confidence: high
|
||||
tags: [skills, hermes]
|
||||
sources: []
|
||||
@@ -12,7 +12,7 @@ sources: []
|
||||
|
||||
# Installed Skills
|
||||
|
||||
**Total installed: 299 skills** in `~/.hermes/skills/`.
|
||||
**Total installed: 300 skills** in `~/.hermes/skills/`.
|
||||
|
||||
- **50 archived skills** are parked under `~/.hermes/skills/.archive/` and are excluded from this count — the loader does not expose them.
|
||||
- The loader's own catalogue (`hermes skills list`, e.g. *34 hub-installed, 52 builtin, N local — N enabled*) is the authoritative loadable figure; this page is a filesystem inventory.
|
||||
@@ -98,7 +98,7 @@ This page is auto-regenerated from the live skill inventory. Do not hand-edit.
|
||||
|
||||
- `ddia-systems` — # Designing Data-Intensive Applications Framework
|
||||
|
||||
## Devops (107)
|
||||
## Devops (108)
|
||||
|
||||
- `abyss-ios-pairing` — # Pair iPhone with The Abyss (iOS)
|
||||
- `agent-extension-audit` — # Agent Extension Audit
|
||||
@@ -193,6 +193,7 @@ This page is auto-regenerated from the live skill inventory. Do not hand-edit.
|
||||
- `sdlc-review` — # SDLC Review Skill
|
||||
- `self-hosted-app-deploy` — # Self-Hosted App Deployment
|
||||
- `solutions-first-agent-conduct` — # Solutions-First Agent Conduct
|
||||
- `stored-instruction-search-and-removal` — # Stored Instruction Search and Removal
|
||||
- `tailscale-ops` — # Tailscale Operations 🦝🔗
|
||||
- `tailscale-serve-route-management` — # Tailscale Serve Route Management
|
||||
- `tailscale-serve-routes` — # Tailscale Serve Route Management
|
||||
|
||||
Reference in New Issue
Block a user