[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 main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

adcontextprotocol@3.2.0-rc.4

Minor Changes

• 121d8b3: Add owner-selectable Legacy and Strict Spec grading profiles for verified agents, with Sandbox preview support. Persist immutable exact-role/version assessments and audited selections, project public badges through durable retries, and expose the selected profile through registry APIs, feeds, dashboard controls, badge metadata, and verification tokens.

• dc69e0b: Publish canonical supply-path verification golden vectors and an explicit evaluator semantics version. Clarify fail-closed owner-sold carriage verification for affirmative collection constraints, dangling property references, unknown or unevaluated authorization constraints, revocation precedence, agent URL identity and independent domain-level paths.

  Retain authority-scoped revocations and authoritative-location pins in persistent registry state. Refuse stale or non-authoritative cache provenance and require explicit publisher attribution in cross-origin shared catalogs. Expose cache observation times and resolved URLs.

  Add publisher_domain attribution to shared collection declarations and require it for cross-origin owner evidence. Preserve successful-fetch provenance through failed crawls and provide an operator command for independently confirmed authority migrations.

• 3cea56c: Add protocol-specific anonymous_discovery declarations for media-buy product discovery and signal discovery. The optional booleans let callers plan anonymous catalog reads without making catalog-completeness claims or weakening authentication requirements for mutations and private state.

• cfc33f6: Require recovery on AdCP 3.2 producer errors while preserving legacy 3.1 decoding and adding compatibility vectors for retry classification and scheduling.

• 33edf91: Add an optional account field to sync_accounts response rows, echoed for settings-update-mode entries. Previously the response schema required brand + operator on every row, which made settings-update mode unimplementable for account-id-namespace sellers with no buyer-declared natural key, and made action: "failed" rows for such accounts unrepresentable entirely. The new discriminator mirrors the pattern sync_governance already uses. Closes sync_accounts settings-update rows require brand + operator, which an account-id-namespace seller may not have #7517.

Patch Changes

• 70a91fe: Add compliance scenario for frequency-cap negotiation through proposal refinement (refine_frequency_cap_negotiation). Exercises replace-cap, clear-cap, and unable outcomes against the fields introduced in feat(media-buy): add shared media-buy frequency cap #7449.

• 336546b: Align the 3.2 docs, announcement banner, and SDK guidance with the published 3.2.0-rc.3 checkpoint and @adcp/sdk@14.0.0-rc.36.

• eb3cbd6: canonical_format_validate_input no longer lists comply_test_controller in required_tools. The storyboard runner's per-storyboard gate admits a storyboard when any listed tool is present, so any agent exposing the (universal) test controller was selected and then failed all 17 steps on the missing validate_input. Agents without validate_input now receive a coverage-gap skip; agents implementing it run unchanged. Same shape as fix(compliance): drop get_adcp_capabilities from required_tools across 17 storyboards (OR-gate bug) #6774 (fixes Hosted grader: 11 failing steps remain on two cards after #7454/#7405/#7406 (sales 10, signals 1); budget-truncated runs still published as complete grades #7404, bug 1).

• 8b9868a: Allow complete reporting summaries to carry the nearest future period start
  from active committed configuration schedules while preserving both scope
  guards, obligation boundaries, and evaluated coverage. Clarify the seller's
  population rule and add portable compliance vectors, a lifecycle storyboard,
  and source, generated, and runtime validation regressions.

• 17f0921: Provenance storyboards now mark every creative-library and test-controller step
  with its actual tool prerequisite, so hosted grading does not fail sellers for
  optional surfaces they do not advertise. Fixes Provenance storyboards: add requires_tool: sync_creatives to the sync_creatives steps so sellers without a creative library are not graded partial on hosted 3.1 #7586.

• 516c9d2: Skip billing capability discovery when an agent does not advertise the account capability block, preventing unrelated agents from receiving failing billing grades.

• af1ea26: Gate the webhook-emission storyboard's wholesale get_products branch set and its aggregate assertion on the advertised wholesale buying mode, so non-media-buy agents grade the branch family as not applicable.

• 7509a53: Keep the universal media-buy lifecycle and non-governance seller specialisms
  ungoverned, and isolate their account natural keys so governance bindings from
  other compliance scenarios cannot leak into their runs. Refs media_buy_seller base storyboard registers a governance agent, then buys without plan_id (3.1.x) / governance_context (main) #7585.

• 4d0b482: Test kits declare the account their storyboards address. acme-outdoor and nova-motors
  now carry an account: block naming the operator (and both sandbox spellings) that
  account-bearing steps send, so a seller implementing a kit can seed the accounts those
  steps reference instead of inferring them from the storyboards' sample requests. Closes the
  seeding half of Account-scoped steps are graded as failures of the tool they name: one unseeded account produced 19 misattributed check failures across 5 tracks (3.1.1 / sdk 14.0.0-rc.35) #7588, where one unseeded account produced 19 check failures attributed to
  the tools the steps name rather than to the account they could not resolve.

• 8a4aac7: Preserve canonical document identities across bundled schemas and embedded MCP
  profile resources so relocated schema packages resolve nested references fully
  offline.

• 1fdb7fc: Give 35 request-signing conformance vectors bodies that are schema-valid for the operation their URL names, so a seller that validates the request payload before authenticating the caller still reaches the RFC 9421 verifier checklist. Only request.body changes; headers, URLs, verifier_capability and expected_outcome are untouched, and each vector's intended fault is preserved (Request-signing conformance vectors carry schema-invalid bodies, making grading depend on verifier check order #7567).

• 70e8363: Controller-seed canonical test-kit account prerequisites before account-scoped
  storyboard steps run, using deterministic per-storyboard operator units to keep
  account state isolated. This prevents missing or leaked setup from being
  misgraded as failures of the tools those steps exercise. The reference training
  agent now accepts those account fixtures on every applicable tenant and lets
  framework task settlement emit terminal webhooks before controller completion
  returns, with a bounded wait that releases the tenant lock if settlement stalls.
  Refs Account-scoped steps are graded as failures of the tool they name: one unseeded account produced 19 misattributed check failures across 5 tracks (3.1.1 / sdk 14.0.0-rc.35) #7588.

• 98fa207: Add the media_buy_frequency_cap_updates compliance scenario covering root-cap
  replace and clear through update_media_buy_frequency_cap, atomic rejection of
  new_packages whose product cannot join the shared counter, the resulting-state
  rule for clearing a cap while adding packages, and the ACTION_NOT_ALLOWED
  path when the package mix can no longer change the root cap. The reference
  training seller now implements package and shared MediaBuy frequency caps so
  the four frequency-cap scenarios execute against it, and the specification
  states the ACTION_NOT_ALLOWED rule for root-cap changes explicitly.

• 1467e46: Training agent implements the rc.3 Reliable Reporting consumer-status hardening and the conformance storyboard grades it.

  The public training agent now advertises consumer_status_task, serves
  sync_reporting_status, and projects the full RC.3 contract: content_mismatch
  with its closed mismatch_code, obligation_counts.consumer_status_pending,
  issue opened_at / issue_state / external_ref, and the
  operations_contact / consumer_mismatch_escalation_seconds capability fields
  driving recommended_action escalation — with the escalation boundary taking
  precedence over the stale-received grace deadline.

  comply_test_controller's reporting_core_lifecycle_probe gains two additive
  operations, advance_past_status_deadline and advance_past_escalation, and
  the capability-gated reporting_consumer_status storyboard uses them to grade
  counted silence, each mismatch_code, opened_at stability across the
  severity change, escalation to a contact_* action, and operations_contact
  presence.

[bokelley]

HOLD — stale generated release branch.\n\nThis PR was produced by Release run 34842463221 from stale checkout eb3cbd6 after main had advanced through #7485 and #7504 to af1ea26. Exact head 102916b has sole parent/merge-base eb3cbd, is two commits behind current main, and GitHub reports DIRTY/CONFLICTING. Its direct delta against current main modifies already-published rc.3 artifacts and omits #7504 state; the three-dot PR display expands to 2,112 files and 2.77M added lines.\n\nDo not merge or use this branch as an rc.3 release source. It is Draft as a quarantine. A release-workflow current-main/concurrency fencing fix is being prepared separately; this generated branch must be discarded or safely regenerated from current main after that review. Auto-merge must remain off.

[aao-secretariat]

Ladon does not review bot-authored PRs.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
adcp	🟢 Ready	View Preview	Sep 19, 2026, 10:04 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[bokelley]

Coordinator HOLD update — do not mark Ready or merge this head.

The release workflow safely replaced the original stale head with c59427cde5025f273126cc639885f5ce85984df0, generated directly from af1ea2666d77a56e287567567daa72a301562e52; that run performed no signing, tag, GitHub release, R2 upload, or npm publication.

However, main then advanced to 98fa207cb81c14b745f66a90d0b82cb6fad82f4b through #7494. That commit adds training-agent frequency-cap code, compliance-source changes, and a changeset. This rc.4 bundle predates those release inputs. GitHub's mergeable result is therefore insufficient: merging could retain the newer source while shipping stale generated rc.4 artifacts.

Fresh exact-head CI is also red only in two unchanged unstable integration paths (live external-smoke timeouts and the private-ledger concurrency assertion); those are being handled separately and are not evidence that c594's generated version patch is correct.

Keep Draft and auto-merge off. Wait for the current-main release workflow to regenerate the branch from 98fa207c (or later), then repeat exact ancestry/artifact/changeset/CI review and require human maintainer approval. No release/publication action is authorized by this comment.

[bokelley]

COORDINATOR HOLD — exact head fc488660c1501d3cb9db71ee3ecfad8316ee924a was generated by Release run 34854587339 from main 98fa207cb81c14b745f66a90d0b82cb6fad82f4b; current main is 6a5dd853febd511d6a47f03e761839ed3e259284. Exact audit confirms all rc.3 blobs remain immutable, rc.4 internal hashes/signature verify, and the two later main commits touch only non-release-relevant server/test/generated paths, so parent age alone does not demonstrate artifact drift. However, the run skipped signing, GitHub release upload, R2 publication, and CDN verification; no publication occurred. Keep Draft and auto-merge off. Do not merge or publish until exact current merge-tree CI is green, #7509/#7510 and SDK contract blocker #2911 are resolved with human review, and the complete artifact/publication audit is repeated.