Version Packages (beta)

[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-beta.6

Minor Changes

• 4439b18: Add AdCP 3.2 CTV experience profiles implementing the IAB CTV Ad Portfolio without new channel-named canonicals. A shared ctv_ad_experience vocabulary (menu, pause, screensaver, overlay, squeezeback, in_scene) pairs each experience with the canonical contracts sellers ingest in practice: native_in_feed gains a menu profile with a Native 1.2 video slot, menu_placement (tile or headline banner), and focus_behavior; video_vast gains an explicit creative_type (linear, nonlinear, either) superseding linear_required, with nonlinear required for the five video-backed experiences and per-experience constraints (overlay and squeezeback need 10s minimum duration, in_scene needs 3s and forbids interactivity, pause is unfloored). SIMID remains available to ordinary Linear VAST but is rejected on every nonlinear CTV profile because VAST serializes InteractiveCreativeFile only under Linear MediaFiles. image accepts pause and screensaver (the image-plus-copy contract major pause-ad sellers ingest); video_hosted accepts screensaver; sponsored_placement accepts catalog-derived menu tiles, squeezeback, and in_scene. Shared motion_level (AdCOM attributes 21–23) and activation_method (QR, deep link, push, email, tune-in, SMS) vocabularies carry the interaction layer; activations are engagement events, never impressions. Pairings outside the experience matrix fail validation. The docs distinguish buyer-selected experience commitments from player-resolved runtime eligibility and define multi-canonical cells as sibling format options, not an implicit fallback field. The IAB OpenRTB/AdCOM signaling mapping (plcmt 5–9, playbackmethod 8–11, motion attributes, Native plcmttype) is documented as a bridge annex. Includes worked menu/pause/overlay examples and compliance vectors.

• 9a7cf31: Add the experimental AdCP 3.2 seller_rendered_stateful_display and coordinated_placements canonical creative formats. The stateful display declaration is an executable template contract — slots with limits, safe zones, breakpoints, and a disclosed state/transition graph — with supply_mode selecting who renders: components (buyer supplies focal-pointed imagery and copy; seller assembles every state × breakpoint deterministically), rendered_canvases (buyer authors externally against the published contract), or transitional layered_source. Sellers offering the canonical must support deterministic preview_creative rendering of every state × breakpoint. Sizing supports fixed, range, aspect-ratio, and fluid (full_bleed, gutter_residual, viewport-percent) breakpoints; single-state reveal units declare a reveal mechanic and underlay anchoring instead of fabricated states; transitions add in_view_timer, media_event, scroll direction, and hover inputs with per-state click URLs and a clickthrough policy. Validation enforces a dismissibility floor for overlay anchoring, an anti-strobe floor on timer cycles, per-canonical slot asset-type whitelists, and non-blocking LEAN policy warnings for IAB-prohibited trigger/anchoring combinations. coordinated_placements binds multiple product placements atomically with shared slots, optional sequence ordering, and per-component serving_policy, with placement-reference normalization and schema validation of referenced sibling options. Includes compliance scenarios, worked product declarations, and adopter documentation.

• 6a5ceb9: Add leaf metric identities so nested delivery values are individually declarable, committable, aggregatable, and sortable: quartile_25–quartile_100 (resolving to quartile_data.q1_views–q4_views) and viewable_rate, viewable_impressions, measurable_impressions, viewed_seconds (resolving to the same-named viewability fields) join available-metric and sort-metric. This closes an existing contradiction: committed-metric qualifier rules and delivery-metric-aggregate conditionals already referenced these metric_ids, and the shipped committed_metrics / metric_aggregates examples were invalid against their own schemas. Also adds the missing flat transactional scalars (commissionable_value, plays, cost_per_completed_view, cpm, downloads, units_sold, new_to_brand_units) to sort-metric, with survey/model-based lift scalars documented as intentionally sort-excluded. Leaf identities resolve to the nested canonical values — no duplicate flat response fields are introduced. A metric-identity coherence contract test now enforces enum/schema/example agreement.

  Seller conformance note: the viewability description now requires (MUST) that sellers populate standard on reported viewability objects when committed_metrics carry a viewability_standard qualifier — upgraded from a SHOULD. The trigger is any committed_metrics entry with qualifier.viewability_standard set, including the container metric_id: "viewability" (already in the enum). Sellers with an existing {metric_id: "viewability", qualifier: {viewability_standard: "mrc"}} commitment who were sometimes omitting standard become non-conformant. Sellers who never use the viewability_standard qualifier are unaffected.

Patch Changes

• 350a22c: Map the standard unsuffixed display_160x600 legacy format to a canonical 160×600 image declaration.

• a1e72ec: Fix 17 compliance storyboards that incorrectly included get_adcp_capabilities in required_tools alongside capability-specific tools. Because required_tools uses OR semantics, listing a universal tool made the storyboard-level gate trivially satisfied for every conformant agent — agents lacking the actual capability tool (e.g. sync_accounts, build_creative, get_products) would enter the storyboard and fail at the first capability-specific step instead of receiving a clean coverage-gap skip.

  Affected storyboards: billing_gate_dispatch, agent_notification_configs, and 15 scenarios across the media-buy and creative protocol families.

• 03a2186: Run current sales compliance storyboards in isolated child process groups with per-storyboard timeout, RSS telemetry, and durable result capture.

• b407de6: Require a human approval on the final release PR head before publishing committed protocol artifacts, and leave generated documentation snapshots open for human review.

• 9ef1084: Isolate the current sales storyboard matrix, quarantine issue-backed current-source failures without changing released bundle coverage, and terminate completed shard processes deterministically after their results are captured.

[aao-secretariat]

Ladon does not review bot-authored PRs.