@adcp/sdk 15.2.0 → 15.2.1

package/dist/lib/schemas-data/3.2/protocol/get-task-status-request.json

@@ -1,13 +1,13 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/protocol/get-task-status-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/protocol/get-task-status-request.json",
   "title": "Get Task Status Request",
   "description": "Request parameters for the get_task_status AdCP tool. This is a 3.x protocol-namespace alias for the legacy AdCP tasks/get polling surface, not a transport-native MCP/A2A tasks/* method. It retrieves a specific AdCP application-layer async task by ID with optional conversation history and terminal result payload.",
   "x-tool-summary": "Retrieve an AdCP asynchronous task, its conversation history, and terminal result by task ID.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json"
     }
   ],
   "properties": {
@@ -17,7 +17,7 @@
       "x-entity": "task"
     },
     "account": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/account-ref.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/account-ref.json",
       "description": "Account scope for the task lookup. Sellers MUST return REFERENCE_NOT_FOUND for a task_id that exists only under a different account or principal. When omitted, the seller MAY use the credential-bound singleton account, but multi-account credentials SHOULD require an explicit account."
     },
     "include_history": {
@@ -31,10 +31,10 @@
       "description": "Include the task's canonical terminal result payload when one exists. Defaults to false for lightweight status-only polls. When true, sellers MUST include result for completed, failed, or rejected terminal tasks when that task produced a terminal artifact; canceled tasks may have no result. The legacy singular error field remains a convenience for failed tasks but does not replace the canonical terminal result."
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/protocol/get-task-status-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/protocol/get-task-status-response.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/protocol/get-task-status-response.json",
   "title": "Get Task Status Response",
   "description": "Response from the get_task_status AdCP tool, a 3.x protocol-namespace alias for legacy AdCP tasks/get. Contains AdCP application-layer task status, task metadata, and optional conversation history or terminal result payload; distinct from transport-native MCP/A2A task responses.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json"
     },
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/protocol-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/protocol-envelope.json"
     },
     {
       "if": {
@@ -36,7 +36,7 @@
       "then": {
         "properties": {
           "result": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.1/media-buy/get-products-rejected.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.3/media-buy/get-products-rejected.json"
           }
         }
       }
@@ -49,15 +49,15 @@
       "x-entity": "task"
     },
     "task_type": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/task-type.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/task-type.json",
       "description": "Type of AdCP operation"
     },
     "protocol": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/adcp-protocol.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/adcp-protocol.json",
       "description": "AdCP protocol this task belongs to"
     },
     "status": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/task-status.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/task-status.json",
       "description": "Current task status"
     },
     "created_at": {
@@ -123,7 +123,7 @@
           "description": "Additional error context",
           "properties": {
             "protocol": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/adcp-protocol.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/adcp-protocol.json",
               "description": "AdCP protocol where error occurred"
             },
             "operation": {
@@ -184,10 +184,10 @@
       "description": "Canonical task-specific terminal payload. Present when include_result was true and a completed, failed, or rejected task produced a terminal artifact; canceled tasks may omit it. For failed tasks, the singular error field is a convenience summary and MUST agree with the canonical fatal error represented here. Consumers and sellers MUST resolve and validate the exact schema through manifest.task_result_resolution: use terminal_schema_overrides[task_type] when present, otherwise tools[task_type].response_schema. The polling envelope keeps this field generic so get_task_status does not embed every task response schema."
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/protocol/list-tasks-request.json

@@ -1,18 +1,18 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/protocol/list-tasks-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/protocol/list-tasks-request.json",
   "title": "List Tasks Request",
   "description": "Request parameters for the list_tasks AdCP tool. This is a 3.x protocol-namespace alias for the legacy AdCP tasks/list reconciliation surface, not a transport-native MCP/A2A tasks/* method. It lists and filters AdCP application-layer async tasks for state reconciliation while preserving the legacy 3.x payload shape.",
   "x-tool-summary": "List and filter AdCP asynchronous tasks for state reconciliation.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json"
     }
   ],
   "properties": {
     "account": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/account-ref.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/account-ref.json",
       "description": "Account scope for task reconciliation. Sellers MUST only return tasks created for the caller's authenticated account + principal pair. When omitted, the seller MAY use the credential-bound singleton account, but multi-account credentials SHOULD require an explicit account."
     },
     "filters": {
@@ -20,38 +20,38 @@
       "description": "Filter criteria for querying tasks",
       "properties": {
         "protocol": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/adcp-protocol.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/adcp-protocol.json",
           "description": "Filter by single AdCP protocol"
         },
         "protocols": {
           "type": "array",
           "description": "Filter by multiple AdCP protocols",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/adcp-protocol.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/adcp-protocol.json"
           },
           "minItems": 1
         },
         "status": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/task-status.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/task-status.json",
           "description": "Filter by single task status"
         },
         "statuses": {
           "type": "array",
           "description": "Filter by multiple task statuses",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/task-status.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/task-status.json"
           },
           "minItems": 1
         },
         "task_type": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/task-type.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/task-type.json",
           "description": "Filter by single task type"
         },
         "task_types": {
           "type": "array",
           "description": "Filter by multiple task types",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/task-type.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/task-type.json"
           },
           "minItems": 1
         },
@@ -112,7 +112,7 @@
           "description": "Field to sort by"
         },
         "direction": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/sort-direction.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/sort-direction.json",
           "default": "desc",
           "description": "Sort direction"
         }
@@ -120,7 +120,7 @@
       "additionalProperties": true
     },
     "pagination": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/pagination-request.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/pagination-request.json"
     },
     "include_history": {
       "type": "boolean",
@@ -128,10 +128,10 @@
       "description": "Include full conversation history for each task (may significantly increase response size)"
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json"
     }
   },
   "additionalProperties": true,

package/dist/lib/schemas-data/3.2/protocol/list-tasks-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/protocol/list-tasks-response.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/protocol/list-tasks-response.json",
   "title": "List Tasks Response",
   "description": "Response from the list_tasks AdCP tool, a 3.x protocol-namespace alias for legacy AdCP tasks/list. Contains filtered AdCP application-layer task results and reconciliation data while preserving the legacy 3.x domain field shape; distinct from transport-native MCP/A2A task responses.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json"
     },
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/protocol-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/protocol-envelope.json"
     }
   ],
   "properties": {
@@ -101,7 +101,7 @@
             "x-entity": "task"
           },
           "task_type": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/task-type.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/task-type.json",
             "description": "Type of AdCP operation"
           },
           "domain": {
@@ -114,7 +114,7 @@
             ]
           },
           "status": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/task-status.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/task-status.json",
             "description": "Current task status"
           },
           "created_at": {
@@ -149,13 +149,13 @@
       }
     },
     "pagination": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/pagination-response.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/pagination-response.json"
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/protocol/sync-agent-notification-configs-request.json

@@ -1,13 +1,13 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/protocol/sync-agent-notification-configs-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/protocol/sync-agent-notification-configs-request.json",
   "title": "Sync Agent Notification Configs Request",
   "description": "Register, replace, pause, or clear caller-scoped agent-level webhook subscribers. This task manages notifications whose lifecycle belongs to the seller agent itself rather than to an account or media buy. The initial use case is `capabilities.changed`, which invalidates cached `get_adcp_capabilities` responses. Declarative semantics match account-level `notification_configs[]`, but the replacement is scoped to the authenticated caller or registry identity: the submitted array is that caller's complete desired set, keyed by `subscriber_id`; persisted subscribers for that caller whose `subscriber_id` does not appear in the submitted array are removed; sending `[]` clears only that caller's set. Sellers MUST reject this task unless `get_adcp_capabilities.adcp.capability_changes.notifications.supported` is true.",
   "x-tool-summary": "Register, replace, pause, or clear caller-scoped webhooks for agent-level notifications.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json"
     }
   ],
   "x-mutates-state": true,
@@ -25,7 +25,7 @@
       "items": {
         "allOf": [
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/agent-notification-config.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/agent-notification-config.json"
           },
           {
             "if": {
@@ -53,10 +53,10 @@
       "description": "When true, validate the replacement and report what would be persisted without applying it or sending endpoint proof-of-control challenges."
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/protocol/sync-agent-notification-configs-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/protocol/sync-agent-notification-configs-response.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/protocol/sync-agent-notification-configs-response.json",
   "title": "Sync Agent Notification Configs Response",
   "description": "Response from caller-scoped agent-level notification subscriber replacement. Echoes the authenticated caller's persisted subscriber set with legacy credentials redacted, or reports operation-level errors when the replacement failed.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json"
     },
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/protocol-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/protocol-envelope.json"
     }
   ],
   "properties": {
@@ -31,7 +31,7 @@
       "type": "array",
       "description": "Current persisted agent-level notification subscribers owned by the authenticated caller after the request. Entries are keyed by `subscriber_id`; `authentication.credentials` is omitted on every entry because credentials are write-only. Present on successful actions and MAY be present on `failed` responses to show the unchanged prior caller-scoped set.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/agent-notification-config.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/agent-notification-config.json"
       },
       "maxItems": 16
     },
@@ -39,14 +39,14 @@
       "type": "array",
       "description": "Operation-level errors and warnings. Present when action is `failed`, and MAY include non-fatal warnings on successful responses.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/error.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/error.json"
       }
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/protocol/sync-principal-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/protocol/sync-principal-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/protocol/sync-principal-request.json",
   "title": "Sync Principal Request",
   "x-status": "experimental",
   "description": "This task begins after authentication: AdCP defines no credential-registration protocol, and the seller’s authorization system (OAuth, API keys, signed requests, workload identity) issues and maps credentials before the first call. Declaratively synchronize selected sections of the authenticated principal's standing configuration with one AdCP agent. The principal is a party: a buyer agent, or an operator-side identity acting through any client. Use this task only to change state; read current state, the configuration version, and destination setup progress through get_principal, and prefer this task over the narrower sync_agent_notification_configs when both are advertised. This task does not register a buyer agent: the stable principal MAY be a delegated human user or an autonomous workload. Identity is resolved from authenticated transport and MUST NOT be accepted from request-body agent URLs, signing key IDs, account IDs, or other self-asserted fields. Each present section is the caller's complete desired set and replaces only that section; omitted sections remain unchanged. All submitted sections apply atomically or none do. This task configures reusable principal resources but grants no advertiser-account authority. Sellers implementing it MUST advertise adcp.principal and protocol.principal.",
@@ -8,7 +8,7 @@
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json"
     },
     {
       "not": {
@@ -53,7 +53,7 @@
       "description": "Optional optimistic-concurrency fence returned by a previous successful sync. When present and stale, the seller rejects the whole request without mutation. Compare only for equality."
     },
     "expected_principal_kind": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/principal-kind.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/principal-kind.json",
       "description": "Optional assertion fence, not identity input: the caller states which party kind it believes it is authenticating as. When present and different from the seller-resolved principal_kind, the seller rejects the whole request with CONFLICT before mutation. The field never influences resolution."
     },
     "configuration": {
@@ -66,7 +66,7 @@
           "items": {
             "allOf": [
               {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/agent-notification-config.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/agent-notification-config.json"
               },
               {
                 "if": {
@@ -92,12 +92,12 @@
           "type": "array",
           "description": "Complete desired reusable reporting destination set. Omitting a previously present destination_id revokes it, and [] revokes every destination: the seller halts new deliveries to all of its generations within the advertised suspension_interval_seconds and retains it as a retired generation for reporting history. Revocation does not delete caller-owned data already delivered. destination_id values MUST be unique.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/agent-reporting-destination.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/agent-reporting-destination.json"
           },
           "maxItems": 64
         },
         "declarations": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/principal-declarations.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/principal-declarations.json",
           "description": "Complete declared consumption facts for this principal record. A present object replaces the declared set wholesale; {} clears it; omission leaves it unchanged. The seller computes and returns the accepted intersection in state."
         }
       },
@@ -110,10 +110,10 @@
       "description": "Validate the proposed replacements and report the would-be action without persisting them, issuing durable identifiers or grants, or sending endpoint proof challenges."
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/protocol/sync-principal-response.json

@@ -1,16 +1,16 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/protocol/sync-principal-response.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/protocol/sync-principal-response.json",
   "title": "Sync Principal Response",
   "x-status": "experimental",
   "description": "Result of synchronizing selected sections of the principal's standing configuration. Applied responses return the complete current credential-free configuration. Validated dry-run responses report the would-be action without issuing durable identifiers. Failed responses deliberately cannot carry principal identifiers, versions, or configuration state.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json"
     },
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/protocol-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/protocol-envelope.json"
     }
   ],
   "properties": {
@@ -44,7 +44,7 @@
               "description": "Seller-issued opaque identifier for this authenticated principal record. It is response-only, not a credential, not caller identity, and not advertiser-account authority."
             },
             "principal_kind": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.1/enums/principal-kind.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.3/enums/principal-kind.json",
               "description": "Seller-resolved party kind of the authenticated principal: a buyer-agent workload, or an operator-side identity such as a person at the operator. Resolved solely from the seller's authorization system, never from request content, so per-party policy such as billing gates can rely on it."
             },
             "configuration_version": {
@@ -54,12 +54,12 @@
               "description": "Opaque version of the persisted configuration. Compare only for equality and return it as expected_configuration_version on a later guarded replacement."
             },
             "configuration": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/principal-state.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/principal-state.json"
             },
             "warnings": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/error.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/error.json"
               },
               "maxItems": 16
             }
@@ -98,7 +98,7 @@
             "warnings": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/error.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/error.json"
               },
               "maxItems": 16
             }
@@ -121,7 +121,7 @@
             "errors": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/error.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/error.json"
               },
               "minItems": 1,
               "maxItems": 16
@@ -136,10 +136,10 @@
       ]
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/registries/v1-canonical-mapping.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/registries/v1-canonical-mapping.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/registries/v1-canonical-mapping.json",
   "title": "v1 → v2 Canonical Format Mapping Registry",
   "description": "Authoritative AAO-published mapping from v1 named formats to v2 canonical declarations. Used by SDKs to project the v1 wire shape into v2 canonical declarations during the migration window.\n\n**Direction of truth (normative).** This registry is authoritative for **v1 → v2 projection only**. v2 → v1 projection MUST rely on `v1_format_ref` on the v2 `ProductFormatDeclaration` — sellers assert the v1 pairing explicitly. SDKs MUST NOT synthesize a v1 `format_id` from the registry by inverting structural matches: the registry's `id` slugs lack the `agent_url` half of a `FormatId`, and registry entries with `format_id_glob: '*'` or pure-structural matches have no single literal to invert to. SDKs that synthesize unilaterally produce inter-SDK divergence on structurally-equal values (different SDKs pick different `agent_url` and `id` patterns for the same v2 declaration). When a v2 declaration carries no `v1_format_ref` and a v1-only buyer queries the product, the SDK reports the canonical as v1-unreachable via `FORMAT_DECLARATION_V1_AMBIGUOUS` and lets the buyer surface it to the seller; the seller's path is to add `v1_format_ref` to disambiguate.\n\nBest-effort inversion is available only from this registry's non-wildcarded literal format_id_glob entries. Structural matches remain family-level and are not invertible to a specific v1 format_id. SDKs MAY do best-effort inversion for non-wildcarded literals only, AND only when the seller hasn't authored a contradicting `v1_format_ref` — even then, the projection is non-normative and downstream consumers MUST NOT depend on it.\n\n**Resolution order** (per RFC #3305 amendment #3767, normative):\n1. **Authoritative v2→v1 link**: if any v2 `ProductFormatDeclaration` on the same product carries `v1_format_ref` pointing at this v1 format_id, use that v2 declaration. Highest priority — seller asserts the link directly. SDKs SHOULD run the *narrows* check (canonical-formats.mdx 'Narrows — formal definition') between the v2 declaration's `params` and the referenced v1 format's `requirements`; on conflict, surface `FORMAT_DECLARATION_DIVERGENT` on the `get_products` response `errors[]`. Without the narrowing check, `v1_format_ref` is a hint rather than a contract.\n2. **Seller-asserted on the v1 file**: if the v1 format declaration carries an explicit `canonical` field, use it. (Note: `canonical_parameters` on the v1 file is deprecated for 3.1; SDKs reading 3.1 catalogs MUST still honor it when present, but `v1_format_ref` is the path forward.)\n3. **Registry glob**: look up `format_id` in this registry's `format_id_glob` entries.\n4. **Structural match**: attempt structural match against this registry's `structural` entries. A successful structural match yields a *family-level* identification only (e.g., 'this is a `video_vast`') — it does NOT yield a specific v1 `format_id`. SDKs use structural match for v1 → v2 projection (the inbound direction) but MUST NOT invert it to a v1 `format_id` on the outbound path.\n5. **Ambiguous family**: if step 4 succeeded but the matched entries are family-only (pure structural, no invertible literal), the canonical is **v1-unreachable for THIS specific product** unless the seller authors `v1_format_ref`. SDKs MUST surface `FORMAT_DECLARATION_V1_AMBIGUOUS` via `errors[]` augmentation rather than synthesize a plausible-but-arbitrary v1 `format_id`. Distinct from canonical-level v1-unreachability (a canonical with `v1_translatable: false` — `agent_placement`, `sponsored_placement`, `responsive_creative`, `image_carousel` — never has any v1 form regardless of registry coverage).\n6. **Fail closed**: SDK MUST NOT emit `format_options` for products carrying this format. SDKs MUST augment the response's `errors[]` array with an entry carrying `source: \"sdk\"`, `sdk_id: \"<package>@<version>\"`, `code: \"FORMAT_PROJECTION_FAILED\"`, `field: \"products[N].format_ids[K]\"`, and `error.details: { format_id, product_id, resolution_failure: \"no_explicit_canonical\" | \"no_registry_match\" | \"no_structural_match\" }`. Single mandated surface (`errors[]` augmentation) — lint-output channels are NOT acceptable; the multi-hop agent network needs warnings to propagate across SDK boundaries via the wire response. Logger-only warnings die in DEBUG. The advisory is non-fatal: the response stays 200/success, the product is still valid on the v1 path, only the v2 `format_options` projection is absent. Consumer-side counterpart to the producer SHOULD (sellers should add a v2 declaration with `v1_format_ref`, an explicit `canonical` field, or file a registry PR).\n\n**Match modes:**\n- `format_id_glob` — exact / glob match against the v1 `format_id.id`. Published non-wildcarded literals cover independently observed legacy conventions whose names carry semantic narrowing (duration, dimensions, or VAST delivery) that slot shape alone cannot recover. Each literal mapping preserves those constraints in canonical parameters; AAO-catalog-published formats with explicit canonical annotations still project via resolution-order step 2. Glob syntax: `*` matches any segment.\n- `structural` — match against the format's slot shape, asset types, and version constraints. The PRIMARY fallback for v1 wire traffic — catches custom v1 formats (a publisher's `acme_homepage_300x250` is structurally an IAB MREC) without enumerating every possible v1 name. v1 sellers in the wild naming things their own way are handled here, not by literal globs.\n\n**Alias collision precedence (normative).** When a v1 format's `assets[i]` carries multiple `asset_group_id` aliases that resolve to the same canonical asset_group (e.g., two slots both aliasing to `landing_page_url`), the SDK MUST resolve deterministically: the v1 format's `assets[*]` array order is authoritative — the first slot in declaration order wins, subsequent collisions are dropped from the projected v2 manifest and surfaced via `FORMAT_PROJECTION_FAILED` with `error.details: { collision_kind: \"asset_group_id_alias\", asset_group_id, winning_slot_id, dropped_slot_ids }`. SDKs MUST NOT silently pick one and discard the other without surfacing — silent picking creates inter-SDK divergence. Producers SHOULD avoid the collision by deduplicating aliased slots or using distinct `asset_group_id` values when both slots are semantically meaningful.\n\n**Pixel-density version boundary (normative).** In AdCP 3.1.x, `pixel_ratios` and `required_pixel_ratios` inside this registry are opaque forward-projection metadata. A 3.1.x SDK MUST preserve these members unchanged when it copies or re-emits registry-derived metadata, but MUST NOT interpret them as 3.1 constraints, validate creatives against them, or emit pixel-density validation errors. Seller-authored canonical declarations selected by resolution-order step 1 or 2 are authoritative; SDKs MUST NOT merge registry slot or pixel-ratio defaults into them. For this registry, `3.2-aware` describes the active operation, not merely SDK capability: an SDK is 3.2-aware only while projecting or validating against the AdCP 3.2 canonical model. A binary that supports 3.2 but is processing a negotiated 3.1 exchange MUST follow the 3.1 preservation-only behavior. The complete typed contract begins in AdCP 3.2. Under that contract, ratios are unique positive JSON numbers (fractions are valid); top-level `image.params.pixel_ratios` and slot-level `pixel_ratios` are both authoritative constraints and their intersection is the effective accepted set; `required_pixel_ratios` MUST be a subset of that effective set. A 3.2-aware SDK reports `required_pixel_ratio_missing`, `pixel_ratio_duplicate`, `pixel_ratio_not_accepted`, `pixel_ratio_dimension_mismatch`, `pixel_ratio_ambiguous`, `pixel_ratio_intersection_empty`, or `required_pixel_ratio_not_accepted` as specified by the canonical image reference and its test vectors.\n\n**Image rendition-set exception (AdCP 3.2+, normative).** This specific rule takes precedence over the generic alias-collision rule above only when an SDK projects the matched mapping into, and validates it against, the AdCP 3.2 canonical model. When the mapping declares an image slot with `required_pixel_ratios`, v1 image assets sharing that slot's `asset_group_id` are intentional renditions rather than collisions. The SDK MUST validate each asset against a distinct accepted density and collect them, in v1 declaration order, into the canonical slot array. Missing or duplicate required densities fail under the rendition-set rules; only remaining same-group assets enter ordinary collision handling.\n\n**Governance**: same vocabulary-governance rules as `asset-group-vocabulary.json` and `format-shape-vocabulary.json` — additions land via PR with rationale + ≥1 reference adopter; AAO maintainer review; versioned + content-digested. Entries are additive; once published they are not removed (they may be marked `deprecated: true` if superseded).\n\n**Scope**: 7 structural fallback entries cover VAST 4.x / legacy VAST, DAAST 1.x, HTML5 zip bundles, hosted video, hosted audio, and url-shaped display tags. Literal entries cover independently observed legacy duration-, dimension-, and VAST-token naming conventions. Durationless placement ids video_pre_roll and video_mid_roll are deliberately omitted: projecting either to video_hosted without duration_ms_exact would resolve to an untraffickable format and defer failure until ad-server line-item creation. Failing closed during discovery is safer. Platform-specific formats (Meta Reels, TikTok Spark Ads, etc.) project via structural fallback or via the platform's own adagents.json `formats[]` block (#4620). The full v1-format audit dataset (~76% of formats from the 12-platform / 86-format audit in #3305) seeds the long-term roadmap and informs future literal-entry decisions.\n\nDigest the file content (sha256) when emitting in capabilities responses or referencing from SDK output. Buyers cache by `version` + `digest`.",
   "version": "1.5.2",
@@ -99,7 +99,7 @@
             ],
             "properties": {
               "canonical": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/canonical-format-kind.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/canonical-format-kind.json",
                 "description": "v2 canonical format the v1 pattern projects to."
               },
               "parameters": {

package/dist/lib/schemas-data/3.2/signals/activate-signal-request.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.1/signals/activate-signal-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.3/signals/activate-signal-request.json",
   "title": "Activate Signal Request",
   "description": "Request parameters for activating or deactivating a signal on deployment targets",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json"
     }
   ],
   "x-mutates-state": true,
@@ -39,7 +39,7 @@
       "type": "array",
       "description": "Target destination(s) for activation. If the authenticated caller matches one of these destinations, activation keys will be included in the response.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/destination.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/destination.json"
       },
       "minItems": 1
     },
@@ -56,7 +56,7 @@
       "pattern": "^[\\x20-\\x7E]+$"
     },
     "account": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/account-ref.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/account-ref.json",
       "description": "Account for this activation. Associates with a commercial relationship established via sync_accounts."
     },
     "idempotency_key": {
@@ -67,10 +67,10 @@
       "pattern": "^[A-Za-z0-9_.:-]{16,255}$"
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.1/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json"
     }
   },
   "required": [