audit 2026-10-24: conduit page + memory-start-timeout incident; 10-09 storm resolved; window 169/0; frontmatter for 2 legacy incident pages
This commit is contained in:
@@ -1107,3 +1107,50 @@ No secrets written; host names, IPs, VMIDs, job/incident IDs, ports and probe st
|
||||
`systems/model-providers.md` (22 d, updated 2026-10-01). The latter needs a review pass against the live
|
||||
OmniRoute catalogue before its next `verified_on`.
|
||||
- **No secrets written.** Job IDs, incident IDs, table names, counts, paths and HTTP status codes only.
|
||||
|
||||
## [2026-10-24] audit | Nightly wiki audit — window 2026-10-23 00:00 → 2026-10-24 00:3x AWST
|
||||
|
||||
- **New page:** `systems/conduit.md` — the Conduit dashboard plugin + iOS app (voice calls, cards,
|
||||
push). Plugin tree `~/.hermes/plugins/conduit_push`, version `0.64.0` (HEAD `eaa14be`, no tags
|
||||
upstream), remote `kaishi00/hermes-conduit-notifier`; gateway on `:9119`; one registered device
|
||||
(iPhone, app `2.0.0`); state/DB files and sizes recorded. Where the wiki previously had no page for
|
||||
the phone surface at all.
|
||||
- **New incident:** [[incidents/2026-10-22-conduit-memory-start-timeout]] — three
|
||||
`Memory provider 'mnemosyne' start for Conduit timed out; abandoning the call` warnings
|
||||
(10-22 11:28:17, 10-22 13:16:37, 10-23 18:29:16) from a hard-coded 10 s `MEMORY_TIMEOUT_S` in the
|
||||
plugin against Mnemosyne's 10–45 s cold start; calls ran without recall. Patched in the working tree
|
||||
to a 60 s default (`CONDUIT_MEMORY_TIMEOUT_S` override) plus a `TokenError` guard that degrades
|
||||
instead of aborting; the dashboard restarted 18:54:43 and **no abort line exists after it** (two
|
||||
calls closed cleanly at 00:03:23 and 00:06:57 on 10-24). **The patch is uncommitted.**
|
||||
- **`incidents/2026-10-09-cron-provider-timeout-storm.md` → `status: resolved`.** Its last two rows
|
||||
(`1b23c0_c35703f637b8`, `1b23c0_103cbe04a79b`, both on `1b23c042e17d`) closed **2026-10-23 08:04**
|
||||
when that weekly job's Friday slot ran clean; the job reads `ok` again. **All 12 rows closed** —
|
||||
this incident no longer contributes an unclosed row anywhere.
|
||||
- **Cron ledger:** window **2026-10-23 closed 169 `completed` / 0 `failed`** (+ this audit `running`) —
|
||||
the third zero-failure day in four; **2026-10-22 settled at 173 / 0**. Fleet **28 jobs (25 enabled /
|
||||
3 disabled)**, unchanged for a sixth audit. **Unclosed incident rows 4 → 2** (`c0a9fa_764558b5ae83`
|
||||
`alerted` since 10-19 — GitHub Trending Radar revoked token, next slot Mon 10-26 09:00; and
|
||||
`0e753e_e7f8194a7d06` `detected` since 10-01, next slot 11-01). **Non-clean `last_status` 5 → 4**
|
||||
(`c0a9fa314542`, `0e753e9720fd`, `fad5a86979d4`, `066bb5191280`). Pins unchanged (11 `omni-101` /
|
||||
`smart-route`, 8 unpinned, 6 `omni-101` / `free-stack`, 2 `custom:omni` / `smart-route`, 1
|
||||
`deepseek-paid-smart` = this audit). **14 sessions:** 13 `cron` + 1 `desktop` (18:26:12, the Conduit
|
||||
phone-call session that exposed the fault above).
|
||||
- **`systems/mnemosyne.md`:** new block recording the 10–45 s cold start and the consumer-timeout rule
|
||||
(a 10 s budget aborts a voice call; consumers need ≥60 s or must degrade to "no recall"). The cold
|
||||
start itself was **not** optimised — only the budget was raised.
|
||||
- **Also updated:** `systems/scheduled-tasks.md` (new Count bullet + `## Re-verified 2026-10-24`
|
||||
section), `current-state.md` (new Recent Changes block; 10-23 block marked superseded), `index.md`
|
||||
(date, new `systems/conduit` and incident lines, refresh of the scheduled-tasks / skills-index /
|
||||
storm blurbs), and **frontmatter added** to `incidents/2026-07-29-mnemosyne-relay.md` and
|
||||
`incidents/2026-08-04-omniroute-free-deepseek-silent-stops.md` — both sat outside the SCHEMA
|
||||
(rule 4: every page has frontmatter).
|
||||
- **Freshness:** 102 pages scanned at the last stocktake; **3 carry a `verified_on` older than 21 days**
|
||||
— `infrastructure/hosts.md`, `runbooks/provider-health.md`, `runbooks/update-hermes-safely.md`
|
||||
(all 94 d, unchanged). **Nothing removed or archived** this cycle: no job retired, no system
|
||||
obsolete, no decision reversed in the window.
|
||||
- **Note (hygiene):** a second, older copy of this wiki sits at `/home/hermes/wiki/agent-estate-wiki`
|
||||
(101 pages, 3 incidents, no git remote, last commit `c798304` "mirror(2026-10-22 maintenance)").
|
||||
It is **not** served — `hermes-wiki-serve.service` serves `public/` from *this* repo — so it is a
|
||||
stale duplicate that will drift. Nothing in the audit depends on it; flagging it rather than
|
||||
syncing it, since no script owns it.
|
||||
- **No secrets written.** Job IDs, incident IDs, table names, counts, paths and HTTP status codes only.
|
||||
|
||||
Reference in New Issue
Block a user