Skip to content

MemoryGuard v0.6.2

Choose a tag to compare

View all tags
@irisxc4 irisxc4 released this 10 Aug 12:56
· 14 commits to main since this release
v0.6.2
2d1d395

MemoryGuard v0.6.2

SQLite compatibility correction for the V2 fail-closed boundary.

Fixed

  • Memory, Evidence, and Content schema preflights now inspect a private copy of the SQLite main file plus any -wal/-shm companions.
  • Older SQLite builds may checkpoint the temporary connection while it closes, but the live database is never the connection being closed.
  • Post-failure no-write assertions establish their physical baseline after reading the expected marker, preventing an older SQLite observer from contaminating the no-write check.

Unchanged

  • V2 production cutover semantics remain unchanged.
  • Existing V2_ACTIVE workspaces remain active and do not need to re-run prepare or activation.
  • Frozen-source migration, readiness evidence, live-source drift verification, native routing, and rollback evidence are unchanged.

Verification

  • Full local test suite: 1678 passed / 0 failed.
  • GitHub Linux/Python 3.10 is the release gate for this correction.
Assets 2
Loading