diff --git a/incidents/2026-10-03-ct450-hermes-update.md b/incidents/2026-10-03-ct450-hermes-update.md index b460530..6237548 100644 --- a/incidents/2026-10-03-ct450-hermes-update.md +++ b/incidents/2026-10-03-ct450-hermes-update.md @@ -52,7 +52,7 @@ Two gotchas that cost time: Both instances have since moved on: **CT460 and CT450 now both run `v0.22.3` (2026.9.24), local `5b147ab036d6`** — the same build. CT450 is **0 commits behind `origin/main`** (the "3 commits behind" note below is superseded), though `hermes update --check` reports stable **v0.22.5** available on both. CT450's default model is now **`smart-route`** on `custom` → `http://100.78.63.20:20128`. The **CT450 Mattermost timeout remains** — CT255 is `stopped` on `pve` and its peer has been offline 36 d, so it is an infrastructure condition, not an update regression. ## Follow-ups -- CT450 reports `Update available: 3 commits behind`. Harmless; re-run `hermes update` if the chaos box should track upstream exactly. +- ~~CT450 reports `Update available: 3 commits behind`.~~ **SUPERSEDED 2026-10-26** — CT450 is now **0 commits behind `origin/main`** (it tracks the `NousResearch/hermes-agent` `main` branch; there is no `origin/master` on that remote). Re-run `hermes update` if the chaos box should track upstream exactly. - CT450's Mattermost connection is failing (`mattermost connect timed out after 30s`, retried every 300s) — an infrastructure condition (Mattermost host unreachable), not an update regression. See [[agents/hermes-chaos]]. ## Related diff --git a/incidents/2026-10-03-mnemosyne-vector-recall-fts-only.md b/incidents/2026-10-03-mnemosyne-vector-recall-fts-only.md index 81fe33f..d872625 100644 --- a/incidents/2026-10-03-mnemosyne-vector-recall-fts-only.md +++ b/incidents/2026-10-03-mnemosyne-vector-recall-fts-only.md @@ -66,8 +66,8 @@ monitor job `b63ed5817212` (`last_status: ok`) has nothing to fire on. The 2026- figures below are superseded. ## Follow-ups -- Confirm the embedding-coverage alert job (`b63ed5817212`, every 6h, Telegram topic 102) still fires when working coverage drops below 95%. -- Consider asserting `fastembed` in **all** managed runtimes, not only the bootstrap-selected one, so a runtime switch cannot reintroduce this. +- ~~Confirm the embedding-coverage alert job (`b63ed5817212`, every 6h, Telegram topic 102) still fires when working coverage drops below 95%.~~ **CONFIRMED 2026-10-26** — the job is `enabled` with `last_status: ok`; working coverage is 96.8 %, above the threshold, so it correctly has nothing to fire on. +- ~~Consider asserting `fastembed` in **all** managed runtimes, not only the bootstrap-selected one, so a runtime switch cannot reintroduce this.~~ **DONE 2026-10-26** — `fastembed` 0.8.1 now imports in **both** managed runtimes (`19da945341ad4794ac2bc8ff9fdd3643`, `d41b16c8b6674454a4a819bd4acced1f`) as well as 0.8.0 in the legacy venv. ## Related - [[systems/mnemosyne]]