@adcp/sdk 16.4.0 → 16.5.0

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

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-agent-notification-configs-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/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.",
@@ -21,6 +21,7 @@
     "adcp_major_version": {
       "type": "integer",
       "deprecated": true,
+      "x-removed-in": "4.0.0",
       "description": "DEPRECATED in favor of adcp_version (release-precision string). Servers MUST continue to honor this field through 3.x. Removed in 4.0. Original semantics: the AdCP major version the buyer's payloads conform to. Sellers validate against their supported major_versions and return VERSION_UNSUPPORTED if unsupported. When omitted, the seller assumes its highest supported version.",
       "minimum": 1,
       "maximum": 99
@@ -104,7 +105,7 @@
   ],
   "$defs": {
     "external:core/version-envelope.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/version-envelope.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/version-envelope.json",
       "title": "AdCP Version Envelope",
       "description": "Release-precision AdCP protocol version negotiation fields. Composed via `allOf` into AdCP request schemas and shared response components so the version semantics live in one place. Strict (`additionalProperties: false`) request schemas also redeclare these two fields in their own `properties` via `$ref`, because draft-07 does not evaluate properties across `allOf`. The Trusted Match match requests are the exception: they inline both fields for their strict privacy boundary. 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",
@@ -123,6 +124,7 @@
         "adcp_major_version": {
           "type": "integer",
           "deprecated": true,
+          "x-removed-in": "4.0.0",
           "description": "DEPRECATED in favor of adcp_version (release-precision string). Servers MUST continue to honor this field through 3.x. Removed in 4.0. Original semantics: the AdCP major version the buyer's payloads conform to. Sellers validate against their supported major_versions and return VERSION_UNSUPPORTED if unsupported. When omitted, the seller assumes its highest supported version.",
           "minimum": 1,
           "maximum": 99
@@ -130,7 +132,7 @@
       }
     },
     "external:core/agent-notification-config.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/agent-notification-config.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/agent-notification-config.json",
       "title": "Agent Notification Config",
       "description": "Caller-scoped agent-level webhook subscription. Caller-anchored event types (capabilities.changed, principal.changed) always fire principal-wide; account-anchored event types may also be listed here with the explicit all_authorized_accounts acknowledgment and fire with per-delivery-attempt authorization scoping over the caller's currently authorized accounts. Registration goes through the task declared by get_adcp_capabilities.adcp.capability_changes.notifications.registration_task: sync_principal when the broader principal surface is supported, or the specialized sync_agent_notification_configs compatibility task. Both tasks operate on one underlying caller-scoped subscriber set. This surface is intentionally separate from account-level notification_configs[]: a registry or buyer can subscribe before it has an account, and one fire invalidates the agent-wide get_adcp_capabilities cache. The persisted set is scoped to the authenticated caller or registry identity, so one caller's declarative replacement cannot clear another caller's subscribers. As with other AdCP webhooks, the default signing scheme is the RFC 9421 webhook profile against the seller's brand.json agents[] JWKS; the optional authentication block opts into the deprecated Bearer / HMAC-SHA256 fallback for compatibility. Credentials and shared secrets in authentication.credentials are write-only and MUST NOT be echoed on reads. Sellers MUST verify endpoint control before activating a new or changed active agent-level notification config; delivery-time SSRF validation still applies to every fire.",
       "type": "object",
@@ -153,7 +155,7 @@
           "items": {
             "allOf": [
               {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-agent-notification-configs-request.json#/$defs/external:enums~1notification-type.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-agent-notification-configs-request.json#/$defs/external:enums~1notification-type.json"
               },
               {
                 "not": {
@@ -184,12 +186,13 @@
         "authentication": {
           "type": "object",
           "deprecated": true,
+          "x-removed-in": "4.0.0",
           "description": "Legacy authentication selector. Same precedence and semantics as `push-notification-config.authentication` and account-level `notification-config.authentication`: presence opts the seller into Bearer or HMAC-SHA256 signing; absence selects the default RFC 9421 webhook profile keyed off the seller's brand.json `agents[]` JWKS. Deprecated; removed in AdCP 4.0. Credentials are write-only and MUST NOT be echoed on reads.",
           "properties": {
             "schemes": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-agent-notification-configs-request.json#/$defs/external:enums~1auth-scheme.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-agent-notification-configs-request.json#/$defs/external:enums~1auth-scheme.json"
               },
               "minItems": 1,
               "maxItems": 1
@@ -211,7 +214,7 @@
           "description": "When false, the seller persists the configuration but suppresses fires. Use to pause a subscriber without losing the registration. Paused configs may skip only the outbound proof challenge while inactive; sellers MUST still enforce URL parsing, HTTPS, hostname normalization, and reserved-range rejection at write time. Reactivation requires full SSRF validation with connect pinning plus proof-of-control for any tuple without current valid proof."
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-agent-notification-configs-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-agent-notification-configs-request.json#/$defs/external:core~1ext.json"
         }
       },
       "required": [
@@ -273,7 +276,7 @@
       ]
     },
     "external:enums/notification-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/notification-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/enums/notification-type.json",
       "title": "Notification Type",
       "description": "Type of push notification fired by a seller agent. Media-buy-anchored cadence reports (`scheduled`, `final`, `delayed`, `adjusted`, `window_update`) fire against a media buy's `reporting_webhook`; `impairment` is media-buy-anchored but fires against `push_notification_config`. Account-anchored notifications include creative, account, product, signal, wholesale-feed, and reporting events, including `reporting.delivery_ready`, `reporting.status_changed`, and `reporting.ledger_changed`; these outlive any single media buy and fire against matching account `notification_configs[]`. The reporting events repair through `get_reporting_status`: delivery_ready is managed-delivery-only, while status_changed and ledger_changed are valid in every reporting tier. Caller-anchored notifications (`capabilities.changed`, `principal.changed`) fire against the caller-scoped subscriber set managed by `sync_principal` or the specialized `sync_agent_notification_configs` compatibility task. New notification types MUST declare their anchor (media-buy, account, or caller), logical notification_id semantics, repair key, and classification in enumDescriptions; only invalidation-only caller-eligible types flow through include_future_event_types. Account-level subscribers MUST reject media-buy- or caller-anchored event types, and persistent account- or caller-anchored types MUST NOT use push_notification_config. Caller-level entries MAY include account-anchored types only with all_authorized_accounts true; each delivery attempt, including retries, is scoped to accounts currently authorized for that caller. Caller-level entries MUST NOT include media-buy-anchored types. Caller- and account-level subscriptions to the same event are independent and receivers dedupe by logical notification_id.",
       "type": "string",
@@ -335,9 +338,10 @@
       }
     },
     "external:enums/auth-scheme.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/auth-scheme.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/enums/auth-scheme.json",
       "title": "Authentication Scheme",
       "deprecated": true,
+      "x-removed-in": "4.0.0",
       "description": "Legacy authentication schemes for the webhook auth block. Bearer: token sent in Authorization header. HMAC-SHA256: legacy shared-secret signing. Both are deprecated; new integrations SHOULD omit the authentication block and use the RFC 9421 webhook signing profile (applicable on schemas where authentication is optional). Removed in AdCP 4.0.",
       "type": "string",
       "enum": [
@@ -346,14 +350,14 @@
       ]
     },
     "external:core/ext.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/ext.json",
       "title": "Extension Object",
       "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
       "type": "object",
       "additionalProperties": true
     },
     "external:core/context.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/context.json",
       "title": "Context Object",
       "description": "Opaque correlation data that is echoed unchanged in responses. Used for internal tracking, UI session IDs, trace IDs, and other caller-specific identifiers that don't affect protocol behavior. Context data is never parsed by AdCP agents - it's simply preserved and returned.",
       "type": "object",

package/dist/lib/schemas-data/3.2/mcp/2026-07-28/protocol/sync-principal-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/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.",
@@ -22,6 +22,7 @@
     "adcp_major_version": {
       "type": "integer",
       "deprecated": true,
+      "x-removed-in": "4.0.0",
       "description": "DEPRECATED in favor of adcp_version (release-precision string). Servers MUST continue to honor this field through 3.x. Removed in 4.0. Original semantics: the AdCP major version the buyer's payloads conform to. Sellers validate against their supported major_versions and return VERSION_UNSUPPORTED if unsupported. When omitted, the seller assumes its highest supported version.",
       "minimum": 1,
       "maximum": 99
@@ -180,7 +181,7 @@
   ],
   "$defs": {
     "external:core/version-envelope.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/version-envelope.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/version-envelope.json",
       "title": "AdCP Version Envelope",
       "description": "Release-precision AdCP protocol version negotiation fields. Composed via `allOf` into AdCP request schemas and shared response components so the version semantics live in one place. Strict (`additionalProperties: false`) request schemas also redeclare these two fields in their own `properties` via `$ref`, because draft-07 does not evaluate properties across `allOf`. The Trusted Match match requests are the exception: they inline both fields for their strict privacy boundary. 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",
@@ -199,6 +200,7 @@
         "adcp_major_version": {
           "type": "integer",
           "deprecated": true,
+          "x-removed-in": "4.0.0",
           "description": "DEPRECATED in favor of adcp_version (release-precision string). Servers MUST continue to honor this field through 3.x. Removed in 4.0. Original semantics: the AdCP major version the buyer's payloads conform to. Sellers validate against their supported major_versions and return VERSION_UNSUPPORTED if unsupported. When omitted, the seller assumes its highest supported version.",
           "minimum": 1,
           "maximum": 99
@@ -206,7 +208,7 @@
       }
     },
     "external:enums/principal-kind.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/principal-kind.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/enums/principal-kind.json",
       "title": "Principal Kind",
       "x-status": "experimental",
       "description": "Seller-resolved kind of the authenticated principal: an autonomous buyer-agent workload or an operator-side identity such as a person at the operator.",
@@ -217,7 +219,7 @@
       ]
     },
     "external:core/agent-notification-config.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/agent-notification-config.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/agent-notification-config.json",
       "title": "Agent Notification Config",
       "description": "Caller-scoped agent-level webhook subscription. Caller-anchored event types (capabilities.changed, principal.changed) always fire principal-wide; account-anchored event types may also be listed here with the explicit all_authorized_accounts acknowledgment and fire with per-delivery-attempt authorization scoping over the caller's currently authorized accounts. Registration goes through the task declared by get_adcp_capabilities.adcp.capability_changes.notifications.registration_task: sync_principal when the broader principal surface is supported, or the specialized sync_agent_notification_configs compatibility task. Both tasks operate on one underlying caller-scoped subscriber set. This surface is intentionally separate from account-level notification_configs[]: a registry or buyer can subscribe before it has an account, and one fire invalidates the agent-wide get_adcp_capabilities cache. The persisted set is scoped to the authenticated caller or registry identity, so one caller's declarative replacement cannot clear another caller's subscribers. As with other AdCP webhooks, the default signing scheme is the RFC 9421 webhook profile against the seller's brand.json agents[] JWKS; the optional authentication block opts into the deprecated Bearer / HMAC-SHA256 fallback for compatibility. Credentials and shared secrets in authentication.credentials are write-only and MUST NOT be echoed on reads. Sellers MUST verify endpoint control before activating a new or changed active agent-level notification config; delivery-time SSRF validation still applies to every fire.",
       "type": "object",
@@ -240,7 +242,7 @@
           "items": {
             "allOf": [
               {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:enums~1notification-type.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:enums~1notification-type.json"
               },
               {
                 "not": {
@@ -271,12 +273,13 @@
         "authentication": {
           "type": "object",
           "deprecated": true,
+          "x-removed-in": "4.0.0",
           "description": "Legacy authentication selector. Same precedence and semantics as `push-notification-config.authentication` and account-level `notification-config.authentication`: presence opts the seller into Bearer or HMAC-SHA256 signing; absence selects the default RFC 9421 webhook profile keyed off the seller's brand.json `agents[]` JWKS. Deprecated; removed in AdCP 4.0. Credentials are write-only and MUST NOT be echoed on reads.",
           "properties": {
             "schemes": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:enums~1auth-scheme.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:enums~1auth-scheme.json"
               },
               "minItems": 1,
               "maxItems": 1
@@ -298,7 +301,7 @@
           "description": "When false, the seller persists the configuration but suppresses fires. Use to pause a subscriber without losing the registration. Paused configs may skip only the outbound proof challenge while inactive; sellers MUST still enforce URL parsing, HTTPS, hostname normalization, and reserved-range rejection at write time. Reactivation requires full SSRF validation with connect pinning plus proof-of-control for any tuple without current valid proof."
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1ext.json"
         }
       },
       "required": [
@@ -360,7 +363,7 @@
       ]
     },
     "external:enums/notification-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/notification-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/enums/notification-type.json",
       "title": "Notification Type",
       "description": "Type of push notification fired by a seller agent. Media-buy-anchored cadence reports (`scheduled`, `final`, `delayed`, `adjusted`, `window_update`) fire against a media buy's `reporting_webhook`; `impairment` is media-buy-anchored but fires against `push_notification_config`. Account-anchored notifications include creative, account, product, signal, wholesale-feed, and reporting events, including `reporting.delivery_ready`, `reporting.status_changed`, and `reporting.ledger_changed`; these outlive any single media buy and fire against matching account `notification_configs[]`. The reporting events repair through `get_reporting_status`: delivery_ready is managed-delivery-only, while status_changed and ledger_changed are valid in every reporting tier. Caller-anchored notifications (`capabilities.changed`, `principal.changed`) fire against the caller-scoped subscriber set managed by `sync_principal` or the specialized `sync_agent_notification_configs` compatibility task. New notification types MUST declare their anchor (media-buy, account, or caller), logical notification_id semantics, repair key, and classification in enumDescriptions; only invalidation-only caller-eligible types flow through include_future_event_types. Account-level subscribers MUST reject media-buy- or caller-anchored event types, and persistent account- or caller-anchored types MUST NOT use push_notification_config. Caller-level entries MAY include account-anchored types only with all_authorized_accounts true; each delivery attempt, including retries, is scoped to accounts currently authorized for that caller. Caller-level entries MUST NOT include media-buy-anchored types. Caller- and account-level subscriptions to the same event are independent and receivers dedupe by logical notification_id.",
       "type": "string",
@@ -422,9 +425,10 @@
       }
     },
     "external:enums/auth-scheme.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/auth-scheme.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/enums/auth-scheme.json",
       "title": "Authentication Scheme",
       "deprecated": true,
+      "x-removed-in": "4.0.0",
       "description": "Legacy authentication schemes for the webhook auth block. Bearer: token sent in Authorization header. HMAC-SHA256: legacy shared-secret signing. Both are deprecated; new integrations SHOULD omit the authentication block and use the RFC 9421 webhook signing profile (applicable on schemas where authentication is optional). Removed in AdCP 4.0.",
       "type": "string",
       "enum": [
@@ -433,14 +437,14 @@
       ]
     },
     "external:core/ext.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/ext.json",
       "title": "Extension Object",
       "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
       "type": "object",
       "additionalProperties": true
     },
     "external:core/agent-reporting-destination.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/agent-reporting-destination.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/agent-reporting-destination.json",
       "title": "Agent Reporting Destination",
       "x-status": "experimental",
       "description": "Reusable, non-secret reporting destination owned by the authenticated caller's relationship with one seller. Exactly one delivery pattern per destination; pattern is the discriminator and matches the managed reporting delivery pattern vocabulary. It does not grant account authority: account/reporting configuration separately binds authorized data to the seller-issued destination_ref. Sellers key ownership to the stable transport principal, never a signing key, token, or request-body identity. Credentials, private keys, bearer profiles, signed URLs, and embedded passwords are forbidden. Sellers implementing this schema advertise protocol.principal.",
@@ -473,7 +477,7 @@
               "description": "True permits use. False suspends the destination: the seller MUST stop initiating new deliveries to every generation of this destination_id within the advertised suspension interval, and new account-level delivery configurations MUST NOT select it. Suspension does not delete caller-owned data already delivered."
             },
             "provider": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1delivery-provider.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1delivery-provider.json"
             },
             "transport": {
               "type": "string",
@@ -506,7 +510,7 @@
               "description": "Physical formats accepted by this file-transfer destination."
             },
             "accepted_verification_profiles": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1reporting-verification-profile-set.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1reporting-verification-profile-set.json"
             }
           },
           "required": [
@@ -549,7 +553,7 @@
               "description": "True permits use. False suspends the destination: the seller MUST stop initiating new deliveries to every generation of this destination_id within the advertised suspension interval, and new account-level delivery configurations MUST NOT select it. Suspension does not delete caller-owned data already delivered."
             },
             "provider": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1delivery-provider.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1delivery-provider.json"
             },
             "transport": {
               "type": "string",
@@ -566,7 +570,7 @@
               "description": "Provider-native project/dataset, database/schema, or catalog/schema locator. Printable ASCII without whitespace, '?', '#', '%', '\"', '<', or '>'. Never a credential or signed URL; sellers additionally screen and normalize per the secret_rejection and normalization rules."
             },
             "accepted_verification_profiles": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1reporting-verification-profile-set.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1reporting-verification-profile-set.json"
             }
           },
           "required": [
@@ -608,7 +612,7 @@
               "description": "True permits use. False suspends the destination: the seller MUST stop publishing new revisions to every generation of this destination_id within the advertised suspension interval, and new account-level delivery configurations MUST NOT select it. Suspension does not delete caller-owned data already delivered or revoke provider-side grants by itself."
             },
             "provider": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1delivery-provider.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1delivery-provider.json"
             },
             "transport": {
               "type": "string",
@@ -625,10 +629,10 @@
               "description": "Dataset-share access family, such as databricks_to_databricks, open_sharing, or secure_data_sharing."
             },
             "recipient": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1delivery-recipient.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1delivery-recipient.json"
             },
             "accepted_verification_profiles": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1reporting-verification-profile-set.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1reporting-verification-profile-set.json"
             }
           },
           "required": [
@@ -657,7 +661,7 @@
       }
     },
     "external:core/delivery-provider.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/delivery-provider.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/delivery-provider.json",
       "title": "Delivery Provider",
       "description": "Provider namespace for an external delivery or data-sharing service. This identifies a platform; it is not a credential, trust root, or authorization statement.",
       "type": "object",
@@ -674,7 +678,7 @@
       "additionalProperties": false
     },
     "external:core/reporting-verification-profile-set.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-verification-profile-set.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-verification-profile-set.json",
       "title": "Reporting Verification Profile Set",
       "description": "Verification profiles the destination can accept. native_commit requires provider-native transaction/version evidence plus counts and control totals; manifest_checksums requires a committed file manifest with cryptographic checksums; canonical_digest requires recomputation of the canonical logical-content digest. A reporting feed selects one profile from this allowed set according to the seller offering and the feed's strictness requirements.",
       "type": "array",
@@ -690,7 +694,7 @@
       "uniqueItems": true
     },
     "external:core/delivery-recipient.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/delivery-recipient.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/delivery-recipient.json",
       "title": "Delivery Recipient",
       "description": "Provider-interpreted recipient identity for a seller-hosted share. Examples include a sharing identifier or organization/account pair. The value is an identifier, never a credential.",
       "type": "object",
@@ -701,7 +705,7 @@
           "maxLength": 512
         },
         "cloud": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:enums~1delivery-recipient-cloud.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:enums~1delivery-recipient-cloud.json"
         },
         "region": {
           "type": "string",
@@ -723,7 +727,7 @@
       }
     },
     "external:enums/delivery-recipient-cloud.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/delivery-recipient-cloud.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/enums/delivery-recipient-cloud.json",
       "title": "Delivery Recipient Cloud",
       "x-status": "experimental",
       "description": "Cloud family hosting a delivery recipient's account, used together with region to disambiguate provider-native recipient identities.",
@@ -735,7 +739,7 @@
       ]
     },
     "external:core/principal-declarations.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/principal-declarations.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/principal-declarations.json",
       "title": "Agent Declarations",
       "x-status": "experimental",
       "description": "Bounded, non-secret facts the authenticated caller declares about what it can consume from this seller. This is the buyer-declared half of capability negotiation: get_adcp_capabilities stays objective seller facts, declarations stay caller facts, and the seller-computed accepted intersection is the negotiated contract for asynchronous interactions. Declarations exist chiefly because webhook fires have no request context to negotiate against: the durable declaration is the version and algorithm channel for pushes. Declarations are facts about consumption ability, never preferences, policies, or an open-ended feature language. Submitting an empty object clears the declared set.",
@@ -768,7 +772,7 @@
         "experimental_features": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1experimental-feature-id.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/mcp/2026-07-28/protocol/sync-principal-request.json#/$defs/external:core~1experimental-feature-id.json"
           },
           "minItems": 1,
           "maxItems": 32,
@@ -779,7 +783,7 @@
       "additionalProperties": false
     },
     "external:core/experimental-feature-id.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/experimental-feature-id.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/experimental-feature-id.json",
       "title": "Experimental Feature ID",
       "description": "Dot-separated lowercase identifier for an experimental AdCP surface, such as protocol.principal or media_buy.reporting_delivery.",
       "type": "string",
@@ -788,7 +792,7 @@
       "pattern": "^[a-z][a-z0-9_]*(\\.[a-z][a-z0-9_]*)*$"
     },
     "external:core/context.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/context.json",
       "title": "Context Object",
       "description": "Opaque correlation data that is echoed unchanged in responses. Used for internal tracking, UI session IDs, trace IDs, and other caller-specific identifiers that don't affect protocol behavior. Context data is never parsed by AdCP agents - it's simply preserved and returned.",
       "type": "object",