Memex 0.7.2 fixes the seven findings of the post-release review of 0.7.1, each verified and reproduced before it was fixed.
Extraction-rules overlay
- The
never_extractcheck runs on the classifier note exactly as it is persisted — the joined notes as well as each note — so a pattern that only matches across a note boundary can no longer reach the Chronicle. (#30)
Overlay locks and quarantine
- Abandoned-lock recovery is serialized through a
<lock>.reclaimmutex: only its holder re-checks and unlinks, so a writer that acquired the lock in between is never stolen from. (#29) - The quarantine file's read-merge-rename runs under its own lock with the stamp compare-and-swap as a backstop, and in-memory quarantine rows mirror the file once written, so a
memex gate quarantine clearfrom another process is honoured and never undone. (#29) memex gate quarantine clearhonours--dry-run; it takes no--expect-revision, and the docs now say so. (#29)
Documentation
- GUIDE.md and WEBUI-WORKSPACE.md now state that
memex status, the overview attention card and the jobs table show every hold family, and that the embedding-model switch is a later 0.7.x release (#118), not 0.7.1.
Upgrade
Run memex update and restart Codex. No schema change.
All eighteen documented gates passed on the first attempt on code candidate 428195fd0e5998abe1febb191eba64df46d0738c: 151 files / 1629 Vitest tests, node --test test/*.test.mjs 284, installer, marketplace, package runtime (memex-0.7.2.tgz, 398 files, 9 MCP tools), lifecycle 9/9, 272 UI tests, browser E2E 27 probes in English and 27 in Korean, i18n lint/keys, plugin validation, benchmark contract, npm pack --dry-run and the real-root isolation check (162 files identical).