zzhang82/Agent-Memory-Bridge

## Agent Memory Bridge v0.5.0

Agent Memory Bridge is a two-channel MCP memory layer for coding agents:

• durable knowledge in memory
• coordination events in signal

This release turns two important parts of the bridge into something we can measure and trust.

Retrieval became measurable and tunable

• added a canonical benchmark fixture for coding-memory retrieval
• benchmark reports now track precision@1, precision@3, and expected_top1_accuracy
• retrieval now reranks a larger candidate pool instead of relying on raw FTS order
• the benchmark compares bridge recall against a simple file-scan baseline
• the current canonical fixture reports:
  • memory_expected_top1_accuracy = 1.0
  • file_scan_expected_top1_accuracy = 0.5

Signal lifecycle became more production-shaped

• signal now supports claim -> extend -> ack / expire / reclaim
• added extend_signal_lease to the MCP surface
• lease renewal is separate from reclaim
• stale leases must be reclaimed instead of extended
• hard signal expiry remains a strict upper bound for any extension

Proof and regression coverage

• deterministic proof covers signal correctness, duplicate suppression, and recall timing
• stdio integration covers the MCP tool surface, including lease extension
• full test suite passes: 68 passed

Why this release matters

This is the point where the bridge starts to feel less like a clever memory tool and more like a small coordination-aware framework:

• retrieval quality is now benchmarked instead of guessed
• signal coordination has a cleaner lifecycle boundary
• the public surface stays small and inspectable

Current MCP surface

• store, recall
• browse, stats
• forget, promote
• claim_signal, extend_signal_lease, ack_signal
• export

Roadmap

Next likely steps are:

• claim selection fairness
• minimal retry boundaries for signals
• broader benchmark fixtures beyond the current canonical set
• continued learning-quality work in promotion and synthesis