audit 2026-10-25: third consecutive clean cron day; new incident (agent refused 3 Conduit call requests); correct 10-22 memory-fix evidence; conduit 0.69.0/f000bf0
This commit is contained in:
@@ -1154,3 +1154,48 @@ No secrets written; host names, IPs, VMIDs, job/incident IDs, ports and probe st
|
||||
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.
|
||||
|
||||
## [2026-10-25] audit | Nightly wiki audit — window 2026-10-24 00:00 → 2026-10-25 00:5x AWST: a third consecutive clean cron day, and a Conduit call request the agent refused
|
||||
|
||||
- **Window 2026-10-24: 167 `completed` / 0 `failed`** (+ this audit `running`); **2026-10-23 settled
|
||||
at 170 / 0** (169 at the 10-24 audit). Third consecutive clean day (10-22 → 10-24). Fleet **28 jobs
|
||||
(25 enabled / 3 disabled)**, **4 non-clean `last_status`**, **2 unclosed incident rows**
|
||||
(`c0a9fa_764558b5ae83` `alerted` since 10-19; `0e753e_e7f8194a7d06` `detected` since 10-01) —
|
||||
**nothing opened, nothing closed in-window**. Pins unchanged. **14 sessions: 11 `cron` + 3
|
||||
`desktop`.**
|
||||
- **New incident page: `incidents/2026-10-24-conduit-call-request-refused.md`.** Anthony asked to be
|
||||
phoned three times on 2026-10-24 12:53–12:56 (`Call me now to test calls.` → `Yes. You do` →
|
||||
`CAL ME`); every reply asserted the agent cannot make calls, with **0 tool calls** in the session.
|
||||
`conduit_call_user` exists, is registered for every session, is discoverable via `tool_search`, and
|
||||
has a bundled skill (`calling-the-user`); the call settings were permissive
|
||||
(`enabled` / `when_asked` / `decides` / `alerts` all true). Root cause: **capability asserted
|
||||
instead of discovered** — not a missing tool, and not one weak model (the free model's answer was
|
||||
repeated after a switch to `smart-route`).
|
||||
- **Correction to `incidents/2026-10-22-conduit-memory-start-timeout.md`:** its closing evidence
|
||||
(“two Conduit call sessions closed cleanly 00:03:23 / 00:06:57 on 10-24”) is a **false positive**.
|
||||
`conduit-calls.json → ends` is a ring buffer of **turn-ends that fire a watch**
|
||||
(`MAX_RECENT_ENDS = 64`), and its two entries are the **cron** sessions of that night (Mnemosyne
|
||||
Embedding Coverage Monitor 00:01, Health Monitor 00:04). `history` — real call records — is
|
||||
**empty**, so no call has been placed since the fix and the 60 s budget is **unexercised by a
|
||||
call**. The surviving evidence for the fix is only the absence of abort lines after the 18:54:43
|
||||
restart.
|
||||
- **`systems/conduit.md` refreshed:** version `0.64.0` / `eaa14be` → **`0.69.0` / `f000bf0` (22
|
||||
commits on)**; the gateway is still the 2026-10-23 18:54:43 process, so none of it is live; the
|
||||
uncommitted `plugin_api.py` patch is now **five releases behind HEAD**; new section documenting the
|
||||
`conduit_call_user` tool, its gate conditions and rate limits; device/state figures re-verified
|
||||
(`last_seen` 10-23 19:10:30 tracks phone-status contact; health ingestion ran to 10-24 09:59:59);
|
||||
store **569.9 MB / 1,520,229 events / 3,028 `buckets`** — the 10-24 page's 308 `buckets` / 62
|
||||
`windows` was a **narrower grouping**, corrected rather than read as a collapse.
|
||||
- **Also updated:** `systems/scheduled-tasks.md` (new Count bullet + `## Re-verified 2026-10-25`
|
||||
section + a date-bucketing note), `current-state.md` (new Recent Changes block; 10-24 block marked
|
||||
superseded), `index.md` (date, conduit + scheduled-tasks blurbs, new incident line, corrected 10-22
|
||||
line).
|
||||
- **Freshness:** not re-scanned this cycle — the 03:00 stocktake owns that. Carried over from its last
|
||||
run: 102 pages scanned, **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). They are
|
||||
the next cleanup candidates. **Nothing removed or archived** this cycle: no job retired, no system
|
||||
obsolete, no decision reversed in the window.
|
||||
- **Method note recorded in `systems/scheduled-tasks.md`:** `executions.db` stores `started_at` with a
|
||||
`+08:00` offset and SQLite's `date()` normalises to UTC, so `date(started_at)` moves 00:00–07:59
|
||||
AWST rows onto the previous day. Bucket days with `substr(started_at,1,10)`.
|
||||
- **No secrets written.** Job IDs, incident IDs, table names, counts, paths and timestamps only.
|
||||
|
||||
Reference in New Issue
Block a user