v0.13.1 - Launch Surface Polish

Agent Memory Bridge 0.13.1 is a small polish checkpoint over the 0.13
coordination runtime.

Thesis

0.13.1 = stable launch surface for persistent engineering memory.

This release does not add new MCP tools or runtime behavior. It packages the
current main branch as a clean public checkpoint after documentation, security,
comparison, onboarding, and release-evidence hardening.

What Changed

• README and Chinese README now present the product as local-first MCP memory
  plus context compiler, not a Codex-only helper.
• Install examples are platform-neutral and keep OS-specific details out of the
  primary path.
• The before/after gotcha demo is easier to find from the README.
• Security, comparison, authority-contract, integration, and onboarding docs are
  aligned with the current public story.
• The release contract now checks test-count drift across the README,
  production status, and release announcement evidence.
• Tracked benchmark snapshot files are no longer hidden by .gitignore.

Evidence

Current release snapshot:

• pytest: 201 passed
• public MCP tools: 10
• deterministic proof: 4/4 checks
• signal contention benchmark:
  • signal_contention_case_count = 5
  • signal_contention_case_pass_rate = 1.0
  • unique_active_claim_rate = 1.0
  • duplicate_active_claim_count = 0
  • active_reclaim_block_rate = 1.0
  • stale_ack_blocked_rate = 1.0
  • stale_reclaim_success_rate = 1.0
  • pending_under_pressure_claim_rate = 1.0
  • initial_hard_expiry_cap_rate = 1.0
• adversarial memory-governance benchmark:
  • adversarial_case_count = 6
  • adversarial_task_count = 7
  • adversarial_governed_task_pass_rate = 1.0
  • adversarial_governed_blocked_record_leak_rate = 0.0

Boundaries

The public MCP surface remains the same 10 tools:

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

There are still no separate startup_packet or task_packet MCP tools. Startup
and task-time assembly remain context-compiler behavior behind the existing
surface while the packet shape continues to mature internally.

This release also does not add:

• scheduler
• watcher runtime
• hosted backend
• autonomous task runner
• graph database
• distributed queue

Next

Pause feature expansion and shift to distribution, dogfood, and user feedback.
The next engineering thesis should stay narrow: improve startup/task context
assembly without expanding the public MCP surface unless the internal packet
shape proves stable.