wiki: nightly audit 2026-10-01 — cron fleet re-verified, Telegram delivery root cause, memory hygiene

This commit is contained in:
Tony0410
2026-10-01 00:10:55 +08:00
parent 4e7d99064e
commit a32475bd54
8 changed files with 115 additions and 48 deletions
+9 -7
View File
@@ -3,8 +3,8 @@ title: Hermes Agent
type: system
status: active
created: 2026-07-22
updated: 2026-09-30
verified_on: 2026-09-30
updated: 2026-10-01
verified_on: 2026-10-01
confidence: high
tags: [system, hermes, agent, llm]
sources: [live-hermes-version, live-config]
@@ -36,7 +36,9 @@ Primary personal agent for Anthony. Runs automation, research, communication, kn
- **Default provider:** `custom` → `http://100.78.63.20:20128` (OmniRoute) — verified 2026-09-30
- **Default model:** `smart-route` — verified 2026-09-30
- **History:** as at 2026-07-22 this was `custom:litellm` → `litellm:4000` with model `freellmapi-auto`
- **Provider model count:** ~3430 (omniroute), ~1512 (litellm)
- **Provider model count (2026-10-01):** 5 custom providers — `omni-101` 5,384, `Omniroute:20128` 5,398, `litellm` 1,728, `command-code` 71, `guacano` 46
- **MCP servers:** 5 configured (`Not human search`, `asana`, `cua-driver`, `hound`, `mcp-portal`) — verified 2026-10-01
- **Plugins enabled:** 11 — verified 2026-10-01
- **free-stack combo (OmniRoute):** Nemotron 3 Ultra 550B configured with `max_tokens: 8192`, `reasoning_effort: medium`, `chat_template_kwargs.force_nonempty_content: true` (see [[omniroute]])
- See [[model-providers]] for full breakdown.
@@ -72,7 +74,7 @@ Primary personal agent for Anthony. Runs automation, research, communication, kn
- See [[terminal-backend]] for details.
## Skills
- **Total installed:** 341 (per stocktake 2026-09-25)
- **Total installed:** 344 `SKILL.md` files across 72 top-level skill directories (live count, 2026-10-01; the last full stocktake on 2026-09-25 recorded 341)
- Key skills: hermes, hermes-gateway-troubleshooting, hermes-mcp-troubleshooting, hermes-api-vault, omniroute, job-search-automation, weekly-review, fresh-rss-intelligence-filter, etc.
- See [[skills-index]] for categorized list (auto-regenerated daily).
@@ -113,7 +115,7 @@ The `allowed_chats` gate runs on the **default profile's adapter** before `profi
- See [[messaging-integrations]] for details.
## Scheduled Tasks
- **Cron jobs:** 30 total (27 enabled, 3 disabled) — verified 2026-09-30
- **Cron jobs:** 30 total (27 enabled, 3 disabled) — verified 2026-10-01
- Delivery targets: Telegram (primary), Discord, origin, local
- Notable: Birthday checker, job radar, newsletter digests, GitHub trending, mnemosyne health/watchdog/backup, AgentMail watcher, skills stock-take regeneration
- See [[scheduled-tasks]] for full table.
@@ -127,8 +129,8 @@ The `allowed_chats` gate runs on the **default profile's adapter** before `profi
## Known Issues
- Managed-runtime venvs previously drifted on dependencies, breaking cron workers — now guarded every 15 min. See [[incidents/2026-09-28-hermes-managed-runtime-deps]].
- Daily Marketing Job Radar pinned to a model its upstream plan rejects (`gpt-5.6-terra` → 403 `MODEL_NOT_IN_PLAN`). See [[systems/scheduled-tasks]].
- Telegram thread delivery failures on `telegram:1793951355` (thread `34795` not found).
- **Three cron jobs are pinned to models that no longer exist upstream and cannot self-recover** (`1a8e90ea2271` → `qwen3.5:397b` retired 2026-09-25, HTTP 410; `dca8482e4f76` → `gpt-5.6-terra` plan-gated, 403 `MODEL_NOT_IN_PLAN`; `fad5a86979d4` → `deepseek-v4-flash` absent from the NVIDIA live catalog, HTTP 400). Repinning to the `smart-route` alias is the durable fix. See [[systems/scheduled-tasks]] and [[systems/model-providers]].
- **Telegram thread delivery failures — root-caused and fixed 2026-09-30.** A bare `deliver: "telegram"` resolves to the home DM (`1793951355`), where group forum topic IDs cannot exist; the send hard-failed and the message was lost. Two jobs were retargeted to `telegram:-1004321904721:102` and verified. Three jobs still use bare `telegram` targets. See [[systems/messaging-integrations]].
- **Two wiki trees drift:** `/home/hermes/workspace/agent-estate-wiki` (Gitea + Quartz source, pages at root) and `/home/hermes/wiki/agent-estate-wiki` (Obsidian/Ignis vault, pages under `wiki/`). They are separate git repos with different history. See [[current-state]].
- **Vault repo git objects can be unwritable:** `/home/hermes/wiki/.git` still holds root-owned object fanout dirs/objects (`04`, `42`, `82`, `91`) left by root-run maintenance commits on 2026-07-22. When a new blob or tree hashes into one of those fanouts, `git commit` dies with `insufficient permission for adding an object to repository database` (even though `git add`/`write-tree` look fine). Workaround that works: build the objects in a writable store via `GIT_OBJECT_DIRECTORY=<tmp>` + `GIT_ALTERNATE_OBJECT_DIRECTORIES=/home/hermes/wiki/.git/objects`, then `git pack-objects /home/hermes/wiki/.git/objects/pack/pack-<name>` and move the branch with `git update-ref refs/heads/master <commit>`. Permanent fix is a root `chown -R hermes:hermes /home/hermes/wiki/.git`. Do **not** run overwrite/rename probes against `.git/objects`: on 2026-09-30 one such probe overwrote loose tree `0d23eba37eb65f5e5021f558a370358f1e394c58` (breaking the 2026-07-22 commit `9141a88`); it was reconstructed byte-exactly from its parent tree `d8185c99` plus the two replaced children (`comparisons` tree `822b90a7`, `log.md` blob `043dc1cd`) and reinserted, and `git fsck` is clean again.
- Browser persistence not yet fully verified