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:
Tony0410
2026-10-24 00:24:44 +08:00
parent 250c73530a
commit 573a4a2434
10 changed files with 384 additions and 23 deletions
+38 -5
View File
@@ -3,18 +3,51 @@ title: Current State
type: concept
status: active
created: 2026-07-22
updated: 2026-10-23
verified_on: 2026-10-23
review_after: 2026-10-30
updated: 2026-10-24
verified_on: 2026-10-24
review_after: 2026-10-31
confidence: high
tags: [system]
sources: [live-cron-list, live-sqlite-cron-executions, live-sqlite-sessions, live-probe]
---
# Current State
Updated: 2026-10-23
Updated: 2026-10-24
## Recent Changes (2026-10-23, nightly audit; live probes 2026-10-23 00:0x–00:16 AWST)
## Recent Changes (2026-10-24, nightly audit; live probes 2026-10-24 00:1x–00:3x AWST)
- **A clean cron day, and the 2026-10-09 timeout storm is finally closed.** Window 2026-10-23:
**169 `completed` / 0 `failed`** (+ this audit `running`) — the third zero-failure day in four;
**2026-10-22 settled at 173 / 0**. `1b23c042e17d` (Enhanced Weekend Adventure Planner, weekly Fri 08:00)
ran clean on its 10-23 slot, closing the storm's **last two incident rows**
(`1b23c0_c35703f637b8`, `1b23c0_103cbe04a79b`) at **08:04** — all 12 rows closed, job `ok` again.
**Unclosed incident rows 4 → 2**, **non-clean `last_status` 5 → 4**, **fleet unchanged at 28 jobs
(25 enabled / 3 disabled)**, pins unchanged. → [[incidents/2026-10-09-cron-provider-timeout-storm]],
[[systems/scheduled-tasks]]
- **New: Conduit is documented.** The dashboard plugin + iOS app that puts Hermes on Anthony's phone
(voice calls, cards, push) now has a system page — plugin tree, version `0.64.0` (HEAD `eaa14be`),
upstream `kaishi00/hermes-conduit-notifier`, gateway on `:9119`, one registered device (iPhone, app
`2.0.0`), its state/DB files and their sizes, and the uncommitted patch it carries.
→ [[systems/conduit]]
- **⚠ New fault, found and fixed in-window: Conduit voice calls were being abandoned by the memory
layer.** The plugin hard-coded a **10 s** budget for one request *including the Mnemosyne provider
start*, while Mnemosyne's cold start for a `conduit-voice` session runs **10–45 s**. Three calls hit it
(10-22 11:28:17, 10-22 13:16:37, 10-23 18:29:16: `Memory provider 'mnemosyne' start for Conduit timed
out; abandoning the call`) and ran **without recall**. Patched in the plugin's working tree to a **60 s**
default (`CONDUIT_MEMORY_TIMEOUT_S` override) plus a `TokenError` guard that proceeds without recall
instead of aborting; the dashboard restarted **18:54:43** and **no abort line exists after it**, with two
calls closing cleanly at 00:03:23 and 00:06:57 on 10-24. **The patch is uncommitted** — a plugin update
reverts it. → [[incidents/2026-10-22-conduit-memory-start-timeout]], [[systems/mnemosyne]]
- **Sessions: 14 in the window** — 13 `cron` + 1 `desktop` (10-23 18:26:12, the phone-call session above);
no other interactive sessions.
- **Stocktake:** the 10-22 sixfold overrun did not repeat — the 10-23 03:07 slot ran and committed
(`250c735`: freshness 2 stale / 94 fresh, skills-index 306). → [[systems/skills-index]]
- **Housekeeping:** frontmatter added to `incidents/2026-07-29-mnemosyne-relay.md` and
`incidents/2026-08-04-omniroute-free-deepseek-silent-stops.md`, both of which sat outside the SCHEMA
(rule 4). Freshness: 102 pages; **3** carry a `verified_on` older than 21 days — `infrastructure/hosts.md`,
`runbooks/provider-health.md`, `runbooks/update-hermes-safely.md` (all 94 d). Nothing removed or archived.
## Recent Changes (2026-10-23, nightly audit; live probes 2026-10-23 00:0x–00:16 AWST) *(superseded by the 2026-10-24 entry above)*
- **First zero-failure cron day in three days, and five incidents cleared at once.** Window 2026-10-22: **172
`completed` / 0 `failed`** (+ this audit `running`); 4 runs had already completed on 10-23 by 00:0x. **Five