@adcp/sdk 13.0.1 → 13.0.3

package/dist/lib/schemas-data/3.1/core/format.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/format.json",
+  "$id": "/schemas/3.1.20/core/format.json",
   "title": "Format",
   "description": "Represents a creative format with its requirements",
   "type": "object",
@@ -29,7 +29,7 @@
           "type": "array",
           "description": "Publisher-controlled elements rendered on top of buyer content at this asset's position (e.g., video player controls, publisher logos). Creative agents should avoid placing critical content (CTAs, logos, key copy) within overlay bounds.",
           "items": {
-            "$ref": "/schemas/3.1.15/core/overlay.json"
+            "$ref": "/schemas/3.1.20/core/overlay.json"
           }
         },
         "asset_group_id": {
@@ -68,7 +68,7 @@
           "type": "array",
           "description": "Publisher-controlled elements rendered on top of buyer content at this asset's position (e.g., carousel navigation arrows, slide indicators). Creative agents should avoid placing critical content within overlay bounds.",
           "items": {
-            "$ref": "/schemas/3.1.15/core/overlay.json"
+            "$ref": "/schemas/3.1.20/core/overlay.json"
           }
         }
       },
@@ -81,7 +81,7 @@
   },
   "properties": {
     "format_id": {
-      "$ref": "/schemas/3.1.15/core/format-id.json",
+      "$ref": "/schemas/3.1.20/core/format-id.json",
       "description": "This format's own identifier — a structured object {agent_url, id}, not a string. See /schemas/core/format-id.json for the full shape."
     },
     "name": {
@@ -101,7 +101,7 @@
       "type": "array",
       "description": "List of parameters this format accepts in format_id. Template formats define which parameters (dimensions, duration, etc.) can be specified when instantiating the format. Empty or omitted means this is a concrete format with fixed parameters.",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/format-id-parameter.json"
+        "$ref": "/schemas/3.1.20/enums/format-id-parameter.json"
       },
       "uniqueItems": true
     },
@@ -154,7 +154,7 @@
                 "description": "Maximum height for responsive renders"
               },
               "unit": {
-                "$ref": "/schemas/3.1.15/enums/dimension-unit.json",
+                "$ref": "/schemas/3.1.20/enums/dimension-unit.json",
                 "description": "Unit of measurement for width/height values. Defaults to 'px' when absent. Print formats use 'inches' or 'cm'."
               },
               "responsive": {
@@ -235,7 +235,7 @@
                 "const": "image"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/image-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/image-asset-requirements.json"
               }
             }
           },
@@ -255,7 +255,7 @@
                 "const": "video"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/video-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/video-asset-requirements.json"
               }
             }
           },
@@ -275,7 +275,7 @@
                 "const": "audio"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/audio-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/audio-asset-requirements.json"
               }
             }
           },
@@ -295,7 +295,7 @@
                 "const": "text"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/text-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/text-asset-requirements.json"
               }
             }
           },
@@ -315,7 +315,7 @@
                 "const": "markdown"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/markdown-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/markdown-asset-requirements.json"
               }
             }
           },
@@ -335,7 +335,7 @@
                 "const": "html"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/html-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/html-asset-requirements.json"
               }
             }
           },
@@ -355,7 +355,7 @@
                 "const": "css"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/css-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/css-asset-requirements.json"
               }
             }
           },
@@ -375,7 +375,7 @@
                 "const": "javascript"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/javascript-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/javascript-asset-requirements.json"
               }
             }
           },
@@ -412,7 +412,7 @@
                 "const": "vast"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/vast-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/vast-asset-requirements.json"
               }
             }
           },
@@ -432,7 +432,7 @@
                 "const": "daast"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/daast-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/daast-asset-requirements.json"
               }
             }
           },
@@ -452,7 +452,7 @@
                 "const": "url"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/url-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/url-asset-requirements.json"
               }
             }
           },
@@ -472,7 +472,7 @@
                 "const": "webhook"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/webhook-asset-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/webhook-asset-requirements.json"
               }
             }
           },
@@ -509,7 +509,7 @@
                 "const": "catalog"
               },
               "requirements": {
-                "$ref": "/schemas/3.1.15/core/requirements/catalog-requirements.json"
+                "$ref": "/schemas/3.1.20/core/requirements/catalog-requirements.json"
               }
             }
           },
@@ -571,7 +571,7 @@
                           "const": "image"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/image-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/image-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -591,7 +591,7 @@
                           "const": "video"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/video-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/video-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -611,7 +611,7 @@
                           "const": "audio"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/audio-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/audio-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -631,7 +631,7 @@
                           "const": "text"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/text-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/text-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -651,7 +651,7 @@
                           "const": "markdown"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/markdown-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/markdown-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -671,7 +671,7 @@
                           "const": "html"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/html-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/html-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -691,7 +691,7 @@
                           "const": "css"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/css-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/css-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -711,7 +711,7 @@
                           "const": "javascript"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/javascript-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/javascript-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -748,7 +748,7 @@
                           "const": "vast"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/vast-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/vast-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -768,7 +768,7 @@
                           "const": "daast"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/daast-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/daast-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -788,7 +788,7 @@
                           "const": "url"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/url-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/url-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -808,7 +808,7 @@
                           "const": "webhook"
                         },
                         "requirements": {
-                          "$ref": "/schemas/3.1.15/core/requirements/webhook-asset-requirements.json"
+                          "$ref": "/schemas/3.1.20/core/requirements/webhook-asset-requirements.json"
                         }
                       },
                       "required": [
@@ -842,7 +842,7 @@
       "items": {
         "anyOf": [
           {
-            "$ref": "/schemas/3.1.15/enums/universal-macro.json"
+            "$ref": "/schemas/3.1.20/enums/universal-macro.json"
           },
           {
             "type": "string",
@@ -856,7 +856,7 @@
       "deprecated": true,
       "description": "**DEPRECATED in 3.1. Removed at 4.0.** Use `list_transformers` instead — a transformer declares its own `input_format_ids`/`output_format_ids`, so build capability is a property of the transformer (the unit you select and that carries pricing), not a relationship hung on a format. Discover build capability via `list_transformers` (optionally filtered by `input_format_ids`/`output_format_ids`).\n\nMigration: sellers that expressed transform capability by hanging `input_format_ids` on a format SHOULD declare a transformer via `list_transformers` instead. Buyers SHOULD discover build capability via `list_transformers` rather than filtering formats.\n\n*Legacy behavior, retained for 3.1–3.x backward compatibility:* array of format IDs this format accepts as input creative manifests; when present, indicates this format can take existing creatives in these formats as input. SDKs reading 3.1 catalogs MUST continue to honor this field when present; 4.0+ SDKs MAY reject it. New code SHOULD NOT emit this field.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/format-id.json"
+        "$ref": "/schemas/3.1.20/core/format-id.json"
       }
     },
     "output_format_ids": {
@@ -864,7 +864,7 @@
       "deprecated": true,
       "description": "**DEPRECATED in 3.1. Removed at 4.0.** Use `list_transformers` instead — a transformer declares its own `output_format_ids`, so what a builder can produce is a property of the transformer, not a relationship hung on a format. Discover via `list_transformers`.\n\nMigration: sellers that expressed multi-output build capability (e.g. a multi-publisher template) by hanging `output_format_ids` on a format SHOULD declare a transformer via `list_transformers` instead.\n\n*Legacy behavior, retained for 3.1–3.x backward compatibility:* array of format IDs this format can produce as output; when present, indicates this format can build creatives in these output formats. SDKs reading 3.1 catalogs MUST continue to honor this field when present; 4.0+ SDKs MAY reject it. New code SHOULD NOT emit this field.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/format-id.json"
+        "$ref": "/schemas/3.1.20/core/format-id.json"
       }
     },
     "format_card": {
@@ -872,7 +872,7 @@
       "description": "Optional standard visual card (300x400px) for displaying this format in user interfaces. Can be rendered via preview_creative or pre-generated.",
       "properties": {
         "format_id": {
-          "$ref": "/schemas/3.1.15/core/format-id.json",
+          "$ref": "/schemas/3.1.20/core/format-id.json",
           "description": "Creative format defining the card layout (typically format_card_standard)"
         },
         "manifest": {
@@ -892,7 +892,7 @@
       "description": "Accessibility posture of this format. Declares the WCAG conformance level that creatives produced by this format will meet.",
       "properties": {
         "wcag_level": {
-          "$ref": "/schemas/3.1.15/enums/wcag-level.json",
+          "$ref": "/schemas/3.1.20/enums/wcag-level.json",
           "description": "WCAG conformance level that this format achieves. For format-rendered creatives, the format guarantees this level. For opaque creatives, the format requires assets that self-certify to this level."
         },
         "requires_accessible_assets": {
@@ -908,7 +908,7 @@
       "type": "array",
       "description": "Disclosure positions this format can render. Buyers use this to determine whether a format can satisfy their compliance requirements before submitting a creative. When omitted, the format makes no disclosure rendering guarantees — creative agents SHOULD treat this as incompatible with briefs that require specific disclosure positions. Values correspond to positions on creative-brief.json required_disclosures.",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/disclosure-position.json"
+        "$ref": "/schemas/3.1.20/enums/disclosure-position.json"
       },
       "minItems": 1,
       "uniqueItems": true
@@ -920,14 +920,14 @@
         "type": "object",
         "properties": {
           "position": {
-            "$ref": "/schemas/3.1.15/enums/disclosure-position.json",
+            "$ref": "/schemas/3.1.20/enums/disclosure-position.json",
             "description": "The disclosure position"
           },
           "persistence": {
             "type": "array",
             "description": "Persistence modes this position supports",
             "items": {
-              "$ref": "/schemas/3.1.15/enums/disclosure-persistence.json"
+              "$ref": "/schemas/3.1.20/enums/disclosure-persistence.json"
             },
             "minItems": 1,
             "uniqueItems": true
@@ -946,7 +946,7 @@
       "description": "Optional detailed card with carousel and full specifications. Provides rich format documentation similar to ad spec pages.",
       "properties": {
         "format_id": {
-          "$ref": "/schemas/3.1.15/core/format-id.json",
+          "$ref": "/schemas/3.1.20/core/format-id.json",
           "description": "Creative format defining the detailed card layout (typically format_card_detailed)"
         },
         "manifest": {
@@ -965,7 +965,7 @@
       "type": "array",
       "description": "Metrics this format can produce in delivery reporting. Buyers receive the intersection of format reported_metrics and product available_metrics. If omitted, the format defers entirely to product-level metric declarations.",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/available-metric.json"
+        "$ref": "/schemas/3.1.20/enums/available-metric.json"
       },
       "minItems": 1,
       "uniqueItems": true
@@ -975,16 +975,16 @@
       "deprecated": true,
       "description": "**DEPRECATED in 3.1. Removed at 4.0.** Use `transformer.pricing_options` (via `list_transformers`) instead — pricing belongs on the transformer (the unit selected and billed), exactly as it belongs on a media-buy product. Once formats only describe output shape, format-level pricing is vestigial.\n\nMigration: transformation/generation agents that charged via `format.pricing_options` SHOULD move the same `vendor-pricing-option` entries onto the corresponding transformer. The applied option is echoed per-leaf on the build_creative response and reconciled via report_usage, unchanged.\n\n*Legacy behavior, retained for 3.1–3.x backward compatibility:* pricing options for this format, used by transformation/generation agents that charge per format adapted, per image generated, or per unit of work; present when the request included include_pricing=true and account. SDKs reading 3.1 catalogs MUST continue to honor this field when present; 4.0+ SDKs MAY reject it. New code SHOULD NOT emit this field.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/vendor-pricing-option.json"
+        "$ref": "/schemas/3.1.20/core/vendor-pricing-option.json"
       },
       "minItems": 1
     },
     "canonical": {
-      "$ref": "/schemas/3.1.15/core/canonical-projection-ref.json",
+      "$ref": "/schemas/3.1.20/core/canonical-projection-ref.json",
       "description": "Optional v2 canonical-projection annotation. Always an object — bare-string shorthand (`canonical: \"image\"`) is not supported; the minimal form is `canonical: { \"kind\": \"image\" }`. Carries `kind` (which canonical the v1 format projects to) plus optional `asset_source` and `slots_override` for cases where the v1 format's shape doesn't follow the canonical's defaults (e.g., generative entries whose input is `generation_prompt: text` instead of `image_main: image`).\n\nWhen set, SDKs use this annotation as the authoritative v1 → v2 mapping for this format, bypassing the [v1 canonical mapping registry](/schemas/registries/v1-canonical-mapping.json) lookup. Combined with the slot-level `asset_group_id` declarations on each `assets[i]` entry, a v1 format declaration with `canonical` set is fully self-describing for v1↔v2 translation.\n\nResolution order for SDK projection from v1 wire shape to v2 (per RFC #3305 amendment #3767):\n1. If this `canonical` field is set, use it (seller-declared, highest priority). Apply `asset_source` and `slots_override` from the projection ref when present; otherwise inherit the canonical's defaults.\n2. Else, look up `format_id` in the canonical mapping registry's `format_id_glob` entries.\n3. Else, attempt structural match against the registry's `structural` entries (asset types, slot shape, vast_versions, etc.).\n4. Else, fail closed: SDK MUST NOT emit `format_options` for products carrying this format. Surface `FORMAT_PROJECTION_FAILED` on the response `errors[]` suggesting the seller add an explicit `canonical` annotation or file a registry entry.\n\nWhen `canonical.kind` is `custom`, the seller MUST also declare `canonical_format_shape` and `canonical_format_schema` (parallel to ProductFormatDeclaration's `format_shape` and `format_schema`) so buyer SDKs can fetch the seller's custom format schema.\n\nSee `canonical-projection-ref.json` for full projection semantics and examples (default-slot case, generative case, brief-driven case)."
     },
     "canonical_parameters": {
-      "$ref": "/schemas/3.1.15/core/product-format-declaration.json",
+      "$ref": "/schemas/3.1.20/core/product-format-declaration.json",
       "deprecated": true,
       "description": "**DEPRECATED in 3.1. Removed at 4.0.** Use `v1_format_ref` on the v2 `ProductFormatDeclaration` instead — the seller authors a v2 declaration (in `Product.format_options` or `creative.supported_formats`) and links it back to this v1 format via `v1_format_ref: { agent_url, id }`. The directional link from v2 → v1 is the same fact as `canonical_parameters` without the parallel-shape drift surface (v1 file and `canonical_parameters` were two declarations of the same thing; hand-authored, drifting silently).\n\nMigration: every seller currently authoring `canonical_parameters` SHOULD migrate to authoring a v2 declaration on the corresponding product (or capability) with `v1_format_ref` pointing back at this v1 format. v1 files become pure v1 again — no v2-shape mirroring.\n\n*Legacy behavior, retained for 3.1–3.x backward compatibility:* When `canonical` is set, this field carries the full ProductFormatDeclaration that the SDK projects this v1 format into. The `format_kind` MUST equal the `canonical` field value (validators enforce). When set, this is the authoritative source for SDK v1→v2 projection — the registry's structural-match parameter inference is bypassed. SDKs reading 3.1 catalogs MUST continue to honor `canonical_parameters` when present; 4.0+ SDKs MAY reject the field. New code SHOULD NOT emit this field.\n\n**Drift contract (still normative while supported).** Hand-authored `canonical_parameters` MUST satisfy the *narrows* relation against this v1 format's `requirements` and `assets[*]` shape (see canonical-formats.mdx 'Narrows — formal definition'). SDKs that read this v1 file SHOULD lint-time check the equivalence at build/load and emit `FORMAT_PROJECTION_FAILED` if the two disagree."
     }

package/dist/lib/schemas-data/3.1/core/frequency-cap.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/frequency-cap.json",
+  "$id": "/schemas/3.1.20/core/frequency-cap.json",
   "title": "Frequency Cap",
   "description": "Frequency capping settings for package-level application. Two types of frequency control can be used independently or together: suppress enforces a cooldown between consecutive exposures; max_impressions + per + window caps total exposures per entity in a time window. When both suppress and max_impressions are set, an impression is delivered only if both constraints permit it (AND semantics). At least one of suppress, suppress_minutes, or max_impressions must be set.",
   "type": "object",
@@ -8,7 +8,7 @@
     "suppress": {
       "allOf": [
         {
-          "$ref": "/schemas/3.1.15/core/duration.json"
+          "$ref": "/schemas/3.1.20/core/duration.json"
         }
       ],
       "description": "Cooldown period between consecutive exposures to the same entity. Prevents back-to-back ad delivery (e.g. {\"interval\": 60, \"unit\": \"minutes\"} for a 1-hour cooldown). Preferred over suppress_minutes."
@@ -26,7 +26,7 @@
     "per": {
       "allOf": [
         {
-          "$ref": "/schemas/3.1.15/enums/reach-unit.json"
+          "$ref": "/schemas/3.1.20/enums/reach-unit.json"
         }
       ],
       "description": "Entity granularity for impression counting. Required when max_impressions is set."
@@ -34,7 +34,7 @@
     "window": {
       "allOf": [
         {
-          "$ref": "/schemas/3.1.15/core/duration.json"
+          "$ref": "/schemas/3.1.20/core/duration.json"
         }
       ],
       "description": "Time window for the max_impressions cap (e.g. {\"interval\": 7, \"unit\": \"days\"} or {\"interval\": 1, \"unit\": \"campaign\"} for the full flight). Required when max_impressions is set."

package/dist/lib/schemas-data/3.1/core/generation-credential.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/generation-credential.json",
+  "$id": "/schemas/3.1.20/core/generation-credential.json",
   "title": "Generation Credential",
   "description": "A scoped credential issued by an LLM provider for generating rights-cleared content. The rights agent coordinates with the provider to issue the credential; the provider enforces usage constraints at generation time. Any creative agent can use the credential.",
   "type": "object",
@@ -17,7 +17,7 @@
       "type": "array",
       "description": "Which rights uses this credential covers",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/right-use.json"
+        "$ref": "/schemas/3.1.20/enums/right-use.json"
       },
       "minItems": 1
     },
@@ -32,7 +32,7 @@
       "description": "Provider API endpoint to use with this credential, if different from the provider's default"
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/geo-breakdown-support.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/geo-breakdown-support.json",
+  "$id": "/schemas/3.1.20/core/geo-breakdown-support.json",
   "title": "Geographic Breakdown Support",
   "description": "Declares which geographic levels and classification systems are available for by_geo reporting breakdowns in product-level reporting_capabilities.",
   "type": "object",
@@ -17,7 +17,7 @@
       "type": "object",
       "description": "Metro area breakdown support. Keys are metro-system enum values; true means supported.",
       "propertyNames": {
-        "$ref": "/schemas/3.1.15/enums/metro-system.json"
+        "$ref": "/schemas/3.1.20/enums/metro-system.json"
       },
       "additionalProperties": {
         "type": "boolean"
@@ -25,7 +25,7 @@
     },
     "postal_area": {
       "description": "Postal area breakdown support. Prefer the native country-keyed map where each ISO 3166-1 alpha-2 country lists supported country-local postal systems. Deprecated legacy country-fused postal-system boolean maps remain accepted for compatibility.",
-      "$ref": "/schemas/3.1.15/core/postal-area-support.json"
+      "$ref": "/schemas/3.1.20/core/postal-area-support.json"
     }
   },
   "additionalProperties": false

package/dist/lib/schemas-data/3.1/core/geo-delivery-metrics.json

@@ -1,17 +1,17 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/geo-delivery-metrics.json",
+  "$id": "/schemas/3.1.20/core/geo-delivery-metrics.json",
   "title": "Geo Delivery Metrics",
   "description": "Delivery metrics row for one geographic area within a package.",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.15/core/delivery-metrics.json"
+      "$ref": "/schemas/3.1.20/core/delivery-metrics.json"
     },
     {
       "type": "object",
       "properties": {
         "geo_level": {
-          "$ref": "/schemas/3.1.15/enums/geo-level.json",
+          "$ref": "/schemas/3.1.20/enums/geo-level.json",
           "description": "Geographic level of this entry (country, region, metro, postal_area)"
         },
         "system": {
@@ -109,7 +109,7 @@
           "then": {
             "properties": {
               "system": {
-                "$ref": "/schemas/3.1.15/enums/metro-system.json"
+                "$ref": "/schemas/3.1.20/enums/metro-system.json"
               }
             },
             "required": [
@@ -136,12 +136,12 @@
           "then": {
             "anyOf": [
               {
-                "$ref": "/schemas/3.1.15/core/postal-country-system.json"
+                "$ref": "/schemas/3.1.20/core/postal-country-system.json"
               },
               {
                 "properties": {
                   "system": {
-                    "$ref": "/schemas/3.1.15/enums/legacy-postal-system.json"
+                    "$ref": "/schemas/3.1.20/enums/legacy-postal-system.json"
                   }
                 },
                 "required": [

package/dist/lib/schemas-data/3.1/core/hotel-item.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/hotel-item.json",
+  "$id": "/schemas/3.1.20/core/hotel-item.json",
   "title": "Hotel Item",
   "description": "A hotel or lodging property within a hotel-type catalog. Carries the property data that platforms use for hotel ads, dynamic remarketing, and travel campaign creatives. Maps to Google Hotel Center feeds, Meta hotel catalogs, and similar platform-native formats.",
   "type": "object",
@@ -75,7 +75,7 @@
       "description": "Official star rating (1–5)."
     },
     "price": {
-      "$ref": "/schemas/3.1.15/core/price.json",
+      "$ref": "/schemas/3.1.20/core/price.json",
       "description": "Nightly rate or starting price. Use period 'night' for nightly rates."
     },
     "image_url": {
@@ -132,12 +132,12 @@
       "type": "array",
       "description": "Typed creative asset pools for this hotel. Uses the same OfferingAssetGroup structure as offering-type catalogs. Standard group IDs: 'images_landscape' (16:9 hero images), 'images_vertical' (9:16 for Snap, Stories), 'images_square' (1:1), 'logo'. Enables formats to declare typed image requirements that map unambiguously to the right asset regardless of platform.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/offering-asset-group.json"
+        "$ref": "/schemas/3.1.20/core/offering-asset-group.json"
       },
       "minItems": 1
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/identifier.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/identifier.json",
+  "$id": "/schemas/3.1.20/core/identifier.json",
   "title": "Identifier",
   "description": "A property identifier with type and value. Used to identify properties across platforms (domains, app store IDs, etc.).",
   "type": "object",
   "properties": {
     "type": {
-      "$ref": "/schemas/3.1.15/enums/identifier-types.json",
+      "$ref": "/schemas/3.1.20/enums/identifier-types.json",
       "description": "Type of identifier"
     },
     "value": {

package/dist/lib/schemas-data/3.1/core/impairment.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/impairment.json",
+  "$id": "/schemas/3.1.20/core/impairment.json",
   "title": "Impairment",
   "description": "A single upstream dependency state change that affects delivery for one or more packages within a media buy. An impairment is open until the underlying resource returns to a serviceable state. Materiality: an impairment MUST list at least one package whose ability to serve is degraded; cosmetic-only effects (e.g., one rejected creative when peers remain serviceable in the same package) MUST NOT be reported as impairments. Sellers MAY report conservatively when uncertain (list a package when the materiality join is expensive to compute); sellers MUST NOT report when serving is provably unaffected. Materiality is required (MUST) for resource types where the resource→buy join is cheap and 1:N — audience, event_source, property; SHOULD-strength for creative and catalog_item, where the resource is shared across a larger pool and the join cost is higher.",
   "type": "object",
@@ -46,14 +46,14 @@
           "description": "Prior status of the resource (e.g., 'ready', 'approved', 'good'). Optional — sellers SHOULD include when known, MAY omit when the resource was discovered already in an offline state (e.g., a property depublished via brand.json crawl with no prior snapshot). Open string at the schema layer because each resource_type has its own serviceable-state vocabulary; the pattern constraint blocks free-form garbage, and the impairment.coherence assertion validates that 'from' is a known serviceable value for the resource_type."
         },
         "to": {
-          "$ref": "/schemas/3.1.15/enums/impairment-offline-state.json",
+          "$ref": "/schemas/3.1.20/enums/impairment-offline-state.json",
           "description": "Current (offline) status of the resource. Drawn from the resource_type's canonical lifecycle enum; see impairment-offline-state for per-value resource_type pairing. The pairing is validated by impairment.coherence."
         }
       },
       "additionalProperties": false
     },
     "reason_code": {
-      "$ref": "/schemas/3.1.15/enums/impairment-reason-code.json",
+      "$ref": "/schemas/3.1.20/enums/impairment-reason-code.json",
       "description": "Categorical reason for the offline transition. Drives buyer-side remediation logic."
     },
     "reason": {

package/dist/lib/schemas-data/3.1/core/industry-identifier.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/industry-identifier.json",
+  "$id": "/schemas/3.1.20/core/industry-identifier.json",
   "title": "Industry Identifier",
   "description": "An industry-standard or market-specific identifier for an advertising creative (e.g., Ad-ID, ISCI, Clearcast clock number, IDcrea). These identifiers are managed by external registries or clearance bodies and used across the supply chain to track and reference specific creative assets. Add a PR to extend creative-identifier-type when another shared identifier scheme needs first-class support.",
   "type": "object",
   "properties": {
     "type": {
-      "$ref": "/schemas/3.1.15/enums/creative-identifier-type.json"
+      "$ref": "/schemas/3.1.20/enums/creative-identifier-type.json"
     },
     "value": {
       "type": "string",

package/dist/lib/schemas-data/3.1/core/insertion-order.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/insertion-order.json",
+  "$id": "/schemas/3.1.20/core/insertion-order.json",
   "title": "Insertion Order",
   "description": "A signing wrapper attached to a committed proposal. The IO does not introduce new deal terms — all negotiated terms (performance standards, measurement terms, cancellation policy, pricing) live on the product and package. The IO exists for human signature workflows and provides summary fields so buyer agents can verify the IO matches the committed proposal before a human signs.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/installment-deadlines.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/installment-deadlines.json",
+  "$id": "/schemas/3.1.20/core/installment-deadlines.json",
   "title": "Installment Deadlines",
   "description": "Deadlines associated with a bookable installment. Applies to any channel where inventory is tied to a scheduled unit: print issues, podcast episodes, linear TV airings, influencer posts, DOOH rotations.",
   "type": "object",
@@ -19,7 +19,7 @@
       "type": "array",
       "description": "Stages for creative material submission. Items MUST be in chronological order by due_at (earliest first). Typical pattern: 'draft' for raw materials the seller will process, 'final' for production-ready assets. Print example: draft artwork then press-ready PDF. Influencer example: talking points then approved script.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/material-deadline.json"
+        "$ref": "/schemas/3.1.20/core/material-deadline.json"
       },
       "minItems": 1
     }