SDK beta.4 built-in test agent cannot run 3.2 compact lifecycle storyboards

[bokelley]

Version

@adcp/sdk@14.0.0-beta.4 (ADCP_VERSION is 3.2.0-beta.3)

Problem

The CLI's built-in test-mcp agent is not compatible with the protocol pin shipped by the current SDK beta. It advertises support only through 3.2-beta.2, while SDK beta.4 sends 3.2-beta.3 and correctly treats prerelease pins as exact.

As a result, an adopter cannot use the published CLI and built-in test agent to execute the compact product or direct-buy lifecycles. Capability discovery returns VERSION_UNSUPPORTED; the runner then falls back to a v2-shaped profile and skips the compact storyboard as capability-unsupported.

Reproduction

From a project containing @adcp/sdk@14.0.0-beta.4:

node node_modules/@adcp/sdk/bin/adcp.js \
  storyboard run test-mcp \
  media_buy_seller/compact_product_lifecycle \
  --json

Observed output includes:

{
  "adcp_error": {
    "code": "VERSION_UNSUPPORTED",
    "message": "AdCP version 3.2-beta.3 is not supported",
    "details": {
      "adcp_version": "3.2-beta.3",
      "supported_versions": [
        "3.0",
        "3.1-beta.5",
        "3.1-beta.7",
        "3.1-rc.4",
        "3.1-rc.6",
        "3.1-rc.7",
        "3.1-rc.8",
        "3.1-rc.9",
        "3.1-rc.10",
        "3.1-rc.14",
        "3.1-rc.15",
        "3.2-beta.2"
      ]
    }
  }
}

The final result is partial, with zero executed steps and one not_applicable skip. The same issue blocks media_buy_seller/compact_direct_buy_lifecycle.

Expected

The built-in public test targets used by the current @beta CLI should support the exact protocol prerelease shipped by that SDK beta, so these end-to-end smoke tests actually execute:

• media_buy_seller/compact_product_lifecycle
• media_buy_seller/compact_direct_buy_lifecycle

If coordinated deployment cannot be atomic, the CLI should point @beta users at a version-compatible test target or produce a direct actionable incompatibility result rather than degrading the profile to v2 and reporting the storyboard as merely not applicable.

Adoption impact

The SDK's local integration matrix is strong, but the documented public CLI path currently cannot validate a real buyer-to-seller 3.2 proposal or wholesale product lifecycle. That removes the most accessible independent end-to-end check for adopters evaluating the beta.

[bokelley]

Triage

Classification: Bug (two-part: remote test server + client-side runner error surfacing)
Bucket(s): cli, cross-repo
Status: ready-to-implement

What the experts said:

• code-reviewer: Root fix is the remote test server (outside this repo); client has a real error-surfacing gap — VERSION_UNSUPPORTED from get_adcp_capabilities is swallowed into a silent v2 fallback and never reaches the discovery-failure path; client-side fix is non-breaking (patch changeset).
• dx-expert: High-severity DX failure — beta adopters running the primary documented CLI path get a misleading false all-clear; extractVersionUnsupportedDetails (already in src/lib/utils/error-extraction.ts) is disconnected from the discovery path that needs it; fix is fully non-breaking.

My take: The test server at test-agent.adcontextprotocol.org needs to add 3.2-beta.3 to its supported_versions — that is infrastructure work outside this repo and the primary unblock. The actionable item here is patching the runner so VERSION_UNSUPPORTED from get_adcp_capabilities is surfaced explicitly rather than silently collapsing into a v2 profile.

Implementation scope:

• src/lib/testing/storyboard/compliance.ts — in testCapabilityDiscovery (or equivalent discovery pass): detect VERSION_UNSUPPORTED error code, call extractVersionUnsupportedDetails to extract supported_versions, emit an explicit failure message with the version delta rather than recording the v2 fallback step as passed: true.
• bin/adcp.js — when agent URL matches a key in BUILT_IN_AGENTS and VERSION_UNSUPPORTED is returned, append: "The built-in test agent does not yet support this ADCP prerelease; wait for a server update or point to a local agent with --agent-url."
• Patch changeset required; no generated-file edits; npm run ci:quick to validate.
• Non-breaking: additive error text only, no type or response-shape changes.

---

Triaged by Claude Code. Session: https://claude.ai/code/session_0177bJgAQYfSpjF83hFdgGjy

---

Generated by Claude Code