MemoryGuard v0.7.4

MemoryGuard v0.7.4

Released: 2026-08-27

v0.7.4 consolidates the governance and runtime fixes prepared after the
v0.7.3 shared-history release.

Included

• Canonical reconciliation merges related rules, habits, and memories into a
  single evolving record instead of leaving equivalent updates scattered.
  Neural-graph branches may still derive automatically, while provenance,
  scope, evidence, and reversible supersede history remain intact.
• Mandatory-rule counts above 20 are a health warning, not a storage or
  injection cap. Character/token aggregate limits, per-item limits, sensitive
  content, and corrupt governance state remain fail-closed.
• Agent, automatic-decision, GUI, and risk-signal surfaces expose readable
  labels and explanations. Governance groups default to collapsed, and
  conflict/risk summaries open their details; risk entries show reason, impact,
  and action; CodeGraph/GUI operations use the governed identity and scope
  contracts.
• run_audit and get_audit return explicit completion state and timezone-aware
  timestamps. The GUI uses this evidence consistently, so completed scans do
  not remain 待扫描; missing numeric health evidence stays unknown rather
  than being fabricated. The reader popover stays above navigation, and
  governance phases display readable completed/current/pending/undetermined
  states.
• Codex Hook/bootstrap diagnostics distinguish mandatory-budget overflow from
  generic context-build errors. NO_SOURCE/absent is treated as a neutral
  canonical fallback, not as a mandatory-rule failure.
• Provider MCP installation detects editable/local-source origins and uses a
  content-keyed, non-editable snapshot. Snapshot creation is atomic, package
  static assets participate in refresh, failed builds preserve the last valid
  runtime/configuration, and PEP 610 copied-install origin diagnostics are
  available without mutating state during inspection.
• GUI partial mutation and evidence publication conflict paths preserve the
  prior valid state. Migration replay tests cover idempotent retries,
  read-only failure evidence, and safe recovery.
• System group_outbox projection advances the projected event and checkpoint
  in one transaction. A lagging checkpoint can be repaired safely; pending or
  failed events remain fail-closed and cannot be projected as successful.

Validation evidence

This release preparation relies on existing evidence rather than a duplicate
full-suite run:

• incremental CI tail: 447/447 passed;
• related focused governance, runtime, GUI, migration, and provider suites
  passed;
• git diff --check passed.

The complete test suite was not rerun during release preparation. Package
artifacts must still pass twine check and the staged-content exclusion audit
before publication.

Upgrade

python -m pip install --upgrade agent-memguard
memoryguard --version
memoryguard doctor

For Codex, use the provider installation path so the MCP process is pointed at
an immutable snapshot rather than an editable checkout. Restart the MCP
process after installation so its imported code matches the selected snapshot.