Patch Changes

• Backport compliance storyboard fixes for idempotency webhook placeholders, past-start reject-or-adjust handling, initialized security probes, RFC 9421 webhook receiver URLs, and media-buy state transitions.

• c57bcd8: Backport the proposal-finalize storyboard gate to 3.0.x so sellers that do not declare media_buy.supports_proposals: true skip the proposal lifecycle scenario instead of receiving false-negative compliance failures, and refresh the idempotency storyboard flight dates so the 3.0.x runner preserves byte-identical replay payloads.

• 895f74a: spec(tmp): add required seller_agent_url to context_match_request.

  The context-match request now carries seller_agent_url, matching the identity-match request's field shape and placement (PR #3687). The resolution semantics are deliberately actor-specific, not a mirror: on the context path the provider resolves the active package set it has synced for the asking seller, whereas on the identity path the buyer agent resolves the set it has registered. When package_ids is omitted, evaluation runs against that seller's full active set; a seller_agent_url the provider has not synced packages for MUST return an empty offer set rather than fall back to another seller's set.

  This reverses the prior decision (PR #3063's seller-attribution section) that kept seller identity off context_match_request. That section argued the provider already holds the sync-time seller_agent binding so the request field is redundant, and that putting seller on the context path opens a request-time filtering vector. In practice a provider serves many sellers and needs the asking seller's identity on the wire to scope its active-set resolution without a deployment-pinned constant — the same need the buyer agent has on the identity path, even though the actor and the set it resolves against differ. The decorrelation argument does not apply: seller_agent_url is a single stable value identifying the asking seller, identical for every user on a placement and carrying no user identity, so it adds no per-user signal that context and identity requests could be correlated on. The package-set decorrelation guarantee constrains per-user-varying data (package_ids), which is unchanged.

  Required, consistent with identity-match. context_match_request is x-status: experimental, so the added required field is permitted pre-stable.

  Files:

  • static/schemas/source/tmp/context-match-request.json — seller_agent_url property (string, uri) added to properties and to required.
  • docs/trusted-match/specification.mdx — §Seller Attribution "Placement rationale", the Router participant row, and the "What This Is Not" bullet rewritten so the normative text matches: both request types carry seller_agent_url; the package-side seller_agent remains attribution-only; neither may be used as a per-user filter.
  • docs/trusted-match/{index,buyer-guide,context-and-identity,ai-mediation}.mdx and docs/trusted-match/surfaces/{web,mobile,ctv,ai-assistants,retail-media}.mdx — request examples updated with seller_agent_url.
  • tests/example-validation-simple.test.cjs — both context-match request fixtures updated.

AdCP 3.1.0-rc.14

AdCP 3.1.0-rc.13

AdCP 3.1.0-rc.12

AdCP 3.1.0-rc.11

AdCP 3.1.0-rc.10

AdCP 3.1.0-rc.9

AdCP 3.1.0-rc.8

AdCP 3.1.0-rc.7

Patch Changes

• de5dfde: Fix hosted compliance target recovery after temporary adcp.supported_versions
  declaration regressions. Diagnostic storyboard flows now re-derive the hosted
  target from the agent's live supported versions, preferring 3.1-rc, then
  3.1-beta, then 3.0; canonical badge-writing flows keep the stable 3.0
  target when the agent still advertises it and only fall forward when no stable
  target is available. Canonical flows now also revoke stale public 3.0 badges
  when confirmed capabilities no longer advertise 3.0 support.

  Also patch the affected media_buy_state_machine,
  measurement_terms_rejected, and universal idempotency fixture copies to use
  forward-looking Q3 2026 windows, repair selected prerelease
  measurement_terms_rejected idempotency aliases, and fail the compliance build
  when a mutating storyboard step authors a stable or duplicate generated
  idempotency_key.