wiki audit 2026-10-03: cliprox second job confirmed (2/3), work-mailbox incident page, streak recount, skills-index 341->344
This commit is contained in:
+13
-4
@@ -3,16 +3,25 @@ title: Current State
|
||||
type: concept
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-02
|
||||
verified_on: 2026-10-02
|
||||
review_after: 2026-10-30
|
||||
updated: 2026-10-03
|
||||
verified_on: 2026-10-03
|
||||
review_after: 2026-10-31
|
||||
confidence: high
|
||||
tags: [system]
|
||||
sources: [live-config, live-cron-list, live-hermes-version]
|
||||
---
|
||||
|
||||
# Current State
|
||||
Updated: 2026-10-02
|
||||
Updated: 2026-10-03
|
||||
|
||||
## Recent Changes (2026-10-03)
|
||||
- **Cron fleet re-verified:** 30 jobs, 27 enabled / 3 disabled (live `~/.hermes/cron/jobs.json`). Failing set stays at **6**, but the composition changed: `1b23c042e17d` (Enhanced Weekend Adventure Planner, Fri 08:00) failed on 2026-10-02 with the *identical* HTTP 401 the cliprox incident predicted — `HTTP 401: [openai-compatible-chat-2ea20f63-…] All 1 connection(s) authentication expired — please reconnect in the dashboard`. That makes **2 of the 3** `cliprox/terra` jobs confirmed broken, so the provider-connection auth expiry is a real credential fault, not a one-job fluke. `79f9bb41ecf5` (Weekly Review, Sun 18:00) is the last untested one — its only run (2026-09-27) predates the expiry and succeeded; next due **2026-10-04 18:00**. See [[incidents/2026-10-01-cliproxy-connection-auth-expired]].
|
||||
- **Streaks recounted from `executions.db` — one number corrected:** `dca8482e4f76` 6 → **7** (one more daily run), but `1a8e90ea2271` **8 → 7** — the ×8 carried since 2026-10-01 was an overcount; that job has exactly 7 recorded runs and all 7 failed. Recount before quoting a streak.
|
||||
- **A delivered notice is not a successful job.** Both `cliprox/terra` failures are recorded `delivery_outcome: delivered` because the *failure notice* is itself a deliverable — the execution `status` is `failed` and no digest/plan was produced. Judge cron health on the `status` column, not the delivery outcome.
|
||||
- **Resolved — `1b23c042e17d` stale `delivery_failed` flag cleared:** the 2026-09-30 retarget to `telegram:-1004321904721:102` worked exactly as predicted; its 2026-10-02 run delivered (then failed on the model pin). The prediction held.
|
||||
- **[[systems/skills-index]] regenerated by hand: 341 → 344 skills.** The daily stocktake job (`1a8e90ea2271`) is still blocked on a retired model (HTTP 410, `qwen3.5:397b`), but its **script is healthy** — `wiki-maintain.sh` was run manually on 2026-10-03 and completed cleanly, refreshing the index and writing `raw/stocktake/freshness-20261003.txt`. One new skill appeared: `fleet-wide-failure-triage` (devops). Only the scheduled wrapper is broken; every non-model step of the stocktake now needs a manual run each day until it is repinned.
|
||||
- **Work mailbox blocker documented — and it is older than it looks.** A new incident page records that the `work` Outlook account has been unreachable since **2026-08-26**, not this week: the account uses password auth while the tenant advertises only `XOAuth2`, so `himalaya -a work` dies with `login not supported`. The TCP/TLS path is fine — it is a tenant policy wall, not a bad password, and re-running the credential helper can never fix it. It needs an OAuth2 path. No cron job polls that mailbox, so this is an on-demand capability gap. See [[incidents/2026-08-26-work-outlook-basic-auth-disabled]].
|
||||
- **GitHub Trending Radar token claim downgraded to "unverified":** the revoked-bot-token (`getMe` → 401) diagnosis could not be reproduced — `c0a9fa314542`'s last recorded run (2026-09-30 19:22, off-schedule) **completed and delivered**. Re-confirm at the next scheduled run (Mon 2026-10-05 09:00) before acting on it.
|
||||
|
||||
## 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 —
|
||||
|
||||
Reference in New Issue
Block a user