@adcp/sdk 12.0.5 → 12.1.0

package/dist/lib/schemas-data/3.1/core/cancellation-policy.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/cancellation-policy.json",
+  "$id": "/schemas/3.1.5/core/cancellation-policy.json",
   "title": "Cancellation Policy",
   "description": "Seller-declared cancellation terms for a product. Declares the minimum notice period required before cancellation takes effect and the cancellation fee for insufficient notice. Buyers accept these terms by creating a media buy against the product.",
   "type": "object",
   "properties": {
     "notice_period": {
-      "$ref": "/schemas/3.1.2/core/duration.json",
+      "$ref": "/schemas/3.1.5/core/duration.json",
       "description": "Minimum notice period before cancellation takes effect (e.g., { interval: 30, unit: 'days' }). A guaranteed buy canceled without sufficient notice incurs the declared cancellation fee."
     },
     "cancellation_fee": {
@@ -38,6 +38,44 @@
       "required": [
         "type"
       ],
+      "allOf": [
+        {
+          "$comment": "rate quantifies a percent_remaining fee; without it the cancellation cost is undefined.",
+          "if": {
+            "properties": {
+              "type": {
+                "const": "percent_remaining"
+              }
+            },
+            "required": [
+              "type"
+            ]
+          },
+          "then": {
+            "required": [
+              "rate"
+            ]
+          }
+        },
+        {
+          "$comment": "amount quantifies a fixed_fee; without it the cancellation cost is undefined.",
+          "if": {
+            "properties": {
+              "type": {
+                "const": "fixed_fee"
+              }
+            },
+            "required": [
+              "type"
+            ]
+          },
+          "then": {
+            "required": [
+              "amount"
+            ]
+          }
+        }
+      ],
       "additionalProperties": true
     }
   },

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/canonical-format-kind.json",
+  "$id": "/schemas/3.1.5/core/canonical-format-kind.json",
   "title": "Canonical Format Kind",
   "description": "Discriminator value naming one of the 12 canonical creative formats — plus `custom` for adopter-defined shapes that don't fit the canonicals (multi-placement takeover, roadblock, branded content, cross-screen sponsorship, AR lens, etc.). Used by `product-format-declaration.json` (the product's inline format declaration), `creative-manifest.json` (the buyer's v2 manifest path), and any other surface that needs to identify which canonical a payload targets.\n\nWhen `format_kind: \"custom\"`, the declaration MUST also carry `format_shape` (referencing the [format-shape vocabulary registry](/schemas/core/format-shape-vocabulary.json) — recognized global pattern this custom shape is an instance of) and `format_schema` (URI+digest reference to a fetchable schema describing the shape's actual `params` and `slots`). Buyer agents fetch the schema, validate manifests structurally, and reason about manifests without per-seller integration code — same mechanic as `platform_extensions`. See [adcp#3666](https://github.com/adcontextprotocol/adcp/issues/3666) for the canonical promotion queue.\n\nThe canonical enum mirrors the `oneOf` branches in `product-format-declaration.json`; keep them in sync.\n\n**Open-enum semantics (normative).** The enum list above is the AdCP 3.1 baseline. New canonical formats promoted from `format_shape` entries (see [#3666](https://github.com/adcontextprotocol/adcp/issues/3666)) extend this enum in subsequent minor releases — adding a value is non-breaking by design. Consumer SDKs MUST treat this enum as **open** at parse time: an unknown `format_kind` value MUST be retained as-is on the in-memory object (not silently dropped or rewritten to `\"custom\"`) and MUST NOT cause the surrounding payload to fail validation. Buyers reading a declaration with an unknown `format_kind` SHOULD treat the declaration as a local SDK-only declared/unsupported route for routing purposes (filter out of default product views; opt-in to surface) so adopters on older SDK versions don't crash on newer canonical values, and adopters on newer SDK versions get a graceful unknown-value handling story. The producer-side enum stays closed (sellers MUST NOT mint ad-hoc `format_kind` values — use `format_kind: \"custom\"` with `format_shape` + `format_schema` for non-registered shapes); the consumer-side enum stays open for forward compatibility.",
   "type": "string",

package/dist/lib/schemas-data/3.1/core/canonical-projection-ref.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/canonical-projection-ref.json",
+  "$id": "/schemas/3.1.5/core/canonical-projection-ref.json",
   "title": "Canonical Projection Reference",
   "description": "Authoritative v1 → v2 projection annotation on a v1 named format. Tells SDKs which canonical-formats v2 declaration to produce when projecting this v1 format to v2, including any non-default `asset_source` and slot-override hints needed when the v1 format's asset shape doesn't follow the canonical's defaults.\n\n**Why an object, not just a string.** A bare-string annotation like `canonical: \"image\"` carries the canonical's default slot shape (image_main: image, required) and default asset_source (buyer_uploaded). For v1 formats that genuinely follow those defaults (e.g., a 300×250 image upload), that's correct. For v1 formats whose asset shape differs (e.g., a generative entry whose input is `generation_prompt: text`, not an image upload), a bare-string annotation is lossy — the projected v2 declaration would claim buyer-uploaded image bytes when the underlying inventory wants a text prompt. The object form lets the catalog carry the asset_source + slot override so projection is lossless.\n\n**SDK projection rules (normative).**\n1. Read `kind` — this becomes `format_kind` on the projected v2 ProductFormatDeclaration.\n2. If `asset_source` is set, copy to the projected declaration's `params.asset_source`. If absent, projection uses the canonical's default asset_source (typically `buyer_uploaded`).\n3. If `slots_override` is set, copy to the projected declaration's `params.slots[]`, REPLACING the canonical's default slot set. If absent, projection inherits the canonical's defaults.\n4. v1 format's `requirements` (dimensions, durations, codecs, etc.) become `params` fields on the projected declaration per the canonical's parameter schema.\n5. v1 format's `assets[*]` shape MUST be consistent with the resulting `slots[]` — the v1 assets are the projected slots, just identified by `asset_id` (v1) ↔ `asset_group_id` (v2). The asset-group-vocabulary registry resolves aliases.\n\n**Examples.**\n\nDefault-slot case (a 300×250 image upload format):\n```json\n\"canonical\": { \"kind\": \"image\" }\n```\nGenerative case (a 300×250 entry whose input is a text prompt):\n```json\n\"canonical\": {\n  \"kind\": \"image\",\n  \"asset_source\": \"agent_synthesized\",\n  \"slots_override\": [\n    { \"asset_group_id\": \"generation_prompt\", \"asset_type\": \"text\", \"required\": true }\n  ]\n}\n```\nBoth project to `format_kind: \"image\"` — the difference is the per-product `asset_source` + `slots[]` shape. v2-aware buyers see the projection and know whether to ship image bytes or a text prompt.",
   "type": "object",
@@ -9,7 +9,7 @@
   ],
   "properties": {
     "kind": {
-      "$ref": "/schemas/3.1.2/core/canonical-format-kind.json",
+      "$ref": "/schemas/3.1.5/core/canonical-format-kind.json",
       "description": "The v2 canonical-format-kind this v1 format projects to (`image`, `html5`, `display_tag`, `image_carousel`, `video_hosted`, `video_vast`, `audio_hosted`, `audio_daast`, `sponsored_placement`, `responsive_creative`, `agent_placement`, or `custom`)."
     },
     "asset_source": {
@@ -29,7 +29,7 @@
       "minItems": 1,
       "description": "When the v1 named format's slot shape differs from the canonical's default slots, this carries the override that the projected v2 declaration's `params.slots[]` should use. REPLACES (does not merge with) the canonical's default slots — projection-time semantics. The slot vocabulary follows `asset-group-vocabulary.json`. Asset IDs in the v1 format's `assets[*]` MUST resolve (directly or via the vocabulary's aliases) to the `asset_group_id` values declared here.",
       "items": {
-        "$ref": "/schemas/3.1.2/core/canonical-projection-slot-override.json"
+        "$ref": "/schemas/3.1.5/core/canonical-projection-slot-override.json"
       }
     }
   },

package/dist/lib/schemas-data/3.1/core/canonical-projection-slot-override.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/canonical-projection-slot-override.json",
+  "$id": "/schemas/3.1.5/core/canonical-projection-slot-override.json",
   "title": "Canonical Projection Slot Override",
   "description": "A single slot override used when projecting a legacy named format to a v2 canonical ProductFormatDeclaration. The override replaces the canonical format's default slot with an asset-group-vocabulary entry.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/catalog-field-mapping.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/catalog-field-mapping.json",
+  "$id": "/schemas/3.1.5/core/catalog-field-mapping.json",
   "title": "Catalog Field Mapping",
   "description": "Declares how a field in an external feed maps to the AdCP catalog item schema. Used in sync_catalogs feed_field_mappings to normalize non-AdCP feeds (Google Merchant Center, LinkedIn Jobs XML, hotel XML, etc.) to the standard catalog item schema without requiring the buyer to preprocess every feed. Multiple mappings can assemble a nested object via dot notation (e.g., separate mappings for price.amount and price.currency).",
   "type": "object",
@@ -52,7 +52,7 @@
       "description": "Fallback value to use when feed_field is absent, null, or empty. Applied after any transform would have been applied. Allows optional feed fields to have a guaranteed baseline value."
     },
     "ext": {
-      "$ref": "/schemas/3.1.2/core/ext.json"
+      "$ref": "/schemas/3.1.5/core/ext.json"
     }
   },
   "allOf": [

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

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/catalog-item-delivery-metrics.json",
+  "$id": "/schemas/3.1.5/core/catalog-item-delivery-metrics.json",
   "title": "Catalog Item Delivery Metrics",
   "description": "Delivery metrics row for one catalog item within a package.",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.2/core/delivery-metrics.json"
+      "$ref": "/schemas/3.1.5/core/delivery-metrics.json"
     },
     {
       "type": "object",
@@ -15,7 +15,7 @@
           "description": "Catalog item identifier (e.g., SKU, GTIN, job_id, offering_id)"
         },
         "content_id_type": {
-          "$ref": "/schemas/3.1.2/enums/content-id-type.json",
+          "$ref": "/schemas/3.1.5/enums/content-id-type.json",
           "description": "Identifier type for this content_id"
         }
       },

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/catalog.json",
+  "$id": "/schemas/3.1.5/core/catalog.json",
   "title": "Catalog",
   "description": "A typed data feed. Catalogs carry the items, locations, stock levels, or pricing that publishers use to render ads. They can be synced to a platform via sync_catalogs (managed lifecycle with approval), provided inline, or fetched from an external URL. The catalog type determines the item schema and can be structural (offering, product, inventory, store, promotion) or vertical-specific (hotel, flight, job, vehicle, real_estate, education, destination, app). Selectors (ids, tags, category, query) filter items regardless of sourcing method.",
   "type": "object",
@@ -15,7 +15,7 @@
       "description": "Human-readable name for this catalog (e.g., 'Summer Products 2025', 'Amsterdam Store Locations')."
     },
     "type": {
-      "$ref": "/schemas/3.1.2/enums/catalog-type.json",
+      "$ref": "/schemas/3.1.5/enums/catalog-type.json",
       "description": "Catalog type. Structural types: 'offering' (AdCP Offering objects), 'product' (ecommerce entries), 'inventory' (stock per location), 'store' (physical locations), 'promotion' (deals and pricing). Vertical types: 'hotel', 'flight', 'job', 'vehicle', 'real_estate', 'education', 'destination', 'app' — each with an industry-specific item schema."
     },
     "url": {
@@ -24,11 +24,11 @@
       "description": "URL to an external catalog feed. The platform fetches and resolves items from this URL. For offering-type catalogs, the feed contains an array of Offering objects. For other types, the feed format is determined by feed_format. When omitted with type 'product', the platform uses its synced copy of the brand's product catalog."
     },
     "feed_format": {
-      "$ref": "/schemas/3.1.2/enums/feed-format.json",
+      "$ref": "/schemas/3.1.5/enums/feed-format.json",
       "description": "Format of the external feed at url. Required when url points to a non-AdCP feed (e.g., Google Merchant Center XML, Meta Product Catalog). Omit for offering-type catalogs where the feed is native AdCP JSON."
     },
     "update_frequency": {
-      "$ref": "/schemas/3.1.2/enums/update-frequency.json",
+      "$ref": "/schemas/3.1.5/enums/update-frequency.json",
       "description": "How often the platform should re-fetch the feed from url. Only applicable when url is provided. Platforms may use this as a hint for polling schedules."
     },
     "items": {
@@ -76,20 +76,20 @@
       "type": "array",
       "description": "Event types that represent conversions for items in this catalog. Declares what events the platform should attribute to catalog items — e.g., a job catalog converts via submit_application, a product catalog via purchase. The event's content_ids field carries the item IDs that connect back to catalog items. Use content_id_type to declare what identifier type content_ids values represent.",
       "items": {
-        "$ref": "/schemas/3.1.2/enums/event-type.json"
+        "$ref": "/schemas/3.1.5/enums/event-type.json"
       },
       "minItems": 1,
       "uniqueItems": true
     },
     "content_id_type": {
-      "$ref": "/schemas/3.1.2/enums/content-id-type.json",
+      "$ref": "/schemas/3.1.5/enums/content-id-type.json",
       "description": "Identifier type that the event's content_ids field should be matched against for items in this catalog. For example, 'gtin' means content_ids values are Global Trade Item Numbers, 'sku' means retailer SKUs. Omit when using a custom identifier scheme not listed in the enum."
     },
     "feed_field_mappings": {
       "type": "array",
       "description": "Declarative normalization rules for external feeds. Maps non-standard feed field names, date formats, price encodings, and image URLs to the AdCP catalog item schema. Applied during sync_catalogs ingestion. Supports field renames, named transforms (date, divide, boolean, split), static literal injection, and assignment of image URLs to typed asset pools.",
       "items": {
-        "$ref": "/schemas/3.1.2/core/catalog-field-mapping.json"
+        "$ref": "/schemas/3.1.5/core/catalog-field-mapping.json"
       },
       "minItems": 1
     }

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/catchment.json",
+  "$id": "/schemas/3.1.5/core/catchment.json",
   "title": "Catchment",
   "description": "A catchment area definition for a store or location. Defines the geographic area from which a store draws customers. Three methods are supported: isochrone inputs (travel time + transport mode, platform resolves the shape), simple radius (distance from location), or pre-computed GeoJSON geometry (buyer provides the exact boundary). Provide exactly one method per catchment.",
   "type": "object",
@@ -23,7 +23,7 @@
           "description": "Travel time limit."
         },
         "unit": {
-          "$ref": "/schemas/3.1.2/enums/travel-time-unit.json"
+          "$ref": "/schemas/3.1.5/enums/travel-time-unit.json"
         }
       },
       "required": [
@@ -33,7 +33,7 @@
       "additionalProperties": false
     },
     "transport_mode": {
-      "$ref": "/schemas/3.1.2/enums/transport-mode.json",
+      "$ref": "/schemas/3.1.5/enums/transport-mode.json",
       "description": "Transportation mode for isochrone calculation. Required when travel_time is provided."
     },
     "radius": {
@@ -46,7 +46,7 @@
           "description": "Radius distance."
         },
         "unit": {
-          "$ref": "/schemas/3.1.2/enums/distance-unit.json",
+          "$ref": "/schemas/3.1.5/enums/distance-unit.json",
           "description": "Distance unit."
         }
       },
@@ -80,7 +80,7 @@
       "additionalProperties": false
     },
     "ext": {
-      "$ref": "/schemas/3.1.2/core/ext.json"
+      "$ref": "/schemas/3.1.5/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/collection-distribution.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/collection-distribution.json",
+  "$id": "/schemas/3.1.5/core/collection-distribution.json",
   "title": "Collection Distribution",
   "description": "A collection's presence on a specific publisher platform, identified by platform-specific identifiers. Enables cross-seller matching when the same collection is sold by different agents.",
   "type": "object",
@@ -16,7 +16,7 @@
         "type": "object",
         "properties": {
           "type": {
-            "$ref": "/schemas/3.1.2/enums/distribution-identifier-type.json",
+            "$ref": "/schemas/3.1.5/enums/distribution-identifier-type.json",
             "description": "Type of distribution identifier"
           },
           "value": {

package/dist/lib/schemas-data/3.1/core/collection-list-ref.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/collection-list-ref.json",
+  "$id": "/schemas/3.1.5/core/collection-list-ref.json",
   "title": "Collection List Reference",
   "description": "Reference to an externally managed collection list. Enables passing large collection exclusion/inclusion sets without embedding them in requests. The receiving agent fetches and caches the list independently.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/collection-selector.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/collection-selector.json",
+  "$id": "/schemas/3.1.5/core/collection-selector.json",
   "title": "Collection Selector",
   "description": "References collections declared in an adagents.json. Buyers resolve full collection objects by fetching the adagents.json at the given domain and matching collection_ids against its collections array.",
   "type": "object",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/collection.json",
+  "$id": "/schemas/3.1.5/core/collection.json",
   "title": "Collection",
   "description": "A recurring inventory container — a named program, publication, event series, or rotation that produces bookable installments on a defined cadence. The kind field indicates how to interpret this collection: 'series' for TV/podcast programs, 'publication' for print/newsletter titles, 'event_series' for live events, 'rotation' for DOOH scheduling. Declared in the publisher's adagents.json and referenced by products via collection selectors.",
   "type": "object",
@@ -14,7 +14,7 @@
       "description": "Human-readable collection name"
     },
     "kind": {
-      "$ref": "/schemas/3.1.2/enums/collection-kind.json",
+      "$ref": "/schemas/3.1.5/enums/collection-kind.json",
       "description": "What kind of content program this is. Helps agents interpret installments correctly. Defaults to 'series' when absent."
     },
     "description": {
@@ -37,11 +37,11 @@
       "description": "Primary language (BCP 47 tag, e.g., 'en', 'es-MX')"
     },
     "content_rating": {
-      "$ref": "/schemas/3.1.2/core/content-rating.json",
+      "$ref": "/schemas/3.1.5/core/content-rating.json",
       "description": "Baseline content rating for the collection. Individual installments may override this."
     },
     "cadence": {
-      "$ref": "/schemas/3.1.2/enums/collection-cadence.json",
+      "$ref": "/schemas/3.1.5/enums/collection-cadence.json",
       "description": "How frequently the collection releases new installments"
     },
     "season": {
@@ -49,37 +49,37 @@
       "description": "Current or most recent season identifier (e.g., '3', '2026', 'spring_2026'). A lightweight label — not a full season object."
     },
     "status": {
-      "$ref": "/schemas/3.1.2/enums/collection-status.json",
+      "$ref": "/schemas/3.1.5/enums/collection-status.json",
       "description": "Lifecycle status of the collection"
     },
     "production_quality": {
-      "$ref": "/schemas/3.1.2/enums/production-quality.json",
+      "$ref": "/schemas/3.1.5/enums/production-quality.json",
       "description": "Production quality tier. Seller-declared. Maps to OpenRTB content.prodq (professional=1, prosumer=2, ugc=3)."
     },
     "talent": {
       "type": "array",
       "description": "Hosts, recurring cast, creators associated with the collection. Each talent entry may include a brand_url linking to their brand.json identity.",
       "items": {
-        "$ref": "/schemas/3.1.2/core/talent.json"
+        "$ref": "/schemas/3.1.5/core/talent.json"
       }
     },
     "special": {
-      "$ref": "/schemas/3.1.2/core/special.json",
+      "$ref": "/schemas/3.1.5/core/special.json",
       "description": "When present, this collection is a special — content anchored to a real-world event or occasion. Individual installments may override with their own event context."
     },
     "limited_series": {
-      "$ref": "/schemas/3.1.2/core/limited-series.json",
+      "$ref": "/schemas/3.1.5/core/limited-series.json",
       "description": "When present, this collection is a limited series — a bounded run with a defined arc, installment count, and end date."
     },
     "distribution": {
       "type": "array",
       "description": "Where this collection is distributed. Each entry maps the collection to a publisher platform with platform-specific identifiers. Collections SHOULD include at least one platform-independent identifier (imdb_id, gracenote_id, eidr_id) when available.",
       "items": {
-        "$ref": "/schemas/3.1.2/core/collection-distribution.json"
+        "$ref": "/schemas/3.1.5/core/collection-distribution.json"
       }
     },
     "deadline_policy": {
-      "$ref": "/schemas/3.1.2/core/deadline-policy.json",
+      "$ref": "/schemas/3.1.5/core/deadline-policy.json",
       "description": "Default deadline rules for installments of this collection. Agents compute absolute deadlines from each installment's scheduled_at and these lead times. Installments with explicit deadlines override this policy."
     },
     "related_collections": {
@@ -93,7 +93,7 @@
             "description": "The related collection's collection_id within this seller's response"
           },
           "relationship": {
-            "$ref": "/schemas/3.1.2/enums/collection-relationship.json",
+            "$ref": "/schemas/3.1.5/enums/collection-relationship.json",
             "description": "How the collections are related"
           }
         },
@@ -105,7 +105,7 @@
       }
     },
     "ext": {
-      "$ref": "/schemas/3.1.2/core/ext.json"
+      "$ref": "/schemas/3.1.5/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/committed-metric.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/committed-metric.json",
+  "$id": "/schemas/3.1.5/core/committed-metric.json",
   "title": "Committed Metric",
   "description": "One metric in a package's binding reporting contract. Each entry uses `scope` as the discriminator and identifies a standard or vendor-defined metric that the seller has committed to populate in delivery reports.",
   "type": "object",
@@ -16,7 +16,7 @@
           "description": "Standard metric from the closed `available-metric.json` enum."
         },
         "metric_id": {
-          "$ref": "/schemas/3.1.2/enums/available-metric.json",
+          "$ref": "/schemas/3.1.5/enums/available-metric.json",
           "description": "Identifier for the standard metric."
         },
         "qualifier": {
@@ -24,23 +24,23 @@
           "description": "Disambiguates metrics whose definition varies by qualifier. Today carries five keys — `viewability_standard` (MRC vs GroupM viewability), `completion_source` (seller- vs vendor-attested completion), `attribution_methodology` (how attribution was computed for outcome metrics), `attribution_window` (the time window over which outcomes were attributed), and `lift_dimension` (which dimension of brand_lift this row represents — awareness, consideration, etc.). Required when the underlying `metric_id` has multiple incompatible measurement paths AND the seller commits to a specific one. Symmetric on `missing_metrics`. Reserved for additive qualifiers in future minors — schema is closed (`additionalProperties: false`); new keys ship explicitly. **Heterogeneous value types**: qualifier values can be either string enums (`viewability_standard`, `completion_source`, `attribution_methodology`, `lift_dimension`) or structured objects (`attribution_window` is a duration `{interval, unit}`). Consumers MUST dispatch on key name to know value shape; structured-value qualifiers join on canonical (key-sorted) deep equality so `{interval: 14, unit: 'days'}` and `{unit: 'days', interval: 14}` resolve to the same partition. Rate-style metrics (`new_to_brand_rate`, `engagement_rate`, etc.) inherit the methodology of their numerator — when a rate carries `attribution_methodology` qualifier, it applies to the underlying conversions/events being rated.",
           "properties": {
             "viewability_standard": {
-              "$ref": "/schemas/3.1.2/enums/viewability-standard.json",
+              "$ref": "/schemas/3.1.5/enums/viewability-standard.json",
               "description": "Viewability standard the seller commits to for this metric. MUST be set when `metric_id` ∈ {`viewable_impressions`, `viewable_rate`, `measurable_impressions`} and the seller commits to a specific standard; absence means the contract leaves the standard unspecified and reconciliation falls back to whatever standard the delivery report carries on its `viewability.standard` field."
             },
             "completion_source": {
-              "$ref": "/schemas/3.1.2/enums/completion-source.json",
+              "$ref": "/schemas/3.1.5/enums/completion-source.json",
               "description": "Source of `completion_rate` attestation. MUST be set when `metric_id` is `completion_rate` and the seller commits to a specific source — `seller_attested` when the player/ad server's own completion event is the contract, `vendor_attested` when a third-party measurement vendor (anchored on the matching `performance_standard.vendor` BrandRef) is the contract. Absence means the contract leaves the source unspecified and reconciliation falls back to whatever the delivery report happens to carry."
             },
             "attribution_methodology": {
-              "$ref": "/schemas/3.1.2/enums/attribution-methodology.json",
+              "$ref": "/schemas/3.1.5/enums/attribution-methodology.json",
               "description": "How attribution between ad exposure and outcome events was computed. SHOULD be set when `metric_id` is an outcome metric (`conversions`, `conversion_value`, `roas`, `cost_per_acquisition`, `incremental_sales_lift`, `brand_lift`, `foot_traffic`, `conversion_lift`, `brand_search_lift`, `units_sold`, `new_to_brand_rate`, `new_to_brand_units`, `leads`) and the seller commits to a specific methodology. `deterministic_purchase` is the retail-media default; `modeled` covers MMM and clean-room outputs; `probabilistic` and `panel_based` cover their respective methodologies. Two outcome rows with the same `metric_id` and different `attribution_methodology` are not interchangeable and must not be summed."
             },
             "attribution_window": {
-              "$ref": "/schemas/3.1.2/core/duration.json",
+              "$ref": "/schemas/3.1.5/core/duration.json",
               "description": "Time window over which outcome attribution is computed. **Object-valued, not string** — MUST be a structured duration object like `{interval: 14, unit: 'days'}`, NEVER a shorthand string like `'14d'`. SHOULD be set when `metric_id` is an outcome metric and the seller commits to a specific window. Common windows: `{interval: 7, unit: 'days'}`, `{interval: 14, unit: 'days'}`, `{interval: 30, unit: 'days'}`, `{interval: 90, unit: 'days'}`. Two outcome rows with the same `metric_id` and `attribution_methodology` but different `attribution_window` represent the same metric measured over different periods — the join on `(metric_id, qualifier)` keeps them as separate rows so buyers don't accidentally aggregate across windows."
             },
             "lift_dimension": {
-              "$ref": "/schemas/3.1.2/enums/lift-dimension.json",
+              "$ref": "/schemas/3.1.5/enums/lift-dimension.json",
               "description": "Which dimension of `brand_lift` this row represents — awareness, consideration, favorability, purchase intent, or ad recall. MUST be set when `metric_id` is `brand_lift` and the seller commits to (or is reporting) a specific dimension. Brand-lift vendors (Kantar, Upwave, Cint, DoubleVerify) report each dimension separately with its own sample size and confidence interval; combining them into a single number is a category error. Two `brand_lift` rows under different `lift_dimension` are different surveyed outcomes and must not be summed."
             }
           },
@@ -67,11 +67,11 @@
           "description": "Vendor-defined metric, identified by the tuple `(vendor, metric_id)`."
         },
         "vendor": {
-          "$ref": "/schemas/3.1.2/core/brand-ref.json",
+          "$ref": "/schemas/3.1.5/core/brand-ref.json",
           "description": "Vendor that defines and computes this metric. The vendor's `brand.json` `agents[type='measurement']` is the canonical anchor."
         },
         "metric_id": {
-          "$ref": "/schemas/3.1.2/core/vendor-metric-id.json",
+          "$ref": "/schemas/3.1.5/core/vendor-metric-id.json",
           "description": "Identifier for the metric within the vendor's vocabulary."
         },
         "committed_at": {

package/dist/lib/schemas-data/3.1/core/content-rating.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/content-rating.json",
+  "$id": "/schemas/3.1.5/core/content-rating.json",
   "title": "Content Rating",
   "description": "Content advisory rating using a specified rating system",
   "type": "object",
   "properties": {
     "system": {
-      "$ref": "/schemas/3.1.2/enums/content-rating-system.json",
+      "$ref": "/schemas/3.1.5/enums/content-rating-system.json",
       "description": "Rating system used"
     },
     "rating": {

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/context.json",
+  "$id": "/schemas/3.1.5/core/context.json",
   "title": "Context Object",
   "description": "Opaque correlation data that is echoed unchanged in responses. Used for internal tracking, UI session IDs, trace IDs, and other caller-specific identifiers that don't affect protocol behavior. Context data is never parsed by AdCP agents - it's simply preserved and returned.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/creative-asset.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/creative-asset.json",
+  "$id": "/schemas/3.1.5/core/creative-asset.json",
   "title": "Creative Asset",
   "description": "Creative asset for upload to library — supports static assets, generative formats, and third-party snippets. Identifies which format this creative conforms to via EITHER a legacy `format_id` (structured `{agent_url, id}`) OR a 3.1+ `format_kind` (canonical format name), with optional `format_option_ref` when the target product needs disambiguation. Mutually exclusive — see the `oneOf` at the schema root.",
   "type": "object",
@@ -15,15 +15,15 @@
       "description": "Human-readable creative name"
     },
     "format_id": {
-      "$ref": "/schemas/3.1.2/core/format-id.json",
+      "$ref": "/schemas/3.1.5/core/format-id.json",
       "description": "Legacy named-format path. Always a structured object {agent_url, id} — never a plain string. Format identifier specifying which format this creative conforms to. Can be: (1) concrete format_id referencing a format with fixed dimensions, (2) template format_id referencing a template format, or (3) parameterized format_id with dimensions/duration parameters for template formats. Mutually exclusive with `format_kind`."
     },
     "format_kind": {
-      "$ref": "/schemas/3.1.2/core/canonical-format-kind.json",
+      "$ref": "/schemas/3.1.5/core/canonical-format-kind.json",
       "description": "3.1+ canonical-format path. The canonical format name this creative targets (e.g., `image`, `video_hosted`). Mutually exclusive with `format_id`."
     },
     "format_option_ref": {
-      "$ref": "/schemas/3.1.2/core/format-option-ref.json",
+      "$ref": "/schemas/3.1.5/core/format-option-ref.json",
       "description": "3.1+ format-option path, optional. Structured format option reference matching one of the target product's `format_options[]` declarations. Publisher-catalog-backed options match by `{ scope: \"publisher\", publisher_domain, format_option_id }`; product-local options match by `{ scope: \"product\", format_option_id }`. Required when the target product has multiple `format_options` entries sharing the same `format_kind`; optional when `format_kind` alone routes the creative to a single declaration. Product-scoped refs require an enclosing target product/package context."
     },
     "assets": {
@@ -33,12 +33,12 @@
         "^[a-z0-9_]+$": {
           "oneOf": [
             {
-              "$ref": "/schemas/3.1.2/core/assets/asset-union.json"
+              "$ref": "/schemas/3.1.5/core/assets/asset-union.json"
             },
             {
               "type": "array",
               "items": {
-                "$ref": "/schemas/3.1.2/core/assets/asset-union.json"
+                "$ref": "/schemas/3.1.5/core/assets/asset-union.json"
               },
               "minItems": 1
             }
@@ -83,7 +83,7 @@
       }
     },
     "status": {
-      "$ref": "/schemas/3.1.2/enums/creative-status.json",
+      "$ref": "/schemas/3.1.5/enums/creative-status.json",
       "description": "For generative creatives: set to 'approved' to finalize, 'rejected' to request regeneration with updated assets/message. Omit for non-generative creatives (system will set based on processing state)."
     },
     "weight": {
@@ -96,7 +96,7 @@
       "type": "array",
       "description": "Optional structured placement references where this uploaded creative should run when uploading via create_media_buy or update_media_buy. New senders SHOULD use this field for placement-level targeting because placement IDs are publisher-scoped. References product placements by `{ publisher_domain, placement_id }`. If omitted, creative runs on all buyer-targetable placements. If both `placement_refs` and legacy `placement_ids` are present, `placement_refs` wins and receivers MUST ignore `placement_ids`. Only used during upload to media buy - not stored in creative library.",
       "items": {
-        "$ref": "/schemas/3.1.2/core/placement-ref.json"
+        "$ref": "/schemas/3.1.5/core/placement-ref.json"
       },
       "minItems": 1
     },
@@ -112,12 +112,12 @@
       "type": "array",
       "description": "Industry-standard or market-specific identifiers for this creative (e.g., Ad-ID, ISCI, Clearcast clock number, IDcrea). In broadcast and scheduled audio/video buying, these identifiers tie the creative to rotation instructions, clearance records, and traffic systems. A creative may have multiple identifiers when different systems reference the same asset. Add a PR to extend creative-identifier-type when another shared identifier scheme needs first-class support.",
       "items": {
-        "$ref": "/schemas/3.1.2/core/industry-identifier.json"
+        "$ref": "/schemas/3.1.5/core/industry-identifier.json"
       },
       "uniqueItems": true
     },
     "provenance": {
-      "$ref": "/schemas/3.1.2/core/provenance.json",
+      "$ref": "/schemas/3.1.5/core/provenance.json",
       "description": "Provenance metadata for this creative. Serves as the default provenance for all manifests and assets within this creative. A manifest or asset with its own provenance replaces this object entirely (no field-level merging)."
     }
   },

package/dist/lib/schemas-data/3.1/core/creative-assignment.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/creative-assignment.json",
+  "$id": "/schemas/3.1.5/core/creative-assignment.json",
   "title": "Creative Assignment",
   "description": "Assignment of a creative asset to a package with optional creative routing by placement. Used in create_media_buy and update_media_buy requests. Buyers identify the stored creative with `creative_id` only. A generic `id` alias, if present due to adapter-internal payload reuse, is not an AdCP identifier and sellers MUST ignore it on input. Note: sync_creatives does not support placement_refs or placement_ids - use create/update_media_buy for placement-level creative routing.",
   "type": "object",
@@ -20,7 +20,7 @@
       "type": "array",
       "description": "Optional array of structured placement references where this creative should run within the already-purchased package inventory. New senders SHOULD use this field for placement-level creative routing because placement IDs are publisher-scoped. This field does not narrow the purchased package inventory by itself; use product refinement or seller-supported package targeting to buy only one placement. When omitted, the creative runs on all buyer-targetable placements in the package. References entries from the product's `placements[]` array by `{ publisher_domain, placement_id }`; if `publisher_domain` is omitted in the ref, receivers MAY interpret it relative to the seller agent's own publisher domain in legacy single-publisher contexts. If both `placement_refs` and legacy `placement_ids` are present, `placement_refs` wins and receivers MUST ignore `placement_ids`.",
       "items": {
-        "$ref": "/schemas/3.1.2/core/placement-ref.json"
+        "$ref": "/schemas/3.1.5/core/placement-ref.json"
       },
       "minItems": 1
     },

package/dist/lib/schemas-data/3.1/core/creative-brief.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/creative-brief.json",
+  "$id": "/schemas/3.1.5/core/creative-brief.json",
   "title": "Creative Brief",
   "description": "Campaign-level creative context for AI-powered creative generation. Provides the layer between brand identity (stable across campaigns) and individual creative execution (per-request). A brand has one identity (defined in brand.json) but different creative briefs for each campaign or flight.",
   "type": "object",
@@ -62,7 +62,7 @@
       "type": "array",
       "description": "Visual and strategic reference materials such as mood boards, product shots, example creatives, and strategy documents",
       "items": {
-        "$ref": "/schemas/3.1.2/core/reference-asset.json"
+        "$ref": "/schemas/3.1.5/core/reference-asset.json"
       }
     },
     "compliance": {
@@ -80,7 +80,7 @@
                 "description": "The disclosure text that must appear in the creative"
               },
               "position": {
-                "$ref": "/schemas/3.1.2/enums/disclosure-position.json",
+                "$ref": "/schemas/3.1.5/enums/disclosure-position.json",
                 "description": "Where the disclosure should appear within the creative. prominent: clearly visible in the main creative area; footer: at the bottom of visual creatives; audio: spoken in audio/video creatives; subtitle: displayed in the subtitle or closed-caption track; overlay: superimposed on video content; end_card: displayed on video end card; pre_roll: spoken or displayed before main content; companion: in companion ad unit alongside primary creative"
               },
               "jurisdictions": {
@@ -106,7 +106,7 @@
                 "description": "Language of the disclosure text as a BCP 47 language tag (e.g., 'en', 'fr-CA', 'es'). When omitted, the disclosure is assumed to match the creative's language."
               },
               "persistence": {
-                "$ref": "/schemas/3.1.2/enums/disclosure-persistence.json",
+                "$ref": "/schemas/3.1.5/enums/disclosure-persistence.json",
                 "description": "How long the disclosure must persist during content playback or display. When omitted, the creative agent should use the most restrictive persistence mode supported by the target format."
               }
             },

package/dist/lib/schemas-data/3.1/core/creative-consumption.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.2/core/creative-consumption.json",
+  "$id": "/schemas/3.1.5/core/creative-consumption.json",
   "title": "Creative Consumption",
   "description": "Structured consumption details returned by build_creative when a paid creative agent computes cost. Contains well-known fields for common consumption metrics. The consumption object is informational — it lets the buyer verify that vendor_cost is consistent with the rate card. vendor_cost is the billing source of truth, not consumption.",
   "type": "object",