wiki audit 2026-10-05: cliprox/terra pin settled 3/3 (Weekly Review failed 2026-10-04 18:00), failing set 6->7, streak-counter/executions.db-retention caveat

This commit is contained in:
Tony0410
2026-10-05 00:09:58 +08:00
parent 78048bdf0b
commit 543e7782f8
5 changed files with 64 additions and 30 deletions
+9 -3
View File
@@ -3,8 +3,8 @@ title: Current State
type: concept
status: active
created: 2026-07-22
updated: 2026-10-04
verified_on: 2026-10-04
updated: 2026-10-05
verified_on: 2026-10-05
review_after: 2026-10-31
confidence: high
tags: [system]
@@ -12,7 +12,13 @@ sources: [live-config, live-cron-list, live-hermes-version]
---
# Current State
Updated: 2026-10-04
Updated: 2026-10-05
## Recent Changes (2026-10-05)
- **Cron fleet re-verified 2026-10-05 00:01 AWST — failing set 6 → 7.** Job count unchanged at 30 (27 enabled / 3 disabled). The one new failure event in the audit window is `79f9bb41ecf5` (Weekly Review, Sun 18:00), which ran on schedule **2026-10-04 18:00** and failed with the *identical* `cliprox/terra` error the incident predicted: `HTTP 401: [openai-compatible-chat-2ea20f63-…] All 1 connection(s) authentication expired — please reconnect in the dashboard`. That is the last untested job on the pin, so the provider-connection auth expiry is now **3 of 3 confirmed** — settled as a credential fault, not per-job. No review was produced; `delivery_outcome: delivered` again because the failure notice is the deliverable. See [[incidents/2026-10-01-cliproxy-connection-auth-expired]].
- **`1a8e90ea2271` failed again — 2026-10-04 03:00 (HTTP 410).** The `wiki-stocktake-maintenance` job remains pinned to the Ollama-retired `qwen3.5:397b`; no change, still needs a repin. Its script is healthy. See [[systems/scheduled-tasks]].
- **No interactive (non-cron) sessions in the window** — all 10 sessions active in the past 24h were cron. The only durable changes are cron-fleet status, reflected above.
- **Streak-number caveat for future audits:** the `N failures in a row` figure in `hermes cron list` is the `failure_streak` counter from `jobs.json`, not a DB-derived count. `~/.hermes/cron/executions.db` now retains only rows from **2026-09-30 onward** (1,001 rows), so DB recounts undercount older streaks. Live counters 2026-10-05: `1a8e90ea2271` ×11, `dca8482e4f76` ×7, `fad5a86979d4` ×3. Quote the live counter, and note the retention floor.
## Recent Changes (2026-10-04)
- **Both Hermes instances updated on 2026-10-03, from opposite directions.** CT460 (production) was rebuilt to `v0.21.5+6169.gab86a20` (upstream `ab86a20a`, tree mtime 10:11 AWST) and CT450 (chaos) came up from `v0.19.0` to `v0.21.5+6170.ga510d6c` (upstream `a510d6c6`, tree mtime 10:22 AWST). Same semver token, different builds, separate state. CT450 now reports `Update available: 3 commits behind`. CT450 has no SSH — it is reached via `ssh root@100.96.100.82` + `pct exec 450`, and `hermes` is not on the default `pct exec` PATH. See [[incidents/2026-10-03-ct450-hermes-update]].