audit(2026-11-01): Conduit updated to 0.122.2 (memory-timeout patch now upstream, call store re-shaped); document the local-voice-mode fault, the force-drained gateway reload that orphaned a cron run, and both dead Asana paths; 2026-10-31 settled 160/4

This commit is contained in:
Tony0410
2026-11-01 00:30:42 +08:00
parent 74a5b2d117
commit 0c826f2b5f
8 changed files with 488 additions and 22 deletions
+52
View File
@@ -1681,3 +1681,55 @@ recorded wrong.**
`incidents/2026-10-30-mnemosyne-health-monitor-paused.md`.
- **Checked, unchanged:** 12 sessions active in-window (longest `local-40472e0b…`, 1,351 messages), no orphaned
`running` rows, no incidents opened or closed after 10-30, no obsolete pages to archive, no secrets written.
## [2026-11-01] audit | Nightly review — Conduit 0.122.2, the Local Live fault, a force-drained reload, dead Asana paths
- **NEW PAGE — [[incidents/2026-10-31-conduit-voice-local-mode-not-applying]].** The app's **"local" voice mode
never applies** even though its connection test succeeds — because the test checks **socket reachability only**.
Every local turn is still impossible: the Mac mini speech server's **LLM proxy is disabled** (LLM endpoint →
**HTTP 501**, *"start the server with `--enable_llm_proxy`"*), `/v1/usage` reads **`llm_proxy.requests: 0`**
across 25 observed turns, and its realtime socket **accepts the connection but rejects `session.update` as an
unknown event**. `voice.mode` is a **phone-side** selector: **no `mode` key exists** in `config.yaml → voice`
or `conduit-settings.json` (whose only device state is `devices/<UUID>/mode: small` ×3), so "the change did not
apply" cannot be diagnosed on host config. Evidence from session `20261031_193709_40b9c2` (started **19:37:09**,
30 msgs / 17 tool calls, still open at the 00:2x reading); `voice.local_live.front_model` was repointed to
`mistral/voxtral-small-latest` mid-session (`config.yaml` mtime **21:02:30**). **Nothing was changed on the
Mac.** ⚠ One misread was caught in-session and is recorded as a lesson: `local_live.py:882` is the **only**
writer of `_local_live_last_request`, inside the chat-completions route — so a "recent `last_request_at`" was
the investigation's **own probe**, not phone traffic (`last_request_at` is `null`).
- **NEW PAGE — [[incidents/2026-10-31-gateway-reload-force-drain-orphaned-run]].** The **18:06:41** gateway reload
waited the **full 1,800 s** drain cap and force-drained at **18:37:38** (new gateway **18:38:43**), orphaning
`ea79a2107e36` (**Mnemosyne Health Monitor**, 12:01:06 slot*, **6 h 38 m 09 s** in) which closed **`failed`** at
**18:39:15** on *"lost its durable fire claim ownership"*. Derivative watchdog reds at 18:39:23 / 18:45:23 /
19:00:22 cleared **19:15:21**. A **second, clean** restart followed at **19:23:39 → 19:24:40**. Same class as
the 10-26 planned-restart orphan — **second instance, first on a plain reload**.
- **NEW PAGE — [[incidents/2026-10-31-asana-access-failures]].** Both Asana paths on CT460 are non-functional:
the MCP server `asana` (`https://mcp.asana.com/v2/mcp`, `auth: oauth`, `enabled: true`) has **never
authenticated** (`~/.hermes/mcp-tokens/` holds only `asana.client.json`, **319 B**, mtime 2026-10-26 01:07;
logs read *"MCP OAuth setup failed for 'asana' … no cached tokens found. Run `hermes mcp login asana`
interactively first"*), and the hosted connector rejects the call shape. The repair needs an **interactive**
login, which cron cannot perform.
- **UPDATED — `systems/conduit.md`** (13,184 → 18,722 B; frontmatter `updated` / `verified_on` → 2026-11-01).
Version `0.69.2` / `942ddb8` → **`0.122.2` / `9eac857`** (10-26 reading kept explicitly superseded); the
⚠ *"uncommitted patch, five releases behind"* warning is **RESOLVED** — the tree is clean and
**`MEMORY_TIMEOUT_S = 10.0` ships upstream** in `dashboard/api/memory.py` (with a `wait_for` backstop and
`tests/test_memory.py`), so the 10-23 in-tree edit is no longer needed; dashboard gateway
`pid 4042003` (10-29 08:03:26) → **`pid 176771` (10-31 19:35:02)**; the **call-store shape change** is recorded
(`v: 1`; **`history` empty**; **`last_request_at: null`**; `ends` = 2 × `outcome: stopped` at 21:06:05 /
21:10:48; `settings.quiet_at_screen: true` = #479); data volume 930.0 MB → **938.2 MB** (983,793,664 B) with
**2,623,879 `events` / 4,384 `buckets` / 504 `windows`** (≈8 MB/day, no retention policy); new dated section;
`Open items` — patch item marked resolved, three new local-live items added.
- **UPDATED — `systems/scheduled-tasks.md`** (same pass): fleet **29 jobs (26 enabled / 3 disabled)**; 2026-10-31
closed **160 / 4**; non-clean `last_status` **4** (2 `error` + 2 `delivery_failed`); failing jobs **1**
(`ea79a2107e36`, `failure_streak` 2); superseded readings marked rather than overwritten.
- **UPDATED — `systems/hermes-agent.md`:** Asana MCP auth-state re-verification note (enabled but never
authenticated) + both 2026-10-31 gateway restarts (18:06:41 force-drain, 19:23:39 → 19:24:40 clean).
- **UPDATED — `index.md`:** frontmatter and banner → **2026-11-01**; Conduit entry (version, patch resolved,
gateway pid, new fault, empty call history); **three new incident entries** added above the 10-30 pair.
- **UPDATED — `log.md`:** this entry.
- **Checked, unchanged:** ship rows before 10-30 (nothing new); `inc_20261031_000001` (gateway-update) is **still
open**, `inc_20261030_000001` closed 2026-10-30 18:05; **3** `deliveries.db` rows for 2026-10-31 carry a
failure error (`child run failed: exit status 1`) — they are the failing runs' own notices, not new faults;
no page archived; **no secrets, tokens, passwords or keys written**.
- **Probes (context, not findings):** `omniroute-1` `100.78.63.20:20128` → **HTTP 200**; `m93p` `100.104.51.98`
and `pve` `100.96.100.82` answered neither ICMP, SSH nor `:8006` from CT460 at the 00:2x reading —
recorded as **unverified reachability from this container**, not as a host outage.