audit(2026-10-26): runaway Gmail digest + dead Nous credential; model default reverted to OmniRoute; conduit 0.69.2 live; freshness floor still 2026-10-08
This commit is contained in:
@@ -1264,3 +1264,49 @@ No secrets written; host names, IPs, VMIDs, job/incident IDs, ports and probe st
|
||||
still **2** (`0e753e_e7f8194a7d06`, `c0a9fa_764558b5ae83`) — identical to the page's 2026-10-25
|
||||
entry. No drift, nothing to change.
|
||||
- **No secrets written.** Job IDs, incident IDs, IPs, counts, paths and timestamps only.
|
||||
|
||||
## [2026-10-26] audit | Nightly wiki audit — window 2026-10-25 00:00 → 2026-10-26 00:5x AWST: a runaway digest and a dead Nous credential
|
||||
|
||||
- **Fleet was quiet but one job was not.** Live `executions.db`: 2026-10-25 settled **172 `completed` / 2 `failed`**;
|
||||
**both failures are `08eb86f02d37` (Gmail Action Digest)**, which also fired **six times** in the day (08:31:14 →
|
||||
10:26:37 runaway at **1 h 55 m** vs 91 s / 104 s the two prior days; then 17:19:36, 18:40:06, 19:18:41, 19:30:31,
|
||||
19:38:53). New signature on the 19:18:41 fire: **`Cron admission missing: the owner never admitted this fire`**.
|
||||
All six fires — failures included — carry `delivery_outcome: delivered`. **Neither failure created a `cron_incidents`
|
||||
row**; the page's open-incident count is unchanged at 2. → new `incidents/2026-10-25-gmail-digest-runaway-and-refire.md`
|
||||
- **Root cause of the missing context compression found: the Nous Portal credential is dead.**
|
||||
`Nous Portal runtime credentials unavailable: Invalid refresh token` — **1** line 2026-10-22, **3** on 10-24,
|
||||
**20** on 10-25 (last 14:53:04, `agent.context_compressor: Failed to generate context summary`), **0** since the
|
||||
19:27:13 restart. → new `incidents/2026-10-22-nous-portal-refresh-token-invalid.md`
|
||||
- **⚠ The global model default moved BACK to OmniRoute — and the last three audits recorded the stale value.**
|
||||
A 2026-10-24 19:06:10 switch note reads *"model was just switched from meituan/longcat-2.5-preview:free to
|
||||
`smart-route` via omni-101"*; live config confirms `custom:omni-101` / `smart-route` (`api_mode:
|
||||
chat_completions`), `config.yaml` last written 2026-10-25 19:13. A **six-provider top-level `fallback_providers`
|
||||
chain is live again** (headed by the dead `nous` credential), so the 2026-10-21 "no fallback chain" record is
|
||||
stale too. Consequence: the 8 unpinned jobs are back on OmniRoute → **the fleet is a single upstream path again**.
|
||||
Corrected on `systems/current-profile.md`, `systems/model-providers.md`, `concepts/model-routing.md`,
|
||||
`comparisons/model-routers.md`, `systems/omniroute.md`.
|
||||
- **Auxiliary routing captured.** At 2026-10-25 19:13 **all eight** `auxiliary:` slots (approval, compression,
|
||||
curator, mcp, profile_describer, skills_hub, title_generation, vision) moved off `nous` to
|
||||
**`no-think/freeapi/auto` on `custom:omni-101`** with `free_only: true` and a `freeapi/deepseek-v4-flash` →
|
||||
`kg/kilo-auto/free` chain. ⚠ Masking, not fixing — `nous` remains first in `fallback_providers`. New section on
|
||||
`systems/model-providers.md`.
|
||||
- **`systems/scheduled-tasks.md` — new 2026-10-26 entry added**; the 2026-10-25 entry marked superseded. Fleet
|
||||
unchanged (28 jobs / 25 enabled / 3 disabled, all 28 IDs present); non-clean `last_status` **4 → 5**
|
||||
(`08eb86f02d37` joined as `delivery_queued` with an empty `last_error`); pins unchanged.
|
||||
- **`systems/conduit.md` re-probed live.** Version **`0.69.2`** in `plugin.yaml` *and* `dashboard/manifest.json`
|
||||
(both), HEAD **`942ddb8`** (2026-10-24 15:35:42, *"Pulse: list candidates, decide in code, journal them (#342)"*),
|
||||
**0 behind `origin/main`**, 24 commits on since the `0.64.0` baseline, working tree still carrying the
|
||||
uncommitted `dashboard/plugin_api.py` patch. **The dashboard gateway restarted 2026-10-25 18:42:33, so the
|
||||
upstream commits are now live** — the previous "not live" note is superseded. `conduit-calls.json → history`
|
||||
is still **empty**; `conduit_show` ran once on 10-25 14:37. Status on
|
||||
`incidents/2026-10-24-conduit-call-request-refused.md` **stays open** (untested, not fixed).
|
||||
- **`systems/messaging-integrations.md`** — CT255 still `stopped` (Mattermost offline **36 d**, `tx 312 / rx 0`);
|
||||
268 timeouts on 10-25 vs 264 on 10-24; reconnect counter reset to 54 by the 19:27 restart (per-process, not
|
||||
outage duration).
|
||||
- **`systems/hermes-agent.md`** — gateway restart record added (three starts on 2026-10-25: 00:32:20, 18:30:04,
|
||||
19:27:13; pid 2476414 up since 19:26:33) plus the credential fault and its restart-resets-counters caveat.
|
||||
- **`index.md`** — header date, the two new incident links, and rewritten `conduit`, `messaging-integrations` and
|
||||
`scheduled-tasks` summaries.
|
||||
- **No secrets written.** Job IDs, incident IDs, base URLs, counts, paths and timestamps only.
|
||||
- **Not changed:** `current-state.md` (its dated sections are historical records), and the dead `custom:omni`
|
||||
provider entry (still named by 2 jobs — Anthony's call, not the wiki's).
|
||||
|
||||
Reference in New Issue
Block a user