@adcp/sdk 15.9.6 → 15.9.8

package/dist/lib/schemas-data/3.2/core/proposal.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/proposal.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/proposal.json",
   "title": "Proposal",
   "description": "A proposed media plan with fixed or seller-optimized budget allocation across products. Represents the publisher's strategic recommendation for how to structure a campaign based on the brief. Proposals are actionable: committed proposals can be executed directly via create_media_buy by providing the proposal_id; draft proposals must first be finalized via get_products refine action 'finalize'.",
   "type": "object",
@@ -24,28 +24,28 @@
       "type": "array",
       "description": "Products and budget constraints in this plan. Fixed proposals require allocation_percentage on every entry and percentages MUST sum to 100. Seller-optimized proposals forbid exact allocation_percentage and may instead supply min_spend_target_percentage and max_spend_percentage, each only when the seller advertises the matching package-control capability (seller_optimized_min_spend_targets, seller_optimized_package_budgets). Publishers are responsible for validating cross-entry sums; buyers SHOULD validate them before execution.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/product-allocation.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/product-allocation.json"
       },
       "minItems": 1
     },
     "budget_allocation": {
       "allOf": [
         {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/budget-allocation.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/budget-allocation.json"
         }
       ],
       "description": "How the executed total budget is allocated across proposal products. Omit for legacy fixed proposals."
     },
     "pacing": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/pacing.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/pacing.json",
       "description": "Recommended aggregate pacing for the executed media-buy budget. On a committed proposal this is part of the firm delivery terms."
     },
     "frequency_cap": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/media-buy-frequency-cap.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/media-buy-frequency-cap.json",
       "description": "Aggregate cap bound into this legacy proposal. It is authoritative when the proposal is executed and uses one counter across its packages."
     },
     "proposal_status": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/proposal-status.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/proposal-status.json",
       "description": "Lifecycle status of this proposal and the per-proposal source of truth for whether finalization is required before create_media_buy. When absent, the proposal is ready to buy (backward compatible). 'draft' means indicative pricing — finalize via refine before purchasing. 'committed' means firm pricing with inventory reserved until expires_at and executable via create_media_buy."
     },
     "expires_at": {
@@ -54,7 +54,7 @@
       "description": "When this proposal expires and can no longer be executed. For draft proposals, indicates when indicative pricing becomes stale. For committed proposals, indicates when the inventory hold lapses — the buyer must call create_media_buy before this time."
     },
     "insertion_order": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/insertion-order.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/insertion-order.json",
       "description": "Formal insertion order attached to a committed proposal. Present when the seller requires a signed agreement before the media buy can proceed. The buyer references the io_id in io_acceptance on create_media_buy."
     },
     "total_budget_guidance": {
@@ -89,11 +89,11 @@
       "maxLength": 2000
     },
     "forecast": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/delivery-forecast.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/delivery-forecast.json",
       "description": "Aggregate forecasted delivery metrics for the entire proposal. When both proposal-level and allocation-level forecasts are present, the proposal-level forecast is authoritative for total delivery estimation."
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/core/protocol-envelope.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/protocol-envelope.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/protocol-envelope.json",
   "title": "Protocol Envelope",
   "description": "Canonical envelope field-set for AdCP task responses, normalized across transports. Defines the protocol-layer fields (status, context_id, context, task_id, timestamp, replayed, adcp_error, push_notification_config, governance_context) and the conceptual `payload` grouping for task-specific response data. The serialization rules — whether envelope fields appear as siblings of payload fields, as a nested `payload` object, or via transport-native containers — are transport-specific and normative per transport (see Transport serialization below). The `status` field is REQUIRED on every task response envelope, including synchronous metadata responses (e.g., `get_adcp_capabilities`) where the value is `completed`. Agents shipping responses without a top-level `status` are non-conformant regardless of whether the task body schema would otherwise validate.",
   "type": "object",
@@ -10,7 +10,7 @@
       "description": "Transport-managed conversation identifier. On A2A, this maps to the native Message/Task `contextId` used to associate messages with a conversation; it is not carried inside the AdCP DataPart. On MCP, a request-body `context_id`, where admitted by the selected request schema, is a compatibility-only field: servers MUST ignore it, callers MUST NOT rely on it for continuity, and it MUST NOT select session state, identity, account, authorization, task continuation, or idempotency scope. MCP continuity, if provided, comes from the transport session. Distinct from `context` (per-request opaque echo, see below) and from `task_id` (AdCP operation tracking)."
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/context.json",
       "description": "Per-request opaque caller-supplied correlation object echoed unchanged in the response. Used for buyer-side tracking (UI session IDs, trace IDs, custom metadata) that the agent MUST preserve byte-for-byte without parsing. Distinct from `context_id` (transport-managed A2A conversation correlation or MCP compatibility metadata) — `context` is caller-owned echo and never selects transport state. Both MAY appear on the same response.\n\n**Relationship to per-task body-level `context` declarations.** Many task request/response schemas (147 as of 3.1) already declare a body-level `context` field that `$ref`s `/schemas/core/context.json` at the body root. Under the flat-on-the-wire MCP serialization (see `notes` below), envelope-level `context` and body-level `context` occupy the same key on the response root — they are NOT separate fields, they MUST share the same value, and they MUST both `$ref` `core/context.json`. The envelope declaration is **authoritative** for the schema definition; per-task body declarations are mirrors retained for tooling reasons (SDK codegen completeness, per-task validation against the response schema in isolation). Future versions MAY drop body-level `context` declarations from per-task schemas; conformance does not require either declaration to be present, only that the wire value `$ref`s `core/context.json`."
     },
     "task_id": {
@@ -19,7 +19,7 @@
       "x-entity": "task"
     },
     "status": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/task-status.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/task-status.json",
       "description": "Current AdCP task state or structured outcome. Indicates whether the task completed, is in progress, was submitted for async processing, failed, requires user input, or returned a typed business rejection. REQUIRED on every task response envelope. Synchronous tasks (including read-only metadata calls like `get_adcp_capabilities`) normally emit `status: \"completed\"`; a task-specific rejection arm emits `status: \"rejected\"` without turning the transport into a failure. Async tasks emit `submitted`, `working`, `input-required`, etc. per their lifecycle. Agents MUST NOT emit the legacy task_status or response_status fields alongside this field — the status field is the single authoritative AdCP response state."
     },
     "message": {
@@ -37,11 +37,11 @@
       "default": false
     },
     "adcp_error": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/error.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/error.json",
       "description": "Transport-envelope error signal for fatal task failures. Per the two-layer model in `error-handling.mdx#envelope-vs-payload-errors-the-two-layer-model`, a fatal task failure SHOULD populate both this envelope-level field AND the payload's `errors[]` array — the envelope carries a typed, extractable error so MCP/A2A clients can dispatch without re-parsing the payload, while the payload's structured `errors[]` remains the canonical normative shape. Non-fatal warnings populate ONLY `payload.errors[]` with `severity: warning` — the envelope MUST NOT carry `adcp_error` for non-failures."
     },
     "push_notification_config": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/push-notification-config.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/push-notification-config.json",
       "description": "AdCP application-layer webhook configuration for async task updates over MCP, A2A, or REST. Echoed from the request to confirm webhook settings. It is distinct from transport-native progress or A2A TaskPushNotificationConfig delivery and can outlive the originating transport session."
     },
     "governance_context": {

package/dist/lib/schemas-data/3.2/core/provenance.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/provenance.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/provenance.json",
   "title": "Provenance",
   "description": "Declares how content was produced, whether AI was involved, and what disclosure obligations apply. Attaches to creative manifests, individual assets, or content-standards artifacts. When present at multiple levels, the most specific provenance object replaces the inherited one entirely (no field-level merging). Provenance is a claim by the declaring party — receiving parties should verify claims independently via their own detection tools.",
   "type": "object",
   "properties": {
     "digital_source_type": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/digital-source-type.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/digital-source-type.json",
       "description": "IPTC-aligned classification of AI involvement in producing this content"
     },
     "synthetic_depiction": {
@@ -116,7 +116,7 @@
         "type": "object",
         "properties": {
           "method": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/embedded-provenance-method.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/embedded-provenance-method.json",
             "description": "How provenance data is carried within the content"
           },
           "standard": {
@@ -167,7 +167,7 @@
         "type": "object",
         "properties": {
           "media_type": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/watermark-media-type.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/watermark-media-type.json",
             "description": "Media category of the watermarked content"
           },
           "provider": {
@@ -195,7 +195,7 @@
             "additionalProperties": false
           },
           "c2pa_action": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/c2pa-watermark-action.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/c2pa-watermark-action.json",
             "description": "C2PA action classification for this watermark"
           },
           "embedded_at": {
@@ -246,7 +246,7 @@
                 "minProperties": 1,
                 "properties": {
                   "persistence": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/disclosure-persistence.json",
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/disclosure-persistence.json",
                     "description": "How long the disclosure must persist during content playback or display"
                   },
                   "min_duration_ms": {
@@ -258,13 +258,13 @@
                     "type": "array",
                     "description": "Preferred disclosure positions in priority order. The first position a format supports should be used.",
                     "items": {
-                      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/disclosure-position.json"
+                      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/disclosure-position.json"
                     },
                     "minItems": 1,
                     "uniqueItems": true
                   },
                   "ext": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
                   }
                 }
               }
@@ -326,7 +326,7 @@
       }
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
     }
   }
 }

package/dist/lib/schemas-data/3.2/core/publisher-property-selector.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/publisher-property-selector.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/publisher-property-selector.json",
   "title": "Publisher Property Selector",
   "description": "Selects properties from a publisher's adagents.json. Used for both product definitions and agent authorization. Supports three selection patterns: all properties, specific IDs, or by tags. Each selector targets one publisher via `publisher_domain` (string) or a fan-out across many publishers that share the same selector via `publisher_domains` (array). Exactly one of `publisher_domain` or `publisher_domains` MUST be present. When `publisher_domains` is used, the selector is logically equivalent to repeating the same entry once per listed domain.",
   "discriminator": {
@@ -79,7 +79,7 @@
           "type": "array",
           "description": "Specific property IDs from the publisher's adagents.json",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/property-id.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/property-id.json"
           },
           "minItems": 1
         }
@@ -119,7 +119,7 @@
           "type": "array",
           "description": "Property tags resolved against each addressed publisher's adagents.json, OR against the parent file's top-level `properties[]` when those properties carry a `publisher_domain` matching the selector. Selector covers all properties carrying any of these tags.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/property-tag.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/property-tag.json"
           },
           "minItems": 1
         }

package/dist/lib/schemas-data/3.2/core/push-notification-config.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/push-notification-config.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/push-notification-config.json",
   "title": "Push Notification Config",
   "description": "Webhook configuration for asynchronous task notifications. Uses A2A-compatible PushNotificationConfig structure. By default, webhooks are signed with the AdCP RFC 9421 profile (see docs/building/by-layer/L1/security.mdx#webhook-callbacks) — the seller signs outbound with a key published at the jwks_uri on its own brand.json `agents[]` entry and the buyer verifies against that JWKS, so no shared secret crosses the wire. The optional `authentication` block selects the legacy Bearer or HMAC-SHA256 fallback for compatibility with receivers that have not yet adopted the 9421 profile; this fallback is deprecated and will be removed in AdCP 4.0. Note: the `idempotency_key` that receivers dedup on lives inside the webhook **payload** body (see docs/building/by-layer/L3/webhooks.mdx#reliability and the mcp-webhook-payload schema), not in this configuration object — this schema only describes the receiver-side transport config sent to the seller. This schema is designed for composition via allOf - consuming schemas should define their own additionalProperties constraints.",
   "type": "object",
@@ -26,13 +26,14 @@
     "authentication": {
       "type": "object",
       "deprecated": true,
+      "x-removed-in": "4.0.0",
       "description": "Legacy authentication configuration (A2A-compatible). Opts the seller into Bearer or HMAC-SHA256 signing instead of the default RFC 9421 webhook profile. Deprecated; removed in AdCP 4.0. **Precedence is a switch, not a fallback:** presence of this block selects the legacy scheme; absence selects 9421. A seller MUST NOT sign the same webhook both ways, and a buyer MUST NOT attempt 'try 9421 first, fall back to HMAC' verification — signature mode is determined solely by whether this block was present at registration time. The seller's baseline 9421 webhook key is published at its brand.json `agents[]` `jwks_uri` using `adcp_use: \"request-signing\"` (deprecated `webhook-signing` keys remain accepted during the compatibility window); it does not override this selector and is only used when `authentication` is omitted. See docs/building/by-layer/L1/security.mdx#webhook-callbacks for the full precedence and downgrade-resistance rules (including the `webhook_mode_mismatch` rejection a buyer MUST apply when a received webhook's signing mode does not match the registered mode).",
       "properties": {
         "schemes": {
           "type": "array",
           "description": "Array of authentication schemes. Supported: ['Bearer'] for simple token auth, ['HMAC-SHA256'] for legacy shared-secret signing. Both are deprecated; new integrations SHOULD omit `authentication` and use the RFC 9421 webhook profile.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/auth-scheme.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/auth-scheme.json"
           },
           "minItems": 1,
           "maxItems": 1

package/dist/lib/schemas-data/3.2/core/real-estate-item.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/real-estate-item.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/real-estate-item.json",
   "title": "Real Estate Item",
   "description": "A property listing within a real-estate-type catalog. Carries the address, pricing, and specification data that platforms use for real estate ads and dynamic remarketing. Maps to Google DynamicRealEstateAsset, Meta home listing catalogs, and similar formats.",
   "type": "object",
@@ -42,7 +42,7 @@
       "additionalProperties": false
     },
     "price": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/price.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/price.json",
       "description": "Property price or rental rate. Use period 'month' for rentals."
     },
     "property_type": {
@@ -156,12 +156,12 @@
       "type": "array",
       "description": "Typed creative asset pools for this property listing. Uses the same OfferingAssetGroup structure as offering-type catalogs. Standard group IDs: 'images_landscape' (exterior/interior 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": "https://adcontextprotocol.org/schemas/3.2.5/core/offering-asset-group.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/offering-asset-group.json"
       },
       "minItems": 1
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/core/reference-asset.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reference-asset.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reference-asset.json",
   "title": "Reference Asset",
   "description": "A reference asset that provides creative context. Carries visual materials (mood boards, product shots, example creatives) with semantic roles that tell creative agents how to use them.",
   "type": "object",

package/dist/lib/schemas-data/3.2/core/reference-renderer.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reference-renderer.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reference-renderer.json",
   "title": "Reference Renderer",
   "description": "Pinned npm package export for a community-maintained reference presentation of a canonical format. The registry references the package but never serves or executes it. A reference renderer is non-authoritative: it demonstrates one interoperable presentation of the format contract and is not evidence of seller, publisher, or serving-platform output. Consumers MUST verify the exact tarball integrity and npm provenance, bind the attestation source repository/workflow and subject digest to this entry, and execute the module in a separate opaque-origin or worker realm with no ambient credentials or network access, a timeout, and input/output size limits. Consumers MUST NOT bundle or import registry-selected code into the host application realm. On confirmation that a pinned renderer version is vulnerable, the community-registry maintainer MUST replace the version and integrity in a reviewed registry update and rotate the enclosing catalog's cache validator. A consumer whose vulnerability policy marks the pin unsafe MUST fail closed for renderer execution, MUST NOT load the package, and MUST continue with the normal rendering fallback order.",
   "type": "object",

package/dist/lib/schemas-data/3.2/core/registry-event.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/registry-event.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/registry-event.json",
   "title": "Registry Event",
   "description": "A single cursor-ordered event from the AgenticAdvertising.org registry change feed. Events are denormalized so RegistrySync clients can update local property, agent, publisher, and authorization indexes without re-reading the full registry. The discriminator is event_type; each branch defines the event-specific payload shape. See specs/registry-change-feed.md.",
   "type": "object",
@@ -826,7 +826,7 @@
       "additionalProperties": true
     },
     "badgeRole": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/adcp-protocol.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/adcp-protocol.json"
     },
     "stringArray": {
       "type": "array",
@@ -877,7 +877,7 @@
         "identifiers": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/identifier.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/identifier.json"
           },
           "minItems": 1
         },
@@ -885,7 +885,7 @@
           "$ref": "#/$defs/domain"
         },
         "property": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/property.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/property.json",
           "description": "Optional full post-change property object when available."
         },
         "changed_fields": {
@@ -902,7 +902,7 @@
           "description": "Distribution platform domain, such as youtube.com or spotify.com."
         },
         "type": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/distribution-identifier-type.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/distribution-identifier-type.json"
         },
         "value": {
           "type": "string"
@@ -941,7 +941,7 @@
         "kind": {
           "anyOf": [
             {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/collection-kind.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/collection-kind.json"
             },
             {
               "type": "null"
@@ -967,7 +967,7 @@
           "description": "Distribution identifiers that alias this collection across platforms."
         },
         "collection": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/collection.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/collection.json",
           "description": "Optional full post-change collection object when available."
         },
         "changed_fields": {
@@ -1023,15 +1023,16 @@
         "format_ids": {
           "type": "array",
           "deprecated": true,
+          "x-removed-in": "4.0.0",
           "description": "Deprecated in AdCP 3.2; removed in AdCP 4.0. Named-format profile projection. Use canonical `format_kinds` and `format_option_refs`.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/format-id.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/format-id.json"
           }
         },
         "format_kinds": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/canonical-format-kind.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/canonical-format-kind.json"
           },
           "uniqueItems": true
         },
@@ -1112,28 +1113,28 @@
         "property_ids": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/property-id.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/property-id.json"
           },
           "minItems": 1
         },
         "property_tags": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/property-tag.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/property-tag.json"
           },
           "minItems": 1
         },
         "properties": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/property.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/property.json"
           },
           "minItems": 1
         },
         "publisher_properties": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/publisher-property-selector.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/publisher-property-selector.json"
           },
           "minItems": 1
         },
@@ -1171,7 +1172,7 @@
           "type": "array",
           "description": "Collection constraints from authorized_agents[*].collections. When set, the event does NOT authorize the property unqualified — consumers building a local authorization index MUST scope the grant to these selectors and fail closed when a query carries no collection scope. A selector without collection_ids is a bulk grant for all collections declared at that publisher_domain.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/collection-selector.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/collection-selector.json"
           },
           "minItems": 1
         },
@@ -1192,7 +1193,7 @@
         "signing_keys": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/agent-signing-key.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/agent-signing-key.json"
           },
           "minItems": 1,
           "description": "Publisher-attested signing keys copied from adagents.json when the registry has them. Advisory in feed events; verifiers MUST re-fetch the authoritative publisher artifact before treating keys as a trust anchor."

package/dist/lib/schemas-data/3.2/core/registry-feed-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/registry-feed-response.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/registry-feed-response.json",
   "title": "Registry Feed Response",
   "description": "Response from GET /api/registry/feed and the `feed` event body from GET /api/registry/feed/stream. The events array contains cursor-ordered registry events; cursor is the value to pass on the next poll or stream reconnect. See specs/registry-change-feed.md.",
   "type": "object",
@@ -8,7 +8,7 @@
     "events": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/registry-event.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/registry-event.json"
       }
     },
     "cursor": {

package/dist/lib/schemas-data/3.2/core/reporting-adjustment-receipt.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-adjustment-receipt.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-adjustment-receipt.json",
   "title": "Reporting Adjustment Receipt",
   "x-status": "experimental",
   "description": "Authenticated consumer acceptance or rejection of one exact post-official adjustment. It does not alter the original official revision or its receipt.",

package/dist/lib/schemas-data/3.2/core/reporting-adjustment.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-adjustment.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-adjustment.json",
   "title": "Reporting Adjustment",
   "x-status": "experimental",
   "description": "One immutable post-official accounting-only correction to billing-purpose reporting evidence/control totals. It never edits rows, supersedes a revision, creates or changes invoices, calculates tax or FX, authorizes accounting entries, settles payment, or determines legal payment obligations.",
@@ -61,7 +61,7 @@
     "control_total_deltas": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-control-total.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-control-total.json"
       },
       "minItems": 1,
       "uniqueItems": true,

package/dist/lib/schemas-data/3.2/core/reporting-canonical-content-digest.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-canonical-content-digest.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-canonical-content-digest.json",
   "title": "Reporting Canonical Content Digest",
   "x-status": "experimental",
   "description": "Cryptographic digest of logical reporting rows under an immutable canonicalization contract.",

package/dist/lib/schemas-data/3.2/core/reporting-canonicalization-contract.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-canonicalization-contract.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-canonicalization-contract.json",
   "title": "Reporting Canonicalization Contract",
   "x-status": "experimental",
   "description": "Executable, immutable contract for producing the canonical logical-report bytes hashed by reporting-canonical-content-digest.json. The fetched document uses application/vnd.adcp.reporting-canonicalization+json and is verified by SHA-256 before parsing.",

package/dist/lib/schemas-data/3.2/core/reporting-capabilities.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-capabilities.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-capabilities.json",
   "title": "Reporting Capabilities",
   "description": "Reporting capabilities available for a product",
   "type": "object",
@@ -9,7 +9,7 @@
       "type": "array",
       "description": "Supported reporting frequency options",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/reporting-frequency.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/reporting-frequency.json"
       },
       "minItems": 1,
       "uniqueItems": true
@@ -42,7 +42,7 @@
       "type": "array",
       "description": "Product-scoped subset of get_adcp_capabilities.media_buy.reporting_delivery.offerings[].offering_id that packages using this product can satisfy. This binds seller-wide managed-delivery offerings to product/package eligibility. An empty array explicitly declares no managed offering; absence means product-level applicability is unknown and MUST NOT be inferred from the seller-wide list. Account, seat, credential, or provider constraints may narrow support further during sync_accounts validation.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-offering-id.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-delivery-offering-id.json"
       },
       "uniqueItems": true
     },
@@ -50,7 +50,7 @@
       "type": "array",
       "description": "Metrics available in reporting. Impressions and spend are always implicitly included. When a creative format declares reported_metrics, buyers receive the intersection of these product-level metrics and the format's reported_metrics.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/available-metric.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/available-metric.json"
       },
       "uniqueItems": true,
       "examples": [
@@ -74,15 +74,15 @@
         "type": "object",
         "properties": {
           "vendor": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/brand-ref.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/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 standard alignment, accreditations, and methodology live at that agent's `get_adcp_capabilities.measurement.metrics[]` and are not duplicated inline here."
           },
           "metric_id": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/vendor-metric-id.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/vendor-metric-id.json",
             "description": "Identifier for the metric within the vendor's vocabulary (e.g., `attention_units`, `gco2e_per_impression`, `demographic_reach`)."
           },
           "vendor_relationship": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/vendor-relationship.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/vendor-relationship.json",
             "description": "Relationship between this product's seller and `vendor` — `first_party` (the seller or its own measurement agent produced the number), `affiliated` (distinct legal entity under common ownership or control: parent/subsidiary, controlling stake, joint venture, disclosed board overlap), or `third_party` (independent vendor). Defined on structural facts only — a commercial dependency does not make a vendor `affiliated`; see the enum. A property of the (seller, vendor) pair, which is why it is declared here rather than on the vendor's catalog. REQUIRED whenever `vendor` resolves to the seller's own `brand.json` or to an entity under common ownership or control with the seller — the self-measurement case is permitted only when it is disclosed, so a seller MUST NOT leave the field absent and let a buyer guess. RECOMMENDED for unrelated third-party vendors. Absence means *undeclared*: buyers MUST treat an absent value as unknown, never as `third_party`, and MAY exclude undeclared rows from reconciliation. This is a relationship disposition, not a trust ranking — quality and independence-of-incentive questions belong to the vendor catalog's `accreditations[]` and `standard_reference`, not to this field. Methodology (sensor, panel, model, instrument) is NOT declared here — it lives at the vendor catalog's `description`, `methodology_url`, `methodology_version`, `standard_reference`, and `accreditations[]`. MAY be echoed on `vendor_metric_values[].vendor_relationship` in delivery."
           }
         },
@@ -113,7 +113,7 @@
       "description": "Whether this product supports keyword-level metric breakdowns in delivery reporting (by_keyword within by_package)"
     },
     "supports_geo_breakdown": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/geo-breakdown-support.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/geo-breakdown-support.json",
       "description": "Geographic breakdown support for this product. Declares which geo levels and systems are available for by_geo reporting within by_package."
     },
     "supports_device_type_breakdown": {
@@ -129,7 +129,7 @@
       "description": "Whether this product supports audience segment breakdowns in delivery reporting (by_audience within by_package)"
     },
     "supports_demographic_breakdown": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/demographic-reporting-capability.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/demographic-reporting-capability.json",
       "description": "Product-scoped demographic breakdown support for by_demographic reporting. Declares reportable age ranges and measurement systems independently from demographic targeting execution."
     },
     "supports_placement_breakdown": {
@@ -161,7 +161,7 @@
       "description": "Whether this product supports placement × property intersection reporting (by_placement_property within by_package)."
     },
     "supports_spot_breakdown": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/spot-reporting-capability.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/spot-reporting-capability.json",
       "description": "Spot-level as-run airing-log support and metrics available at spot grain for broadcast TV, radio, and other scheduled inventory."
     },
     "date_range_support": {
@@ -177,7 +177,7 @@
       "type": "array",
       "description": "Granularities at which this product honors per-window pulls on get_media_buy_delivery (via request `time_granularity` + `include_window_breakdown: true`). Closes the GET-side half of the snapshot/log two-paths-parity contract for data-bearing events: a buyer who missed a webhook fire at any granularity listed here can reconstruct an identical payload by polling. Capability-scoped MUST — sellers MUST honor pulls at any granularity declared here, and MUST return UNSUPPORTED_GRANULARITY for pulls outside the set. Sellers MAY emit higher-frequency webhooks than they expose for pull (common where the webhook is a Kafka tap and historical reads go through a warehouse with coarser granularity); buyers see the gap up front via this capability and treat the webhook as primary for those frequencies. Absent or empty means the product only supports cumulative date-range pulls and full per-window recovery via GET is unavailable — see snapshot-and-log Rule 4.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/reporting-frequency.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/reporting-frequency.json"
       },
       "uniqueItems": true,
       "examples": [
@@ -199,7 +199,7 @@
       "type": "array",
       "description": "Measurement maturation stages available for this product. Used by any channel where billing-grade data is produced in phases rather than arriving final on day one. Examples: broadcast/linear TV (Live → C3 → C7 DVR accumulation), DOOH (tentative plays → post-IVT/fraud-check final), digital with IVT filtering (raw → GIVT filtered → SIVT filtered), podcast (7-day downloads → 30-day downloads). Each window defines an accumulation period and expected data availability. When present, delivery reports reference a specific window_id. Sellers whose data is final on first delivery typically omit this.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/measurement-window.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/measurement-window.json"
       },
       "minItems": 1,
       "uniqueItems": true

package/dist/lib/schemas-data/3.2/core/reporting-consumer-status.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-consumer-status.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-consumer-status.json",
   "title": "Reporting Consumer Status",
   "x-status": "experimental",
   "description": "One immutable, authenticated consumer statement about whether the required reporting for an expected configuration period could actually be consumed. It is operational status, not measurement data, delivery totals, a billing receipt, or authority to overwrite the seller's obligation/revision ledger. New statements supersede the current statement for the same consumer, configuration generation, report definition, and period while preserving append-only history.",

package/dist/lib/schemas-data/3.2/core/reporting-control-total.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-control-total.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-control-total.json",
   "title": "Reporting Control Total",
   "x-status": "experimental",
   "description": "One profile-defined aggregate used to reconcile a reporting revision without rereading every row. Names and units are defined by the immutable report definition. Values use canonical strings so currency and large integer comparisons are exact across SDKs.",