Skip to content

v0.22.2 - Onboarding Coherence

Choose a tag to compare

View all tags
@zzhang82 zzhang82 released this 19 Jul 00:44
v0.22.2
2e0515f

v0.22.2 - Onboarding Coherence

Agent Memory Bridge 0.22.2 makes the released setup flow match the public
onboarding guides. The pinned archive, installed first-run report,
client-config renderer, and verification sequence now use the same .amb-venv
baseline across Windows, macOS, and Linux.

0.22.2 = one released onboarding contract across the docs and CLI, with client registration kept explicit and manual.

What Changed

  • The baseline install uses the immutable v0.22.2 source archive and the
    .amb-venv environment name consistently.
  • first-run derives the venv interpreter for Windows and POSIX hosts and
    renders PowerShell-style Windows commands and sh-compatible POSIX commands.
  • The config renderer and integration guides distinguish placeholder-safe
    --example output from runnable config built with approved local paths.
  • The guides distinguish local validation from client registration:
    doctor checks prerequisites, verify launches an isolated stdio runtime,
    and the client's MCP status/tool view confirms that the config was loaded.
  • The first memory-loop instructions identify store(...) and recall(...)
    as MCP tool calls rather than terminal commands.
  • Cross-platform tests use synthetic fixtures and cover POSIX shell quoting and
    Windows PowerShell command rendering.

Why It Matters

The current onboarding guidance was added after v0.22.1, so users installing
that tag could still receive older first-run output. v0.22.2 puts the public
guides and the installed CLI on the same setup contract.

Validation

  • pytest: 395 passed
  • Release gate: all nine GitHub Actions jobs must be green across Windows,
    macOS, and Linux with Python 3.11, 3.12, and 3.13
  • public MCP surface: unchanged at 10 tools
  • client-config writes from first-run: 0
  • durable memory record writes from first-run: 0

Boundaries

0.22.2 adds no MCP tools or memory features. It does not write client config,
restart clients, or prove that a client loaded its generated config. doctor
and verify remain local checks; client MCP status/tool visibility is the
registration gate.

The Phase 1 pilot will measure independent-user completion time, setup failures,
and maintainer intervention. This release does not claim those outcomes yet.

Assets 2
Loading