@adcp/sdk 6.16.1 → 6.18.0

package/dist/lib/schemas-data/3.0/core/protocol-envelope.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/protocol-envelope.json",
+  "$id": "/schemas/3.0.9/core/protocol-envelope.json",
   "title": "Protocol Envelope",
   "description": "Standard envelope structure for AdCP task responses. This envelope is added by the protocol layer (MCP, A2A, REST) and wraps the task-specific response payload. Task response schemas should NOT include these fields - they are protocol-level concerns.",
   "type": "object",
@@ -15,7 +15,7 @@
       "x-entity": "task"
     },
     "status": {
-      "$ref": "/schemas/3.0.8/enums/task-status.json",
+      "$ref": "/schemas/3.0.9/enums/task-status.json",
       "description": "Current task execution state. Indicates whether the task is completed, in progress (working), submitted for async processing, failed, or requires user input. Managed by the protocol layer. Agents MUST NOT emit the legacy task_status or response_status fields alongside this field — the status field is the single authoritative task state."
     },
     "message": {
@@ -33,7 +33,7 @@
       "default": false
     },
     "push_notification_config": {
-      "$ref": "/schemas/3.0.8/core/push-notification-config.json",
+      "$ref": "/schemas/3.0.9/core/push-notification-config.json",
       "description": "Push notification configuration for async task updates (A2A and REST protocols). Echoed from the request to confirm webhook settings. Specifies URL, authentication scheme (Bearer or HMAC-SHA256), and credentials. MCP uses progress notifications instead of webhooks."
     },
     "governance_context": {

package/dist/lib/schemas-data/3.0/core/provenance.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/provenance.json",
+  "$id": "/schemas/3.0.9/core/provenance.json",
   "title": "Provenance",
   "description": "Declares how content was produced, whether AI was involved, and what disclosure obligations apply. Attaches to creative manifests, individual assets, or content-standards artifacts. When present at multiple levels, the most specific provenance object replaces the inherited one entirely (no field-level merging). Provenance is a claim by the declaring party — receiving parties should verify claims independently via their own detection tools.",
   "type": "object",
   "properties": {
     "digital_source_type": {
-      "$ref": "/schemas/3.0.8/enums/digital-source-type.json",
+      "$ref": "/schemas/3.0.9/enums/digital-source-type.json",
       "description": "IPTC-aligned classification of AI involvement in producing this content"
     },
     "ai_tool": {
@@ -143,7 +143,7 @@
                 "minProperties": 1,
                 "properties": {
                   "persistence": {
-                    "$ref": "/schemas/3.0.8/enums/disclosure-persistence.json",
+                    "$ref": "/schemas/3.0.9/enums/disclosure-persistence.json",
                     "description": "How long the disclosure must persist during content playback or display"
                   },
                   "min_duration_ms": {
@@ -155,13 +155,13 @@
                     "type": "array",
                     "description": "Preferred disclosure positions in priority order. The first position a format supports should be used.",
                     "items": {
-                      "$ref": "/schemas/3.0.8/enums/disclosure-position.json"
+                      "$ref": "/schemas/3.0.9/enums/disclosure-position.json"
                     },
                     "minItems": 1,
                     "uniqueItems": true
                   },
                   "ext": {
-                    "$ref": "/schemas/3.0.8/core/ext.json"
+                    "$ref": "/schemas/3.0.9/core/ext.json"
                   }
                 },
                 "additionalProperties": true
@@ -227,7 +227,7 @@
       }
     },
     "ext": {
-      "$ref": "/schemas/3.0.8/core/ext.json"
+      "$ref": "/schemas/3.0.9/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.0/core/publisher-property-selector.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/publisher-property-selector.json",
+  "$id": "/schemas/3.0.9/core/publisher-property-selector.json",
   "title": "Publisher Property Selector",
   "description": "Selects properties from a publisher's adagents.json. Used for both product definitions and agent authorization. Supports three selection patterns: all properties, specific IDs, or by tags.",
   "discriminator": {
@@ -46,7 +46,7 @@
           "type": "array",
           "description": "Specific property IDs from the publisher's adagents.json",
           "items": {
-            "$ref": "/schemas/3.0.8/core/property-id.json"
+            "$ref": "/schemas/3.0.9/core/property-id.json"
           },
           "minItems": 1
         }
@@ -76,7 +76,7 @@
           "type": "array",
           "description": "Property tags from the publisher's adagents.json. Selector covers all properties with these tags",
           "items": {
-            "$ref": "/schemas/3.0.8/core/property-tag.json"
+            "$ref": "/schemas/3.0.9/core/property-tag.json"
           },
           "minItems": 1
         }

package/dist/lib/schemas-data/3.0/core/push-notification-config.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/push-notification-config.json",
+  "$id": "/schemas/3.0.9/core/push-notification-config.json",
   "title": "Push Notification Config",
   "description": "Webhook configuration for asynchronous task notifications. Uses A2A-compatible PushNotificationConfig structure. By default, webhooks are signed with the AdCP RFC 9421 profile (see docs/building/implementation/security.mdx#webhook-callbacks) — the seller signs outbound with a key published at the jwks_uri on its own brand.json `agents[]` entry and the buyer verifies against that JWKS, so no shared secret crosses the wire. The optional `authentication` block selects the legacy Bearer or HMAC-SHA256 fallback for compatibility with receivers that have not yet adopted the 9421 profile; this fallback is deprecated and will be removed in AdCP 4.0. Note: the `idempotency_key` that receivers dedup on lives inside the webhook **payload** body (see docs/building/implementation/webhooks.mdx#reliability and the mcp-webhook-payload schema), not in this configuration object — this schema only describes the receiver-side transport config sent to the seller. This schema is designed for composition via allOf - consuming schemas should define their own additionalProperties constraints.",
   "type": "object",
@@ -23,7 +23,7 @@
           "type": "array",
           "description": "Array of authentication schemes. Supported: ['Bearer'] for simple token auth, ['HMAC-SHA256'] for legacy shared-secret signing. Both are deprecated; new integrations SHOULD omit `authentication` and use the RFC 9421 webhook profile.",
           "items": {
-            "$ref": "/schemas/3.0.8/enums/auth-scheme.json"
+            "$ref": "/schemas/3.0.9/enums/auth-scheme.json"
           },
           "minItems": 1,
           "maxItems": 1

package/dist/lib/schemas-data/3.0/core/real-estate-item.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/real-estate-item.json",
+  "$id": "/schemas/3.0.9/core/real-estate-item.json",
   "title": "Real Estate Item",
   "description": "A property listing within a real-estate-type catalog. Carries the address, pricing, and specification data that platforms use for real estate ads and dynamic remarketing. Maps to Google DynamicRealEstateAsset, Meta home listing catalogs, and similar formats.",
   "type": "object",
@@ -42,7 +42,7 @@
       "additionalProperties": false
     },
     "price": {
-      "$ref": "/schemas/3.0.8/core/price.json",
+      "$ref": "/schemas/3.0.9/core/price.json",
       "description": "Property price or rental rate. Use period 'month' for rentals."
     },
     "property_type": {
@@ -156,12 +156,12 @@
       "type": "array",
       "description": "Typed creative asset pools for this property listing. Uses the same OfferingAssetGroup structure as offering-type catalogs. Standard group IDs: 'images_landscape' (exterior/interior hero), 'images_vertical' (9:16 for Stories), 'images_square' (1:1). Enables formats to declare typed image requirements that map unambiguously to the right asset regardless of platform.",
       "items": {
-        "$ref": "/schemas/3.0.8/core/offering-asset-group.json"
+        "$ref": "/schemas/3.0.9/core/offering-asset-group.json"
       },
       "minItems": 1
     },
     "ext": {
-      "$ref": "/schemas/3.0.8/core/ext.json"
+      "$ref": "/schemas/3.0.9/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.0/core/reference-asset.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/reference-asset.json",
+  "$id": "/schemas/3.0.9/core/reference-asset.json",
   "title": "Reference Asset",
   "description": "A reference asset that provides creative context. Carries visual materials (mood boards, product shots, example creatives) with semantic roles that tell creative agents how to use them.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/reporting-capabilities.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/reporting-capabilities.json",
+  "$id": "/schemas/3.0.9/core/reporting-capabilities.json",
   "title": "Reporting Capabilities",
   "description": "Reporting capabilities available for a product",
   "type": "object",
@@ -9,7 +9,7 @@
       "type": "array",
       "description": "Supported reporting frequency options",
       "items": {
-        "$ref": "/schemas/3.0.8/enums/reporting-frequency.json"
+        "$ref": "/schemas/3.0.9/enums/reporting-frequency.json"
       },
       "minItems": 1,
       "uniqueItems": true
@@ -42,7 +42,7 @@
       "type": "array",
       "description": "Metrics available in reporting. Impressions and spend are always implicitly included. When a creative format declares reported_metrics, buyers receive the intersection of these product-level metrics and the format's reported_metrics.",
       "items": {
-        "$ref": "/schemas/3.0.8/enums/available-metric.json"
+        "$ref": "/schemas/3.0.9/enums/available-metric.json"
       },
       "uniqueItems": true,
       "examples": [
@@ -68,7 +68,7 @@
       "description": "Whether this product supports keyword-level metric breakdowns in delivery reporting (by_keyword within by_package)"
     },
     "supports_geo_breakdown": {
-      "$ref": "/schemas/3.0.8/core/geo-breakdown-support.json",
+      "$ref": "/schemas/3.0.9/core/geo-breakdown-support.json",
       "description": "Geographic breakdown support for this product. Declares which geo levels and systems are available for by_geo reporting within by_package."
     },
     "supports_device_type_breakdown": {
@@ -100,7 +100,7 @@
       "type": "array",
       "description": "Measurement maturation stages available for this product. Used by any channel where billing-grade data is produced in phases rather than arriving final on day one. Examples: broadcast/linear TV (Live → C3 → C7 DVR accumulation), DOOH (tentative plays → post-IVT/fraud-check final), digital with IVT filtering (raw → GIVT filtered → SIVT filtered), podcast (7-day downloads → 30-day downloads). Each window defines an accumulation period and expected data availability. When present, delivery reports reference a specific window_id. Sellers whose data is final on first delivery typically omit this.",
       "items": {
-        "$ref": "/schemas/3.0.8/core/measurement-window.json"
+        "$ref": "/schemas/3.0.9/core/measurement-window.json"
       },
       "minItems": 1,
       "uniqueItems": true

package/dist/lib/schemas-data/3.0/core/reporting-webhook.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/reporting-webhook.json",
+  "$id": "/schemas/3.0.9/core/reporting-webhook.json",
   "title": "Reporting Webhook",
   "description": "Webhook configuration for automated reporting delivery. Configures where and how campaign performance reports are sent.",
   "type": "object",
@@ -17,20 +17,20 @@
     },
     "authentication": {
       "type": "object",
-      "description": "Authentication configuration for webhook delivery (A2A-compatible)",
+      "description": "Legacy authentication configuration for webhook delivery (A2A-compatible). Opts the receiver into Bearer or HMAC-SHA256 signing. Both schemes are deprecated; the preferred signing profile for new integrations is RFC 9421, where the seller signs with a key published at its brand.json agents[] entry and the buyer verifies against the seller's JWKS — no shared secret crosses the wire (see docs/building/implementation/security.mdx#webhook-callbacks). This field is required in AdCP 3.x; the requirement is removed in AdCP 4.0 when the default RFC 9421 path becomes the only path.",
       "properties": {
         "schemes": {
           "type": "array",
-          "description": "Array of authentication schemes. Supported: ['Bearer'] for simple token auth, ['HMAC-SHA256'] for signature verification (recommended for production)",
+          "description": "Array of authentication schemes. ['Bearer'] for simple token auth, ['HMAC-SHA256'] for legacy shared-secret signing. Both are deprecated; new integrations SHOULD use the RFC 9421 webhook signing profile instead.",
           "items": {
-            "$ref": "/schemas/3.0.8/enums/auth-scheme.json"
+            "$ref": "/schemas/3.0.9/enums/auth-scheme.json"
           },
           "minItems": 1,
           "maxItems": 1
         },
         "credentials": {
           "type": "string",
-          "description": "Credentials for authentication. For Bearer: token sent in Authorization header. For HMAC-SHA256: shared secret used to generate signature. Minimum 32 characters. Exchanged out-of-band during onboarding.",
+          "description": "Credentials for the legacy scheme. For Bearer: token sent in Authorization header. For HMAC-SHA256: shared secret used to generate signature. Minimum 32 characters. Exchanged out-of-band during onboarding.",
           "minLength": 32
         }
       },
@@ -53,7 +53,7 @@
       "type": "array",
       "description": "Optional list of metrics to include in webhook notifications. If omitted, all available metrics are included. Must be subset of product's available_metrics.",
       "items": {
-        "$ref": "/schemas/3.0.8/enums/available-metric.json"
+        "$ref": "/schemas/3.0.9/enums/available-metric.json"
       },
       "uniqueItems": true
     }

package/dist/lib/schemas-data/3.0/core/requirements/asset-requirements.json

@@ -1,44 +1,44 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/asset-requirements.json",
   "title": "Asset Requirements",
   "description": "Technical requirements for creative assets. The applicable schema is determined by the sibling asset_type field.",
   "anyOf": [
     {
-      "$ref": "/schemas/3.0.8/core/requirements/image-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/image-asset-requirements.json"
     },
     {
-      "$ref": "/schemas/3.0.8/core/requirements/video-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/video-asset-requirements.json"
     },
     {
-      "$ref": "/schemas/3.0.8/core/requirements/audio-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/audio-asset-requirements.json"
     },
     {
-      "$ref": "/schemas/3.0.8/core/requirements/text-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/text-asset-requirements.json"
     },
     {
-      "$ref": "/schemas/3.0.8/core/requirements/markdown-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/markdown-asset-requirements.json"
     },
     {
-      "$ref": "/schemas/3.0.8/core/requirements/html-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/html-asset-requirements.json"
     },
     {
-      "$ref": "/schemas/3.0.8/core/requirements/css-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/css-asset-requirements.json"
     },
     {
-      "$ref": "/schemas/3.0.8/core/requirements/javascript-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/javascript-asset-requirements.json"
     },
     {
-      "$ref": "/schemas/3.0.8/core/requirements/vast-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/vast-asset-requirements.json"
     },
     {
-      "$ref": "/schemas/3.0.8/core/requirements/daast-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/daast-asset-requirements.json"
     },
     {
-      "$ref": "/schemas/3.0.8/core/requirements/url-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/url-asset-requirements.json"
     },
     {
-      "$ref": "/schemas/3.0.8/core/requirements/webhook-asset-requirements.json"
+      "$ref": "/schemas/3.0.9/core/requirements/webhook-asset-requirements.json"
     }
   ]
 }

package/dist/lib/schemas-data/3.0/core/requirements/audio-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/audio-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/audio-asset-requirements.json",
   "title": "Audio Asset Requirements",
   "description": "Requirements for audio creative assets.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/requirements/catalog-field-binding.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/catalog-field-binding.json",
+  "$id": "/schemas/3.0.9/core/requirements/catalog-field-binding.json",
   "title": "Catalog Field Binding",
   "description": "Maps a format template slot to a catalog item field or typed asset pool. The 'kind' field identifies the binding variant. All bindings are optional — agents can still infer mappings without them.",
   "definitions": {
@@ -21,7 +21,7 @@
           "description": "Dot-notation path to the field on the catalog item (e.g., 'name', 'price.amount', 'location.city')."
         },
         "ext": {
-          "$ref": "/schemas/3.0.8/core/ext.json"
+          "$ref": "/schemas/3.0.9/core/ext.json"
         }
       },
       "required": [
@@ -48,7 +48,7 @@
           "description": "The asset_group_id on the catalog item's assets array to pull from (e.g., 'images_landscape', 'images_vertical', 'logo')."
         },
         "ext": {
-          "$ref": "/schemas/3.0.8/core/ext.json"
+          "$ref": "/schemas/3.0.9/core/ext.json"
         }
       },
       "required": [
@@ -99,7 +99,7 @@
           "minItems": 1
         },
         "ext": {
-          "$ref": "/schemas/3.0.8/core/ext.json"
+          "$ref": "/schemas/3.0.9/core/ext.json"
         }
       },
       "required": [

package/dist/lib/schemas-data/3.0/core/requirements/catalog-requirements.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/catalog-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/catalog-requirements.json",
   "title": "Catalog Requirements",
   "description": "Format-level declaration of what catalog feeds a creative needs. Formats that render product listings, store locators, or promotional content declare which catalog types must be synced and what fields each catalog must provide. Buyers use this to ensure the right catalogs are synced before submitting creatives.",
   "type": "object",
   "properties": {
     "catalog_type": {
-      "$ref": "/schemas/3.0.8/enums/catalog-type.json",
+      "$ref": "/schemas/3.0.9/enums/catalog-type.json",
       "description": "The catalog type this requirement applies to"
     },
     "required": {
@@ -37,7 +37,7 @@
       "type": "array",
       "description": "Accepted feed formats for this catalog type. When specified, the synced catalog must use one of these formats. When omitted, any format is accepted.",
       "items": {
-        "$ref": "/schemas/3.0.8/enums/feed-format.json"
+        "$ref": "/schemas/3.0.9/enums/feed-format.json"
       },
       "minItems": 1,
       "uniqueItems": true
@@ -46,7 +46,7 @@
       "type": "array",
       "description": "Per-item creative asset requirements. Declares what asset groups (headlines, images, videos) each catalog item must provide in its assets array, along with count bounds and per-asset technical constraints. Applicable to 'offering' and all vertical catalog types (hotel, flight, job, etc.) whose items carry typed assets.",
       "items": {
-        "$ref": "/schemas/3.0.8/core/requirements/offering-asset-constraint.json"
+        "$ref": "/schemas/3.0.9/core/requirements/offering-asset-constraint.json"
       },
       "minItems": 1,
       "uniqueItems": true
@@ -55,7 +55,7 @@
       "type": "array",
       "description": "Explicit mappings from format template slots to catalog item fields or typed asset pools. Optional — creative agents can infer mappings without them, but bindings make the relationship self-describing and enable validation. Covers scalar fields (asset_id → catalog_field), asset pools (asset_id → asset_group_id on the catalog item), and repeatable groups that iterate over catalog items.",
       "items": {
-        "$ref": "/schemas/3.0.8/core/requirements/catalog-field-binding.json"
+        "$ref": "/schemas/3.0.9/core/requirements/catalog-field-binding.json"
       },
       "minItems": 1,
       "uniqueItems": true

package/dist/lib/schemas-data/3.0/core/requirements/css-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/css-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/css-asset-requirements.json",
   "title": "CSS Asset Requirements",
   "description": "Requirements for CSS creative assets.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/requirements/daast-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/daast-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/daast-asset-requirements.json",
   "title": "DAAST Asset Requirements",
   "description": "Requirements for DAAST (Digital Audio Ad Serving Template) creative assets.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/requirements/html-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/html-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/html-asset-requirements.json",
   "title": "HTML Asset Requirements",
   "description": "Requirements for HTML creative assets. These define the execution environment constraints that the HTML must be compatible with.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/requirements/image-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/image-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/image-asset-requirements.json",
   "title": "Image Asset Requirements",
   "description": "Requirements for image creative assets. These define the technical constraints for image files.",
   "type": "object",
@@ -26,7 +26,7 @@
       "description": "Maximum height. Interpretation depends on unit (default: pixels). For exact dimensions, set min_height = max_height."
     },
     "unit": {
-      "$ref": "/schemas/3.0.8/enums/dimension-unit.json",
+      "$ref": "/schemas/3.0.9/enums/dimension-unit.json",
       "description": "Unit of measurement for width/height values. Defaults to 'px' when absent. Print formats use 'inches' or 'cm'."
     },
     "aspect_ratio": {

package/dist/lib/schemas-data/3.0/core/requirements/javascript-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/javascript-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/javascript-asset-requirements.json",
   "title": "JavaScript Asset Requirements",
   "description": "Requirements for JavaScript creative assets. These define the execution environment constraints that the JavaScript must be compatible with.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/requirements/markdown-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/markdown-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/markdown-asset-requirements.json",
   "title": "Markdown Asset Requirements",
   "description": "Requirements for markdown creative assets.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/requirements/offering-asset-constraint.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/offering-asset-constraint.json",
+  "$id": "/schemas/3.0.9/core/requirements/offering-asset-constraint.json",
   "title": "Offering Asset Constraint",
   "description": "Declares per-group creative requirements that each offering must satisfy. Allows formats to specify what asset groups (headlines, images, videos) offerings must provide, along with count and per-asset technical constraints.",
   "type": "object",
@@ -10,7 +10,7 @@
       "description": "The asset group this constraint applies to. Values are format-defined vocabulary — each format chooses its own group IDs (e.g., 'headlines', 'images', 'videos'). Buyers discover them via list_creative_formats."
     },
     "asset_type": {
-      "$ref": "/schemas/3.0.8/enums/asset-content-type.json",
+      "$ref": "/schemas/3.0.9/enums/asset-content-type.json",
       "description": "The expected content type for this group."
     },
     "required": {
@@ -29,11 +29,11 @@
       "description": "Maximum number of items allowed in this group."
     },
     "asset_requirements": {
-      "$ref": "/schemas/3.0.8/core/requirements/asset-requirements.json",
+      "$ref": "/schemas/3.0.9/core/requirements/asset-requirements.json",
       "description": "Technical requirements for each item in this group (e.g., max_length for text, min_width/aspect_ratio for images). Applies uniformly to all items in the group."
     },
     "ext": {
-      "$ref": "/schemas/3.0.8/core/ext.json"
+      "$ref": "/schemas/3.0.9/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.0/core/requirements/text-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/text-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/text-asset-requirements.json",
   "title": "Text Asset Requirements",
   "description": "Requirements for text creative assets such as headlines, body copy, and CTAs.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/requirements/url-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/url-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/url-asset-requirements.json",
   "title": "URL Asset Requirements",
   "description": "Requirements for URL assets such as click-through URLs, tracking pixels, and landing pages.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/requirements/vast-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/vast-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/vast-asset-requirements.json",
   "title": "VAST Asset Requirements",
   "description": "Requirements for VAST (Video Ad Serving Template) creative assets.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/requirements/video-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/video-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/video-asset-requirements.json",
   "title": "Video Asset Requirements",
   "description": "Requirements for video creative assets. These define the technical constraints for video files.",
   "type": "object",
@@ -97,15 +97,15 @@
       "description": "Whether the video must include an audio track"
     },
     "frame_rate_type": {
-      "$ref": "/schemas/3.0.8/enums/frame-rate-type.json",
+      "$ref": "/schemas/3.0.9/enums/frame-rate-type.json",
       "description": "Required frame rate type. Broadcast and SSAI require constant frame rate for seamless splicing."
     },
     "scan_type": {
-      "$ref": "/schemas/3.0.8/enums/scan-type.json",
+      "$ref": "/schemas/3.0.9/enums/scan-type.json",
       "description": "Required scan type. Modern delivery requires progressive scan."
     },
     "gop_type": {
-      "$ref": "/schemas/3.0.8/enums/gop-type.json",
+      "$ref": "/schemas/3.0.9/enums/gop-type.json",
       "description": "Required GOP structure. SSAI and broadcast require closed GOPs for clean splice points."
     },
     "min_gop_interval_seconds": {
@@ -119,7 +119,7 @@
       "description": "Maximum keyframe interval in seconds. SSAI typically requires 1-2 second intervals."
     },
     "moov_atom_position": {
-      "$ref": "/schemas/3.0.8/enums/moov-atom-position.json",
+      "$ref": "/schemas/3.0.9/enums/moov-atom-position.json",
       "description": "Required moov atom position in MP4 container. 'start' enables progressive download without buffering the entire file."
     },
     "audio_codecs": {
@@ -150,7 +150,7 @@
     "audio_channels": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.0.8/enums/audio-channel-layout.json"
+        "$ref": "/schemas/3.0.9/enums/audio-channel-layout.json"
       },
       "description": "Accepted audio channel configurations"
     },

package/dist/lib/schemas-data/3.0/core/requirements/webhook-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/requirements/webhook-asset-requirements.json",
+  "$id": "/schemas/3.0.9/core/requirements/webhook-asset-requirements.json",
   "title": "Webhook Asset Requirements",
   "description": "Requirements for webhook creative assets.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/response.json",
+  "$id": "/schemas/3.0.9/core/response.json",
   "title": "Protocol Response",
   "description": "Protocol-level response wrapper (MCP/A2A) - contains AdCP task data plus protocol fields",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/rights-constraint.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.8/core/rights-constraint.json",
+  "$id": "/schemas/3.0.9/core/rights-constraint.json",
   "title": "Rights Constraint",
   "description": "Rights metadata attached to a creative manifest. Each entry represents constraints from a single rights holder. A creative may combine multiple rights constraints (e.g., talent likeness + music license). For v1, rights constraints are informational metadata — the buyer/orchestrator manages creative lifecycle against these terms.",
   "type": "object",
@@ -42,7 +42,7 @@
       "type": "array",
       "description": "Rights uses covered by this constraint",
       "items": {
-        "$ref": "/schemas/3.0.8/enums/right-use.json"
+        "$ref": "/schemas/3.0.9/enums/right-use.json"
       },
       "minItems": 1
     },
@@ -68,7 +68,7 @@
       "description": "Maximum total impressions allowed for the full validity period (valid_from to valid_until). This is the absolute cap across all creatives using this rights grant, not a per-creative or per-period limit."
     },
     "right_type": {
-      "$ref": "/schemas/3.0.8/enums/right-type.json",
+      "$ref": "/schemas/3.0.9/enums/right-type.json",
       "description": "Type of rights (talent, music, etc.). Helps identify constraints when a creative combines multiple rights types."
     },
     "approval_status": {
@@ -86,7 +86,7 @@
       "description": "URL where downstream supply chain participants can verify this rights grant is active. Returns HTTP 200 with the current grant status, or 404 if revoked. Enables SSPs and verification vendors to confirm rights before serving."
     },
     "ext": {
-      "$ref": "/schemas/3.0.8/core/ext.json"
+      "$ref": "/schemas/3.0.9/core/ext.json"
     }
   },
   "required": [