Skip to content

MemoryGuard v0.7.9

Choose a tag to compare

View all tags
@irisxc4 irisxc4 released this 04 Sep 08:16
v0.7.9
a406efe

MemoryGuard v0.7.9

Released: 2026-09-04

v0.7.9 is a focused governance, telemetry, and public-distribution release
after v0.7.8. It keeps the local-first, evidence-first, fail-closed boundaries.
GitHub Release, GitHub CI, PyPI, and official MCP Registry publication all
succeeded. This note does not claim a Glama score or any other third-party
directory acceptance.

Included

  • Canonical rule, habit, and memory reconciliation keeps one maintained
    definition per related concept while preserving source links, evidence,
    graph branches, supersede history, conflict decisions, and reversible
    settlement receipts.
  • Governance surfaces use readable verified Agent/provider identities, shared
    group context, safe family-aware icons, actionable risk/conflict states, and
    explicit stale-conflict closure. Technical identifiers remain available in
    details for audit.
  • Local token telemetry has a documented benchmark path for seven- and
    thirty-day windows. Provider-reported totals, input/output-derived totals,
    deterministic MemoryGuard estimates, coverage, and unsupported hosts remain
    separate. Missing local samples are reported as unavailable, never zero.
  • The repository includes MCP Registry metadata in server.json, the PyPI
    mcp-name marker in the source README, and public contribution/security
    guidance. The official MCP Registry lists the released local stdio server as
    active/latest under io.github.irisxc4/memoryguard.

Recorded publication evidence

Evidence and demo boundary

Run the benchmark only against an authorized local workspace:

python scripts/benchmark_usage_telemetry.py --workspace . --window-days 7 --sync

Use docs/benchmarks/README.md for measurement
semantics and docs/benchmarks/demo-script.md
for a sanitized recording. The repository's synthetic graph artwork is not a
live product capture; do not describe a placeholder asset as a telemetry or
benchmark result.

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.

Validation boundary

The release workflow recorded final wheel/sdist checks, CI, PyPI visibility,
and official MCP Registry publication. Third-party directory ingestion remains
separate and must not be inferred from these results.

Historical release notes: v0.7.8, v0.7.7.

Assets 2
Loading