wiki audit 2026-10-07 (correction): real window tally 176/0/1 from executions.db TEXT timestamps; stocktake incident ids/closure times corrected

This commit is contained in:
Tony0410
2026-10-07 00:18:43 +08:00
parent 01f1db3aae
commit 8c1d12e29e
3 changed files with 6 additions and 6 deletions
+2 -2
View File
@@ -15,8 +15,8 @@ sources: [live-config, live-cron-list, live-hermes-version]
Updated: 2026-10-07
## Recent Changes (2026-10-07)
- **Cron fleet green for a second consecutive day — 0 failing.** Job count unchanged at 30 (27 enabled / 3 disabled) and all 30 `failure_streak` counters read 0. Window tally (`executions.db`, 2026-10-06 00:00 → 2026-10-07 00:00 AWST): **180 `completed`, 0 `failed`, 1 `running`** (the nightly audit itself). **No interactive (non-cron) sessions** in the window — every session was cron. No new incidents raised or resolved in the window.
- **The stocktake job proved its repin — first fully automatic run since 2026-09-25.** `1a8e90ea2271` (`wiki-stocktake-maintenance`, 03:00 daily) ran on schedule **2026-10-06 03:00:31 → 03:03:32** on its new `custom:omni-101` / `free-stack` pin and completed cleanly. Two of its own incidents (`069d7834bd68`, `7061381d4259`) flipped to `resolved` at 03:03:31. It regenerated `systems/skills-index.md` (**344 → 346 skills**), wrote `raw/stocktake/freshness-20261006.txt`, rebuilt Quartz and committed to Gitea as `33f4e95`. Its stale pre-repin `last_status: error` is now cleared — live `last_status: ok`, streak 0. **The daily manual `wiki-maintain.sh` run is no longer needed.** See [[systems/scheduled-tasks]].
- **Cron fleet green for a second consecutive day — 0 failing.** Job count unchanged at 30 (27 enabled / 3 disabled) and all 30 `failure_streak` counters read 0. Window tally (`executions.db`, 2026-10-06 00:00 → 2026-10-07 00:00 AWST): **176 `completed`, 0 `failed`, 1 `running`** (the nightly audit itself) — 177 rows. 14 sessions started in the window, all `source = cron`; **no interactive (non-cron) sessions**. **No new incident was opened.** The repin wrap-up closures at 00:10–00:12 on 2026-10-06 fall inside this window but were already recorded by the 2026-10-06 audit.
- **The stocktake job proved its repin — first fully automatic run since 2026-09-25.** `1a8e90ea2271` (`wiki-stocktake-maintenance`, 03:00 daily) ran on schedule **2026-10-06 03:00:31 → 03:03:32** on its new `custom:omni-101` / `free-stack` pin and completed cleanly. Its four HTTP-410 incidents (`6df957a05ec6`, `d284168d3663`, `cda67de5b3e3`, `e31584909bd2`) had already been closed at 00:10–00:11 on 2026-10-06 during the repin wrap-up. It regenerated `systems/skills-index.md` (**344 → 346 skills**), wrote `raw/stocktake/freshness-20261006.txt` and committed to Gitea as `33f4e95`. Its stale pre-repin `last_status: error` is now cleared — live `last_status: ok`, streak 0. **The daily manual `wiki-maintain.sh` run is no longer needed.** See [[systems/scheduled-tasks]].
- **Three jobs still carry a stale pre-repin `last_status: error`** — `1b23c042e17d`, `fad5a86979d4`, `0e753e9720fd` (down from four). Each clears on its next scheduled slot (Fri 08:00 / Mon 03:00 / 1st 09:00); none is a live failure. The bare-`telegram` target warning still stands on `066bb5191280` and `0e753e9720fd` (unchanged).
- **Wiki vault mirror refreshed.** `systems/skills-index.md` in `/home/hermes/wiki/agent-estate-wiki/` had drifted to 2026-10-03 / 344 skills while the canonical copy regenerated to 2026-10-06 / 346; this audit re-mirrored it along with the pages below. The two-wiki-tree drift remains a standing open item.
+3 -3
View File
@@ -363,14 +363,14 @@ No secrets written; credential-shaped values referenced by connection ID only.
Reviewed window: 2026-10-06 00:00 → 2026-10-07 00:00 AWST.
**Updated**
- `systems/scheduled-tasks.md` — Count block corrected: the stale pre-repin `last_status: error` set is now **three** (`1b23c042e17d`, `fad5a86979d4`, `0e753e9720fd`), not four — `1a8e90ea2271` cleared its own when it ran at 03:00. Added a **Re-verified 2026-10-07 AWST** bullet (30 jobs, 27 enabled / 3 disabled, 0 failing; 180 `completed` / 0 `failed` / 1 `running`; no interactive sessions). The stocktake job-table row and the "Verified live, not assumed" bullet now record the live-run verification. Historic count progression extended.
- `systems/scheduled-tasks.md` — Count block corrected: the stale pre-repin `last_status: error` set is now **three** (`1b23c042e17d`, `fad5a86979d4`, `0e753e9720fd`), not four — `1a8e90ea2271` cleared its own when it ran at 03:00. Added a **Re-verified 2026-10-07 AWST** bullet (30 jobs, 27 enabled / 3 disabled, 0 failing; 176 `completed` / 0 `failed` / 1 `running`; 14 sessions, all cron). The stocktake job-table row and the "Verified live, not assumed" bullet now record the live-run verification. Historic count progression extended.
- `index.md` — last-updated → 2026-10-07; cron-fleet line re-dated (**0 failing as of 2026-10-07**, 4 of the 7 verified by live run); the skills-index line no longer reads "being refreshed by hand while the stocktake job is blocked" — it now names 346 skills and the auto-regeneration.
- `current-state.md` — new Recent Changes (2026-10-07) block; frontmatter dates bumped.
**Findings worth the ink**
- **`1a8e90ea2271` ran itself at 03:00 and proved the repin.** `wiki-stocktake-maintenance` completed **2026-10-06 03:00:31 → 03:03:32** on `custom:omni-101` / `free-stack` — its first automatic success since 2026-09-25 (it had failed HTTP 410 ×11 on the retired `qwen3.5:397b`). It regenerated `systems/skills-index.md` (**344 → 346 skills**), wrote `raw/stocktake/freshness-20261006.txt`, rebuilt Quartz and committed to Gitea as `33f4e95`. Two of its own incidents (`069d7834bd68`, `7061381d4259`) auto-resolved at 03:03:31. **The daily manual `wiki-maintain.sh` run can stop.**
- **`1a8e90ea2271` ran itself at 03:00 and proved the repin.** `wiki-stocktake-maintenance` completed **2026-10-06 03:00:31 → 03:03:32** on `custom:omni-101` / `free-stack` — its first automatic success since 2026-09-25 (it had failed HTTP 410 ×11 on the retired `qwen3.5:397b`). It regenerated `systems/skills-index.md` (**344 → 346 skills**), wrote `raw/stocktake/freshness-20261006.txt` and committed to Gitea as `33f4e95`. Its four HTTP-410 incidents (`6df957a05ec6`, `d284168d3663`, `cda67de5b3e3`, `e31584909bd2`) had already been closed at 00:10–00:11 on 2026-10-06 during the repin wrap-up. **The daily manual `wiki-maintain.sh` run can stop.**
- **Vault mirror drift found and partly repaired.** `systems/skills-index.md` in `/home/hermes/wiki/agent-estate-wiki/` was still 2026-10-03 / 344 skills while the canonical copy had regenerated to 2026-10-06 / 346 — a knock-on of the stocktake having been blocked. Re-mirrored in this audit; the underlying two-wiki-tree split remains a standing open item.
- **Window tally** (`executions.db`, 2026-10-06 00:00 → 2026-10-07 00:00): 180 `completed`, 0 `failed`, 1 `running` (this audit). No interactive (non-cron) sessions; no new incidents raised or resolved in the window.
- **Window tally** (`executions.db`, 2026-10-06 00:00 → 2026-10-07 00:00): 176 `completed`, 0 `failed`, 1 `running` (this audit) — 177 rows. 14 sessions, all `cron`; no interactive (non-cron) sessions, and no new incident opened.
**Vault mirror:** `systems/scheduled-tasks.md`, `systems/skills-index.md`, `index.md`, `current-state.md` and `log.md` mirrored into `/home/hermes/wiki/agent-estate-wiki/` for the iPad/Ignis view.
+1 -1
View File
@@ -21,7 +21,7 @@ sources: [live-cron-list, live-jobs-json, cron-executions-db]
- **Verified live, not assumed:** `79f9bb41ecf5` succeeded on a manual run 2026-10-05 23:39 and `06a0a1c8704f` at 23:45 (both incidents auto-resolved); `dca8482e4f76` completed 23:56 and delivered to `telegram:-1004321904721:1030` (incident resolved 2026-10-06 00:05:07); and `1a8e90ea2271` completed automatically on **2026-10-06 03:00**. Four of the seven are therefore verified by live run. The remaining three (`1b23c042e17d`, `fad5a86979d4`, `0e753e9720fd`) are repinned but not yet re-run — they are due on their normal schedules.
- **Streak counting note:** the `N failures in a row` figure in `hermes cron list` comes from the `failure_streak` counter in `jobs.json`. `executions.db` retains only rows from **2026-09-30 onward**, so DB-based recounts undercount older streaks. Live counters as of 2026-10-06: **all 0**.
- **Re-verified 2026-10-06 AWST:** job count unchanged at 30 (27 enabled / 3 disabled). `066bb5191280` and `0e753e9720fd` still carry the bare-`telegram` target warning (`configured thread_id 34795 for telegram:1793951355 was not found`).
- **Re-verified 2026-10-07 AWST:** job count unchanged at 30 (27 enabled / 3 disabled); **0 failing** — all 30 `failure_streak` counters read 0. Audit window 2026-10-06 00:00 → 2026-10-07 00:00: 180 `completed`, 0 `failed`, 1 `running` (the audit itself); **no interactive (non-cron) sessions**. The stocktake job `1a8e90ea2271` ran on schedule at 03:00 and regenerated [[systems/skills-index]] (344 → 346 skills) plus `raw/stocktake/freshness-20261006.txt`, committing to Gitea as `33f4e95` — the first fully automatic stocktake since its repin. Only three jobs now carry a stale pre-repin `last_status: error` (`1b23c042e17d`, `fad5a86979d4`, `0e753e9720fd`).
- **Re-verified 2026-10-07 AWST:** job count unchanged at 30 (27 enabled / 3 disabled); **0 failing** — all 30 `failure_streak` counters read 0. Audit window 2026-10-06 00:00 → 2026-10-07 00:00: 176 `completed`, 0 `failed`, 1 `running` (the audit itself); 14 sessions, all `cron` — **no interactive (non-cron) sessions**. The stocktake job `1a8e90ea2271` ran on schedule at 03:00 and regenerated [[systems/skills-index]] (344 → 346 skills) plus `raw/stocktake/freshness-20261006.txt`, committing to Gitea as `33f4e95` — the first fully automatic stocktake since its repin. Only three jobs now carry a stale pre-repin `last_status: error` (`1b23c042e17d`, `fad5a86979d4`, `0e753e9720fd`).
- **A stale notice, not a live outage, drove this review.** The interactive session on 2026-10-05 23:16 began because Anthony replied to a `85edf6772bca` failure notice that had been sitting in topic `346` since the **2026-09-29 07:00** run. That job completed on every run from 2026-09-30 17:53 onward and its three incidents were already `resolved` on 2026-09-30 17:55:13. The notice looked current only because its wording matches the live 2026-09-28 managed-runtime incident. Check `executions.started_at` (and the `cron_incidents` state) before acting on a notice.
- Historic count progression: 26 (2026-09-19) → 30 (2026-09-25) → 30 (2026-09-30) → 30 (2026-10-01) → 30 (2026-10-02) → 30 (2026-10-03) → 30 (2026-10-05) → 30, **0 failing** (2026-10-06) → 30, **0 failing** (2026-10-07)