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

Releases

adcontextprotocol@3.2.0

Minor Changes

• 4cdebb9: Allow null for video-only delivery metrics (quartile_data, completion_rate). Sellers running non-video inventory (display, audio-only, DOOH-without-video) legitimately have no value for these metrics, and returning null is the correct "not applicable" signal. The schema previously required type: "number" / type: "object" and rejected null, causing receivers to fail validation on every valid display-inventory delivery report.

  delivery-metrics.json (totals / by_package[]) now accepts ["number", "null"] for completion_rate and ["object", "null"] for quartile_data; get-media-buy-delivery-response.json aggregated_totals.completion_rate gets the same loosening so the aggregate path can't re-trigger the failure. The minimum/maximum constraints on completion_rate still apply to non-null values, and the type stays narrowed to null (no strings/arrays). Every other delivery metric continues to signal "not applicable" by omission, not null — this exception is scoped to the two video-only fields. Spec-loosening for the receiver contract: producers already sending numbers/objects remain valid.

  The separate inline completion_rate in report-plan-outcome-request.json (a governance self-report block, not on the get_media_buy_delivery path) is intentionally left unchanged.

• e75f12f: Add property_list_exclude to the targeting overlay: a reference to a property list whose properties must not carry the buyer's ads, for brand-safety do-not-run lists (apps and sites). Mirrors collection_list_exclude and reuses property-list-ref.json. Exclude wins on overlap with property_list and applies regardless of the product's property_targeting_allowed flag. Sellers declare support via the property/collection list entries in the get_adcp_capabilities targeting table.

Patch Changes

• 4eda22a: Clarify the boundary between validate_input manifest preflight and sync_creatives dry-run trafficking rehearsal.
• 19a6447: Move stale active-window dates in compliance fixtures and 3.0 compatibility bundles forward so storyboard runs continue to exercise protocol behavior instead of calendar drift.
• c68d545: Fix a misleading get_media_buy_delivery example that implied buyers can look up delivery by their own reference. media_buy_ids are seller-assigned; the top-level buyer_ref field was removed in 3.0.0. The example is retitled "Correlating Your Own Reference", uses seller-assigned mb_... IDs, and adds a note pointing buyers to reconcile their own reference via context echoed on create_media_buy / get_media_buys.
• a335070: Clarify and enforce governed signal activation: activate_signal now documents governance_context, signal agents fail closed on governed accounts without a valid approval context, and signal governance compliance checks no longer require the signals tenant to own sync_plans.
• 24a83c5: Allow governance checks to accept human approval from ext.human_approval and use that approval to clear reallocation-threshold human review.

[aao-release-bot]

Argus is not auto-reviewing this PR because it is a generated Changesets release PR.

A human release reviewer should verify CI, package/version/changelog changes, and generated dist/** artifacts. Argus will resume on source PRs before the next release PR is generated.

[aao-secretariat]

Argus is not auto-reviewing this PR because it is a generated Changesets release PR.

A human release reviewer should verify CI, package/version/changelog changes, and generated dist/** artifacts. Argus will resume on source PRs before the next release PR is generated.