MemoryGuard v0.6.0
MemoryGuard v0.6.0
MemoryGuard v0.6.0 ships the production V2 cutover path and native V2 data plane.
Highlights
- Separate authoritative V2 SQLite domains for Memory, Rules, Evidence, Content, Runtime, Projection, Assets, CodeGraph, Skills, and System state.
- Four-state cutover manifest with explicit
V1_ACTIVE → V2_BUILDING → V2_READY → V2_ACTIVEtransitions. - Packaged
memoryguard-v2operator CLI for zero-write status, frozen-source preparation, and explicit activation. - Coherent SQLite online-backup migration, immutable source snapshots, source/target digest validation, and repeated live-source drift gates.
- Two-epoch Reference Audit, maintenance/integrity checks, outbox drain proof, and native coverage readiness.
- All 233 registered MCP/CLI/GUI/Hook surfaces explicitly closed: 138 implemented, 95 retired, 0 neutral, 0 blocker.
- V2-native Rule lifecycle, RuleMerge, extraction/enrichment, External MCP, provider control-plane, history, Knowledge reference, and GUI governance paths.
doctorandmcp-statusnow work safely in unbound terminals after V2 activation without exposing tenant memory counts.
Upgrading an existing v0.5.x workspace
Package upgrade alone does not activate V2. After upgrading:
memoryguard-v2 status -w .
memoryguard-v2 prepare -w . --apply
memoryguard-v2 activate -w . --confirm V2_ACTIVEThe prepare step preserves legacy V1 data and .memoryguard/migration-backups. Activation performs a fresh live-source drift check before changing the manifest. Do not delete V1 data or migration backups during cutover.
Release verification
- V2 suite: 589 passed
- Non-V2 suite: 1087 passed
- Split full-suite total: 1676 passed / 0 failed
- Production ACTIVE readiness:
READY, blockers[] - Reference Audit: 12 domains,
PASS, blockers[] - All 12 authoritative SQLite reports:
integrity_check=ok,foreign_key_errors=0 - Wheel and sdist:
twine checkPASS - Wheel isolated-install smoke:
memoryguard 0.6.0,memoryguard-v2entrypoint PASS
The repository CI additionally validates Python 3.10/3.12 on Linux and Windows runtime-lease behavior before release publication.