stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)

- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13)
- skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299)
- runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated
- comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest
- incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised
- incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused)
- 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists)
- log.md addendum + index.md date bump; no page deleted, no secrets written
This commit is contained in:
Hermes
2026-11-11 03:52:48 +08:00
parent 7ceaec1a2f
commit 341dda95dd
41 changed files with 579 additions and 102 deletions
@@ -3,9 +3,9 @@ title: Mnemosyne Automatic Capture Failure
type: incident
status: active
created: 2026-08-01
updated: 2026-10-20
updated: 2026-11-11
resolved_on: 2026-10-20
verified_on: 2026-10-20
verified_on: 2026-11-11
confidence: high
tags: [memory, mnemosyne, hermes, incident]
sources: [live-config, mnemosyne-db, hermes-cli-e2e]
@@ -82,6 +82,14 @@ no Mnemosyne trace.
`~/.hermes/backups/mnemosyne-capture-fix-20260801_180249/` and
`~/.hermes/backups/legacy-memory-slim-20260801_180702/`.
> **Resolution re-confirmed 2026-11-11.** The whole `memory.mnemosyne` block in
> `~/.hermes/config.yaml` is still natively typed — `sync_roles: [user]` (list),
> `skip_contexts: [cron, flush, subagent, background, skill_loop]` (list),
> `reflect: {disabled_for_cron: true, max_calls_per_session: 3}` (dict), `sleep_threshold: 50`
> (int), `ignore_patterns: []` (list), `profile_isolation: true` (bool), `auto_sleep: true`,
> `default_scope: session`, `vector_type: int8`. No stringification regression. Both backup
> directories named in the repair still exist. `status: resolved` stands.
## Related
- [[systems/mnemosyne]]
- [[systems/memory-backend]]