v0.7.6.2 — BLAST OFF v3 hardening
An autonomous adversarial hardening + security + performance + reliability pass. 16 fixes (all 7 P1
- 9 P2) across PRs #698–713, including the 3 incomplete v2 fixes now fully closed (#638→#698,
#649→#708, #653→#699). No API or behavior changes for normal use.
Security (P1)
- Prompt-injection / exfil hardening — recalled memory + directive text is escaped/sanitized before
injection so stored content can't forge<truememory-*>/<system…>framing (#698); Stop/drain
hooks guard the transcript path against out-of-tree reads (#699). - Least privilege — DB +
-wal/-shm+ the TrueMemory root are chmod'd 0600/0700 (#704). forget()completeness — purges all derived/aggregate tables, not just the row (#701).
Reliability (P1/P2)
- Engine auto-reconnect on a dead SQLite handle (#700).
- Crash-safe cosine migration via a commit-coupled done sentinel (#702).
- Near-duplicate dedup keeps facts differing only by a number (#703).
build_summariesnow uses the SAVEPOINT transaction wrapper — completes the #649 txn-hygiene fix
that was the v2 live-lock root cause (#708).- Atomic writes everywhere: 20 adapter config sites + recall cache (fixes a fixed-tmp interleave race) +
Online-Backup snapshot for pre-migration backups (#707). - Per-session debounce on the per-exchange store (#709); extracted-marker pruning runs independent of
the stale-session scan (#710, the 54K-marker unbounded-growth bug).
Performance
- Empty-consolidation recall no longer double-scans FTS — a measured ~185 ms/recall saved at 3k
rows (PERF-01 #705); recall p50 168 ms → 47 ms at 1k. - Recall/dedup-only hot paths skip the cross-encoder (#706).
Supply chain & hygiene
- Every GitHub Action SHA-pinned, incl. the OIDC publish job (#711).
hdbscandeclared as an optional extra; untrusted text control-char-stripped before logging (#712).- Docs accuracy (11 MCP tools, live
metadatafield), sdist excludestests/, test offline-env
centralized in conftest (#713).
Validation
1941 tests pass; perf A/B confirms the recall improvement; real-embedding sanity OK. Ratings vs the
post-v2 baseline: operational 8 → 9.0/10, security 6 → 8.5/10.
Known residual: torch CVE-2025-3000 (core dependency, no upstream fix published; pre-existing, not
introduced here).