@adcp/sdk 9.6.0 → 9.6.2

package/dist/lib/schemas-data/3.1/bundled/media-buy/build-creative-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/bundled/media-buy/build-creative-response.json",
+  "$id": "/schemas/3.1.1/bundled/media-buy/build-creative-response.json",
   "title": "Build Creative Response",
   "description": "Response payload for build_creative. Exactly one of six shapes: (1) synchronous single-format success — creative_manifest issued in-line (target_format_id request); (2) synchronous multi-format success — creative_manifests issued in-line (target_format_ids request); (3) multiplicity success — creatives[] each carrying variants[], returned when the request used item (max_creatives) and/or variant (max_variants) fan-out; (4) dry-run estimate — mode 'estimate' returns a BuildCreativeEstimate cost band and produces/bills nothing; (5) terminal failure — an errors array; (6) submitted task envelope — status 'submitted' with task_id when the build is queued (e.g., slow generative or multi-minute LLM pipeline). The submitted branch MAY carry advisory errors for non-blocking warnings; terminal failures belong in the error branch. These six shapes are mutually exclusive — a response has exactly one.",
   "type": "object",
@@ -28,7 +28,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.0/core/version-envelope.json"
+      "$id": "/schemas/3.1.1/core/version-envelope.json"
     },
     {
       "title": "Protocol Envelope",
@@ -44,7 +44,7 @@
           "description": "Per-request opaque caller-supplied correlation object echoed unchanged in the response. Used for buyer-side tracking (UI session IDs, trace IDs, custom metadata) that the agent MUST preserve byte-for-byte without parsing. Distinct from `context_id` (server-managed session identifier) — `context` is caller-owned echo, `context_id` is server-owned session scope. Both MAY appear on the same response.\n\n**Relationship to per-task body-level `context` declarations.** Many task request/response schemas (147 as of 3.1) already declare a body-level `context` field that `$ref`s `/schemas/core/context.json` at the body root. Under the flat-on-the-wire MCP serialization (see `notes` below), envelope-level `context` and body-level `context` occupy the same key on the response root — they are NOT separate fields, they MUST share the same value, and they MUST both `$ref` `core/context.json`. The envelope declaration is **authoritative** for the schema definition; per-task body declarations are mirrors retained for tooling reasons (SDK codegen completeness, per-task validation against the response schema in isolation). Future versions MAY drop body-level `context` declarations from per-task schemas; conformance does not require either declaration to be present, only that the wire value `$ref`s `core/context.json`.",
           "type": "object",
           "additionalProperties": true,
-          "$id": "/schemas/3.1.0/core/context.json"
+          "$id": "/schemas/3.1.1/core/context.json"
         },
         "task_id": {
           "type": "string",
@@ -77,7 +77,7 @@
             "auth-required": "Task requires authentication to proceed",
             "unknown": "Task is in an unknown or indeterminate state"
           },
-          "$id": "/schemas/3.1.0/enums/task-status.json"
+          "$id": "/schemas/3.1.1/enums/task-status.json"
         },
         "message": {
           "type": "string",
@@ -216,7 +216,7 @@
             "message"
           ],
           "additionalProperties": true,
-          "$id": "/schemas/3.1.0/core/error.json"
+          "$id": "/schemas/3.1.1/core/error.json"
         },
         "push_notification_config": {
           "title": "Push Notification Config",
@@ -256,7 +256,7 @@
                       "Bearer",
                       "HMAC-SHA256"
                     ],
-                    "$id": "/schemas/3.1.0/enums/auth-scheme.json"
+                    "$id": "/schemas/3.1.1/enums/auth-scheme.json"
                   },
                   "minItems": 1,
                   "maxItems": 1
@@ -277,7 +277,7 @@
           "required": [
             "url"
           ],
-          "$id": "/schemas/3.1.0/core/push-notification-config.json"
+          "$id": "/schemas/3.1.1/core/push-notification-config.json"
         },
         "governance_context": {
           "type": "string",
@@ -427,7 +427,7 @@
         "`status` is REQUIRED on the conceptual envelope across all transports. On MCP and REST it appears as a sibling field at the JSON root (or `structuredContent` root for MCP); on A2A the canonical carrier is `task.status.state`, which maps 1:1 to this `status` value — receivers MUST extract A2A's `task.status.state` into the in-memory envelope `status` per the canonical extraction algorithm. The schema-level `required: [status]` enforces the post-extraction in-memory shape; the transport-native form satisfies the requirement on each wire. `payload` remains intentionally NOT required — it is a documentary grouping construct, never a required wire field. See `mcp-guide.mdx` and `a2a-guide.mdx` for the wire-level patterns receivers MUST implement.",
         "Receivers MUST handle absence of an envelope field (e.g., `replayed` omitted) as the field's documented default — see each field's `default` clause."
       ],
-      "$id": "/schemas/3.1.0/core/protocol-envelope.json"
+      "$id": "/schemas/3.1.1/core/protocol-envelope.json"
     }
   ],
   "oneOf": [
@@ -486,7 +486,7 @@
                   "width"
                 ]
               },
-              "$id": "/schemas/3.1.0/core/format-id.json"
+              "$id": "/schemas/3.1.1/core/format-id.json"
             },
             "format_kind": {
               "$ref": "#/$defs/CanonicalFormatKind"
@@ -550,7 +550,7 @@
                 }
               ],
               "additionalProperties": true,
-              "$id": "/schemas/3.1.0/core/format-option-ref.json"
+              "$id": "/schemas/3.1.1/core/format-option-ref.json"
             },
             "assets": {
               "type": "object",
@@ -861,7 +861,7 @@
                                                 "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
                                                 "type": "object",
                                                 "additionalProperties": true,
-                                                "$id": "/schemas/3.1.0/core/ext.json"
+                                                "$id": "/schemas/3.1.1/core/ext.json"
                                               }
                                             },
                                             "additionalProperties": true
@@ -946,7 +946,8 @@
                         },
                         {
                           "title": "Video Asset",
-                          "description": "Video asset with URL and technical specifications including audio track properties",
+                          "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                          "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                           "type": "object",
                           "properties": {
                             "asset_type": {
@@ -962,12 +963,12 @@
                             "width": {
                               "type": "integer",
                               "minimum": 1,
-                              "description": "Width in pixels"
+                              "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                             },
                             "height": {
                               "type": "integer",
                               "minimum": 1,
-                              "description": "Height in pixels"
+                              "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                             },
                             "duration_ms": {
                               "type": "integer",
@@ -1867,7 +1868,7 @@
                         },
                         {
                           "title": "VAST Asset",
-                          "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving",
+                          "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving. Unlike the hosted `video` asset, a VAST tag carries no `width`/`height`: a VAST response can return multiple renditions of differing dimensions, and the player selects one per device at serve time, so there is no single width/height for the ad. Dimensional, duration, and codec *constraints* for a placement live on the format/requirements layer, not on this asset.",
                           "type": "object",
                           "properties": {
                             "asset_type": {
@@ -5563,7 +5564,7 @@
                                       "role"
                                     ],
                                     "additionalProperties": true,
-                                    "$id": "/schemas/3.1.0/core/reference-asset.json"
+                                    "$id": "/schemas/3.1.1/core/reference-asset.json"
                                   }
                                 },
                                 "compliance": {
@@ -5878,7 +5879,7 @@
                                         }
                                       }
                                     ],
-                                    "$id": "/schemas/3.1.0/core/catalog-field-mapping.json"
+                                    "$id": "/schemas/3.1.1/core/catalog-field-mapping.json"
                                   },
                                   "minItems": 1
                                 }
@@ -6855,7 +6856,8 @@
                                 },
                                 {
                                   "title": "Video Asset",
-                                  "description": "Video asset with URL and technical specifications including audio track properties",
+                                  "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                                  "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                                   "type": "object",
                                   "properties": {
                                     "asset_type": {
@@ -6871,12 +6873,12 @@
                                     "width": {
                                       "type": "integer",
                                       "minimum": 1,
-                                      "description": "Width in pixels"
+                                      "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                                     },
                                     "height": {
                                       "type": "integer",
                                       "minimum": 1,
-                                      "description": "Height in pixels"
+                                      "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                                     },
                                     "duration_ms": {
                                       "type": "integer",
@@ -7777,7 +7779,7 @@
                                     "digest": "sha256:a3f5b7c9d8e2f1a4b6c8d0e2f4a6b8c0d2e4f6a8b0c2d4e6f8a0b2c4d6e8f0a2"
                                   }
                                 ],
-                                "$id": "/schemas/3.1.0/core/platform-extension-ref.json"
+                                "$id": "/schemas/3.1.1/core/platform-extension-ref.json"
                               }
                             },
                             "provenance": {
@@ -9798,7 +9800,8 @@
                           },
                           {
                             "title": "Video Asset",
-                            "description": "Video asset with URL and technical specifications including audio track properties",
+                            "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                            "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                             "type": "object",
                             "properties": {
                               "asset_type": {
@@ -9814,12 +9817,12 @@
                               "width": {
                                 "type": "integer",
                                 "minimum": 1,
-                                "description": "Width in pixels"
+                                "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                               },
                               "height": {
                                 "type": "integer",
                                 "minimum": 1,
-                                "description": "Height in pixels"
+                                "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                               },
                               "duration_ms": {
                                 "type": "integer",
@@ -10719,7 +10722,7 @@
                           },
                           {
                             "title": "VAST Asset",
-                            "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving",
+                            "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving. Unlike the hosted `video` asset, a VAST tag carries no `width`/`height`: a VAST response can return multiple renditions of differing dimensions, and the player selects one per device at serve time, so there is no single width/height for the ad. Dimensional, duration, and codec *constraints* for a placement live on the format/requirements layer, not on this asset.",
                             "type": "object",
                             "properties": {
                               "asset_type": {
@@ -15705,7 +15708,8 @@
                                   },
                                   {
                                     "title": "Video Asset",
-                                    "description": "Video asset with URL and technical specifications including audio track properties",
+                                    "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                                    "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                                     "type": "object",
                                     "properties": {
                                       "asset_type": {
@@ -15721,12 +15725,12 @@
                                       "width": {
                                         "type": "integer",
                                         "minimum": 1,
-                                        "description": "Width in pixels"
+                                        "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                                       },
                                       "height": {
                                         "type": "integer",
                                         "minimum": 1,
-                                        "description": "Height in pixels"
+                                        "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                                       },
                                       "duration_ms": {
                                         "type": "integer",
@@ -18288,7 +18292,7 @@
                     "nike",
                     "pampers"
                   ],
-                  "$id": "/schemas/3.1.0/core/brand-id.json"
+                  "$id": "/schemas/3.1.1/core/brand-id.json"
                 },
                 "industries": {
                   "type": "array",
@@ -19540,7 +19544,7 @@
                           "additionalProperties": true
                         }
                       ],
-                      "$id": "/schemas/3.1.0/creative/preview-render.json"
+                      "$id": "/schemas/3.1.1/creative/preview-render.json"
                     },
                     "minItems": 1
                   },
@@ -19760,7 +19764,7 @@
             }
           },
           "additionalProperties": true,
-          "$id": "/schemas/3.1.0/core/creative-consumption.json"
+          "$id": "/schemas/3.1.1/core/creative-consumption.json"
         },
         "context": {
           "title": "Context Object",
@@ -20294,7 +20298,8 @@
                           },
                           {
                             "title": "Video Asset",
-                            "description": "Video asset with URL and technical specifications including audio track properties",
+                            "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                            "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                             "type": "object",
                             "properties": {
                               "asset_type": {
@@ -20310,12 +20315,12 @@
                               "width": {
                                 "type": "integer",
                                 "minimum": 1,
-                                "description": "Width in pixels"
+                                "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                               },
                               "height": {
                                 "type": "integer",
                                 "minimum": 1,
-                                "description": "Height in pixels"
+                                "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                               },
                               "duration_ms": {
                                 "type": "integer",
@@ -21215,7 +21220,7 @@
                           },
                           {
                             "title": "VAST Asset",
-                            "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving",
+                            "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving. Unlike the hosted `video` asset, a VAST tag carries no `width`/`height`: a VAST response can return multiple renditions of differing dimensions, and the player selects one per device at serve time, so there is no single width/height for the ad. Dimensional, duration, and codec *constraints* for a placement live on the format/requirements layer, not on this asset.",
                             "type": "object",
                             "properties": {
                               "asset_type": {
@@ -26201,7 +26206,8 @@
                                   },
                                   {
                                     "title": "Video Asset",
-                                    "description": "Video asset with URL and technical specifications including audio track properties",
+                                    "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                                    "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                                     "type": "object",
                                     "properties": {
                                       "asset_type": {
@@ -26217,12 +26223,12 @@
                                       "width": {
                                         "type": "integer",
                                         "minimum": 1,
-                                        "description": "Width in pixels"
+                                        "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                                       },
                                       "height": {
                                         "type": "integer",
                                         "minimum": 1,
-                                        "description": "Height in pixels"
+                                        "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                                       },
                                       "duration_ms": {
                                         "type": "integer",
@@ -29143,7 +29149,8 @@
                             },
                             {
                               "title": "Video Asset",
-                              "description": "Video asset with URL and technical specifications including audio track properties",
+                              "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                              "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                               "type": "object",
                               "properties": {
                                 "asset_type": {
@@ -29159,12 +29166,12 @@
                                 "width": {
                                   "type": "integer",
                                   "minimum": 1,
-                                  "description": "Width in pixels"
+                                  "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                                 },
                                 "height": {
                                   "type": "integer",
                                   "minimum": 1,
-                                  "description": "Height in pixels"
+                                  "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                                 },
                                 "duration_ms": {
                                   "type": "integer",
@@ -30064,7 +30071,7 @@
                             },
                             {
                               "title": "VAST Asset",
-                              "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving",
+                              "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving. Unlike the hosted `video` asset, a VAST tag carries no `width`/`height`: a VAST response can return multiple renditions of differing dimensions, and the player selects one per device at serve time, so there is no single width/height for the ad. Dimensional, duration, and codec *constraints* for a placement live on the format/requirements layer, not on this asset.",
                               "type": "object",
                               "properties": {
                                 "asset_type": {
@@ -35050,7 +35057,8 @@
                                     },
                                     {
                                       "title": "Video Asset",
-                                      "description": "Video asset with URL and technical specifications including audio track properties",
+                                      "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                                      "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                                       "type": "object",
                                       "properties": {
                                         "asset_type": {
@@ -35066,12 +35074,12 @@
                                         "width": {
                                           "type": "integer",
                                           "minimum": 1,
-                                          "description": "Width in pixels"
+                                          "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                                         },
                                         "height": {
                                           "type": "integer",
                                           "minimum": 1,
-                                          "description": "Height in pixels"
+                                          "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                                         },
                                         "duration_ms": {
                                           "type": "integer",
@@ -39368,7 +39376,7 @@
                             "additionalProperties": true
                           }
                         ],
-                        "$id": "/schemas/3.1.0/core/signal-ref.json"
+                        "$id": "/schemas/3.1.1/core/signal-ref.json"
                       },
                       "signal_id": {
                         "title": "Signal ID",
@@ -39434,7 +39442,7 @@
                             "additionalProperties": true
                           }
                         ],
-                        "$id": "/schemas/3.1.0/core/signal-id.json"
+                        "$id": "/schemas/3.1.1/core/signal-id.json"
                       },
                       "value_type": {
                         "type": "string",
@@ -39990,7 +39998,7 @@
                     "additionalProperties": true
                   }
                 ],
-                "$id": "/schemas/3.1.0/core/signal-targeting.json",
+                "$id": "/schemas/3.1.1/core/signal-targeting.json",
                 "x-status": "experimental"
               },
               "variants": {
@@ -40520,7 +40528,8 @@
                                     },
                                     {
                                       "title": "Video Asset",
-                                      "description": "Video asset with URL and technical specifications including audio track properties",
+                                      "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                                      "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                                       "type": "object",
                                       "properties": {
                                         "asset_type": {
@@ -40536,12 +40545,12 @@
                                         "width": {
                                           "type": "integer",
                                           "minimum": 1,
-                                          "description": "Width in pixels"
+                                          "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                                         },
                                         "height": {
                                           "type": "integer",
                                           "minimum": 1,
-                                          "description": "Height in pixels"
+                                          "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                                         },
                                         "duration_ms": {
                                           "type": "integer",
@@ -41441,7 +41450,7 @@
                                     },
                                     {
                                       "title": "VAST Asset",
-                                      "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving",
+                                      "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving. Unlike the hosted `video` asset, a VAST tag carries no `width`/`height`: a VAST response can return multiple renditions of differing dimensions, and the player selects one per device at serve time, so there is no single width/height for the ad. Dimensional, duration, and codec *constraints* for a placement live on the format/requirements layer, not on this asset.",
                                       "type": "object",
                                       "properties": {
                                         "asset_type": {
@@ -46427,7 +46436,8 @@
                                             },
                                             {
                                               "title": "Video Asset",
-                                              "description": "Video asset with URL and technical specifications including audio track properties",
+                                              "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                                              "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                                               "type": "object",
                                               "properties": {
                                                 "asset_type": {
@@ -46443,12 +46453,12 @@
                                                 "width": {
                                                   "type": "integer",
                                                   "minimum": 1,
-                                                  "description": "Width in pixels"
+                                                  "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                                                 },
                                                 "height": {
                                                   "type": "integer",
                                                   "minimum": 1,
-                                                  "description": "Height in pixels"
+                                                  "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                                                 },
                                                 "duration_ms": {
                                                   "type": "integer",
@@ -49369,7 +49379,8 @@
                                       },
                                       {
                                         "title": "Video Asset",
-                                        "description": "Video asset with URL and technical specifications including audio track properties",
+                                        "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                                        "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                                         "type": "object",
                                         "properties": {
                                           "asset_type": {
@@ -49385,12 +49396,12 @@
                                           "width": {
                                             "type": "integer",
                                             "minimum": 1,
-                                            "description": "Width in pixels"
+                                            "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                                           },
                                           "height": {
                                             "type": "integer",
                                             "minimum": 1,
-                                            "description": "Height in pixels"
+                                            "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                                           },
                                           "duration_ms": {
                                             "type": "integer",
@@ -50290,7 +50301,7 @@
                                       },
                                       {
                                         "title": "VAST Asset",
-                                        "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving",
+                                        "description": "VAST (Video Ad Serving Template) tag for third-party video ad serving. Unlike the hosted `video` asset, a VAST tag carries no `width`/`height`: a VAST response can return multiple renditions of differing dimensions, and the player selects one per device at serve time, so there is no single width/height for the ad. Dimensional, duration, and codec *constraints* for a placement live on the format/requirements layer, not on this asset.",
                                         "type": "object",
                                         "properties": {
                                           "asset_type": {
@@ -55276,7 +55287,8 @@
                                               },
                                               {
                                                 "title": "Video Asset",
-                                                "description": "Video asset with URL and technical specifications including audio track properties",
+                                                "description": "A hosted video file delivered directly (e.g., an MP4 you host), with URL and technical specifications including audio track properties. `width` and `height` are required because a hosted video file has intrinsic, native pixel dimensions that are known when the file is created. Tag-delivered video uses the separate `vast` asset, which carries no `width`/`height`: a VAST response resolves geometry per-`MediaFile` at serve time, so there is no single width/height for the ad. Aspect-ratio and size *constraints* (what a placement accepts) belong on the format/requirements layer, not on the asset.",
+                                                "$comment": "Dimension policy is deliberate and differs by asset type: a hosted `video` asset requires width/height (intrinsic pixels of a concrete file), while the `vast` asset omits them entirely (renditions are selected per-MediaFile by the player at serve time). Do not infer that AdCP forces a single width/height onto all video — only onto hosted files.",
                                                 "type": "object",
                                                 "properties": {
                                                   "asset_type": {
@@ -55292,12 +55304,12 @@
                                                   "width": {
                                                     "type": "integer",
                                                     "minimum": 1,
-                                                    "description": "Width in pixels"
+                                                    "description": "Width in pixels — the video file's intrinsic native width. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no width; see the `vast` asset.)"
                                                   },
                                                   "height": {
                                                     "type": "integer",
                                                     "minimum": 1,
-                                                    "description": "Height in pixels"
+                                                    "description": "Height in pixels — the video file's intrinsic native height. Required: a hosted file always has concrete dimensions. (Tag-delivered video carries no height; see the `vast` asset.)"
                                                   },
                                                   "duration_ms": {
                                                     "type": "integer",
@@ -58939,7 +58951,7 @@
                               "value"
                             ],
                             "additionalProperties": false,
-                            "$id": "/schemas/3.1.0/creative/creative-feature-result.json"
+                            "$id": "/schemas/3.1.1/creative/creative-feature-result.json"
                           }
                         },
                         "ranked_against": {
@@ -59236,7 +59248,7 @@
             "inventory_priority": "Rank by seller-side catalog metadata (margin, overstock, promotional priority). No buyer input.",
             "random": "Status-quo fallback: agent samples without a ranking preference. Default when selection_strategy is omitted."
           },
-          "$id": "/schemas/3.1.0/enums/creative-selection-strategy.json"
+          "$id": "/schemas/3.1.1/enums/creative-selection-strategy.json"
         },
         "budget_status": {
           "type": "string",
@@ -59986,7 +59998,7 @@
         "agent_placement",
         "custom"
       ],
-      "$id": "/schemas/3.1.0/core/canonical-format-kind.json"
+      "$id": "/schemas/3.1.1/core/canonical-format-kind.json"
     },
     "DigitalSourceType": {
       "title": "Digital Source Type",
@@ -60014,7 +60026,7 @@
         "human_edits": "Content augmented, corrected, or enhanced by humans using non-generative tools",
         "data_driven_media": "Assembled from structured data feeds (DCO templates, product catalogs, weather-triggered variants)"
       },
-      "$id": "/schemas/3.1.0/enums/digital-source-type.json"
+      "$id": "/schemas/3.1.1/enums/digital-source-type.json"
     },
     "EmbeddedProvenanceMethod": {
       "title": "Embedded Provenance Method",
@@ -60028,7 +60040,7 @@
         "manifest_wrapper": "A provenance manifest embedded in the file container per format-specific rules (e.g., JUMBF box in JPEG, C2PATextManifestWrapper in plaintext per C2PA Section A.7). The manifest travels with the file but is tied to the file's byte structure.",
         "provenance_markers": "Invisible markers embedded within the content stream that encode or reference a provenance record. Designed to survive reformatting, copy-paste, CMS ingestion, and ad-server transcoding that breaks file-level bindings."
       },
-      "$id": "/schemas/3.1.0/enums/embedded-provenance-method.json"
+      "$id": "/schemas/3.1.1/enums/embedded-provenance-method.json"
     },
     "WatermarkMediaType": {
       "title": "Watermark Media Type",
@@ -60046,7 +60058,7 @@
         "video": "Watermark applied to video content (e.g., per-frame image watermarking, temporal watermarking)",
         "text": "Watermark applied to text content (e.g., synonym substitution, structural modification)"
       },
-      "$id": "/schemas/3.1.0/enums/watermark-media-type.json"
+      "$id": "/schemas/3.1.1/enums/watermark-media-type.json"
     },
     "C2PAWatermarkAction": {
       "title": "C2PA Watermark Action",
@@ -60060,7 +60072,7 @@
         "c2pa.watermarked.bound": "Watermark linked to a C2PA manifest for this asset. The watermark and manifest are mutually reinforcing: the manifest references the watermark, and the watermark can be used to locate the manifest.",
         "c2pa.watermarked.unbound": "Watermark independent of any C2PA manifest. Applied before any provenance signing event (e.g., by the AI generator at creation time) or in pipelines where no manifest is present."
       },
-      "$id": "/schemas/3.1.0/enums/c2pa-watermark-action.json"
+      "$id": "/schemas/3.1.1/enums/c2pa-watermark-action.json"
     },
     "DisclosurePersistence": {
       "title": "Disclosure Persistence",
@@ -60076,7 +60088,7 @@
         "initial": "Disclosure must appear at the start of content for a minimum duration before it may be removed. Pair with min_duration_ms in render_guidance or creative brief to specify the required duration.",
         "flexible": "Disclosure presence is sufficient; placement timing and duration are at the publisher's discretion"
       },
-      "$id": "/schemas/3.1.0/enums/disclosure-persistence.json"
+      "$id": "/schemas/3.1.1/enums/disclosure-persistence.json"
     },
     "DisclosurePosition": {
       "title": "Disclosure Position",
@@ -60092,7 +60104,7 @@
         "pre_roll",
         "companion"
       ],
-      "$id": "/schemas/3.1.0/enums/disclosure-position.json"
+      "$id": "/schemas/3.1.1/enums/disclosure-position.json"
     },
     "FrameRateType": {
       "title": "Frame Rate Type",
@@ -60106,7 +60118,7 @@
         "constant": "Constant frame rate (CFR) — each frame occupies an identical time interval",
         "variable": "Variable frame rate (VFR) — frame intervals may differ"
       },
-      "$id": "/schemas/3.1.0/enums/frame-rate-type.json"
+      "$id": "/schemas/3.1.1/enums/frame-rate-type.json"
     },
     "ScanType": {
       "title": "Scan Type",
@@ -60120,7 +60132,7 @@
         "progressive": "All lines of each frame are drawn in sequence",
         "interlaced": "Alternating lines drawn in two passes per frame (legacy broadcast)"
       },
-      "$id": "/schemas/3.1.0/enums/scan-type.json"
+      "$id": "/schemas/3.1.1/enums/scan-type.json"
     },
     "GOPType": {
       "title": "GOP Type",
@@ -60134,7 +60146,7 @@
         "closed": "Each GOP is independently decodable — required for SSAI and broadcast splicing",
         "open": "GOPs may reference frames from adjacent GOPs — not suitable for splicing"
       },
-      "$id": "/schemas/3.1.0/enums/gop-type.json"
+      "$id": "/schemas/3.1.1/enums/gop-type.json"
     },
     "MoovAtomPosition": {
       "title": "Moov Atom Position",
@@ -60148,7 +60160,7 @@
         "start": "moov atom at beginning of file — enables progressive download and streaming delivery",
         "end": "moov atom at end of file — requires full download before playback can begin"
       },
-      "$id": "/schemas/3.1.0/enums/moov-atom-position.json"
+      "$id": "/schemas/3.1.1/enums/moov-atom-position.json"
     },
     "AudioChannelLayout": {
       "title": "Audio Channel Layout",
@@ -60160,7 +60172,7 @@
         "5.1",
         "7.1"
       ],
-      "$id": "/schemas/3.1.0/enums/audio-channel-layout.json"
+      "$id": "/schemas/3.1.1/enums/audio-channel-layout.json"
     },
     "VASTVersion": {
       "title": "VAST Version",
@@ -60173,7 +60185,7 @@
         "4.1",
         "4.2"
       ],
-      "$id": "/schemas/3.1.0/enums/vast-version.json"
+      "$id": "/schemas/3.1.1/enums/vast-version.json"
     },
     "VASTTrackingEvent": {
       "title": "VAST Tracking Event",
@@ -60217,7 +60229,7 @@
         "measurableImpression",
         "viewableImpression"
       ],
-      "$id": "/schemas/3.1.0/enums/vast-tracking-event.json"
+      "$id": "/schemas/3.1.1/enums/vast-tracking-event.json"
     },
     "URLAssetType": {
       "title": "URL Asset Type",
@@ -60228,7 +60240,7 @@
         "tracker_pixel",
         "tracker_script"
       ],
-      "$id": "/schemas/3.1.0/enums/url-asset-type.json"
+      "$id": "/schemas/3.1.1/enums/url-asset-type.json"
     },
     "JavaScriptModuleType": {
       "title": "JavaScript Module Type",
@@ -60239,7 +60251,7 @@
         "commonjs",
         "script"
       ],
-      "$id": "/schemas/3.1.0/enums/javascript-module-type.json"
+      "$id": "/schemas/3.1.1/enums/javascript-module-type.json"
     },
     "HTTPMethod": {
       "title": "HTTP Method",
@@ -60249,7 +60261,7 @@
         "GET",
         "POST"
       ],
-      "$id": "/schemas/3.1.0/enums/http-method.json",
+      "$id": "/schemas/3.1.1/enums/http-method.json",
       "default": "POST"
     },
     "UniversalMacro": {
@@ -60410,7 +60422,7 @@
         "ITEM_PRICE": "Price amount of the catalog item being rendered (catalog_field: price.amount). Catalog content macro — scalar text value substituted under the catalog-item substitution-safety rules.",
         "ITEM_PRICE_CURRENCY": "ISO 4217 currency code of the catalog item being rendered (catalog_field: price.currency). Catalog content macro — scalar text value substituted under the catalog-item substitution-safety rules."
       },
-      "$id": "/schemas/3.1.0/enums/universal-macro.json"
+      "$id": "/schemas/3.1.1/enums/universal-macro.json"
     },
     "WebhookResponseType": {
       "title": "Webhook Response Type",
@@ -60422,7 +60434,7 @@
         "xml",
         "javascript"
       ],
-      "$id": "/schemas/3.1.0/enums/webhook-response-type.json"
+      "$id": "/schemas/3.1.1/enums/webhook-response-type.json"
     },
     "WebhookSecurityMethod": {
       "title": "Webhook Security Method",
@@ -60433,7 +60445,7 @@
         "api_key",
         "none"
       ],
-      "$id": "/schemas/3.1.0/enums/webhook-security-method.json"
+      "$id": "/schemas/3.1.1/enums/webhook-security-method.json"
     },
     "DAASTVersion": {
       "title": "DAAST Version",
@@ -60443,7 +60455,7 @@
         "1.0",
         "1.1"
       ],
-      "$id": "/schemas/3.1.0/enums/daast-version.json"
+      "$id": "/schemas/3.1.1/enums/daast-version.json"
     },
     "DAASTTrackingEvent": {
       "title": "DAAST Tracking Event",
@@ -60474,7 +60486,7 @@
         "measurableImpression",
         "viewableImpression"
       ],
-      "$id": "/schemas/3.1.0/enums/daast-tracking-event.json"
+      "$id": "/schemas/3.1.1/enums/daast-tracking-event.json"
     },
     "MarkdownFlavor": {
       "title": "Markdown Flavor",
@@ -60484,7 +60496,7 @@
         "commonmark",
         "gfm"
       ],
-      "$id": "/schemas/3.1.0/enums/markdown-flavor.json",
+      "$id": "/schemas/3.1.1/enums/markdown-flavor.json",
       "default": "commonmark"
     },
     "CatalogType": {
@@ -60506,7 +60518,7 @@
         "destination",
         "app"
       ],
-      "$id": "/schemas/3.1.0/enums/catalog-type.json"
+      "$id": "/schemas/3.1.1/enums/catalog-type.json"
     },
     "FeedFormat": {
       "title": "Feed Format",
@@ -60532,7 +60544,7 @@
         "openai_product_feed": "OpenAI Commerce product feed for ChatGPT shopping — a GMC-derived dialect adding ChatGPT-specific eligibility flags (is_eligible_search / is_eligible_checkout / is_eligible_ads). Spec: https://developers.openai.com/commerce/specs/file-upload/products",
         "custom": "A feed whose shape is not one of the named formats above. The buyer MUST supply feed_field_mappings to normalize it to the AdCP catalog item schema."
       },
-      "$id": "/schemas/3.1.0/enums/feed-format.json"
+      "$id": "/schemas/3.1.1/enums/feed-format.json"
     },
     "UpdateFrequency": {
       "title": "Update Frequency",
@@ -60544,7 +60556,7 @@
         "daily",
         "weekly"
       ],
-      "$id": "/schemas/3.1.0/enums/update-frequency.json"
+      "$id": "/schemas/3.1.1/enums/update-frequency.json"
     },
     "EventType": {
       "title": "Event Type",
@@ -60616,7 +60628,7 @@
         "submit_application": "User submitted an application (loan, job, etc.)",
         "custom": "Custom event type (specify in custom_event_name)"
       },
-      "$id": "/schemas/3.1.0/enums/event-type.json"
+      "$id": "/schemas/3.1.1/enums/event-type.json"
     },
     "ContentIDType": {
       "title": "Content ID Type",
@@ -60636,7 +60648,7 @@
         "destination_id",
         "app_id"
       ],
-      "$id": "/schemas/3.1.0/enums/content-id-type.json"
+      "$id": "/schemas/3.1.1/enums/content-id-type.json"
     },
     "RightUse": {
       "title": "Right Use",
@@ -60671,7 +60683,7 @@
         "commercial": "Use in commercial advertising and promotional contexts",
         "ai_generated_image": "License to produce AI-generated still imagery derived from the rights holder's IP (brand assets, character designs, talent likeness). Distinct from likeness/voice by output modality — a get_rights query filtered on ai_generated_image returns rights whose pricing options cover image generation, regardless of the underlying IP category."
       },
-      "$id": "/schemas/3.1.0/enums/right-use.json"
+      "$id": "/schemas/3.1.1/enums/right-use.json"
     },
     "RightType": {
       "title": "Right Type",
@@ -60692,7 +60704,7 @@
         "music": "Rights to musical compositions or recordings (sync, background music)",
         "stock_media": "Rights to stock photography, video, or audio collections"
       },
-      "$id": "/schemas/3.1.0/enums/right-type.json"
+      "$id": "/schemas/3.1.1/enums/right-type.json"
     },
     "CreativeIdentifierType": {
       "title": "Creative Identifier Type",
@@ -60716,11 +60728,11 @@
         "clearcast_clock",
         "idcrea"
       ],
-      "$id": "/schemas/3.1.0/enums/creative-identifier-type.json"
+      "$id": "/schemas/3.1.1/enums/creative-identifier-type.json"
     }
   },
   "_bundled": {
-    "generatedAt": "2026-06-18T08:17:00.728Z",
+    "generatedAt": "2026-06-30T19:14:40.120Z",
     "note": "This is a bundled schema with all $ref resolved inline. For the modular version with references, use the parent directory."
   }
 }