diff --git a/current-state.md b/current-state.md index 6723045..9f8a7a8 100644 --- a/current-state.md +++ b/current-state.md @@ -29,10 +29,13 @@ Updated: 2026-10-18 - **Fleet count fell 29 → 28: the Mosquito Tracker was removed.** `1b31187397a5` is absent from `jobs.json` (file `updated_at 2026-10-18T00:36:17+08:00`); its last execution was **10-16 15:00** (`completed`, delivered). The three disabled jobs are unchanged — **25 enabled / 3 disabled**. -- **Non-clean `last_status`: 12 → 8.** Two of the eight cannot self-heal before their next slot — - `1b23c042e17d` sits at `error` (streak 2) until **Fri 10-23 08:00**; `0e519874d280`, `06a0a1c8704f`, - `c8d52904e1d6`, `0e753e9720fd` and `066bb5191280` are unchanged. **Open incidents 12 → 8** - (5 `alerted` / 3 `detected`); **9 opened and 6 closed** inside this window. → [[systems/scheduled-tasks]] +- **Non-clean `last_status`: 12 → 8 — and seven of the eight cannot clear until their next slot**, because + every one of them is a weekly, Mon/Thu or monthly job: `1b23c042e17d` (`error`, streak **2**, last + failure 10-16 08:03 with the 503, next **Fri 10-23 08:00**), `0e519874d280` (Mon 10-19 08:00), + `c8d52904e1d6` (Thu 10-22 18:00), `06a0a1c8704f` (Thu 10-22 10:00), and the monthlies `0e753e9720fd` + and `066bb5191280` (both 11-01). The eighth is `cbfe434a3b5e` — this audit, whose 10-17 run died on the + 503 and whose 10-18 run clears it. **Open incidents 12 → 8** (5 `alerted` / 3 `detected`); **9 opened and + 6 closed** in-window. → [[systems/scheduled-tasks]] - **The watchdog double-counts — 4 of the 13 failure rows are one sentinel.** `96eb95ce12f2` exited 1 on 10-16 12:15 + 12:30 and 10-17 00:15 + 00:30, each row quoting the coverage monitor's own 503 error. Read failures per job, not per row. → [[systems/mnemosyne]] diff --git a/log.md b/log.md index 0787da4..e407bd5 100644 --- a/log.md +++ b/log.md @@ -833,11 +833,14 @@ new Re-verified section); `current-state.md` (frontmatter + `Updated:` line + ne `index.md` (`Last updated`, new incident entry, scheduled-tasks bullet, skills-index note); `log.md` (this entry). **Nothing removed or archived** — no page became obsolete in the window. -**Bridge housekeeping:** the shared pages are byte-identical between the authoring tree -(`/home/hermes/workspace/agent-estate-wiki`) and the vault copy (`/home/hermes/wiki/agent-estate-wiki`, -pages nested under `wiki/`), so this run mirrored the touched pages into the vault *after* writing the -authoring tree, and left the vault-only pages (`systems/ignis.md`, `systems/nextcloud.md`, three -`incidents/` pages, `raw/stocktake/`, `agents/`) untouched. No deletions, no one-way sync. +**Bridge housekeeping (verified 2026-10-18):** every page this run touched was byte-identical between the +authoring tree (`/home/hermes/workspace/agent-estate-wiki`) and the vault copy +(`/home/hermes/wiki/agent-estate-wiki`, pages nested under `wiki/`) *before* the edits, so the seven files +were written to the authoring tree first, committed and pushed (`4137dd6`), then copied into the vault — +sha256 matched on all seven. The vault-only pages (`wiki/systems/ignis.md`, `wiki/systems/nextcloud.md`) +and the vault's own `wiki/raw/stocktake/` series were not touched; nothing was deleted and no one-way sync +was run. **Drift found, not fixed:** `incidents/2026-09-02-sftpgo-outage.md` exists only in the authoring +tree — 17 incident pages canonical vs 16 in the vault — so the vault is still missing that one page. **Durable fix still open (needs Anthony's call):** the single-node topology — all 18 model-calling jobs on `custom:omni-101` with no failover, now seen failing two different ways in five days. Options remain a