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:
@@ -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]]
|
||||
|
||||
Reference in New Issue
Block a user