wiki audit 2026-10-02: 2 new cron failures, cliprox/terra connection auth incident, delivery-failure semantics corrected, profile rewrite, broken wikilinks repaired
- new: incidents/2026-10-01-cliproxy-connection-auth-expired.md (HTTP 401, credential fault, cannot self-recover)
- systems/scheduled-tasks.md: 30 jobs / 27 enabled; failing 3 -> 6; streaks advanced; wiki-tree drift recorded
- systems/messaging-integrations.md: two distinct thread-failure variants (lost vs thread-less fallback)
- systems/current-profile.md: full rewrite from live config (no profiles/default/, smart-route, OmniRoute)
- current-state.md / index.md / log.md: 2026-10-02 entry
- repair: copied 5 vault-only pages referenced by index.md (ignis, nextcloud, 3 incidents) so wikilinks resolve
- include pending stocktake output: skills-index.md 2026-09-27, raw/stocktake/freshness-2026-09-2{6,7}.txt
This commit is contained in:
+13
-3
@@ -3,8 +3,8 @@ title: Current State
|
||||
type: concept
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-01
|
||||
verified_on: 2026-10-01
|
||||
updated: 2026-10-02
|
||||
verified_on: 2026-10-02
|
||||
review_after: 2026-10-30
|
||||
confidence: high
|
||||
tags: [system]
|
||||
@@ -12,7 +12,17 @@ sources: [live-config, live-cron-list, live-hermes-version]
|
||||
---
|
||||
|
||||
# Current State
|
||||
Updated: 2026-10-01
|
||||
Updated: 2026-10-02
|
||||
|
||||
## Recent Changes (2026-10-02)
|
||||
- **Cron fleet re-verified:** 30 jobs, 27 enabled / 3 disabled (live `~/.hermes/cron/jobs.json`). Failing set **3 → 6**: two *new* failures landed on 2026-10-01 —
|
||||
- `06a0a1c8704f` (AI Newsletter Curation for Patrick, Thu 10:00) — `HTTP 401 … All 1 connection(s) authentication expired — please reconnect in the dashboard` on provider `custom:Omniroute:20128`, model `cliprox/terra`. Its failure notice reached topic 346; no digest was produced. **Not self-recovering** — needs the OmniRoute connection re-authenticated. Two other enabled jobs share that pin (`1b23c042e17d`, `79f9bb41ecf5`) and will fail next run.
|
||||
- `0e753e9720fd` (Facebook Birthday Monthly Scrape, 09:00) — `HTTP 400`, `nvidia/deepseek-ai/deepseek-v4-flash` absent from the active NVIDIA catalog, confirming the earlier diagnosis that this is a **shared-pin** problem (sibling `fad5a86979d4` uses the same model).
|
||||
- `066bb5191280` (Uber Eats Monthly Spend Report, 02:11) — report generated correctly; **delivery** failed with `configured thread_id 34795 for telegram:1793951355 was not found`.
|
||||
- **Carried-over failures, streaks advanced:** `dca8482e4f76` 403 `MODEL_NOT_IN_PLAN` → streak 6; `1a8e90ea2271` HTTP 410 (retired `qwen3.5:397b`) → streak 8; `fad5a86979d4` HTTP 400 → streak 3. All three still need a model repin.
|
||||
- **Telegram delivery semantics corrected — a "failed" delivery is not always a lost message.** Against `~/.hermes/cron/executions.db`, the 2026-10-01 failures carry the *fallback* variant: `configured thread_id <n> for telegram:<dm> was not found; delivered without thread_id`. Content reaches the DM, yet the run is recorded `delivery_outcome: failed`. The 2026-09-30 incident's `Message thread not found` variant is the one that truly loses the message. Both variants are now documented in [[systems/messaging-integrations]].
|
||||
- **The wiki has two trees, and they have drifted in both directions (new finding, 2026-10-02):** the canonical source is **`/home/hermes/workspace/agent-estate-wiki`** — it holds the Gitea remote (`Anthony/agent-estate-wiki`), the Quartz build (`serve.py`, `package.json`, `public/`) and is what `wiki-maintain.sh` commits. **`/home/hermes/wiki/agent-estate-wiki`** is the *Obsidian/Ignis vault copy* (pages nested under `wiki/`, no git remote) that the iPad reads. The nightly audit is told to write to the vault path, so edits that skip the canonical tree never reach Gitea or the published site. Worse, the trees have diverged backwards too: `systems/ignis.md`, `systems/nextcloud.md` and three `incidents/` pages exist **only in the vault**, while `raw/stocktake/*`, `incidents/2026-09-02-sftpgo-outage.md`, `reports/communities-wa-social-media-audit-2026.md` and `agents/` exist **only in canonical**. `index.md` in canonical links `[[systems/ignis]]` and `[[systems/nextcloud]]`, both of which are broken there. Any one-way sync will silently delete pages — reconcile before trusting either tree. See [[systems/scheduled-tasks]].
|
||||
- **Skills inventory:** 344 `SKILL.md` under `~/.hermes/skills/` (live count 2026-10-02), against 341 in the last generated [[systems/skills-index]] (2026-09-27). The page cannot refresh while the stocktake job stays broken.
|
||||
|
||||
## Recent Changes (2026-10-01)
|
||||
- **Cron fleet re-verified:** 30 jobs, 27 enabled / 3 disabled (live `~/.hermes/cron/jobs.json`). Failing set **4 → 3**: `cbfe434a3b5e` returned to `ok` as predicted on 2026-09-30. The residual `1a8e90ea2271` dispatch error also cleared — its current failure is a different, upstream problem (below).
|
||||
|
||||
Reference in New Issue
Block a user