@adcp/sdk 17.0.0-beta.7 → 17.0.0-beta.9

package/dist/lib/schemas-data/3.1/core/async-response-refs/media-buy/get-products-async-response-working.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/media-buy/get-products-async-response-working.json",
+  "$id": "/schemas/3.1.31/media-buy/get-products-async-response-working.json",
   "title": "Get Products - Working",
   "description": "Progress payload for active get_products task.",
   "type": "object",
@@ -24,10 +24,10 @@
       "description": "Current step number (1-indexed)"
     },
     "context": {
-      "$ref": "/schemas/3.1.29/core/context.json"
+      "$ref": "/schemas/3.1.31/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.1/core/async-response-refs/media-buy/sync-catalogs-async-response-input-required.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/media-buy/sync-catalogs-async-response-input-required.json",
+  "$id": "/schemas/3.1.31/media-buy/sync-catalogs-async-response-input-required.json",
   "title": "Sync Catalogs - Input Required",
   "description": "Payload when sync_catalogs task is paused waiting for buyer clarification or approval.",
   "type": "object",
@@ -16,10 +16,10 @@
       "description": "Reason code indicating why buyer input is needed. APPROVAL_REQUIRED: platform requires explicit approval before activating the catalog. FEED_VALIDATION: feed URL returned unexpected format or schema errors. ITEM_REVIEW: platform flagged items for manual review. FEED_ACCESS: platform cannot access the feed URL (authentication, CORS, etc.)."
     },
     "context": {
-      "$ref": "/schemas/3.1.29/core/context.json"
+      "$ref": "/schemas/3.1.31/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.1/core/async-response-refs/media-buy/sync-catalogs-async-response-submitted.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/media-buy/sync-catalogs-async-response-submitted.json",
+  "$id": "/schemas/3.1.31/media-buy/sync-catalogs-async-response-submitted.json",
   "title": "Sync Catalogs - Submitted",
   "description": "Async task envelope returned when sync_catalogs cannot be confirmed before the response — for example, when catalog ingestion and deduplication are queued for batch processing. The buyer polls tasks/get with task_id or receives a webhook when the task completes; the per-catalog results land on the completion artifact, not this envelope.",
   "type": "object",
@@ -24,14 +24,14 @@
       "type": "array",
       "description": "Optional advisory errors accompanying the submitted envelope. Use only for non-blocking warnings (e.g., throttled_severity advisories, governance observations). Terminal failures belong in the error branch, not here.",
       "items": {
-        "$ref": "/schemas/3.1.29/core/error.json"
+        "$ref": "/schemas/3.1.31/core/error.json"
       }
     },
     "context": {
-      "$ref": "/schemas/3.1.29/core/context.json"
+      "$ref": "/schemas/3.1.31/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/async-response-refs/media-buy/sync-catalogs-async-response-working.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/media-buy/sync-catalogs-async-response-working.json",
+  "$id": "/schemas/3.1.31/media-buy/sync-catalogs-async-response-working.json",
   "title": "Sync Catalogs - Working",
   "description": "Progress payload for active sync_catalogs task.",
   "type": "object",
@@ -46,10 +46,10 @@
       "description": "Total number of catalog items to process across all catalogs"
     },
     "context": {
-      "$ref": "/schemas/3.1.29/core/context.json"
+      "$ref": "/schemas/3.1.31/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.1/core/async-response-refs/media-buy/update-media-buy-async-response-input-required.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/media-buy/update-media-buy-async-response-input-required.json",
+  "$id": "/schemas/3.1.31/media-buy/update-media-buy-async-response-input-required.json",
   "title": "Update Media Buy - Input Required",
   "description": "Payload when update_media_buy task is paused waiting for user input or approval.",
   "type": "object",
@@ -14,10 +14,10 @@
       "description": "Reason code indicating why input is needed"
     },
     "context": {
-      "$ref": "/schemas/3.1.29/core/context.json"
+      "$ref": "/schemas/3.1.31/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.1/core/async-response-refs/media-buy/update-media-buy-async-response-submitted.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/media-buy/update-media-buy-async-response-submitted.json",
+  "$id": "/schemas/3.1.31/media-buy/update-media-buy-async-response-submitted.json",
   "title": "Update Media Buy - Submitted",
   "description": "Async task envelope returned when update_media_buy cannot be confirmed before the response — for example, when operator re-approval is required for mid-flight changes. The buyer polls tasks/get with task_id or receives a webhook when the task completes; the updated media buy state lands on the completion artifact, not this envelope.",
   "type": "object",
@@ -24,14 +24,14 @@
       "type": "array",
       "description": "Optional advisory errors accompanying the submitted envelope. Use only for non-blocking warnings (e.g., throttled_severity advisories, governance observations). Terminal failures belong in the error branch, not here.",
       "items": {
-        "$ref": "/schemas/3.1.29/core/error.json"
+        "$ref": "/schemas/3.1.31/core/error.json"
       }
     },
     "context": {
-      "$ref": "/schemas/3.1.29/core/context.json"
+      "$ref": "/schemas/3.1.31/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/async-response-refs/media-buy/update-media-buy-async-response-working.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/media-buy/update-media-buy-async-response-working.json",
+  "$id": "/schemas/3.1.31/media-buy/update-media-buy-async-response-working.json",
   "title": "Update Media Buy - Working",
   "description": "Progress payload for active update_media_buy task.",
   "type": "object",
@@ -26,10 +26,10 @@
       "description": "Current step number"
     },
     "context": {
-      "$ref": "/schemas/3.1.29/core/context.json"
+      "$ref": "/schemas/3.1.31/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.1/core/async-response-refs/signals/get-signals-async-response-submitted.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/signals/get-signals-async-response-submitted.json",
+  "$id": "/schemas/3.1.31/signals/get-signals-async-response-submitted.json",
   "title": "Get Signals - Submitted",
   "description": "Async task envelope returned when get_signals cannot be confirmed before the response — for example, when semantic discovery depends on slow provider queries or review. This envelope is valid only for `discovery_mode: \"brief\"`; `discovery_mode: \"wholesale\"` is a synchronous wholesale signals feed read and MUST NOT use the Submitted arm. The caller can always poll `get_task_status` (legacy `tasks/get`) with `task_id`. If the originating request carried `push_notification_config`, the agent also delivers at least the terminal completion/failure notification to that webhook URL; intermediate progress notifications are MAY. The signals array lands on the completion artifact, not this envelope.",
   "type": "object",
@@ -29,14 +29,14 @@
       "type": "array",
       "description": "Optional advisory errors accompanying the submitted envelope. Use only for non-blocking warnings (e.g., throttled_severity advisories or partial provider unavailability). Terminal failures belong in the error branch, not here.",
       "items": {
-        "$ref": "/schemas/3.1.29/core/error.json"
+        "$ref": "/schemas/3.1.31/core/error.json"
       }
     },
     "context": {
-      "$ref": "/schemas/3.1.29/core/context.json"
+      "$ref": "/schemas/3.1.31/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/async-response-refs/signals/get-signals-async-response-working.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/signals/get-signals-async-response-working.json",
+  "$id": "/schemas/3.1.31/signals/get-signals-async-response-working.json",
   "title": "Get Signals - Working",
   "description": "Progress payload for an active get_signals task after a submitted semantic discovery request has started processing. Valid only for `discovery_mode: \"brief\"`; wholesale signals feed reads report partial completion via `incomplete[]`, not async task progress.",
   "type": "object",
@@ -24,10 +24,10 @@
       "description": "Current step number (1-indexed)."
     },
     "context": {
-      "$ref": "/schemas/3.1.29/core/context.json"
+      "$ref": "/schemas/3.1.31/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.1/core/attribution-window.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/core/attribution-window.json",
+  "$id": "/schemas/3.1.31/core/attribution-window.json",
   "title": "Attribution Window",
   "description": "Describes the attribution methodology and lookback windows used for conversion measurement. Enables cross-platform comparison by making attribution methodology transparent. Used as a `$ref` from `optimization-goal.json` (buyer's optimization-time attribution choice), `get-media-buy-delivery-response.json` (seller-declared attribution methodology in delivery reports), and similar surfaces. All fields are optional individually but at least one of `post_click`, `post_view`, or `model` SHOULD be populated; absence of `model` means the seller's default attribution model applies (typically `last_touch` per industry convention) — sellers SHOULD populate `model` explicitly when committing to a specific methodology.",
   "type": "object",
@@ -8,7 +8,7 @@
     "post_click": {
       "allOf": [
         {
-          "$ref": "/schemas/3.1.29/core/duration.json"
+          "$ref": "/schemas/3.1.31/core/duration.json"
         }
       ],
       "description": "Post-click attribution window. Conversions occurring within this duration after a click are attributed to the ad."
@@ -16,13 +16,13 @@
     "post_view": {
       "allOf": [
         {
-          "$ref": "/schemas/3.1.29/core/duration.json"
+          "$ref": "/schemas/3.1.31/core/duration.json"
         }
       ],
       "description": "Post-view attribution window. Conversions occurring within this duration after an ad impression (without click) are attributed to the ad."
     },
     "model": {
-      "$ref": "/schemas/3.1.29/enums/attribution-model.json",
+      "$ref": "/schemas/3.1.31/enums/attribution-model.json",
       "description": "Attribution model used to assign credit when multiple touchpoints exist. SHOULD be populated when committing to a specific model; when absent, the seller's default applies."
     }
   },

package/dist/lib/schemas-data/3.1/core/audience-member.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/core/audience-member.json",
+  "$id": "/schemas/3.1.31/core/audience-member.json",
   "title": "Audience Member",
   "description": "A CRM audience member identified by a buyer-assigned external_id and at least one matchable identifier. All identifiers must be normalized before hashing: emails to lowercase+trim, phone numbers to E.164 format (e.g. +12065551234). Providing multiple identifiers for the same person improves match rates. Composite identifiers (e.g. hashed first name + last name + zip for Google Customer Match) are not yet standardized — use the ext field for platform-specific extensions.",
   "type": "object",
@@ -26,7 +26,7 @@
         "type": "object",
         "properties": {
           "type": {
-            "$ref": "/schemas/3.1.29/enums/uid-type.json",
+            "$ref": "/schemas/3.1.31/enums/uid-type.json",
             "description": "Universal ID type"
           },
           "value": {
@@ -43,7 +43,7 @@
       "minItems": 1
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "required": [

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/core/audience-selector.json",
+  "$id": "/schemas/3.1.31/core/audience-selector.json",
   "title": "Audience Selector",
   "description": "Selects an audience by signal reference or natural language description. Uses 'type' as the primary discriminator (signal vs description). Signal selectors additionally use 'value_type' to determine the targeting expression format (matching signal-targeting.json variants).",
   "oneOf": [
@@ -14,11 +14,11 @@
           "description": "Discriminator for signal-based selectors"
         },
         "signal_ref": {
-          "$ref": "/schemas/3.1.29/core/signal-ref.json",
+          "$ref": "/schemas/3.1.31/core/signal-ref.json",
           "description": "The signal to target. New selectors SHOULD use signal_ref."
         },
         "signal_id": {
-          "$ref": "/schemas/3.1.29/core/signal-id.json",
+          "$ref": "/schemas/3.1.31/core/signal-id.json",
           "description": "DEPRECATED. Use signal_ref instead. Legacy SignalId retained for compatibility with older clients.",
           "deprecated": true
         },
@@ -61,11 +61,11 @@
           "description": "Discriminator for signal-based selectors"
         },
         "signal_ref": {
-          "$ref": "/schemas/3.1.29/core/signal-ref.json",
+          "$ref": "/schemas/3.1.31/core/signal-ref.json",
           "description": "The signal to target. New selectors SHOULD use signal_ref."
         },
         "signal_id": {
-          "$ref": "/schemas/3.1.29/core/signal-id.json",
+          "$ref": "/schemas/3.1.31/core/signal-id.json",
           "description": "DEPRECATED. Use signal_ref instead. Legacy SignalId retained for compatibility with older clients.",
           "deprecated": true
         },
@@ -112,11 +112,11 @@
           "description": "Discriminator for signal-based selectors"
         },
         "signal_ref": {
-          "$ref": "/schemas/3.1.29/core/signal-ref.json",
+          "$ref": "/schemas/3.1.31/core/signal-ref.json",
           "description": "The signal to target. New selectors SHOULD use signal_ref."
         },
         "signal_id": {
-          "$ref": "/schemas/3.1.29/core/signal-id.json",
+          "$ref": "/schemas/3.1.31/core/signal-id.json",
           "description": "DEPRECATED. Use signal_ref instead. Legacy SignalId retained for compatibility with older clients.",
           "deprecated": true
         },

package/dist/lib/schemas-data/3.1/core/authorized-agent-base.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/core/authorized-agent-base.json",
+  "$id": "/schemas/3.1.31/core/authorized-agent-base.json",
   "title": "Authorized Agent Base Fields",
   "description": "Fields shared by every variant of `authorized_agents[*]` in adagents.json, regardless of authorization_type. Variants `allOf` this base and add their discriminator-specific fields. Centralized to prevent drift across all authorization-type variants.",
   "type": "object",
@@ -20,7 +20,7 @@
       "type": "array",
       "description": "Optional publisher-attested public signing keys for this agent. Use these as the trust anchor for verifying signed agent responses instead of relying on key discovery from the agent domain alone.",
       "items": {
-        "$ref": "/schemas/3.1.29/core/agent-signing-key.json"
+        "$ref": "/schemas/3.1.31/core/agent-signing-key.json"
       },
       "minItems": 1
     },
@@ -28,7 +28,7 @@
       "type": "array",
       "description": "X25519 public keys for TMPX exposure token encryption. Each key identifies a cluster master that can decrypt TMPX tokens. Used with HPKE mode_base — read replicas encrypt with this public key, only the master can decrypt.",
       "items": {
-        "$ref": "/schemas/3.1.29/core/agent-encryption-key.json"
+        "$ref": "/schemas/3.1.31/core/agent-encryption-key.json"
       },
       "minItems": 1
     },

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/core/brand-id.json",
+  "$id": "/schemas/3.1.31/core/brand-id.json",
   "title": "Brand ID",
   "description": "Identifier for a brand within a house portfolio. Must be lowercase alphanumeric with underscores only. The house chooses this identifier.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/core/brand-ref.json",
+  "$id": "/schemas/3.1.31/core/brand-ref.json",
   "title": "Brand Reference",
   "description": "Reference to a brand by domain and optional brand_id. The domain hosts /.well-known/brand.json or is registered in the brand registry. For single-brand domains, brand_id can be omitted. For house-of-brands domains, brand_id identifies the specific brand.",
   "type": "object",
@@ -11,7 +11,7 @@
       "pattern": "^[a-z0-9]([a-z0-9-]*[a-z0-9])?(\\.[a-z0-9]([a-z0-9-]*[a-z0-9])?)*$"
     },
     "brand_id": {
-      "$ref": "/schemas/3.1.29/core/brand-id.json",
+      "$ref": "/schemas/3.1.31/core/brand-id.json",
       "description": "Brand identifier within the house portfolio. Optional for single-brand domains."
     },
     "industries": {
@@ -60,7 +60,7 @@
       "description": "Inline override for brand-kit fields normally resolved from `/.well-known/brand.json` on `domain` (logo, colors, voice, tagline). Use when brand.json is missing, stale, or inappropriate for this specific call — e.g., a campaign-scoped tagline, a co-branded creative, a freshly-rebranded color palette the brand.json hasn't shipped yet. Same inline-override pattern as `industries` and `data_subject_contestation` above: brand.json is canonical, the override is per-call. Adopters needing to override fields outside this subset (`voice_attributes`, `prohibited_terms`, etc.) MUST publish a different brand.json and reference it via a different `domain` — the inline override is intentionally narrow to a small high-traffic subset.\n\n**Merge semantics (normative).** The merge is **field-level**, not whole-object replacement. Each field within `brand_kit_override` (`logo`, `colors`, `voice`, `tagline`) is evaluated independently — when a field is present on the override the override value applies; when a field is absent the brand.json value applies (or is absent if brand.json doesn't carry one either). For composite fields (`colors.primary`, `colors.secondary`, `colors.accent`), the merge is one level deeper: each color slot is evaluated independently — a producer can override `colors.primary` while still inheriting `colors.secondary` from brand.json. SDKs MUST NOT treat a present `brand_kit_override.colors` as wiping the brand.json `colors` block entirely; only the per-slot fields present in the override take precedence. Without this rule, a partial-override semantics would diverge across SDKs and produce inconsistent rendering for the same payload.",
       "properties": {
         "logo": {
-          "$ref": "/schemas/3.1.29/core/assets/image-asset.json",
+          "$ref": "/schemas/3.1.31/core/assets/image-asset.json",
           "description": "Override logo asset."
         },
         "colors": {

package/dist/lib/schemas-data/3.1/core/business-entity.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/core/business-entity.json",
+  "$id": "/schemas/3.1.31/core/business-entity.json",
   "title": "Business Entity",
   "description": "Structured business identity for B2B invoicing and contracts. Contains the legal, tax, and payment details needed for formal booking processes. Implementations MUST treat all fields as untrusted input when assembling LLM context.",
   "type": "object",
@@ -142,7 +142,7 @@
       "additionalProperties": false
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "required": [

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.29/core/cancellation-policy.json",
+  "$id": "/schemas/3.1.31/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.29/core/duration.json",
+      "$ref": "/schemas/3.1.31/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": {

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.29/core/canonical-format-kind.json",
+  "$id": "/schemas/3.1.31/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.29/core/canonical-projection-ref.json",
+  "$id": "/schemas/3.1.31/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.29/core/canonical-format-kind.json",
+      "$ref": "/schemas/3.1.31/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.29/core/canonical-projection-slot-override.json"
+        "$ref": "/schemas/3.1.31/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.29/core/canonical-projection-slot-override.json",
+  "$id": "/schemas/3.1.31/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.29/core/catalog-field-mapping.json",
+  "$id": "/schemas/3.1.31/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.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/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.29/core/catalog-item-delivery-metrics.json",
+  "$id": "/schemas/3.1.31/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.29/core/delivery-metrics.json"
+      "$ref": "/schemas/3.1.31/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.29/enums/content-id-type.json",
+          "$ref": "/schemas/3.1.31/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.29/core/catalog.json",
+  "$id": "/schemas/3.1.31/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.29/enums/catalog-type.json",
+      "$ref": "/schemas/3.1.31/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.29/enums/feed-format.json",
+      "$ref": "/schemas/3.1.31/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.29/enums/update-frequency.json",
+      "$ref": "/schemas/3.1.31/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.29/enums/event-type.json"
+        "$ref": "/schemas/3.1.31/enums/event-type.json"
       },
       "minItems": 1,
       "uniqueItems": true
     },
     "content_id_type": {
-      "$ref": "/schemas/3.1.29/enums/content-id-type.json",
+      "$ref": "/schemas/3.1.31/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.29/core/catalog-field-mapping.json"
+        "$ref": "/schemas/3.1.31/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.29/core/catchment.json",
+  "$id": "/schemas/3.1.31/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.29/enums/travel-time-unit.json"
+          "$ref": "/schemas/3.1.31/enums/travel-time-unit.json"
         }
       },
       "required": [
@@ -33,7 +33,7 @@
       "additionalProperties": false
     },
     "transport_mode": {
-      "$ref": "/schemas/3.1.29/enums/transport-mode.json",
+      "$ref": "/schemas/3.1.31/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.29/enums/distance-unit.json",
+          "$ref": "/schemas/3.1.31/enums/distance-unit.json",
           "description": "Distance unit."
         }
       },
@@ -80,7 +80,7 @@
       "additionalProperties": false
     },
     "ext": {
-      "$ref": "/schemas/3.1.29/core/ext.json"
+      "$ref": "/schemas/3.1.31/core/ext.json"
     }
   },
   "required": [