Repository navigation
v0.38.2 — Gateway Contract Wording
Agent Memory Bridge v0.38.2 — Gateway Contract Wording
Agent Memory Bridge v0.38.2 corrects the current trust and deployment wording around the optional HTTP gateway. It does not change gateway, memory, or MCP behavior. The schema remains v12 and the public MCP surface remains exactly 17 tools. There is no automatic learning and no MCP tool #18.
What changed since v0.38.1
- Deployment modes: Current docs distinguish the static single-token private-bearer profile from the optional gateway/RBAC deployment. In the static profile, one dedicated token grants the whole tool surface. In gateway/RBAC mode, each token selects a configured principal limited by its role and
allowed_namespaces. Configuration selects the mode; token count does not. Local stdio uses neither HTTP profile. - Actor binding: In gateway/RBAC mode,
store,annotate, andrevisebind top-levelactortoprincipal_id;feedbackbindsprovenance.actor. A configured principal does not prove the person or model behind a request. - Audit contract: The deployment guide now lists the twelve always-present serialized audit fields, the conditional
error_message, and the seven status labels, includingtool_errorandunknown_truncated. Dedicated content and query fields are recorded by size or count. This is field minimization, not a general redaction guarantee. - Role contract: The documented allowlists are the normative role contract. Consistency tests compare them with
ROLE_PERMISSIONSand compare the documented audit fields with serialized records. - Scope: No runtime, schema, database, or public MCP tool change is included. The published
v0.38.1tag and artifacts remain historical.
Compatibility and limitations
Installing the package does not automatically connect every coding agent. Clients that should share one store still point at the same persistent AGENT_MEMORY_BRIDGE_HOME.
- The public tool-schema SHA-256 remains
24c5c52321d61b4b6f647c0d74e2d8304ca68716c403e08a274e9badfd8dc9f8. - There are exactly 17 tools in the public MCP interface, and the schema remains v12.
- No schema migration is required for existing v12 data.
- The gateway does not add human approval, OAuth or token issuance, TLS termination, or human/model identity.
- This release does not authorize upgrading an existing production deployment. That remains an independent operator decision.
PyPI Distribution and release provenance
After this release is published, install the version-pinned package with:
pip install agent-memory-bridge==0.38.2GitHub Releases remains the release source of truth, and actual PyPI and GHCR availability must be checked separately. Publishing a GitHub Release for the v0.38.2 tag triggers the existing wheel/sdist verification workflow, PyPI Trusted Publishing through GitHub OIDC, and the container workflow that validates and publishes ghcr.io/zzhang82/agent-memory-bridge:0.38.2. A tag alone is not evidence that either artifact was published.