Skip to content

Agent Memory Bridge v0.30.0

Choose a tag to compare

View all tags
@zzhang82 zzhang82 released this 23 Aug 06:31
· 39 commits to main since this release
v0.30.0
8801841
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Project Knowledge Activation

Agent Memory Bridge v0.30.0 activates repository-derived project knowledge inside real agent workflows while preserving strict authority boundaries.

Included

  • Persistent, bounded, rebuildable repository snapshots with explicit namespace binding.
  • Clone/worktree-isolated local source identity based on canonical local Git roots.
  • Clean-HEAD eligibility with fail-closed dirty, stale, moved-root, and unavailable-status behavior.
  • Bounded repository-derived WHAT in existing MCP recall, structurally separate from governed durable project WHY.
  • Inspect provenance showing repository authority, binding, commit, selection, and exclusion state.
  • Existing schema v12 and exactly 17 public MCP tools; the public tool-schema digest is unchanged.
  • 968 local tests passed at the release candidate.

Evidence and boundaries

  • DeepSeek Harness: SESSION VERIFIED for the captured official runtime and upstream SHA b150a551b8d465e31e418e1b2eaf5e79bbb7d28e; MODEL VERIFIED = No.
  • OpenCode: SESSION VERIFIED for version 1.18.21; MODEL VERIFIED = No.
  • Host evidence used official deterministic/mock model infrastructure and does not claim real-model quality, broad provider compatibility, vendor endorsement, productivity improvement, or support for every host version.
  • Governed durable WHY remains separate from repository-derived WHAT. There is no automatic learning, automatic promotion, durable repository writeback, prompt/context archive, application claim, or causal claim.

Verification

The release tag points to the exact post-merge main commit whose push CI completed successfully with 13/13 jobs successful, including Python MCP 2.0 raw-wire coverage, concurrent-write and process-cleanup reliability, package validation, and platform test matrices.

P5 evidence: #22 (comment)

Assets 2
Loading