@adcp/sdk 9.6.0 → 9.6.2

package/dist/lib/schemas-data/3.1/core/truncation-sentinel.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/truncation-sentinel.json",
+  "$id": "/schemas/3.1.1/core/truncation-sentinel.json",
   "title": "Truncation Sentinel",
   "description": "Universal AdCP sentinel value that replaces a field's content when the seller has truncated it due to a size cap. Used wherever an AdCP field may carry large user-supplied content (e.g., webhook request/response payloads under a future `include_webhook_payloads` extension, large structured-event blobs, captured response bodies) and the seller has elected to surface a bounded preview instead of the full value. The leading-underscore key `_truncation` is a deliberate control marker — its presence on an object is the discriminator that distinguishes a truncation sentinel from the natural value the field would otherwise carry. Schemas that may carry truncated content reference this shape via `oneOf` against the natural value type — e.g., `{ \"oneOf\": [ { \"$ref\": \"#/definitions/NaturalValue\" }, { \"$ref\": \"/schemas/core/truncation-sentinel.json\" } ] }`. Receivers detect a sentinel by testing `'_truncation' in value`. See snapshot-and-log.mdx § Webhook activity log pattern for the cross-resource context this sentinel was introduced under.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/user-match.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/user-match.json",
+  "$id": "/schemas/3.1.1/core/user-match.json",
   "title": "User Match",
   "description": "User identifiers for attribution matching. Supports universal IDs, hashed identifiers, click IDs, and probabilistic matching.",
   "type": "object",
@@ -12,7 +12,7 @@
         "type": "object",
         "properties": {
           "type": {
-            "$ref": "/schemas/3.1.0/enums/uid-type.json",
+            "$ref": "/schemas/3.1.1/enums/uid-type.json",
             "description": "Universal ID type"
           },
           "value": {
@@ -55,7 +55,7 @@
       "description": "Client user agent string for probabilistic matching"
     },
     "ext": {
-      "$ref": "/schemas/3.1.0/core/ext.json"
+      "$ref": "/schemas/3.1.1/core/ext.json"
     }
   },
   "anyOf": [

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/vehicle-item.json",
+  "$id": "/schemas/3.1.1/core/vehicle-item.json",
   "title": "Vehicle Item",
   "description": "A vehicle listing within a vehicle-type catalog. Carries the make/model, pricing, and specification data that platforms use for automotive inventory ads. Maps to Meta Automotive Inventory Ads, Microsoft Auto Inventory feeds, Google vehicle ads, and similar formats.",
   "type": "object",
@@ -27,7 +27,7 @@
       "description": "Model year."
     },
     "price": {
-      "$ref": "/schemas/3.1.0/core/price.json",
+      "$ref": "/schemas/3.1.1/core/price.json",
       "description": "Vehicle price."
     },
     "condition": {
@@ -158,12 +158,12 @@
       "type": "array",
       "description": "Typed creative asset pools for this vehicle. Uses the same OfferingAssetGroup structure as offering-type catalogs. Standard group IDs: 'images_landscape' (exterior 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.0/core/offering-asset-group.json"
+        "$ref": "/schemas/3.1.1/core/offering-asset-group.json"
       },
       "minItems": 1
     },
     "ext": {
-      "$ref": "/schemas/3.1.0/core/ext.json"
+      "$ref": "/schemas/3.1.1/core/ext.json"
     }
   },
   "required": [

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/vendor-metric-id.json",
+  "$id": "/schemas/3.1.1/core/vendor-metric-id.json",
   "title": "Vendor Metric ID",
   "description": "Identifier for a vendor-defined metric within the vendor's vocabulary. Stable lookup key; the vendor publishes the canonical list (with category, methodology, and standard alignment) in `brand.json` `agents[type='measurement']`. Lowercase with underscores so a future enum promotion into `available-metric.json` is a literal string lift. Identifier is namespaced by the vendor — the same `metric_id` may mean different things in different vendors' vocabularies.",
   "type": "string",

package/dist/lib/schemas-data/3.1/core/vendor-metric-optimization-supported-metric.json

@@ -1,16 +1,16 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/vendor-metric-optimization-supported-metric.json",
+  "$id": "/schemas/3.1.1/core/vendor-metric-optimization-supported-metric.json",
   "title": "Vendor Metric Optimization Supported Metric",
   "description": "One vendor-defined metric that a product can optimize toward. Identified by the tuple `(vendor, metric_id)` plus the supported target kinds for optimization goals.",
   "type": "object",
   "properties": {
     "vendor": {
-      "$ref": "/schemas/3.1.0/core/brand-ref.json",
+      "$ref": "/schemas/3.1.1/core/brand-ref.json",
       "description": "Vendor that defines and computes this metric. The vendor's `brand.json` is the discovery anchor for the measurement agent (entry with `type: 'measurement'` in the `agents[]` array); the metric's definition, methodology, and unit live at that agent's `get_adcp_capabilities.measurement.metrics[]` and are not duplicated inline here. Same shape as the `vendor` field on `reporting_capabilities.vendor_metrics` for symmetry across optimization and reporting capability declarations."
     },
     "metric_id": {
-      "$ref": "/schemas/3.1.0/core/vendor-metric-id.json",
+      "$ref": "/schemas/3.1.1/core/vendor-metric-id.json",
       "description": "Identifier for the metric within the vendor's vocabulary (e.g., `attention_score`, `attention_seconds`, `gco2e_per_impression`, `awareness_lift`). MUST be present in the vendor's published `measurement.metrics[]` catalog."
     },
     "supported_targets": {

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/vendor-metric-optimization.json",
+  "$id": "/schemas/3.1.1/core/vendor-metric-optimization.json",
   "title": "Vendor Metric Optimization",
   "description": "Vendor-attested metric optimization capabilities for a product. Presence indicates the product supports `optimization_goals` with `kind: 'vendor_metric'` — i.e., the seller's bidding stack can steer delivery toward a specific vendor's metric. This is the optimization-side counterpart to `reporting_capabilities.vendor_metrics`, which declares which vendor metrics the product can *report*. The two are related but distinct: a product may be able to commit to reporting a vendor metric (the vendor's SDK fires on the inventory) without being able to optimize against it (the optimization signal isn't actionable in the seller's bidding stack). Each `supported_metrics` entry is the tuple `(vendor, metric_id)` plus the target kinds the seller supports for that pair. Buyers MUST set `vendor_metric` goals only against entries declared here; sellers MUST reject goals whose `(vendor, metric_id)` is not in `supported_metrics`, and MUST reject goals whose `target.kind` is not in the matching entry's `supported_targets`. Buyers SHOULD also verify the metric is in the vendor's published `measurement.metrics[]` catalog (the discovery-layer check — softened from MUST while measurement-vendor adoption of AdCP-conformant capability publication catches up; tightens to MUST at the next minor) and that the package's `committed_metrics[]` includes a matching `{ scope: 'vendor', vendor, metric_id }` entry (the reporting-coherence check — optimizing for a metric you don't commit to reporting is unverifiable). The `maximize_value` target kind from the `event` goal kind is intentionally excluded — it's monetary-only; a buyer wanting to maximize a vendor metric uses the target-less form of the `vendor_metric` goal. Precondition checks are seller-runtime, not JSON-Schema-enforceable: the schema's `required` only validates structural presence of `vendor` and `metric_id`.",
   "type": "object",
@@ -10,7 +10,7 @@
       "description": "Vendor-defined metrics this product can steer delivery toward. Each entry pairs a vendor identity (BrandRef anchored on the vendor's `brand.json` `agents[type='measurement']`) with a `metric_id` from that vendor's published `measurement.metrics[]` catalog, plus the target kinds the seller supports for the pair. Semantic uniqueness key is `(vendor.domain, vendor.brand_id, metric_id)`; sellers MUST de-duplicate before publication. JSON Schema `uniqueItems` blocks exact-object duplicates; semantic deduplication on the BrandRef-domain key is a seller obligation.",
       "uniqueItems": true,
       "items": {
-        "$ref": "/schemas/3.1.0/core/vendor-metric-optimization-supported-metric.json"
+        "$ref": "/schemas/3.1.1/core/vendor-metric-optimization-supported-metric.json"
       }
     }
   },

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

@@ -1,16 +1,16 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/vendor-metric-value.json",
+  "$id": "/schemas/3.1.1/core/vendor-metric-value.json",
   "title": "Vendor Metric Value",
   "description": "A reported value for a vendor-defined metric, emitted in `delivery-metrics.json` `vendor_metric_values` parallel to standard scalars. Identifies the vendor (BrandRef), the metric name within that vendor's vocabulary, the value, and the coverage denominator (`measurable_impressions`) — vendor measurement is rarely 100% coverage. The `breakdown` slot accommodates vendors that emit structured payloads beyond a single scalar (panel demographic breakouts, co-view ratios, incremental decompositions). To add fields beyond what this schema defines, vendors place them inside `breakdown` rather than alongside the standard envelope.",
   "type": "object",
   "properties": {
     "vendor": {
-      "$ref": "/schemas/3.1.0/core/brand-ref.json",
+      "$ref": "/schemas/3.1.1/core/brand-ref.json",
       "description": "Vendor that produced this value. Matches a `vendor_metrics[].vendor` declaration on the product."
     },
     "metric_id": {
-      "$ref": "/schemas/3.1.0/core/vendor-metric-id.json",
+      "$ref": "/schemas/3.1.1/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": {

package/dist/lib/schemas-data/3.1/core/vendor-pricing-option.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/vendor-pricing-option.json",
+  "$id": "/schemas/3.1.1/core/vendor-pricing-option.json",
   "title": "Vendor Pricing Option",
   "description": "A pricing option offered by a vendor agent (signals, creative, governance). Combines pricing_option_id with the pricing model fields. Pass pricing_option_id in report_usage for billing verification. All vendor discovery responses return pricing_options as an array — vendors may offer multiple options (volume tiers, context-specific rates, different models per product line).",
   "allOf": [
@@ -16,7 +16,7 @@
           "type": "array",
           "description": "Creative transformers only: scopes this pricing option to specific output formats, so one transformer can price different outputs differently (e.g. a multi-publisher template charging per publisher format). When present, the option applies only to leaves whose format matches one of these; an unscoped option (this field absent) is the default for any output. A build targeting an output that matches no scoped option AND has no unscoped default is rejected with UNPRICEABLE_OUTPUT — never billed at a guessed rate (no silent fallback). Inert for non-creative vendors (signals/governance), which omit it.",
           "items": {
-            "$ref": "/schemas/3.1.0/core/format-id.json"
+            "$ref": "/schemas/3.1.1/core/format-id.json"
           },
           "minItems": 1
         }
@@ -26,7 +26,7 @@
       ]
     },
     {
-      "$ref": "/schemas/3.1.0/core/signal-pricing.json"
+      "$ref": "/schemas/3.1.1/core/signal-pricing.json"
     }
   ]
 }

package/dist/lib/schemas-data/3.1/core/version-envelope.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/version-envelope.json",
+  "$id": "/schemas/3.1.1/core/version-envelope.json",
   "title": "AdCP Version Envelope",
   "description": "Release-precision AdCP protocol version negotiation fields. Composed via `allOf` into every AdCP request and response schema so the version semantics live in exactly one place. Distinct from `core/protocol-envelope.json`, which wraps responses at the transport layer (context_id / task_id / status / payload). This envelope is part of the payload itself.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/webhook-activity-record.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/webhook-activity-record.json",
+  "$id": "/schemas/3.1.1/core/webhook-activity-record.json",
   "title": "Webhook Activity Record",
   "description": "Single webhook delivery attempt surfaced to a calling principal as a buyer-side debug aid. Represents one HTTP attempt of a logical webhook fire from the seller to the buyer's registered endpoint — retries of the same logical fire share `idempotency_key` and differ by `attempt`. This is the canonical record shape for any AdCP resource that exposes a `webhook_activity[]` log on its read API; see snapshot-and-log.mdx § Webhook activity log pattern for the full normative contract (scoping, retention, three-state presence, request-field conventions).",
   "type": "object",
@@ -27,7 +27,7 @@
       "description": "ISO 8601 timestamp when the seller observed the response (or terminal timeout / connection error — for `timeout` and `connection_error` outcomes, `completed_at` is set to the moment the seller declared the attempt terminal). Explicitly `null` when the attempt is still in flight or queued for retry (status `pending`); MUST be set as `null` rather than omitted so callers can distinguish 'still in flight' from 'field missing'."
     },
     "notification_type": {
-      "$ref": "/schemas/3.1.0/enums/notification-type.json",
+      "$ref": "/schemas/3.1.1/enums/notification-type.json",
       "description": "Notification type carried by this fire, verbatim from the webhook payload. Includes both delivery-report types (`scheduled`, `final`, `delayed`, `adjusted`) and health-notification types (`impairment`). All share the same persistent-channel webhook contract and the same buyer-side debug need."
     },
     "sequence_number": {
@@ -87,7 +87,7 @@
       "maxLength": 500
     },
     "ext": {
-      "$ref": "/schemas/3.1.0/core/ext.json",
+      "$ref": "/schemas/3.1.1/core/ext.json",
       "description": "Resource-specific extension slot. Adopters MAY surface a resource-specific cross-reference (e.g., `creative_id` on a creative-lifecycle record, `media_buy_id` on a record nested inside an account-level read) under `ext` rather than adding top-level fields — the canonical record shape stays uniform across resources and the `ext` envelope absorbs per-resource needs. Top-level extensions are not permitted (`additionalProperties: false`)."
     }
   },

package/dist/lib/schemas-data/3.1/core/webhook-challenge-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/webhook-challenge-response.json",
+  "$id": "/schemas/3.1.1/core/webhook-challenge-response.json",
   "title": "Webhook Challenge Response",
   "description": "Response body a receiver returns to prove control of an account-level notification_configs[] URL. The receiver must echo the challenge value from webhook-challenge.json in exactly one of `challenge` or `token`.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/webhook-challenge.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/webhook-challenge.json",
+  "$id": "/schemas/3.1.1/core/webhook-challenge.json",
   "title": "Webhook Challenge",
   "description": "Proof-of-control challenge payload sent by a seller to an account-level notification_configs[] URL before activating a new or changed active subscriber. The seller sends this payload as an HTTPS POST after URL normalization and SSRF validation, and before treating the subscriber as active. The challenge POST itself MUST be signed with the seller's RFC 9421 webhook profile key even when the candidate config selects legacy delivery auth; new signers use `adcp_use: \"request-signing\"` and deprecated `webhook-signing` keys remain accepted during the compatibility window. `delivery_auth` describes the future webhook delivery mode, not the challenge's own signing mode.",
   "type": "object",
@@ -105,7 +105,7 @@
       "type": "array",
       "description": "Normalized notification types requested by the subscriber at the time of the challenge. Part of the endpoint proof scope; changing event_types[] requires a fresh challenge before the new set can become active.",
       "items": {
-        "$ref": "/schemas/3.1.0/enums/notification-type.json"
+        "$ref": "/schemas/3.1.1/enums/notification-type.json"
       },
       "minItems": 1,
       "uniqueItems": true

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/wholesale-feed-event.json",
+  "$id": "/schemas/3.1.1/core/wholesale-feed-event.json",
   "title": "Wholesale Feed Event",
   "description": "A single change event emitted by an AdCP agent's wholesale product feed or wholesale signals feed and delivered inside wholesale-feed-webhook payloads. Events are denormalized — the payload carries the post-change state of a buyable product or signal so consumers can update local state without a follow-up get_products / get_signals call. This is distinct from buyer-provided feeds managed by sync_catalogs. The discriminator is `event_type`; each branch defines the payload shape. See specs/wholesale-feed-webhooks.md for webhook delivery and reconciliation semantics.",
   "type": "object",
@@ -81,7 +81,7 @@
               "type": "string"
             },
             "product": {
-              "$ref": "/schemas/3.1.0/core/product.json",
+              "$ref": "/schemas/3.1.1/core/product.json",
               "description": "Full post-change Product object."
             },
             "applies_to": {
@@ -117,7 +117,7 @@
               "type": "string"
             },
             "product": {
-              "$ref": "/schemas/3.1.0/core/product.json",
+              "$ref": "/schemas/3.1.1/core/product.json",
               "description": "Full post-change Product object. Consumers replace the prior product mirror entry with this object."
             },
             "changed_fields": {
@@ -162,7 +162,7 @@
               "type": "array",
               "minItems": 1,
               "items": {
-                "$ref": "/schemas/3.1.0/core/pricing-option.json"
+                "$ref": "/schemas/3.1.1/core/pricing-option.json"
               },
               "description": "Full post-change pricing_options array. NOT a delta — consumers replace the prior options with this list."
             },
@@ -248,7 +248,7 @@
               "type": "string"
             },
             "signal_ref": {
-              "$ref": "/schemas/3.1.0/core/signal-ref.json"
+              "$ref": "/schemas/3.1.1/core/signal-ref.json"
             },
             "applies_to": {
               "$ref": "#/$defs/appliesTo",
@@ -287,7 +287,7 @@
               "type": "string"
             },
             "signal_ref": {
-              "$ref": "/schemas/3.1.0/core/signal-ref.json"
+              "$ref": "/schemas/3.1.1/core/signal-ref.json"
             },
             "changed_fields": {
               "type": "array",
@@ -332,13 +332,13 @@
               "type": "string"
             },
             "signal_ref": {
-              "$ref": "/schemas/3.1.0/core/signal-ref.json"
+              "$ref": "/schemas/3.1.1/core/signal-ref.json"
             },
             "pricing_options": {
               "type": "array",
               "minItems": 1,
               "items": {
-                "$ref": "/schemas/3.1.0/core/vendor-pricing-option.json"
+                "$ref": "/schemas/3.1.1/core/vendor-pricing-option.json"
               },
               "description": "Full post-change pricing_options array. NOT a delta."
             },
@@ -389,7 +389,7 @@
               "type": "string"
             },
             "signal_ref": {
-              "$ref": "/schemas/3.1.0/core/signal-ref.json"
+              "$ref": "/schemas/3.1.1/core/signal-ref.json"
             },
             "removal_reason": {
               "$ref": "#/$defs/removalReason"
@@ -519,16 +519,16 @@
       "description": "One signal entry using the same wire shape as an item in get_signals.signals[].",
       "allOf": [
         {
-          "$ref": "/schemas/3.1.0/core/signal-listing.json"
+          "$ref": "/schemas/3.1.1/core/signal-listing.json"
         }
       ],
       "properties": {
         "signal_ref": {
-          "$ref": "/schemas/3.1.0/core/signal-ref.json",
+          "$ref": "/schemas/3.1.1/core/signal-ref.json",
           "description": "Canonical signal reference for this wholesale signal. New events SHOULD use signal_ref."
         },
         "signal_id": {
-          "$ref": "/schemas/3.1.0/core/signal-id.json",
+          "$ref": "/schemas/3.1.1/core/signal-id.json",
           "description": "DEPRECATED. Use signal_ref instead. Legacy SignalId retained for compatibility with older clients.",
           "deprecated": true
         },
@@ -548,7 +548,7 @@
           "minLength": 1
         },
         "value_type": {
-          "$ref": "/schemas/3.1.0/enums/signal-value-type.json"
+          "$ref": "/schemas/3.1.1/enums/signal-value-type.json"
         },
         "categories": {
           "type": "array",
@@ -574,7 +574,7 @@
           "additionalProperties": false
         },
         "signal_type": {
-          "$ref": "/schemas/3.1.0/enums/signal-catalog-type.json"
+          "$ref": "/schemas/3.1.1/enums/signal-catalog-type.json"
         },
         "data_provider": {
           "type": "string",
@@ -588,20 +588,20 @@
           "deprecated": true
         },
         "coverage_forecast": {
-          "$ref": "/schemas/3.1.0/core/signal-coverage-forecast.json",
+          "$ref": "/schemas/3.1.1/core/signal-coverage-forecast.json",
           "description": "Optional forecast-shaped signal availability guidance using the same wire shape as get_signals.signals[].coverage_forecast. When present, this is authoritative for signal-level discovery coverage."
         },
         "deployments": {
           "type": "array",
           "items": {
-            "$ref": "/schemas/3.1.0/core/deployment.json"
+            "$ref": "/schemas/3.1.1/core/deployment.json"
           },
           "minItems": 1
         },
         "pricing_options": {
           "type": "array",
           "items": {
-            "$ref": "/schemas/3.1.0/core/vendor-pricing-option.json"
+            "$ref": "/schemas/3.1.1/core/vendor-pricing-option.json"
           },
           "minItems": 1
         }

package/dist/lib/schemas-data/3.1/core/wholesale-feed-webhook.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/wholesale-feed-webhook.json",
+  "$id": "/schemas/3.1.1/core/wholesale-feed-webhook.json",
   "title": "Wholesale Feed Webhook",
   "description": "Account-level webhook payload fired when a seller's wholesale product feed or wholesale signals feed changes. Registered through sync_accounts.accounts[].notification_configs[] using product.* / signal.* / wholesale_feed.bulk_change event_types. The payload carries the actual change event so receivers can update a local mirror without immediately re-reading the full feed. get_products / get_signals with if_wholesale_feed_version remain the repair and reconciliation path after missed, stale, or distrusted pushes. Capability consistency: product.* webhooks require wholesale get_products support; signal.* webhooks require wholesale get_signals support; wholesale_feed.bulk_change must name only a feed family backed by a declared wholesale repair path.",
   "type": "object",
@@ -66,11 +66,11 @@
       "description": "Cache layer affected by this change. MUST equal event.payload.applies_to.scope. Mirrors the cache_scope returned by get_products / get_signals for the affected wholesale feed."
     },
     "event": {
-      "$ref": "/schemas/3.1.0/core/wholesale-feed-event.json",
+      "$ref": "/schemas/3.1.1/core/wholesale-feed-event.json",
       "description": "The actual product, signal, or bulk-change event. Consumers MAY apply this payload to their local mirror. Before any binding action, or when ordering/gap checks fail, consumers MUST reconcile through get_products / get_signals."
     },
     "ext": {
-      "$ref": "/schemas/3.1.0/core/ext.json"
+      "$ref": "/schemas/3.1.1/core/ext.json"
     }
   },
   "required": [

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/core/x-entity-types.json",
+  "$id": "/schemas/3.1.1/core/x-entity-types.json",
   "title": "x-entity types",
   "description": "Registry of valid `x-entity` annotation values. Each value tags a schema field whose contents carry identity of the named entity type. The context-entity lint reads this registry to reject unknown `x-entity` values and to catch mismatches between storyboard capture and consume sites. See docs/contributing/x-entity-annotation.md for authoring guidance. To add a value, PR this file and extend the authoring doc.",
   "type": "string",
@@ -78,6 +78,6 @@
     "si_session": "A sponsored-intelligence conversation session. `session_id` in sponsored-intelligence/* schemas.",
     "offering": "A brand-published offering (campaign, promotion, product set, service) promoted via traditional creatives or SI conversations. `offering_id` in core/offering.json, sponsored-intelligence/si-get-offering-*, and sponsored-intelligence/si-initiate-session-request. Also appears as a catalog item-type id when `core/catalog.json::type` is `offering`.",
     "vendor_metric": "A vendor-defined metric within a measurement vendor's vocabulary. `metric_id` in core/vendor-metric-id.json — used by reporting-capabilities.vendor_metrics declarations, delivery-metrics.vendor_metric_values emissions, and required_vendor_metrics filters. Identity is the tuple `(vendor.domain, vendor.brand_id, metric_id)` — the identifier is namespaced by the vendor's BrandRef, not globally unique. Vendor catalog (category, methodology, standard alignment) lives at the vendor's brand.json `agents[type='measurement']`.",
-    "identity_relying_party": "A verified-identity relying party an entity operates for attestation provenance in TMP Identity Match. `relying_party_id` in brand.json identity_relying_parties[] and tmp/identity-match-request.json attestation. Namespaced by the issuer (a vendor BrandRef, `core/brand-ref.json`) — identity is the tuple `(issuer.domain, issuer.brand_id, relying_party_id)`, mirroring vendor_metric's `(vendor.domain, vendor.brand_id, metric_id)`; the same string under a different issuer is a different relying party. The publishing owner (whose brand.json lists it) asserts ownership, and the receiver matches a forwarded attestation's `(issuer, relying_party_id)` against the claimed owner's published list; the issuer's own relying-party registry (e.g. World ID on-chain) is the authoritative root. One entity may operate many relying parties (scope=entity vs scope=property) — not 1:1 with an entity."
+    "identity_relying_party": "A verified-identity relying party an entity operates for attestation provenance in TMP Identity Match. `relying_party_id` in brand.json identity_relying_parties[] and trusted-match/identity-match-request.json attestation. Namespaced by the issuer (a vendor BrandRef, `core/brand-ref.json`) — identity is the tuple `(issuer.domain, issuer.brand_id, relying_party_id)`, mirroring vendor_metric's `(vendor.domain, vendor.brand_id, metric_id)`; the same string under a different issuer is a different relying party. The publishing owner (whose brand.json lists it) asserts ownership, and the receiver matches a forwarded attestation's `(issuer, relying_party_id)` against the claimed owner's published list; the issuer's own relying-party registry (e.g. World ID on-chain) is the authoritative root. One entity may operate many relying parties (scope=entity vs scope=property) — not 1:1 with an entity."
   }
 }

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

@@ -1,10 +1,10 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/creative/asset-types/index.json",
+  "$id": "/schemas/3.1.1/creative/asset-types/index.json",
   "title": "AdCP Asset Type Registry",
   "description": "Registry of asset types used in AdCP creative manifests. Each asset type defines the structure of actual content payloads (what you send), not requirements or constraints (which belong in format specifications).",
   "version": "1.0.0",
-  "lastUpdated": "2026-06-18",
+  "lastUpdated": "2026-06-30",
   "asset_types": {
     "image": {
       "description": "Static image asset (JPG, PNG, GIF, WebP, SVG)",
@@ -140,10 +140,37 @@
     "creative_manifests": "Creative manifests provide actual asset content, keyed by asset_id from the format. Each asset value carries an `asset_type` discriminator (one of the registry keys) so validators can select the matching asset schema and report errors against only that branch. The format specification also defines what asset_type each asset_id should have — payload and format should agree.",
     "example_flow": "Format says 'hero_image' must be type 'image' with width 1200, height 627. Manifest provides hero_image: {url: '...', width: 1200, height: 627}. The format spec tells us it's an image type."
   },
-  "published_version": "3.1.0",
-  "adcp_version": "3.1.0",
-  "baseUrl": "/schemas/3.1.0",
+  "published_version": "3.1.1",
+  "adcp_version": "3.1.1",
+  "baseUrl": "/schemas/3.1.1",
+  "protocol_layers": [
+    {
+      "id": "negotiation",
+      "title": "Negotiation layer",
+      "description": "Planning-time protocols for discovery, buying, creative, signals, accounts, governance, brand identity, and sponsored intelligence.",
+      "schema_groups": [
+        "media-buy",
+        "creative",
+        "signals",
+        "account",
+        "governance",
+        "brand",
+        "sponsored-intelligence"
+      ]
+    },
+    {
+      "id": "decisioning-serving",
+      "title": "Decisioning and serving layer",
+      "description": "Trusted Match Protocol schemas for serve-time Context Match and Identity Match decisions.",
+      "schema_groups": [
+        "trusted-match"
+      ]
+    }
+  ],
+  "stability": "stable",
+  "prerelease": false,
+  "deprecated": false,
   "versioning": {
-    "note": "AdCP uses build-time versioning. This directory contains schemas for AdCP 3.1.0. Full semantic versions are available at /schemas/{version}/ (e.g., /schemas/2.5.0/). Major version aliases point to the latest release: /schemas/v3/ → /schemas/3.1.0/."
+    "note": "AdCP uses build-time versioning. This directory contains schemas for AdCP 3.1.1. Full semantic versions are available at /schemas/{version}/ (e.g., /schemas/2.5.0/). Major version aliases point to the latest stable release in that major line; use /schemas/index.json or /schemas/latest.json for the canonical file-based pointer."
   }
 }

package/dist/lib/schemas-data/3.1/creative/audit-observation.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/creative/audit-observation.json",
+  "$id": "/schemas/3.1.1/creative/audit-observation.json",
   "title": "Creative Audit Observation",
   "description": "Non-blocking observation emitted by a creative governance agent. Audit observations surface claims that deserve human or downstream audit review but are not verifier refutations and are not rejection grounds by themselves.",
   "type": "object",
@@ -99,7 +99,7 @@
       "additionalProperties": false
     },
     "ext": {
-      "$ref": "/schemas/3.1.0/core/ext.json"
+      "$ref": "/schemas/3.1.1/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/creative/creative-feature-result.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/creative/creative-feature-result.json",
+  "$id": "/schemas/3.1.1/creative/creative-feature-result.json",
   "title": "Creative Feature Result",
   "description": "A single feature evaluation result for a creative. Uses the same value structure as property-feature-value (value, confidence, expires_at, etc.).",
   "type": "object",
@@ -58,7 +58,7 @@
       "$comment": "x-entity deliberately omitted — a PolicyEntry reference can resolve to either a governance_registry_policy or a governance_inline_policy depending on the authorizing entry's source. See issue #2685."
     },
     "ext": {
-      "$ref": "/schemas/3.1.0/core/ext.json"
+      "$ref": "/schemas/3.1.1/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/creative/creative-purged-webhook.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/creative/creative-purged-webhook.json",
+  "$id": "/schemas/3.1.1/creative/creative-purged-webhook.json",
   "title": "Creative Purged Webhook",
   "description": "Account-level push notification fired when a creative is destroyed from the seller's library — retention sweep, takedown enforcement, legal erasure. Fires per registered subscriber against each `notification_configs[]` entry whose `event_types` includes `creative.purged`. Distinct from `creative.status_changed` because purge is destruction, not a status transition — the creative is gone; status no longer applies. Soft purges retain a tombstone on `list_creatives` (with `include_purged: true`) for the seller's webhook retention window; hard purges do not — this webhook is the buyer's only signal. Sellers MUST NOT coalesce `creative.purged` fires (default no-coalescence window).",
   "type": "object",
@@ -60,7 +60,7 @@
       "description": "ISO 8601 timestamp when the seller observed the destruction. Distinct from `fired_at`."
     },
     "reason_code": {
-      "$ref": "/schemas/3.1.0/enums/creative-event-reason-code.json",
+      "$ref": "/schemas/3.1.1/enums/creative-event-reason-code.json",
       "description": "Categorical reason for the purge. Typical values: `retention_expired`, `legal_erasure`, `takedown_request`. Receivers MUST treat unknown reason codes as forward-compatible additions."
     },
     "reason_detail": {
@@ -77,7 +77,7 @@
       "description": "Who initiated the purge. `seller` — explicit decision (legal team, content policy, takedown handler). `system` — automated retention sweep, storage policy enforcement. `buyer` never appears on this event — buyer-initiated destruction (if and when supported) is acknowledged on the `sync_creatives` response path."
     },
     "ext": {
-      "$ref": "/schemas/3.1.0/core/ext.json"
+      "$ref": "/schemas/3.1.1/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/creative/creative-status-changed-webhook.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/creative/creative-status-changed-webhook.json",
+  "$id": "/schemas/3.1.1/creative/creative-status-changed-webhook.json",
   "title": "Creative Status Changed Webhook",
   "description": "Account-level push notification fired when a creative in the library transitions status by seller or system initiative. Fires per registered subscriber against each `notification_configs[]` entry whose `event_types` includes `creative.status_changed`. Buyer-initiated transitions (archive, unarchive, resubmit) do NOT fire — those are acknowledged on the `sync_creatives` response path. Receivers MUST verify signing per the registered scheme (RFC 9421 webhook profile by default; legacy Bearer / HMAC-SHA256 when `authentication` was supplied at registration) and dedupe by `idempotency_key`. See docs/protocol/snapshot-and-log.mdx for the snapshot/log duality rules — the current status is always authoritative on `list_creatives`.",
   "type": "object",
@@ -61,7 +61,7 @@
           "description": "Prior status — restricted to the states from which a seller/system-initiated transition can fire. For initial review outcomes the prior status is `pending_review`; for processing outcomes it is `processing`; for seller re-review, post-approval revocation, recoverable suspension, and seller-initiated archive it is `approved`; for recovery from a dependency/authorization outage or terminal escalation after a suspension it is `suspended`."
         },
         "to": {
-          "$ref": "/schemas/3.1.0/enums/creative-status.json",
+          "$ref": "/schemas/3.1.1/enums/creative-status.json",
           "description": "New status."
         },
         "observed_at": {
@@ -178,7 +178,7 @@
       ]
     },
     "reason_code": {
-      "$ref": "/schemas/3.1.0/enums/creative-event-reason-code.json",
+      "$ref": "/schemas/3.1.1/enums/creative-event-reason-code.json",
       "description": "Categorical reason for the transition. Per-transition valid subsets are constrained by impairment.coherence-style narrative rules — see docs/creative/creative-lifecycle-webhooks.mdx. Receivers MUST treat unknown reason codes as forward-compatible additions and not reject the fire."
     },
     "reason_detail": {
@@ -195,7 +195,7 @@
       "description": "Who initiated the transition. `seller` — explicit decision by the seller (human reviewer, policy operator, takedown handler). `system` — automated seller-side process (processing pipeline, retention sweep, inactivity scan). `buyer` never appears on this event — buyer-initiated transitions are acknowledged on the `sync_creatives` response path and MUST NOT fire `creative.status_changed`."
     },
     "ext": {
-      "$ref": "/schemas/3.1.0/core/ext.json"
+      "$ref": "/schemas/3.1.1/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/creative/get-creative-delivery-request.json

@@ -1,17 +1,17 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/creative/get-creative-delivery-request.json",
+  "$id": "/schemas/3.1.1/creative/get-creative-delivery-request.json",
   "title": "Get Creative Delivery Request",
   "description": "Request parameters for retrieving creative delivery data including variant-level metrics from a creative agent. At least one scoping filter (media_buy_ids or creative_ids) is required.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.0/core/version-envelope.json"
+      "$ref": "/schemas/3.1.1/core/version-envelope.json"
     }
   ],
   "properties": {
     "account": {
-      "$ref": "/schemas/3.1.0/core/account-ref.json",
+      "$ref": "/schemas/3.1.1/core/account-ref.json",
       "description": "Account for routing and scoping. Limits results to creatives within this account."
     },
     "media_buy_ids": {
@@ -48,14 +48,14 @@
       "minimum": 1
     },
     "pagination": {
-      "$ref": "/schemas/3.1.0/core/pagination-request.json",
+      "$ref": "/schemas/3.1.1/core/pagination-request.json",
       "description": "Pagination parameters for the creatives array in the response. Uses cursor-based pagination consistent with other list operations."
     },
     "context": {
-      "$ref": "/schemas/3.1.0/core/context.json"
+      "$ref": "/schemas/3.1.1/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.0/core/ext.json"
+      "$ref": "/schemas/3.1.1/core/ext.json"
     }
   },
   "anyOf": [