@adcp/sdk 15.9.7 → 15.9.8

package/dist/lib/schemas-data/3.2/formats/canonical/audio_daast.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/audio_daast.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/audio_daast.json",
   "title": "Canonical Format: DAAST Audio",
   "description": "DAAST-tag-delivered audio creative (audio analog of VAST). Slot: `daast_tag` (daast asset, URL or inline XML). Tracking model: DAAST events inherent to the spec — `impression`, `firstQuartile`, `midpoint`, `thirdQuartile`, `complete`, `start`, `pause`, `resume`, `mute`, `unmute`, `clickTracking`, `error`. Distinct from `audio_hosted` (direct file with external tracking).",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     }
   ],
   "properties": {
@@ -25,12 +25,12 @@
       "description": "Default slots for audio_daast canonical. Buyer ships a DAAST tag (URL or inline XML, 1.0 or 1.1) plus an optional clickthrough URL. Tracking events are inherent to DAAST and don't require explicit slots."
     },
     "daast_version": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/daast-version.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/daast-version.json",
       "deprecated": true,
       "description": "Deprecated one-element alias for `daast_versions`. Producers use either the singular legacy alias or the plural 3.2 field, never both."
     },
     "daast_versions": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/daast-tracker-constraints.json#/definitions/daast_versions",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/daast-tracker-constraints.json#/definitions/daast_versions",
       "description": "Accepted DAAST versions for this format option. A tracker execution selector's daast_versions must be a nonempty subset of this set."
     },
     "duration_ms_range": {

package/dist/lib/schemas-data/3.2/formats/canonical/audio_hosted.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/audio_hosted.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/audio_hosted.json",
   "title": "Canonical Format: Hosted Audio",
   "description": "Direct audio creative — buyer ships an `audio` asset (mp3/aac/wav) for asset-driven products, or ships a `script` / `creative_brief` text asset for products where the seller produces audio internally (podcast host-reads, TTS synthesis). Optional companion slots: `companion_image`, `brand_name`, `landing_page_url`. Tracking model: standard impression + completion + companion-image-click pixels via universal_macros. Distinct from `audio_daast` (DAAST tag, inherent DAAST event tracking). For host-reads and synthesized audio, the format declares `asset_source: 'publisher_host_recorded'` or `'agent_synthesized'` plus `buyer_asset_acceptance: 'rejected'`; the format's `slots` declaration enumerates which assets the buyer ships (e.g., `script` text asset for host-reads). The seller decides how to consume each asset (render verbatim vs produce audio from text) — there is no separate manifest 'inputs' map; everything the buyer ships goes in `assets`.",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     }
   ],
   "properties": {

package/dist/lib/schemas-data/3.2/formats/canonical/audio_vast.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/audio_vast.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/audio_vast.json",
   "title": "Canonical Format: VAST Audio",
   "description": "VAST-tag-delivered audio creative. Standardized VAST audio support begins at 4.1; a seller may explicitly advertise older VAST versions only for legacy audio interoperability. Slot: `vast_tag` (vast asset, URL or inline XML). Tracking is inherent to VAST, including impression, start, quartiles, complete, click, error, pause/resume, and mute/unmute events. Distinct from `audio_hosted` (direct audio bytes) and `audio_daast` (legacy DAAST tag delivery).",
   "properties": {
@@ -22,19 +22,19 @@
     "vast_versions": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/vast-version.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/vast-version.json"
       },
       "minItems": 1,
       "uniqueItems": true,
       "description": "VAST audio versions accepted by this product format option. Standardized audio support begins at VAST 4.1; listing 2.0, 3.0, or 4.0 explicitly declares seller-supported legacy audio interoperability rather than standards-conformant VAST audio. The asset declares exactly one vast_version; compatibility requires membership in this set and the seller-wide execution set."
     },
     "vast_version": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/vast-version.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/vast-version.json",
       "deprecated": true,
       "description": "Deprecated one-element alias for vast_versions. Producers use either the singular legacy alias or the plural 3.2 field, never both. VAST 4.1+ is the standards-conformant audio profile; older values declare legacy audio interoperability."
     },
     "media_file_requirements": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/vast-media-file-requirements.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/vast-media-file-requirements.json",
       "description": "Technical acceptance constraints for alternative audio MediaFile renditions in each resolved InLine linear creative. Declared MIME types must be audio/*; visual-dimension constraints are invalid because VAST represents audio MediaFiles with width and height 0."
     },
     "duration_ms_range": {
@@ -72,7 +72,7 @@
   },
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     }
   ],
   "x-adcp-validation": {

package/dist/lib/schemas-data/3.2/formats/canonical/coordinated_placements.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/coordinated_placements.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/coordinated_placements.json",
   "title": "Canonical Format: Coordinated Placements",
   "description": "One creative manifest atomically supplies assets for multiple declared product placements. Each component binds to a public `Product.placements[]` entry and either declares an inline non-custom canonical format or references a sibling format option on the same product. Components cannot nest coordinated placements. The manifest supplies component slots under `component_assets.<component_id>`; `shared_slots` assets are supplied once at top level. Inventory exclusivity remains `Product.exclusivity`, not a creative-format parameter. Ordinary products whose placements accept independently assigned creatives do not need this canonical.",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     }
   ],
   "properties": {
@@ -47,7 +47,7 @@
             "description": "Stable coordination-local component identifier. Values MUST be unique within `components[]`."
           },
           "placement_ref": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/placement-ref.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/placement-ref.json",
             "description": "Public product placement this component supplies. MUST resolve against the containing product's `placements[]`."
           },
           "required": {
@@ -69,12 +69,12 @@
           "canvas_constraints": {
             "type": "array",
             "items": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/canvas-constraint.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/canvas-constraint.json"
             },
             "description": "Artwork constraints applied to this component, including safe areas and seller-reserved regions."
           },
           "format_option_ref": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/format-option-ref.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/format-option-ref.json",
             "description": "Reference to a sibling `format_options[]` entry on the same product. It MUST NOT resolve to `custom` or `coordinated_placements`."
           },
           "format_kind": {
@@ -127,7 +127,7 @@
                     "const": "image"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/image.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/image.json"
                   }
                 },
                 "required": [
@@ -141,7 +141,7 @@
                     "const": "html5"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/html5.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/html5.json"
                   }
                 },
                 "required": [
@@ -155,7 +155,7 @@
                     "const": "display_tag"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/display_tag.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/display_tag.json"
                   }
                 },
                 "required": [
@@ -169,7 +169,7 @@
                     "const": "image_carousel"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/image_carousel.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/image_carousel.json"
                   }
                 },
                 "required": [
@@ -183,7 +183,7 @@
                     "const": "video_hosted"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/video_hosted.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/video_hosted.json"
                   }
                 },
                 "required": [
@@ -197,7 +197,7 @@
                     "const": "video_vast"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/video_vast.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/video_vast.json"
                   }
                 },
                 "required": [
@@ -211,7 +211,7 @@
                     "const": "audio_hosted"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/audio_hosted.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/audio_hosted.json"
                   }
                 },
                 "required": [
@@ -225,7 +225,7 @@
                     "const": "audio_daast"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/audio_daast.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/audio_daast.json"
                   }
                 },
                 "required": [
@@ -239,7 +239,7 @@
                     "const": "sponsored_placement"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/sponsored_placement.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/sponsored_placement.json"
                   }
                 },
                 "required": [
@@ -253,7 +253,7 @@
                     "const": "native_in_feed"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/native_in_feed.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/native_in_feed.json"
                   }
                 },
                 "required": [
@@ -267,7 +267,7 @@
                     "const": "responsive_creative"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/responsive_creative.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/responsive_creative.json"
                   }
                 },
                 "required": [
@@ -281,7 +281,7 @@
                     "const": "agent_placement"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/agent_placement.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/agent_placement.json"
                   }
                 },
                 "required": [
@@ -295,7 +295,7 @@
                     "const": "seller_rendered_stateful_display"
                   },
                   "params": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/seller_rendered_stateful_display.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/seller_rendered_stateful_display.json"
                   }
                 },
                 "required": [

package/dist/lib/schemas-data/3.2/formats/canonical/display_tag.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/display_tag.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/display_tag.json",
   "title": "Canonical Format: Display Tag",
   "description": "Third-party-served display creative delivered as one of three explicit representations: a single ad-request URL, byte-preserved inline markup, or an atomic paired redirect (`ad_request_url` plus `clickthrough_url`). The backward-compatible default slot remains `tag_url` (`url_type: ad_request`). Format options accepting inline or paired delivery override `slots` with a `display_tag` asset and declare `supported_delivery_types`. Tracking is opaque to the seller except for declared macro resolution. Distinct from `image` and seller-hosted `html5` zip bundles.",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     },
     {
       "title": "Size-mode mutex",

package/dist/lib/schemas-data/3.2/formats/canonical/html5.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/html5.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/html5.json",
   "title": "Canonical Format: HTML5 Banner",
   "description": "Interactive HTML5 banner delivered as a zip archive. Slot: `html5_bundle` (zip asset). Tracking model: MRAID + IAB Open Measurement (OM-SDK) + click-tag macro substitution + backup image fallback. Receivers unpack the zip, validate internal structure, and serve from CDN. Distinct from `image` (static, non-interactive) and `display_tag` (third-party served). The zip's entry point is typically `index.html`; click handling uses `clickTag` (or `clickTAG`) macro substitution.",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     },
     {
       "title": "Size-mode mutex",

package/dist/lib/schemas-data/3.2/formats/canonical/image.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/image.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/image.json",
   "title": "Canonical Format: Image",
   "description": "Static image creative format. Slots: `image_main` (image asset, file or hosted URL), optional `headline` (text), `body_text` (text), `cta` (text/enum), `landing_page_url` (url). Tracking model: impression pixel + click URL via universal_macros, with optional viewability pixel. Distinct from `html5` (interactive bundles) and `display_tag` (third-party served). AR/dimensions narrow to specific sizes via product parameters — covers IAB display sizes (300x250, 728x90, 970x250, etc.) without a separate iab_size enum.",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     },
     {
       "title": "Size-mode mutex",
@@ -369,18 +369,18 @@
       "description": "Whether the product accepts buyer-uploaded assets. When `rejected`, the buyer cannot ship pre-rendered bytes directly — they must use build_creative (or sync_creatives with brief inputs or reference assets) so the seller produces or resolves the asset. Combined with `asset_source`, lets a product declare 'I produce assets from briefs and refuse buyer uploads' (asset_source=`seller_pre_rendered_from_brief`, buyer_asset_acceptance=`rejected`) or 'I accept existing post references, not uploaded bytes' (asset_source=`publisher_owned_reference`, buyer_asset_acceptance=`rejected`)."
     },
     "ctv_ad_experience": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/ctv-ad-experience.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/ctv-ad-experience.json",
       "description": "CTV experience this option serves. On `image` only `pause` and `screensaver` are valid — the image-plus-copy contract the major pause-ad sellers ingest (seller composites the frame; typical canvas 1920×1080 or a transparent-region overlay). Other experiences route per the matrix in docs/creative/ctv-experiences.mdx."
     },
     "motion_level": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/motion-level.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/motion-level.json",
       "description": "Accepted motion class (AdCOM attrs 21-22; `full_motion` is invalid on a static image canonical)."
     },
     "activation_methods": {
       "type": "array",
       "uniqueItems": true,
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/activation-method.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/activation-method.json"
       },
       "description": "Viewer activation mechanisms this option offers (e.g. `qr_code` on a pause frame). Activations are engagement events, not impressions."
     }

package/dist/lib/schemas-data/3.2/formats/canonical/image_carousel.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/image_carousel.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/image_carousel.json",
   "title": "Canonical Format: Image Carousel",
   "description": "Multi-card swipeable carousel. The buyer ships a `cards` slot whose value is an **array** of [card-asset](/schemas/core/assets/card-asset.json) objects (a single key with an array value — NOT one key per card, NOT dotted/bracketed paths). Each card-asset carries: `asset_type: \"card\"`, `media` (an image or video asset), optional `headline` (text), optional `landing_page_url` (url asset). Per-card structure is the same across all cards; mixed orientations not allowed within a single carousel. Tracking model: per-card impression and engagement pixels + carousel-level engagement (swipe, view-time). Allowed asset types for a card's `media` field: `image` and `video` (Meta-style mixed-media); platforms can narrow to image-only or video-only via `allowed_card_media_asset_types`.\n\nThe manifest's `assets.cards` value is an array of card-asset objects. Example: `\"cards\": [{\"asset_type\": \"card\", \"media\": {\"asset_type\": \"image\", \"url\": \"...\"}, \"headline\": \"Buy now\", \"landing_page_url\": {\"asset_type\": \"url\", \"url_type\": \"clickthrough\", \"url\": \"...\"}}, ...]`. Each card-asset validates against the card schema; per-card platform extensions attach via the card's `platform_extensions` field, never via inline non-canonical keys.",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     }
   ],
   "properties": {

package/dist/lib/schemas-data/3.2/formats/canonical/native_in_feed.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/native_in_feed.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/native_in_feed.json",
   "title": "Canonical Format: Native In-Feed",
   "description": "IAB-shaped native creative for in-feed and content-recommendation surfaces. Default slots cover the primary IAB OpenRTB Native 1.2 asset types — `title` (Title Asset), `body_text` (Data Asset type 2), `main_image` (Image Asset main), `icon` (Image Asset icon), `cta` (Data Asset type 12), `advertiser_name` (Data Asset type 1), `sponsored_label` (Title-adjacent), `landing_page_url` (Link Asset), `display_url` (Data Asset type 11 — visible URL/domain, distinct from clickthrough), `rating` (Data Asset type 3 — app/product rating), `price` (Data Asset type 6 — product price), plus renderer-fired `impression_tracker` / `viewability_tracker` / `click_tracker` (`pixel_tracker`). Products MAY use `slots_override` to add other IAB Native data asset types (likes — type 4, downloads — type 5, saleprice — type 7, phone_number — type 8, address — type 9, desc2 — type 10, etc.) or to remove slots the surface doesn't render. The publisher's renderer assembles these into its own look-and-feel — feed card, content-recommendation slot, in-stream native unit. Buyer ships a single asset bundle; the surface chooses presentation.\n\n**Scope (normative — buyer-agent routing).** This canonical is the home for:\n- IAB OpenRTB Native 1.2 in-feed native ads (publisher feeds, app feeds)\n- Content-recommendation widgets (Taboola, Outbrain, Yahoo Recommendations)\n- AdMob Native / Yahoo Native publisher slots\n- In-feed sponsored placements without catalog dependency\n\n**Not this canonical:**\n- Catalog-driven retail-media (Amazon SP, Criteo SP, CitrusAd SP) — use `sponsored_placement` (requires `source_catalog`).\n- Algorithmic surface that picks from a buyer-supplied asset pool (Google PMax, Meta Advantage+) — use `responsive_creative`.\n- Multi-card carousel — use `image_carousel`.\n- Video-first native units where the asset is a hosted video file — use `video_hosted` with `applies_to_channels: [\"native\"]`. (Distinct from the CTV menu profile: a menu hero remains this canonical because the platform assembles the full asset bundle and the video rides the Native 1.2 `vasttag` video asset, playing on focus rather than being the unit itself.)\n\nDistinct from `sponsored_placement` along the catalog axis: native_in_feed is asset-bundle composition; sponsored_placement is catalog-row composition. A buyer agent reading `format_kind: native_in_feed` knows to assemble title + image + body + CTA; reading `format_kind: sponsored_placement` knows to attach a catalog feed.",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     },
     {
       "if": {
@@ -150,7 +150,7 @@
       "description": "Default slot shape for native_in_feed. Mirrors IAB OpenRTB Native 1.2 asset types, including the Native video asset: `video` carries a VAST document (the Native 1.2 `vasttag` field) for video-bearing native units such as CTV menu heroes with focus-triggered playback. Products MAY override (`slots_override` on the projection ref) to narrow per-slot limits (`max_chars` on title/body) or remove unused slots (a content-recommendation slot that doesn't display an icon)."
     },
     "ctv_ad_experience": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/ctv-ad-experience.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/ctv-ad-experience.json",
       "description": "CTV experience this option serves. On native_in_feed `menu` and `overlay` are valid. `menu`: smart-TV home/menu surfaces where the platform assembles buyer assets (background/main image, logo/icon, copy, optional focus-triggered video); `menu_placement` selects the tile vs headline-banner variant, and catalog-derived sponsored tiles route to `sponsored_placement` instead. `overlay`: seller-composited in-stream overlays supplied as an asset bundle (video, logo, imagery, copy, activation copy) — the contract overlay sellers that do not ingest VAST tags use; VAST-ingesting sellers publish a `video_vast` sibling option instead. The wire name stays `native_in_feed` for 3.x even though neither surface is literally in-feed."
     },
     "menu_placement": {
@@ -171,14 +171,14 @@
       "description": "What happens when the viewer's remote focus lands on the unit. `autoplay_*` requires a `video` asset; playback method maps to AdCOM playbackmethod on OpenRTB bridges. Valid only with `ctv_ad_experience: \"menu\"`."
     },
     "motion_level": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/motion-level.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/motion-level.json",
       "description": "Accepted motion class for the rendered unit (AdCOM attrs 21-23)."
     },
     "activation_methods": {
       "type": "array",
       "uniqueItems": true,
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/activation-method.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/activation-method.json"
       },
       "description": "Viewer activation mechanisms this option offers (QR, deep link, send-to-device). Activations are engagement events, not impressions."
     },

package/dist/lib/schemas-data/3.2/formats/canonical/responsive_creative.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/responsive_creative.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/responsive_creative.json",
   "title": "Canonical Format: Responsive Creative",
   "description": "Buyer supplies a pool of typed assets (multiple headlines, descriptions, images, videos, logos); the surface algorithmically composes combinations per placement. **Composition is algorithmic** — surface picks combinations and reports per-asset performance breakdowns. Covers Google Responsive Display Ads (RDA), Responsive Search Ads (RSA), Performance Max (PMax), Demand Gen, and Meta Advantage+ creative. Industry term: \"Responsive\" (Google) / \"Advantage+ creative\" (Meta) / \"Dynamic Creative\" (older Meta term). Distinct from `sponsored_placement` (catalog-driven, deterministic) and `agent_placement` (AI-surface composition). The structured `slots` field below enumerates expected canonical asset_group_id slots; per-slot count/length narrowing lives in flat parameters (`headlines_min`, `headline_max_chars`, etc.).",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     }
   ],
   "properties": {

package/dist/lib/schemas-data/3.2/formats/canonical/seller_rendered_stateful_display.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/seller_rendered_stateful_display.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/seller_rendered_stateful_display.json",
   "title": "Canonical Format: Seller-Rendered Stateful Display",
   "description": "Seller-rendered display unit whose declaration is an executable template contract: buyer-known visual states, explicit transitions, breakpoint canvases, and per-state slot bindings. The seller owns the runtime; `supply_mode` declares which end the buyer feeds. For machine-rendered `components` and `rendered_canvases` supply, sellers MUST support `preview_creative` returning every state × breakpoint from a candidate manifest. `layered_source` instead follows the asynchronous seller-production preview path after the declared production window. `composition_model: deterministic` describes serving the finished states, not instant derivation from layered source. Buyer-executable HTML/MRAID is `html5`, a buyer-delivered tag is `display_tag`, arbitrary games/hotspots/scripts remain `custom`, and per-impression algorithmic assembly is `responsive_creative`.",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     }
   ],
   "properties": {
@@ -843,7 +843,7 @@
       "type": "array",
       "description": "Rectangular areas constraining buyer artwork. Omitted state/breakpoint selectors apply the constraint to every canvas. For fluid or range-sized breakpoints, use percent-unit regions.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/canvas-constraint.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/canvas-constraint.json"
       }
     },
     "duration_ms_range": {

package/dist/lib/schemas-data/3.2/formats/canonical/sponsored_placement.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/sponsored_placement.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/sponsored_placement.json",
   "title": "Canonical Format: Sponsored Placement (retail-media catalog-driven)",
   "description": "Catalog-driven retail-media format. Slot: `source_catalog` (catalog asset — product/SKU/ASIN/GTIN catalog reference, REQUIRED), optional `hero_asset`, optional `landing_page_url`. Buyer supplies the catalog reference; surface composes per-item or multi-item rendering using its native placement template. **Composition is deterministic** — buyer can predict per-slot rendering from the catalog item structure. Tracking model: per-item impression + click + conversion (catalog-keyed via offering_id/sku/gtin macros). Covers Amazon Sponsored Products, Criteo Sponsored Products, CitrusAd Sponsored Products, Walmart Connect Sponsored Products, Pinterest Collection (catalog-driven mode).\n\n**Scope (normative — buyer-agent routing).** This canonical is the home for catalog-driven retail-media placements ONLY. The defining feature is the `source_catalog` slot — products under this canonical compose their creative *per catalog item* using the buyer-supplied catalog feed. Without a catalog feed there is nothing to render against. Buyer agents reading `format_kind: sponsored_placement` MUST attach a catalog reference; sellers MUST require `source_catalog` in the manifest.\n\n**Not this canonical (route elsewhere):**\n- IAB in-feed native ads, content-recommendation widgets (Taboola, Outbrain, Yahoo Native, AdMob Native, in-feed sponsored cards) — use `native_in_feed` (asset-bundle composition; no catalog).\n- Algorithmic surface that picks from a buyer-supplied asset pool (Google PMax, Meta Advantage+) — use `responsive_creative`.\n- Single-image or single-video creative — use `image` or `video_hosted`.\n\nThe earlier broader framing ('any sponsored placement') was too loose for buyer-agent routing — a buyer reading `sponsored_placement` couldn't disambiguate a catalog-driven Amazon SP from an in-feed Taboola widget. As of 3.1, the canonical is narrowed to catalog-keyed retail-media; native moves to `native_in_feed`. Distinct from `responsive_creative` (algorithmic combinator from buyer pool) and `agent_placement` (text/audio AI-surface composition).",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     },
     {
       "if": {
@@ -57,7 +57,7 @@
     "supported_catalog_types": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/catalog-type.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/catalog-type.json"
       },
       "description": "Catalog types this product accepts."
     },
@@ -124,7 +124,7 @@
       "description": "How each per-item creative is produced. Covers the same production-source axis as `asset_source` on `image` / `video_hosted` / `audio_hosted` but with a 4-value subset — drops `publisher_host_recorded` because it's audio-specific and doesn't apply to retail-media catalog placements. SDK codegen MAY share a base enum and narrow per-canonical, or emit two distinct enums; either way the wire values overlap exactly for the 4 retained values. `buyer_uploaded` (default, current Amazon/Criteo/CitrusAd pattern): the buyer's catalog already contains rendered assets per item; the seller composes the placement using those assets. (\"Uploaded\" reads slightly off for catalog-keyed items where the buyer didn't actively upload bytes — the catalog ingestion already supplied them — but the semantic is the same: rendered bytes are buyer-supplied, not seller-produced.) `seller_pre_rendered_from_brief`: the buyer ships a brief plus the catalog reference; the seller renders one creative per catalog item from the brief at sync_creatives time. `seller_human_designed`: seller's design team produces per-item renders manually. `agent_synthesized`: AI synthesis pipeline produces per-item renders; pair with `synthesis_nondeterministic: true` for Veo/Sora-class generative video applied per item. Captures the multi-output generative pattern (1 brief × N catalog items → N rendered creatives) under the existing canonical without requiring a separate canonical. Distinct from `fanout_mode`, which describes how items map to delivery slots after rendering."
     },
     "ctv_ad_experience": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/ctv-ad-experience.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/ctv-ad-experience.json",
       "description": "CTV experience this option serves. On `sponsored_placement`: `menu` (sponsored app/content tiles and rows whose assets derive from a catalog listing — Fire-TV-tile pattern), `squeezeback`, and `in_scene` (seller-composited brand integrations produced from the catalog/brief rather than a buyer wire creative). Asset-bundle menu heroes route to `native_in_feed`."
     }
   },

package/dist/lib/schemas-data/3.2/formats/canonical/video_hosted.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/video_hosted.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/video_hosted.json",
   "title": "Canonical Format: Hosted Video",
   "description": "Direct video file (mp4/webm/mov) hosted by the buyer. Slot: `video_main` (video asset, file or hosted URL), optional `headline`, `brand_name`, `cta`, `companion_banner`, `landing_page_url`. Tracking model: IAB Open Measurement SDK + external impression/click/quartile pixels via universal_macros. Orientation is a parameter (vertical 9:16 / horizontal 16:9 / square 1:1); slot shape includes optional `brand_name` (typical for vertical short-form) and optional `companion_banner` (typical for horizontal instream). Distinct from `video_vast` (VAST tag, inherent VAST event tracking) — receivers fire impression and click pixels at delivery time.",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     },
     {
       "if": {
@@ -242,7 +242,7 @@
       "description": "Whether the product accepts buyer-uploaded video. When `rejected`, the buyer cannot ship a video asset directly — they must use build_creative, sync_creatives with brief inputs, or sync_creatives with an accepted reference asset so the seller produces or resolves the video."
     },
     "ctv_ad_experience": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/ctv-ad-experience.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/ctv-ad-experience.json",
       "description": "CTV experience this option serves. On `video_hosted` only `screensaver` is valid (ambient looping video the platform plays on idle). Other experiences route per the matrix in docs/creative/ctv-experiences.mdx; linear CTV video declares no experience."
     }
   },

package/dist/lib/schemas-data/3.2/formats/canonical/video_vast.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/video_vast.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/video_vast.json",
   "title": "Canonical Format: VAST Video",
   "description": "VAST-tag-delivered video creative. Slot: `vast_tag` (vast asset, URL or inline XML, VAST 2.x-4.x). Tracking model: VAST events inherent to the spec — `impression`, `firstQuartile`, `midpoint`, `thirdQuartile`, `complete`, `start`, `pause`, `resume`, `mute`, `unmute`, `expand`, `collapse`, `fullscreen`, `creativeView`, `clickTracking`, `error`. VPAID interactivity via `vpaid_enabled: true` flag. SIMID is carried by the first-class VAST 4.1+ `<InteractiveCreativeFile apiFramework=\"SIMID\">` element on Linear creatives. Orientation is a parameter (vertical / horizontal / square). Distinct from `video_hosted` (direct file with external tracking).",
   "properties": {
@@ -34,19 +34,19 @@
     "vast_versions": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/vast-version.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/vast-version.json"
       },
       "minItems": 1,
       "uniqueItems": true,
       "description": "VAST versions accepted by this product format option. The asset still declares exactly one `vast_version`; compatibility requires membership in this set and the seller-wide execution set."
     },
     "vast_version": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/vast-version.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/vast-version.json",
       "deprecated": true,
       "description": "Deprecated one-element alias for `vast_versions`. Producers use either the singular legacy alias or the plural 3.2 field, never both."
     },
     "media_file_requirements": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/vast-media-file-requirements.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/vast-media-file-requirements.json",
       "description": "Technical acceptance constraints for alternative VAST MediaFile renditions. Each applicable resolved InLine linear creative needs at least one MediaFile satisfying all declared constraints."
     },
     "vpaid_enabled": {
@@ -109,18 +109,18 @@
       "description": "Required VAST creative class: `linear` (in-stream Linear), `nonlinear` (NonLinearAds overlay-class), or `either`. Supersedes `linear_required`; when both are present `creative_type` wins, and validators treat `linear_required: true` with no `creative_type` as `linear`."
     },
     "ctv_ad_experience": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/ctv-ad-experience.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/ctv-ad-experience.json",
       "description": "CTV experience this option is eligible to serve. On video_vast only `pause`, `screensaver`, `overlay`, `squeezeback`, and `in_scene` are valid (`menu` routes to native_in_feed or sponsored_placement), and `creative_type` MUST be `nonlinear`. Because VAST places `<InteractiveCreativeFile>` only under Linear `<MediaFiles>`, `simid_supported` MUST NOT be true on any of these NonLinear profiles. Per-experience floors: `overlay` and `squeezeback` require a 10s minimum duration; `in_scene` requires a 3s minimum brand-exposure duration and forbids interactivity (`vpaid_enabled` MUST NOT be true); `pause` has no duration floor and ends on viewer or device action."
     },
     "motion_level": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/motion-level.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/motion-level.json",
       "description": "Accepted motion class for the rendered creative (AdCOM attrs 21-23)."
     },
     "activation_methods": {
       "type": "array",
       "uniqueItems": true,
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/activation-method.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/activation-method.json"
       },
       "description": "Viewer activation mechanisms this option offers. Activations are engagement events, not impressions."
     },
@@ -144,7 +144,7 @@
   },
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/formats/canonical/_base.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/formats/canonical/_base.json"
     },
     {
       "if": {

package/dist/lib/schemas-data/3.2/governance/accepted-governance-agents.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/governance/accepted-governance-agents.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/governance/accepted-governance-agents.json",
   "title": "Accepted Governance Agents",
   "description": "Seller-wide advisory acceptance matchers for buyer-bound governance agents. The union is permissive: a candidate satisfying any matcher is accepted by this declaration. The sync_governance response remains authoritative per account.",
   "type": "object",

package/dist/lib/schemas-data/3.2/governance/attribute-definition.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/governance/attribute-definition.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/governance/attribute-definition.json",
   "title": "Attribute Definition",
   "description": "Definition of a restricted personal data attribute in the policy registry. Attributes are the shared vocabulary used across campaign plans (restricted_attributes), signal definitions (restricted_attributes), and data marketplace catalogs. Each definition documents the regulatory basis, scope, and common signal patterns for the attribute category.",
   "type": "object",

package/dist/lib/schemas-data/3.2/governance/audience-constraints.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/governance/audience-constraints.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/governance/audience-constraints.json",
   "title": "Audience Constraints",
   "description": "Buyer-defined audience targeting constraints for a campaign plan. Specifies who the campaign should and should not reach. The governance agent evaluates seller targeting against these constraints during check_governance.",
   "type": "object",
@@ -9,7 +9,7 @@
       "type": "array",
       "description": "Desired audience criteria. The seller's targeting should align with these. Each criterion is evaluated independently — the combined targeting should satisfy at least one inclusion criterion.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/audience-selector.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/audience-selector.json"
       },
       "minItems": 1
     },
@@ -17,7 +17,7 @@
       "type": "array",
       "description": "Excluded audience criteria. The seller's targeting must not overlap with these. Exclusions take precedence over inclusions. Used for protected groups, vulnerable communities, regulatory restrictions, or brand safety.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/audience-selector.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/audience-selector.json"
       },
       "minItems": 1
     }