Version Packages

[aao-release-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to 3.0.x, this PR will be updated.

Releases

adcontextprotocol@3.0.12

Patch Changes

• d8d5cfa: Add comply_controller_mode_gate universal storyboard and acme-outdoor-live test kit.

  New storyboard exercises the live-account denial path for comply_test_controller:
  a seller that exposes the controller must return FORBIDDEN when called by a
  live-mode (non-sandbox) principal. Optional phase for two-deployment sellers;
  required for single-endpoint sellers that implement per-account gating.
  Closes spec/compliance: storyboard coverage gap — no scenario exercises comply_test_controller denial against live-mode accounts #4028.

• 6ed6bed: Fix account.supported_billing schema: require it only when media_buy is in supported_protocols, not unconditionally for all agents. Adds root-level allOf if/then guard following the existing sync-plans-request.json pattern. Non-media-buy agent authors should note that supported_billing was previously enforced on any account block — SDKs using code generators that drop draft-07 if/then (openapi-typescript, zod-to-json-schema, quicktype) should add a runtime guard to require supported_billing when account is present and media_buy is declared.

• 4e9738c: spec(compliance): document force_scenario_unsupported — UNKNOWN_SCENARIO on force_* controller steps grades not_applicable

  Sellers that implement comply_test_controller but have not implemented a specific force_* scenario arm (e.g., force_create_media_buy_arm) correctly return {success: false, error: UNKNOWN_SCENARIO}. The storyboard narrative in create_media_buy_async.yaml already said this grades not_applicable — that narrative was normative English. The runner contract, however, had no machine-readable enforcement layer for force_* scenarios (only fixture_seed_unsupported for auto-injected seed phases), so conforming runners were implementing FAILED instead of not_applicable.

  Patch-eligibility justification (IETF errata test, playbook lines 261-265): the storyboard's own normative narrative text already required not_applicable; any runner grading FAILED was non-conforming against that existing MUST. This change adds the machine-readable form of a rule that was already in force. A conformant 3.0.0 implementation of the surrounding behavior would already have honored the narrative — the schema text closing the gap is an errata clarification, not a new requirement.

  Changes:

  • storyboard-schema.yaml: adds force_scenario_unsupported alongside fixture_seed_unsupported, with a normative MUST: detect the tuple (comply_test_controller IS present, resolved payload scenario begins with `force_`, response {success: false, error: UNKNOWN_SCENARIO}) and grade not_applicable before evaluating declared validations. Documents detection order to prevent misgrading absent-tool cases.
  • runner-output-contract.yaml: adds fixture_seed_unsupported, force_scenario_unsupported, and unresolved_scenario_reference as recognized narrower detail values under canonical reason not_applicable, with the encoding MUST for force_scenario_unsupported.

  No storyboard YAML changes — create_media_buy_async.yaml's narrative was already correct; this closes the machine-readable gap the runner was missing. Runner implementation fix tracked in adcp-client (sibling-repo).

  Closes Runner grades force_create_media_buy_arm UNKNOWN_SCENARIO as failed instead of not_applicable #4226.