v0.22.0 - Cross-Client Activation Receipt

v0.22.0 - Cross-Client Activation Receipt

Agent Memory Bridge 0.22.0 adds a local receipt for one shared-memory loop
across two configured coding-agent clients.

0.22.0 = client A writes reviewed project memory, client B reads it and acks a signal, and AMB emits a sanitized declared-provenance receipt.

What Changed

• Added the activation-receipt CLI/report:

agent-memory-bridge activation-receipt --namespace project:demo --correlation-id activation-demo-001 --format markdown

• The receipt reads existing AMB rows for one namespace and correlation id. It
  requires exactly one writer memory tagged workflow:cross-client-activation,
  activation-role:writer, and reviewed:true, plus exactly one reader signal tagged
  workflow:cross-client-activation and activation-role:reader.
• The reader signal must be acked and must record the writer memory id as
  observed_memory_id.
• The writer and reader must have present, distinct declared source_client
  labels.
• The receipt hashes namespace, correlation id, record ids, and source-client
  labels. It does not print raw memory content, private paths, session ids,
  client workspace values, or model ids.

Why It Matters

Native per-client memory is now table stakes. AMB's useful wedge is shared,
governed, inspectable continuity across coding agents. This release gives
operators a small local receipt that shows two distinct declared client labels
participated in one reviewed memory loop without adding another MCP tool.

Validation

• pytest: 388 passed
• cross-client activation receipt tests: passed
• public MCP surface: unchanged at 10 tools
• durable writeback from receipt generation: 0
• client config writes from receipt generation: 0

Boundaries

This is declared provenance only. It does not authenticate client identity,
certify any vendor, prove marketplace distribution, or claim external adoption.
It does not add MCP tools, write client configuration, promote memory, or perform
automatic durable writeback.

The fixed governed-change proof remains the v0.21 proof: the report
target_release is 0.21.0, and the manifest has current_release = 0.20.0
and target_release = 0.21.0.