stocktake(2026-10-26): strike superseded follow-ups per SCHEMA rule 9
Mark-don't-delete: the CT450 '3 commits behind' follow-up and the two mnemosyne-vector-recall follow-ups are struck through with their verified 2026-10-26 resolution rather than removed. - CT450 tracks origin/main (there is no origin/master on that remote) and is 0 commits behind. - Coverage monitor b63ed5817212 is enabled, last_status ok, working coverage 96.8% — correctly has nothing to fire on. - fastembed 0.8.1 now imports in both managed runtimes plus the legacy venv.
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user