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
+51 -10
View File
@@ -3,8 +3,8 @@ title: Conduit
type: system
status: active
created: 2026-10-24
updated: 2026-10-30
verified_on: 2026-10-30
updated: 2026-11-01
verified_on: 2026-11-01
review_after: 2026-11-08
confidence: high
tags: [conduit, plugin, phone, iphone, push, voice, memory, tool-calling, session-ttl]
@@ -36,7 +36,8 @@ Related: [[systems/mnemosyne]] (memory backend the voice session reads), [[syste
## Where it lives
- **Plugin tree:** `/home/hermes/.hermes/plugins/conduit_push`
- **Version (re-verified 2026-10-26):** `0.69.2` (plugin.yaml) / `0.69.2` (dashboard manifest), git HEAD `942ddb8` — *Plugin and relay fixes left over from earlier reviews (0.69.2) (#342)*, committed 2026-10-24 15:35:42 +0000. **0 commits behind `origin/main`**; **24 commits on from the `0.64.0` / `eaa14be` baseline** of the 2026-10-24 audit (upstream `#324`–`#342`: Pulse cards/decisions/journal, a Live Activity messaging tool, contact cards, a self-update gateway restart, `channels.yaml`, App Store builds following the archived plugin version).
- - **Version (re-verified 2026-11-01):** **`0.122.2`** (`plugin.yaml`) — the plugin **updated itself on 2026-10-31 18:05** (`plugin.yaml` mtime) and fetched at **18:19** (`FETCH_HEAD`); git HEAD **`9eac857`**, *"Every profile that turns Conduit on runs the main install (#482)"*, upstream commit **2026-10-31 12:04:31 AWST**. **Working tree clean**; **+148 commits** on from the `0.69.2` reading below (`#342` → `#482`). See the 2026-11-01 section at the foot of this page.
- ⚠ **Superseded (2026-10-26 reading):** `0.69.2` (plugin.yaml) / `0.69.2` (dashboard manifest), git HEAD `942ddb8` — *Plugin and relay fixes left over from earlier reviews (0.69.2) (#342)*, committed 2026-10-24 15:35:42 +0000. **0 commits behind `origin/main`**; **24 commits on from the `0.64.0` / `eaa14be` baseline** of the 2026-10-24 audit (upstream `#324`–`#342`: Pulse cards/decisions/journal, a Live Activity messaging tool, contact cards, a self-update gateway restart, `channels.yaml`, App Store builds following the archived plugin version).
- **⚠ Superseded provenance:** the 2026-10-24 audit read `0.69.0` / `f000bf0`; two further commits landed on
2026-10-24 15:35. Git HEAD was previously recorded as: `- **Version:** `0.69.0` (`plugin.yaml` and `dashboard/manifest.json`), git HEAD `f000bf0` —
*“Pulse: list candidates, decide in code, journal them (#337)”*. **22 commits on from the
@@ -44,7 +45,7 @@ Related: [[systems/mnemosyne]] (memory backend the voice session reads), [[syste
cards/decisions/journal, a Live Activity messaging tool, contact cards, a self-update gateway
restart, `channels.yaml`, App Store builds following the archived plugin version).
- **Upstream:** `https://github.com/kaishi00/hermes-conduit-notifier.git` (origin, fetch+push)
- ⚠ **The working tree still carries the uncommitted local patch** (`M dashboard/plugin_api.py`, the
- ✅ **The uncommitted local patch is GONE — and it landed upstream.** `git status --short` on the 0.122.2 tree is **clean**, and `dashboard/api/memory.py` now ships **`MEMORY_TIMEOUT_S = 10.0`** applied to every provider call with an `asyncio.wait_for(…, MEMORY_TIMEOUT_S + 2.0)` backstop, plus its own `tests/test_memory.py`. So the fix in [[incidents/2026-10-22-conduit-memory-start-timeout]] is **upstream, not lost** — the 10-23 in-tree edit is no longer needed. ⚠ **Superseded:** the working tree still carries the uncommitted local patch (`M dashboard/plugin_api.py`, the
memory-timeout fix in [[incidents/2026-10-22-conduit-memory-start-timeout]]) — now **five releases
behind HEAD** (`0.64.0` → `0.69.0`), so the chance a plugin update resets the tree and drops it is
rising, not falling.
@@ -58,7 +59,7 @@ Related: [[systems/mnemosyne]] (memory backend the voice session reads), [[syste
contents into the wiki**).
## Current state (re-verified 2026-10-30 00:0x AWST)
- **Dashboard gateway:** listening on `0.0.0.0:9119`; **pid 4042003, started 2026-10-29 08:03:26**
- **Dashboard gateway:** listening on `0.0.0.0:9119`; **pid 176771, started 2026-10-31 19:35:02** (4 h 50 m at the 2026-11-01 00:2x probe; `GET /` → 302 to auth) — ⚠ superseded: pid 4042003, started 2026-10-29 08:03:26
— the restart that put the 30-day session TTL live (see below). The `0.64.0` → `0.69.0` upstream
commits remain **not** live (the process predates nothing relevant; the tree still only carries the
memory-timeout patch).
@@ -74,13 +75,13 @@ Related: [[systems/mnemosyne]] (memory backend the voice session reads), [[syste
is a **separate key and still 43200**; check both.
- **Call settings:** `enabled`, `when_asked`, `decides`, `alerts` all true; rate limits
`min_gap_s 120` / `per_hour 6` / `per_day 20`; `avoid_unknown_place` false.
- **Recent calls — two, both 2026-10-29.** `conduit-calls.json → history` now reads **2**
- ⚠ **The call store was re-shaped by 0.122.x: `history` is now EMPTY (0 entries) and `last_request_at` is `null`.** The file is `v: 1` with keys `outcomes` / `delivered` / `told` / `watches` / `waiting` / `seeded` / `ends` / `settings`; `ends` holds **2** turn-end records (both `outcome: stopped`, at **21:06:05** and **21:10:48** on 10-31) and `settings` has gained **`quiet_at_screen: true`** (upstream #479 — alert calls wait while you're at a screen). The two 10-29 calls below are **no longer in the store** — do not cite them as live history. ⚠ **Superseded — recent calls, as recorded on 2026-10-30: two, both 2026-10-29.** `conduit-calls.json → history` now reads **2**
(08:38:04, 08:49:36). The 08:38:04 call produced no Mac connection and no Hermes turn, and the
iPhone re-authenticated at 08:39:05 — the expired-session fault. The 08:49:36 call was placed after
the `classic` mode switch and the STT/TTS fixes, but the session ended one second earlier, so its
outcome is **unrecorded**. The memory-timeout patch therefore still has no *confirmed* call behind
it → [[incidents/2026-10-29-conduit-voice-silence]].
- **Data volume (2026-10-30 00:0x):** `conduit-health.sqlite3` **930.0 MB** (+360 MB in 5 days;
- **Data volume (2026-11-01 00:2x):** `conduit-health.sqlite3` **938.2 MB** (983,793,664 B) holding **2,623,879 `events`**, **4,384 `buckets`**, **504 `windows`** — +8.2 MB and +22,314 events / +279 buckets / +93 windows since the 10-30 reading: growth is steady at **≈8 MB/day** with **no retention policy**. (`conduit-location.sqlite3` 80 KB, mtime 10-31 12:15; `conduit-phone.sqlite3` 296 KB, mtime 10-31 14:54.) The per-kind event split was not re-measured this pass. ⚠ **Superseded (2026-10-30):** **930.0 MB** (+360 MB in 5 days;
+8.2 MB/25.7 h as measured on 10-25 — the rate has not held, so treat growth as **ingestion-paced,
unbounded**), holding **2,601,565 `events`** (2,592,189 `sample` / 6,146 `sleep` / 3,230 `workout`),
**4,105 `buckets`** and **411 `windows`**; newest health row **2026-10-29 23:12:01 AWST**.
@@ -172,15 +173,55 @@ cat ~/.hermes/conduit-link-status.json
ls -la ~/.hermes/conduit-*.json ~/.hermes/conduit-*.sqlite3
```
## 2026-11-01 00:2x AWST — plugin 0.122.2, a re-shaped call store, and the Local Live fault
One night, three changes. The plugin **self-updated to `0.122.2`** at **18:05** on 2026-10-31 and the
gateway reloaded for it at **18:06:41**; the dashboard gateway came back as **pid 176771** at
**19:35:02**; and a voice conversation opened at **19:37:09** reported that the app's **"local" voice
mode never applies** despite a passing connection test.
- **The memory-timeout patch is resolved, not lost.** The tree at `0.122.2` is **clean**
(`git status --short` empty) and `dashboard/api/memory.py` carries **`MEMORY_TIMEOUT_S = 10.0`**
with a `wait_for` backstop plus `tests/test_memory.py`. The 2026-10-23 in-tree edit that
[[incidents/2026-10-22-conduit-memory-start-timeout]] depended on is no longer required.
- **The call store changed shape.** `conduit-calls.json` is `v: 1` (`outcomes` / `delivered` / `told` /
`watches` / `waiting` / `seeded` / `ends` / `settings`); **`history` is empty (0)** and
**`last_request_at` is `null`**. `ends` = **2** turn-end records, both `outcome: stopped`, at
**21:06:05** and **21:10:48**. `settings` gained **`quiet_at_screen: true`** (#479). ⚠ The two
2026-10-29 calls the page used to cite as live history are **no longer in the store**.
- **New fault — local voice mode.** The Mac mini speech server's **LLM proxy is disabled**
(its LLM endpoint answers **HTTP 501** *"Start the server with `--enable_llm_proxy`"*), `/v1/usage`
reads **`llm_proxy.requests: 0`**, and its realtime socket **accepts the connection but rejects
`session.update` as an unknown event**. The app's **"test connection" only checks socket
reachability**, which is why it reports success. `voice.local_live.front_model` was changed during the
session to `{base_url: http://100.78.63.20:20128/v1, model: mistral/voxtral-small-latest}` (was
`mistral/ministral-14b-latest`); `config.yaml` mtime **21:02:30**. **Nothing was changed on the Mac.**
→ [[incidents/2026-10-31-conduit-voice-local-mode-not-applying]]
- **Misread, corrected mid-session (keep the 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` proves an HTTP request, never a call.
- **Environment:** the **18:06:41 gateway reload waited the full 1,800 s cap and force-drained at
18:37:38**, orphaning the Mnemosyne Health Monitor's 12:01:06 slot.
→ [[incidents/2026-10-31-gateway-reload-force-drain-orphaned-run]]
- **Data volume:** `conduit-health.sqlite3` **938.2 MB** (983,793,664 B) — **2,623,879 `events`** /
**4,384 `buckets`** / **504 `windows`**; ≈**8 MB/day**, no retention policy.
- **Not re-measured:** per-kind event split, health-table freshness, device pairing state.
## Open items
- Commit or upstream the `plugin_api.py` timeout patch so a plugin update cannot revert it — it is
now five releases behind HEAD.
- ✅ **Resolved 2026-11-01** — the `plugin_api.py` timeout patch is no longer needed: the tree is clean
at `0.122.2` and `MEMORY_TIMEOUT_S` ships upstream in `dashboard/api/memory.py`.
- **Verify a call end-to-end from the phone.** The 2026-10-29 08:49:36 call has no recorded outcome,
so `MEMORY_TIMEOUT_S = 60` is still unexercised by a *confirmed* call, and `last_request_at` was
still `null` → [[incidents/2026-10-29-conduit-voice-silence]].
- **Local voice mode does not work — see [[incidents/2026-10-31-conduit-voice-local-mode-not-applying]].**
The Mac mini speech server's **LLM proxy is disabled** (LLM endpoint → **501**, `/v1/usage` shows
**`llm_proxy.requests: 0`**) and its realtime socket **rejects `session.update` as an unknown event**,
while the app's "test connection" checks **socket reachability only**. Nothing changed on the Mac yet.
- `voice.mode` is a **phone-side** selector: neither `config.yaml → voice` nor `conduit-settings.json`
carries a `mode` key, so a "mode change did not apply" cannot be diagnosed on the host config.
- Re-check `voice.speech_server.url` after any Conduit/app update or settings sync — a bare `/v1/`
silently 403s every call.
- No retention policy on `conduit-health.sqlite3` (**930 MB** and growing unbounded).
- No retention policy on `conduit-health.sqlite3` (**938.2 MB**, ≈8 MB/day, growing unbounded).
- The Mnemosyne cold start that motivated the patch is still slow (10–45 s); only the *budget* was
raised. → [[systems/mnemosyne]]