wiki stocktake 2026-11-19: 3 stale pages re-verified (conduit-call open item re-probed, 10-26 orphaned-run incident resolved, WA communities report live-checked); freshness report; skills-index dates

This commit is contained in:
Tony0410
2026-11-19 03:22:49 +08:00
parent 98610466cc
commit 16f2c878c0
6 changed files with 195 additions and 10 deletions
@@ -3,8 +3,8 @@ title: Conduit Call Requests Refused by the Agent
type: incident
status: open
created: 2026-10-25
updated: 2026-10-26
verified_on: 2026-10-25
updated: 2026-11-19
verified_on: 2026-11-19
review_after: 2026-11-08
confidence: high
tags: [conduit, voice, tool-calling, agent-conduct, incident, unresolved]
@@ -93,3 +93,11 @@ into [[incidents/2026-10-22-conduit-memory-start-timeout]].
- The plugin **is** working for cards: `conduit_show` ×1 on 2026-10-25 14:37, delivered live.
- Plugin advanced to **`0.69.2`** and the dashboard gateway restarted at **18:42:33**, so upstream commits are live — see [[systems/conduit]].
- **Status stays open**: the request path is untested, not confirmed good.
## Status update — 2026-11-19 (stocktake re-probe)
- `~/.hermes/conduit-calls.json` → `history` is **still empty (0 entries)** as of 2026-11-19 03:0x
AWST — the call path has now gone unused for ~26 days since the fault. The "verify a real call
end-to-end" open item remains outstanding.
- No new refusal episodes have been recorded against this page. **Status stays open** on the same
basis as before: untested, not confirmed good.
@@ -1,11 +1,11 @@
---
title: Planned Gateway Restart on 2026-10-26 Orphaned a Live Cron Run — Mnemosyne Health Monitor (2 h 34 m in)
type: incident
status: active
status: resolved
created: 2026-10-27
updated: 2026-10-28
verified_on: 2026-10-28
review_after: 2026-11-03
updated: 2026-11-19
verified_on: 2026-11-19
review_after: 2026-12-19
confidence: high
tags: [gateway, cron, scheduler, lifecycle, restart, memory, silent-failure]
sources: [live-logs, live-gateway-ledger, live-sqlite-cron-executions, live-sqlite-cron-incidents, live-sqlite-sessions, live-probe]
@@ -111,3 +111,15 @@ disappears silently. What it did not do is *finish the work* or *avoid the inter
- The `lost its durable fire claim ownership` string did not appear in any 10-27 execution row.
- Open question from the original write-up still stands: why a *planned* stop bypasses the drain deadline
(`timed_out=True` at 1.35 s of a 30 s budget).
## Update — 2026-11-19 (stocktake re-probe)
- **Both `ea79a2_*` rows are now closed** (follow-up 2 satisfied): `ea79a2_c3ab2d784ba3`
`resolved` 2026-10-27T00:38:32, and `ea79a2_a4661554a3c2` **`closed` 2026-11-07T15:43:13**
(live probe of `cron_incidents` in `~/.hermes/cron/executions.db`).
- The `lost its durable fire claim ownership` error string has **no rows in the retained
`executions` window** — no recurrence since 2026-10-27 (subject to the DB's ~18-day retention
floor; the 10-28 update already confirmed the 10-27 window clean).
- **Status → `resolved`.** The fault did not recur and its incident rows are closed. Follow-ups
1, 3 and 4 (drain-policy decision, drain-timeout arithmetic, `failure_streak` semantics)
remain open design questions and were **not** actioned.