@adcp/sdk 13.0.1 → 13.0.3

package/dist/lib/schemas-data/3.1/core/event-source-health.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/event-source-health.json",
+  "$id": "/schemas/3.1.20/core/event-source-health.json",
   "title": "Event Source Health",
   "description": "Health assessment for a configured event source. Sellers evaluate the quality, completeness, and volume of events received from this source. Sellers with native quality scores (Snap EQS, Meta EMQ) relay them in detail; sellers without native scores derive status from operational metrics (volume, error rates, tag activity).",
   "type": "object",
   "properties": {
     "status": {
-      "$ref": "/schemas/3.1.15/enums/assessment-status.json",
+      "$ref": "/schemas/3.1.20/enums/assessment-status.json",
       "description": "Overall health status. Use this for cross-seller decisions — do not rely on detail.score for comparability. 'insufficient' covers the source-offline case (zero events received over the seller's evaluation window) — disambiguate via `events_received_24h: 0` and a stale `last_event_at`. Sellers MUST surface a corresponding impairment (reason_code: source_offline) on any active media buy whose conversion goals depend on an event source that has gone offline."
     },
     "detail": {
@@ -59,7 +59,7 @@
       "type": "array",
       "description": "Actionable issues detected with this event source. Sellers should limit to the top 3-5 most actionable items. Buyer agents should sort by severity rather than relying on array position.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/diagnostic-issue.json"
+        "$ref": "/schemas/3.1.20/core/diagnostic-issue.json"
       }
     }
   },

package/dist/lib/schemas-data/3.1/core/event-surface.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/event-surface.json",
+  "$id": "/schemas/3.1.20/core/event-surface.json",
   "title": "Event Surface",
   "description": "Structured context for the surface where an event source or logged event originated. Use this when the flat `action_source` is too coarse, such as a creator channel, social profile, podcast feed, newsletter list, or another owned platform property. `category` is a closed vocabulary so buyers can reason generically; `property_type` and `namespace` are open strings so new platforms and property shapes do not require a schema change. The flat `action_source` remains for backward compatibility. When `category` matches an ActionSource value, producers SHOULD set `action_source` to the same value. When `category` is `owned_property`, producers SHOULD keep the most compatible flat `action_source` for legacy consumers, commonly `system_generated` for platform-native events or `other` when no closer value applies.",
   "type": "object",
@@ -53,7 +53,7 @@
       "x-entity": "property"
     },
     "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/event.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/event.json",
+  "$id": "/schemas/3.1.20/core/event.json",
   "title": "Event",
   "description": "A marketing event (conversion, engagement, or custom) for attribution and optimization",
   "type": "object",
@@ -12,7 +12,7 @@
       "maxLength": 256
     },
     "event_type": {
-      "$ref": "/schemas/3.1.15/enums/event-type.json",
+      "$ref": "/schemas/3.1.20/enums/event-type.json",
       "description": "Standard event type"
     },
     "event_time": {
@@ -21,19 +21,19 @@
       "description": "ISO 8601 timestamp when the event occurred"
     },
     "user_match": {
-      "$ref": "/schemas/3.1.15/core/user-match.json",
+      "$ref": "/schemas/3.1.20/core/user-match.json",
       "description": "User identifiers for attribution matching"
     },
     "custom_data": {
-      "$ref": "/schemas/3.1.15/core/event-custom-data.json",
+      "$ref": "/schemas/3.1.20/core/event-custom-data.json",
       "description": "Event-specific data (value, currency, items, etc.)"
     },
     "action_source": {
-      "$ref": "/schemas/3.1.15/enums/action-source.json",
+      "$ref": "/schemas/3.1.20/enums/action-source.json",
       "description": "Where the event originated"
     },
     "surface": {
-      "$ref": "/schemas/3.1.15/core/event-surface.json",
+      "$ref": "/schemas/3.1.20/core/event-surface.json",
       "description": "Optional structured surface context for the event, such as an owned channel, profile, feed, podcast, newsletter list, website, app, or store. Complements `action_source`; use it when optimization-relevant meaning would otherwise live only in platform-specific `ext` metadata."
     },
     "event_source_url": {
@@ -46,7 +46,7 @@
       "description": "Name for custom events (used when event_type is 'custom')"
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "allOf": [
@@ -69,7 +69,7 @@
           "custom_data": {
             "allOf": [
               {
-                "$ref": "/schemas/3.1.15/core/event-custom-data.json"
+                "$ref": "/schemas/3.1.20/core/event-custom-data.json"
               },
               {
                 "anyOf": [

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/ext.json",
+  "$id": "/schemas/3.1.20/core/ext.json",
   "title": "Extension Object",
   "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",

package/dist/lib/schemas-data/3.1/core/feature-requirement.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/feature-requirement.json",
+  "$id": "/schemas/3.1.20/core/feature-requirement.json",
   "title": "Feature Requirement",
   "description": "A feature-based requirement — a reusable predicate over a feature value. Used by property list filters today; designed for reuse in other surfaces (audience filters, creative gates) in future versions. Use min_value/max_value for quantitative features, allowed_values for binary/categorical features.",
   "type": "object",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/flight-item.json",
+  "$id": "/schemas/3.1.20/core/flight-item.json",
   "title": "Flight Item",
   "description": "A flight route within a flight-type catalog. Carries origin/destination, airline, pricing, and schedule data that platforms use for flight ads and dynamic travel remarketing. Maps to Google DynamicFlightsAsset, Meta flight catalogs, and similar formats.",
   "type": "object",
@@ -52,7 +52,7 @@
       "description": "Airline name or IATA airline code."
     },
     "price": {
-      "$ref": "/schemas/3.1.15/core/price.json",
+      "$ref": "/schemas/3.1.20/core/price.json",
       "description": "Ticket price or starting fare."
     },
     "description": {
@@ -91,12 +91,12 @@
       "type": "array",
       "description": "Typed creative asset pools for this flight. Uses the same OfferingAssetGroup structure as offering-type catalogs. Standard group IDs: 'images_landscape' (destination hero), 'images_vertical' (9:16 for Stories), 'images_square' (1:1). Enables formats to declare typed image requirements that map unambiguously to the right asset regardless of platform.",
       "items": {
-        "$ref": "/schemas/3.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/forecast-dimension-audience.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/forecast-dimension-audience.json",
+  "$id": "/schemas/3.1.20/core/forecast-dimension-audience.json",
   "title": "Audience Forecast Dimension",
   "description": "An audience segment dimension for a ForecastPoint row. Variant of ForecastPoint dimensions; see forecast-point-dimensions.json for dispatch rules.",
   "type": "object",
@@ -16,7 +16,7 @@
       "x-entity": "audience"
     },
     "audience_source": {
-      "$ref": "/schemas/3.1.15/enums/audience-source.json",
+      "$ref": "/schemas/3.1.20/enums/audience-source.json",
       "description": "Origin of the audience segment."
     },
     "audience_name": {

package/dist/lib/schemas-data/3.1/core/forecast-dimension-device-platform.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/forecast-dimension-device-platform.json",
+  "$id": "/schemas/3.1.20/core/forecast-dimension-device-platform.json",
   "title": "Device Platform Forecast Dimension",
   "description": "An operating-system or platform dimension for a ForecastPoint row. Variant of ForecastPoint dimensions; see forecast-point-dimensions.json for dispatch rules.",
   "type": "object",
@@ -11,7 +11,7 @@
       "description": "Dimension family discriminator."
     },
     "device_platform": {
-      "$ref": "/schemas/3.1.15/enums/device-platform.json",
+      "$ref": "/schemas/3.1.20/enums/device-platform.json",
       "description": "Operating system or platform for this forecast row."
     }
   },

package/dist/lib/schemas-data/3.1/core/forecast-dimension-device-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/forecast-dimension-device-type.json",
+  "$id": "/schemas/3.1.20/core/forecast-dimension-device-type.json",
   "title": "Device Type Forecast Dimension",
   "description": "A device form-factor dimension for a ForecastPoint row. Variant of ForecastPoint dimensions; see forecast-point-dimensions.json for dispatch rules.",
   "type": "object",
@@ -11,7 +11,7 @@
       "description": "Dimension family discriminator."
     },
     "device_type": {
-      "$ref": "/schemas/3.1.15/enums/device-type.json",
+      "$ref": "/schemas/3.1.20/enums/device-type.json",
       "description": "Device form factor for this forecast row."
     }
   },

package/dist/lib/schemas-data/3.1/core/forecast-dimension-geo.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/forecast-dimension-geo.json",
+  "$id": "/schemas/3.1.20/core/forecast-dimension-geo.json",
   "title": "Geo Forecast Dimension",
   "description": "A geographic dimension for a ForecastPoint row. Variant of ForecastPoint dimensions; see forecast-point-dimensions.json for dispatch rules.",
   "type": "object",
@@ -11,7 +11,7 @@
       "description": "Dimension family discriminator."
     },
     "geo_level": {
-      "$ref": "/schemas/3.1.15/enums/geo-level.json",
+      "$ref": "/schemas/3.1.20/enums/geo-level.json",
       "description": "Geographic level for this forecast point."
     },
     "system": {
@@ -122,7 +122,7 @@
       "then": {
         "properties": {
           "system": {
-            "$ref": "/schemas/3.1.15/enums/metro-system.json"
+            "$ref": "/schemas/3.1.20/enums/metro-system.json"
           }
         },
         "required": [
@@ -149,7 +149,7 @@
       "then": {
         "anyOf": [
           {
-            "$ref": "/schemas/3.1.15/core/postal-country-system.json",
+            "$ref": "/schemas/3.1.20/core/postal-country-system.json",
             "required": [
               "country",
               "system"
@@ -158,7 +158,7 @@
           {
             "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/forecast-dimension-placement.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/forecast-dimension-placement.json",
+  "$id": "/schemas/3.1.20/core/forecast-dimension-placement.json",
   "title": "Placement Forecast Dimension",
   "description": "A placement dimension for a ForecastPoint row. Variant of ForecastPoint dimensions; see forecast-point-dimensions.json for dispatch rules.",
   "type": "object",
@@ -11,7 +11,7 @@
       "description": "Dimension family discriminator."
     },
     "placement_ref": {
-      "$ref": "/schemas/3.1.15/core/placement-ref.json",
+      "$ref": "/schemas/3.1.20/core/placement-ref.json",
       "description": "Structured placement reference for this forecast row. References an entry from the product's placements array."
     },
     "placement_name": {

package/dist/lib/schemas-data/3.1/core/forecast-dimension-signal.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/forecast-dimension-signal.json",
+  "$id": "/schemas/3.1.20/core/forecast-dimension-signal.json",
   "title": "Signal Forecast Dimension",
   "description": "A signal value or signal-presence dimension for a ForecastPoint row. Variant of ForecastPoint dimensions; see forecast-point-dimensions.json for dispatch rules.",
   "type": "object",
@@ -11,7 +11,7 @@
       "description": "Dimension family discriminator."
     },
     "signal_ref": {
-      "$ref": "/schemas/3.1.15/core/signal-ref.json",
+      "$ref": "/schemas/3.1.20/core/signal-ref.json",
       "description": "Canonical signal reference for this forecast row. Required when the row needs to disambiguate product-local, data-provider, or signal-source identity. Product-relative forecasts SHOULD use signal_ref."
     },
     "signal_id": {

package/dist/lib/schemas-data/3.1/core/forecast-point-dimensions.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/forecast-point-dimensions.json",
+  "$id": "/schemas/3.1.20/core/forecast-point-dimensions.json",
   "title": "Forecast Point Dimensions",
   "description": "Dimension constraints represented by a ForecastPoint. Use this when one product, proposal, or signal coverage forecast needs to expose availability or forecasted delivery by country, region, placement, device, audience, signal value, or intersections such as placement x country without creating separate products solely for each slice. Each item declares one dimension family via `kind`; when multiple items are present, the point represents their intersection. Sellers MUST NOT emit more than one item for each `kind` in a point. Consumers MUST NOT treat repeated kinds as OR semantics; repeated peer values such as two countries are a seller conformance issue. Dimension values are descriptors of the forecast row and are independent of pricing_options.",
   "x-adcp-validation": {
@@ -15,22 +15,22 @@
   "items": {
     "oneOf": [
       {
-        "$ref": "/schemas/3.1.15/core/forecast-dimension-geo.json"
+        "$ref": "/schemas/3.1.20/core/forecast-dimension-geo.json"
       },
       {
-        "$ref": "/schemas/3.1.15/core/forecast-dimension-placement.json"
+        "$ref": "/schemas/3.1.20/core/forecast-dimension-placement.json"
       },
       {
-        "$ref": "/schemas/3.1.15/core/forecast-dimension-device-type.json"
+        "$ref": "/schemas/3.1.20/core/forecast-dimension-device-type.json"
       },
       {
-        "$ref": "/schemas/3.1.15/core/forecast-dimension-device-platform.json"
+        "$ref": "/schemas/3.1.20/core/forecast-dimension-device-platform.json"
       },
       {
-        "$ref": "/schemas/3.1.15/core/forecast-dimension-audience.json"
+        "$ref": "/schemas/3.1.20/core/forecast-dimension-audience.json"
       },
       {
-        "$ref": "/schemas/3.1.15/core/forecast-dimension-signal.json"
+        "$ref": "/schemas/3.1.20/core/forecast-dimension-signal.json"
       }
     ]
   }

package/dist/lib/schemas-data/3.1/core/forecast-point.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/forecast-point.json",
+  "$id": "/schemas/3.1.20/core/forecast-point.json",
   "title": "Forecast Point",
   "description": "A forecast data point. When budget is present, the point pairs a spend level with expected delivery — multiple points at ascending budgets form a curve. When budget is omitted, the point represents total available inventory for the requested targeting and dates, independent of spend.",
   "type": "object",
@@ -26,7 +26,7 @@
       "x-entity": "product"
     },
     "dimensions": {
-      "$ref": "/schemas/3.1.15/core/forecast-point-dimensions.json",
+      "$ref": "/schemas/3.1.20/core/forecast-point-dimensions.json",
       "description": "Dimension constraints represented by this forecast point, such as country, region, placement, device type, platform, audience, signal value, or intersections such as placement x country or product x signal. Each item declares one dimension family; when multiple items are present, the point represents their intersection. Sellers MUST NOT emit more than one item for each `kind` on a point; consumers MUST NOT treat repeated kinds as OR semantics. Use multiple points with dimensions to expose country/placement/signal availability within one product, proposal, or signal coverage forecast without creating separate products solely for each dimension. Dimensions describe the forecast row and are independent of pricing_options."
     },
     "metrics": {
@@ -34,57 +34,57 @@
       "description": "Forecasted metric values. Keys are forecastable-metric enum values for delivery/engagement or event-type enum values for outcomes. Values are ForecastRange objects (low/mid/high). Use { \"mid\": value } for point estimates. When budget is present, these are the expected metrics at that spend level. When budget is omitted, these represent total available inventory — use spend to express the estimated cost. Additional keys beyond the documented properties are allowed for event-type values (purchase, lead, app_install, etc.).",
       "properties": {
         "audience_size": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "reach": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "frequency": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "impressions": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "clicks": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "spend": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "views": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "completed_views": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "grps": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "engagements": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "follows": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "saves": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "profile_visits": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "measured_impressions": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "downloads": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "plays": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json"
+          "$ref": "/schemas/3.1.20/core/forecast-range.json"
         },
         "coverage_rate": {
           "allOf": [
             {
-              "$ref": "/schemas/3.1.15/core/forecast-range.json"
+              "$ref": "/schemas/3.1.20/core/forecast-range.json"
             },
             {
               "properties": {
@@ -104,7 +104,7 @@
         }
       },
       "additionalProperties": {
-        "$ref": "/schemas/3.1.15/core/forecast-range.json"
+        "$ref": "/schemas/3.1.20/core/forecast-range.json"
       }
     },
     "viewability": {
@@ -112,21 +112,21 @@
       "description": "Forecasted viewability metrics. Mirrors delivery-metrics.viewability, but numeric values are ForecastRange objects because forecast rows may provide low/mid/high bounds. Use this for pre-buy viewability expectations by forecast point without folding measurement metrics into pricing_options.",
       "properties": {
         "vendor": {
-          "$ref": "/schemas/3.1.15/core/brand-ref.json",
+          "$ref": "/schemas/3.1.20/core/brand-ref.json",
           "description": "Vendor expected to produce or verify these viewability values."
         },
         "measurable_impressions": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json",
+          "$ref": "/schemas/3.1.20/core/forecast-range.json",
           "description": "Forecasted impressions where viewability can be measured. Coverage denominator for viewable_rate and viewed_seconds."
         },
         "viewable_impressions": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json",
+          "$ref": "/schemas/3.1.20/core/forecast-range.json",
           "description": "Forecasted impressions expected to meet the viewability threshold defined by standard."
         },
         "viewable_rate": {
           "allOf": [
             {
-              "$ref": "/schemas/3.1.15/core/forecast-range.json"
+              "$ref": "/schemas/3.1.20/core/forecast-range.json"
             },
             {
               "properties": {
@@ -145,11 +145,11 @@
           "description": "Forecasted viewable impression rate (viewable_impressions / measurable_impressions). Range 0.0 to 1.0."
         },
         "viewed_seconds": {
-          "$ref": "/schemas/3.1.15/core/forecast-range.json",
+          "$ref": "/schemas/3.1.20/core/forecast-range.json",
           "description": "Forecasted average in-view duration per measurable impression, in seconds."
         },
         "standard": {
-          "$ref": "/schemas/3.1.15/enums/viewability-standard.json",
+          "$ref": "/schemas/3.1.20/enums/viewability-standard.json",
           "description": "Viewability measurement standard applied to these forecasted values."
         }
       },
@@ -192,7 +192,7 @@
       "type": "array",
       "description": "Forecasted values for vendor-defined metrics that the product's reporting_capabilities.vendor_metrics declared. Mirrors delivery-metrics.vendor_metric_values, but value and measurable_impressions use ForecastRange. These forecasted measurement values are independent of pricing_options.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/forecast-vendor-metric-value.json"
+        "$ref": "/schemas/3.1.20/core/forecast-vendor-metric-value.json"
       }
     }
   },

package/dist/lib/schemas-data/3.1/core/forecast-range.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/forecast-range.json",
+  "$id": "/schemas/3.1.20/core/forecast-range.json",
   "title": "Forecast Range",
   "description": "A forecast value with optional confidence bounds. Either mid (point estimate) or both low and high (range) must be provided. mid represents the most likely outcome. low and high represent conservative and optimistic estimates. All three can be provided together.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/forecast-vendor-metric-value.json

@@ -1,20 +1,20 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/forecast-vendor-metric-value.json",
+  "$id": "/schemas/3.1.20/core/forecast-vendor-metric-value.json",
   "title": "Forecast Vendor Metric Value",
   "description": "A forecasted value for a vendor-defined metric, emitted on ForecastPoint.vendor_metric_values parallel to delivery-metrics vendor_metric_values. The envelope mirrors VendorMetricValue but uses ForecastRange for value and measurable_impressions because forecasts may carry low/mid/high bounds instead of actual delivered values.",
   "type": "object",
   "properties": {
     "vendor": {
-      "$ref": "/schemas/3.1.15/core/brand-ref.json",
+      "$ref": "/schemas/3.1.20/core/brand-ref.json",
       "description": "Vendor that defines and forecasts this metric. Matches a reporting_capabilities.vendor_metrics declaration on the product."
     },
     "metric_id": {
-      "$ref": "/schemas/3.1.15/core/vendor-metric-id.json",
+      "$ref": "/schemas/3.1.20/core/vendor-metric-id.json",
       "description": "Identifier for the metric within the vendor's vocabulary. Matches a vendor_metrics[].metric_id declaration on the product."
     },
     "value": {
-      "$ref": "/schemas/3.1.15/core/forecast-range.json",
+      "$ref": "/schemas/3.1.20/core/forecast-range.json",
       "description": "Forecasted vendor metric value. Unit semantics are vendor-defined; see unit and the vendor's measurement-agent metric definition."
     },
     "unit": {
@@ -31,7 +31,7 @@
       ]
     },
     "measurable_impressions": {
-      "$ref": "/schemas/3.1.15/core/forecast-range.json",
+      "$ref": "/schemas/3.1.20/core/forecast-range.json",
       "description": "Forecasted number of impressions the vendor expects to be able to measure. Coverage denominator for the vendor metric; buyers compute estimated coverage as measurable_impressions / impressions when both are present."
     },
     "breakdown": {

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/format-id.json",
+  "$id": "/schemas/3.1.20/core/format-id.json",
   "title": "Format Reference (Structured Object)",
   "description": "A JSON object — never a plain string — that identifies a creative format by its declaring agent and local slug. Required properties: agent_url (URI of the agent that owns the format) and id (slug matching [a-zA-Z0-9_-]+). Example: {\"agent_url\": \"https://creative.adcontextprotocol.org\", \"id\": \"display_300x250\"}. Can reference: (1) a concrete format with fixed dimensions (id only), (2) a template format without parameters (id only), or (3) a template format with parameters (id + dimensions/duration). Template formats accept parameters in format_id while concrete formats have fixed dimensions in their definition. Parameterized format IDs create unique, specific format variants. Using a plain string here is a schema violation.",
   "x-entity": "creative_format",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/format-option-ref.json",
+  "$id": "/schemas/3.1.20/core/format-option-ref.json",
   "title": "Format Option Reference",
   "description": "Discriminated reference to a product format option. The global canonical shape is still named by `format_kind`; this reference selects one concrete product `format_options[]` entry. `scope: \"publisher\"` identifies a publisher-declared catalog option by `{ publisher_domain, format_option_id }`. `scope: \"product\"` identifies a product-local option by `format_option_id`; the enclosing package/product context supplies the namespace.",
   "type": "object",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/format-shape-vocabulary.json",
+  "$id": "/schemas/3.1.20/core/format-shape-vocabulary.json",
   "title": "AdCP Format Shape Vocabulary Registry",
   "description": "Canonical registry of `format_shape` values used on `ProductFormatDeclaration` when `format_kind: \"custom\"`. Captures recognized creative-structure patterns that are NOT yet first-class canonical formats — composed/coordinated/sponsorship shapes that high-end publishers and broadcast networks sell as headline products. Each registry entry names a global shape; the seller's actual structure lives in `format_schema` (URI+digest reference to the seller-hosted or AAO-mirrored schema) so buyer agents can fetch and validate against a real schema rather than reasoning over an opaque ext blob.\n\n**Two-layer extensibility:**\n- **Canonical** (`format_kind: image`, `video_vast`, etc.): full spec coverage, stable contract.\n- **Custom + format_shape + format_schema** (`format_kind: \"custom\"`): recognized pattern, classified against this vocabulary, but the params/slots structure is supplied by a fetchable schema rather than baked into AdCP.\n\nNon-canonical `format_shape` values remain valid (validators MAY soft-warn) so adopters CAN ship a shape that isn't yet in the registry — adding entries is a vocabulary PR, not a major-version bump. Once a `format_shape` entry sees 2+ adopters with substantively similar `format_schema` content for 90+ days, the working group promotes it to a first-class canonical (creates `/schemas/formats/canonical/<name>.json`, adds the value to `canonical-format-kind.json`, retires the registry entry). See [adcp#3666](https://github.com/adcontextprotocol/adcp/issues/3666) for the promotion queue.\n\n**Promotion migration contract (normative).** Promotion is a wire-shape change for any consumer code branching on `format_kind == \"custom\"` — the same publisher's product now ships under `format_kind: \"<promoted_name>\"`. To avoid silent breakage:\n\n1. **Transition window.** When the working group promotes a `format_shape` to a first-class `format_kind`, sellers MAY ship a product under BOTH shapes during the transition window — two declarations on the same product's `format_options` array, one `format_kind: \"custom\"` + `format_shape: \"<name>\"` and one `format_kind: \"<promoted_name>\"`. Transition window is at minimum 90 days; the promotion PR sets the calendar.\n2. **Consumer-SDK deprecation warning.** SDKs encountering a `format_kind: \"custom\"` declaration whose `format_shape` matches an entry promoted to a first-class canonical SHOULD emit a structured deprecation warning via their lint channel (same pattern as `FORMAT_PROJECTION_FAILED` cross-boundary visibility) carrying `{ format_shape, promoted_to: format_kind, promotion_release, transition_end }`. Adopters branching on `format_kind == \"custom\"` past `transition_end` silently lose that publisher's inventory; the deprecation warning is the early signal.\n3. **`promotion_status` lifecycle.** When promotion is scheduled, the entry's `promotion_status` SHOULD update from `tracking — see adcp#3666` to `promoted to <format_kind> in <version>; transition ends <date>`. SDKs MAY read the registry at codegen / runtime to populate the deprecation warning's `transition_end`.\n4. **Producer-side hygiene.** After the transition window closes, sellers SHOULD drop the legacy `format_kind: \"custom\"` declaration and ship only the first-class canonical. Buyers MAY then assume `format_kind == \"custom\"` + `format_shape: \"<name>\"` is a long-tail / non-promoted shape, not a promoted-canonical-shipped-under-the-old-name.\n\nWithout this contract, every promotion event silently breaks adopter code branching on `format_kind == \"custom\"`. With it, the breakage surfaces as a structured warning during the transition window and adopters can update their branching ahead of the cutover.",
   "version": "1.0.0",