MemoryGuard v0.7.7

MemoryGuard v0.7.7

Release target: 2026-08-28

v0.7.7 is a focused provider-repair and runtime-alignment hotfix. It keeps
the existing fail-closed boundaries and binding identity while repairing the
normal-shell and installed-runtime paths that were still blocked by missing
native context or an inherited stale snapshot.

Included

• A bare memoryguard provider repair ... command can obtain an in-process
  trusted repair capability when the canonical control home is verified and
  exactly one active binding is available. Missing or ambiguous context stays
  fail-closed. This does not widen any other CLI mutation path.
• Non-editable wheel repairs ignore an inherited old runtime snapshot and use
  the current sys.executable for both the Codex MCP entry and all seven
  lifecycle Hooks. Editable and local-source installs continue to use their
  content-keyed immutable snapshots.
• Repair preserves the existing Agent identity and shared-group binding.

Scope boundary

This document describes the 0.7.7 source changes. CI validation and external
publication are handled by the release workflow and are not asserted here.

Upgrade

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

After upgrading a Codex installation, repair the provider binding and restart
the Codex host so the MCP server and lifecycle Hooks load the aligned runtime.