v0.12.0 - Onboarding And Integration Hardening

Agent Memory Bridge 0.12 makes the first five minutes easier for people who are
not already inside the Codex dogfood loop.

Thesis

0.12.0 = onboarding and integration hardening without expanding the public MCP surface.

The bridge still exposes the same 10 MCP tools. The change is around adoption
confidence: platform-neutral install docs, client-specific config snippets,
generic stdio guidance, and local checks that prove the bridge works before it
is wired into a real project.

What Shipped

• platform-neutral setup across the public docs
• a client support matrix with careful status labels:
  • verified
  • documented
  • locally tested
  • supported
• generated config snippets for:
  • generic stdio MCP
  • Codex
  • Cursor
  • Cline
  • Claude Code
  • Claude Desktop
  • Antigravity
• agent-memory-bridge doctor for install diagnostics
• agent-memory-bridge verify for isolated stdio smoke validation
• onboarding contract checks for:
  • required docs
  • README linkage
  • generated config parsing
  • placeholder-safe public examples

Evidence

Current release snapshot:

• pytest: 185 passed
• public MCP tools: 10
• retrieval benchmark:
  • question_count = 11
  • memory_expected_top1_accuracy = 1.0
  • memory_mrr = 1.0
  • file_scan_expected_top1_accuracy = 0.636
  • file_scan_mrr = 0.909
• classifier calibration:
  • sample_count = 16
  • classifier_exact_match_rate = 0.875
  • fallback_exact_match_rate = 0.062
  • classifier_better_count = 13
  • fallback_better_count = 2
• onboarding contracts:
  • generated client configs parse cleanly
  • public onboarding docs are placeholder-safe
  • public surface and release-contract checks pass

Why It Matters

Good memory infrastructure does not help if the install path feels like private
maintainer folklore. This release makes the bridge easier to adopt as a general
MCP stdio server without turning it into a client-specific plugin project.

Honest Boundaries

0.12.0 does not mean:

• every MCP client is locally verified
• automatic client-config mutation
• IDE plugin development
• a new MCP tool surface
• remote deployment parity across every client

Next

The next useful pressure point is not more setup polish. It is stronger
coordination semantics under contention: retry boundaries, reclaim behavior, and
multi-agent handoff examples that stay small enough to fit the bridge's core.