@adcp/sdk 15.9.6 → 15.9.8

package/dist/lib/schemas-data/3.2/mcp/2026-07-28/account/sync-accounts-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/account/sync-accounts-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json",
   "title": "Sync Accounts Request",
   "description": "Sync advertiser account state with a seller. Two modes, distinguished by the key on each per-account entry:\n\n- **Provisioning mode** (`brand` + `operator` + `billing` at the entry root): the agent declares the advertiser identity, operator, optional operator-owned buying unit, optional fixed account currency, conditionally required buyer-selected account timezone, sandbox disposition, and billing model. The seller provisions or links the corresponding advertiser object via upsert. `brand.countries`, `operator_unit.id`, `currency`, buyer-selected `timezone`, and `sandbox` participate in the buyer-declared natural key when present; `operator_unit.name` is display metadata only. The seller MAY echo a seller-assigned account_id but MUST continue accepting the complete natural-key AccountRef.\n\n- **Settings-update mode** (`account` field carrying an [`AccountRef`](/schemas/core/account-ref.json)): targets an existing account by seller/storefront `account_id` or buyer-declared natural key. The seller updates settable state without provisioning side effects. A complete `operator_identity` value reconciles the existing account to the buyer's desired operator domain and optional operator unit; omission leaves identity unchanged.\n\nExactly one key shape is allowed per entry. Sellers that do not implement one mode return `UNSUPPORTED_PROVISIONING` for that mode. Identity reconciliation is additionally gated by `get_adcp_capabilities.account.identity_updates`.",
   "x-tool-summary": "Provision advertiser accounts or update settings for existing accounts through declarative synchronization.",
@@ -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
@@ -481,7 +482,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.8/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",
@@ -500,6 +501,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
@@ -507,7 +509,7 @@
       }
     },
     "external:core/account-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/account-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/account-ref.json",
       "title": "Account Reference",
       "description": "Reference to an advertiser account by seller-assigned ID or natural key. account_id is the seller/storefront handle returned by list_accounts. The natural key is brand + operator + optional operator_unit.id + optional fixed currency + optional buyer-selected account timezone + sandbox; it describes the advertiser object the seller resolves or provisions. After a capability-gated identity rekey, the former natural key is tombstoned and returns ACCOUNT_MOVED to authorized callers rather than resolving or provisioning another account. brand.countries qualifies the advertiser's geographic identity. operator_unit identifies the operator-owned buying seat or business unit and is distinct from the seller account. operator_unit.name is display metadata and does not participate in identity. Use account_id when the seller or upstream platform owns the canonical account namespace; use the natural key for buyer-declared accounts (require_operator_auth: false).",
       "type": "object",
@@ -528,7 +530,7 @@
         {
           "properties": {
             "brand": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1brand-ref.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1brand-ref.json",
               "description": "Brand reference identifying the advertiser"
             },
             "operator": {
@@ -538,7 +540,7 @@
               "x-entity": "operator"
             },
             "operator_unit": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1operator-unit.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1operator-unit.json",
               "description": "Optional operator-owned business unit, agency seat, or platform account. Only id participates in the natural account key; name is mutable display metadata."
             },
             "currency": {
@@ -606,7 +608,7 @@
       ]
     },
     "external:core/brand-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/brand-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/brand-ref.json",
       "title": "Brand Reference",
       "description": "Reference to a brand by domain and optional brand_id. The domain hosts /.well-known/brand.json or is registered in the brand registry. For single-brand domains, brand_id can be omitted. For house-of-brands domains, brand_id identifies the specific brand. For creative production, brand.json is the canonical source of master brand identity (logo, palette, fonts, voice, and visual guidelines), subject only to the supported per-call fields in brand_kit_override. Catalogs supply product or item payload; catalog item asset groups, including property- or franchise-level logos, are item identity and do not override these master brand fields.",
       "type": "object",
@@ -617,7 +619,7 @@
           "pattern": "^[a-z0-9]([a-z0-9-]*[a-z0-9])?(\\.[a-z0-9]([a-z0-9-]*[a-z0-9])?)*$"
         },
         "brand_id": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1brand-id.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1brand-id.json",
           "description": "Brand identifier within the house portfolio. Optional for single-brand domains."
         },
         "countries": {
@@ -676,7 +678,7 @@
           "description": "Inline override for brand-kit fields normally resolved from `/.well-known/brand.json` on `domain` (logo, colors, voice, tagline). Use when brand.json is missing, stale, or inappropriate for this specific call — e.g., a campaign-scoped tagline, a co-branded creative, a freshly-rebranded color palette the brand.json hasn't shipped yet. Same inline-override pattern as `industries` and `data_subject_contestation` above: brand.json is canonical, the override is per-call. Adopters needing to override fields outside this subset (`voice_attributes`, `prohibited_terms`, etc.) MUST publish a different brand.json and reference it via a different `domain` — the inline override is intentionally narrow to a small high-traffic subset.\n\n**Merge semantics (normative).** The merge is **field-level**, not whole-object replacement. Each field within `brand_kit_override` (`logo`, `colors`, `voice`, `tagline`) is evaluated independently — when a field is present on the override the override value applies; when a field is absent the brand.json value applies (or is absent if brand.json doesn't carry one either). For composite fields (`colors.primary`, `colors.secondary`, `colors.accent`), the merge is one level deeper: each color slot is evaluated independently — a producer can override `colors.primary` while still inheriting `colors.secondary` from brand.json. SDKs MUST NOT treat a present `brand_kit_override.colors` as wiping the brand.json `colors` block entirely; only the per-slot fields present in the override take precedence. Without this rule, a partial-override semantics would diverge across SDKs and produce inconsistent rendering for the same payload.",
           "properties": {
             "logo": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1assets~1image-asset.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1assets~1image-asset.json",
               "description": "Override logo asset."
             },
             "colors": {
@@ -735,7 +737,7 @@
       ]
     },
     "external:core/brand-id.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/brand-id.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/brand-id.json",
       "title": "Brand ID",
       "description": "Identifier for a brand within a house portfolio. Must be lowercase alphanumeric with underscores only. The house chooses this identifier.",
       "type": "string",
@@ -750,7 +752,7 @@
       ]
     },
     "external:core/assets/image-asset.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/image-asset.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/assets/image-asset.json",
       "title": "Image Asset",
       "description": "Image asset with URL and dimensions",
       "type": "object",
@@ -814,7 +816,7 @@
           "x-accessibility": true
         },
         "provenance": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1provenance.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1provenance.json",
           "description": "Provenance metadata for this asset, overrides manifest-level provenance"
         }
       },
@@ -827,13 +829,13 @@
       "additionalProperties": true
     },
     "external:core/provenance.json": {
-      "$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/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1digital-source-type.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1digital-source-type.json",
           "description": "IPTC-aligned classification of AI involvement in producing this content"
         },
         "synthetic_depiction": {
@@ -943,7 +945,7 @@
             "type": "object",
             "properties": {
               "method": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1embedded-provenance-method.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1embedded-provenance-method.json",
                 "description": "How provenance data is carried within the content"
               },
               "standard": {
@@ -994,7 +996,7 @@
             "type": "object",
             "properties": {
               "media_type": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1watermark-media-type.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1watermark-media-type.json",
                 "description": "Media category of the watermarked content"
               },
               "provider": {
@@ -1022,7 +1024,7 @@
                 "additionalProperties": false
               },
               "c2pa_action": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1c2pa-watermark-action.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1c2pa-watermark-action.json",
                 "description": "C2PA action classification for this watermark"
               },
               "embedded_at": {
@@ -1073,7 +1075,7 @@
                     "minProperties": 1,
                     "properties": {
                       "persistence": {
-                        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1disclosure-persistence.json",
+                        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1disclosure-persistence.json",
                         "description": "How long the disclosure must persist during content playback or display"
                       },
                       "min_duration_ms": {
@@ -1085,13 +1087,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/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1disclosure-position.json"
+                          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1disclosure-position.json"
                         },
                         "minItems": 1,
                         "uniqueItems": true
                       },
                       "ext": {
-                        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1ext.json"
+                        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1ext.json"
                       }
                     }
                   }
@@ -1153,12 +1155,12 @@
           }
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1ext.json"
         }
       }
     },
     "external:enums/digital-source-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/digital-source-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/enums/digital-source-type.json",
       "title": "Digital Source Type",
       "description": "Classification of AI involvement in content creation, aligned with IPTC digitalsourcetype vocabulary. Used in provenance metadata to declare how a creative asset, artifact, or individual asset was produced.",
       "type": "string",
@@ -1186,7 +1188,7 @@
       }
     },
     "external:enums/embedded-provenance-method.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/embedded-provenance-method.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/enums/embedded-provenance-method.json",
       "title": "Embedded Provenance Method",
       "description": "How provenance data is carried within the content stream. Distinguishes between format-level manifest embedding (where the manifest travels inside the file container) and provenance markers (where invisible markers in the content itself encode or reference a provenance record). Both survive operations that strip sidecar metadata, but provenance markers additionally survive content-level transformations such as copy-paste, reformatting, and CMS re-encoding.",
       "type": "string",
@@ -1200,7 +1202,7 @@
       }
     },
     "external:enums/watermark-media-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/watermark-media-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/enums/watermark-media-type.json",
       "title": "Watermark Media Type",
       "description": "Media category of a content watermark. Identifies what kind of content the watermark is applied to, which determines the detection and verification methods required.",
       "type": "string",
@@ -1218,7 +1220,7 @@
       }
     },
     "external:enums/c2pa-watermark-action.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/c2pa-watermark-action.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/enums/c2pa-watermark-action.json",
       "title": "C2PA Watermark Action",
       "description": "C2PA action classification for a content watermark. Distinguishes watermarks that are cryptographically linked to a C2PA manifest (bound) from watermarks that exist independently (unbound). Aligns with the c2pa.watermarked.* action family in the C2PA action taxonomy.",
       "type": "string",
@@ -1232,7 +1234,7 @@
       }
     },
     "external:enums/disclosure-persistence.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/disclosure-persistence.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/enums/disclosure-persistence.json",
       "title": "Disclosure Persistence",
       "description": "How long a disclosure must persist during content playback or display. Different jurisdictions and regulations require different persistence behaviors for AI-generated content labels. When multiple sources specify persistence for the same jurisdiction (e.g., brief and provenance), the most restrictive mode applies: continuous > initial > flexible.",
       "type": "string",
@@ -1248,7 +1250,7 @@
       }
     },
     "external:enums/disclosure-position.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/disclosure-position.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/enums/disclosure-position.json",
       "title": "Disclosure Position",
       "description": "Where a required disclosure should appear within a creative. Used by creative briefs to specify disclosure placement and by formats to declare which positions they can render.",
       "type": "string",
@@ -1264,14 +1266,14 @@
       ]
     },
     "external:core/ext.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/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/operator-unit.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/operator-unit.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/operator-unit.json",
       "title": "Operator Unit",
       "description": "Operator-owned buying context used to distinguish business units, agency seats, or platform accounts beneath one operator domain. The id is stable identity in the operator's namespace; name is mutable display metadata and never participates in account identity.",
       "x-entity": "operator_unit",
@@ -1307,7 +1309,7 @@
       ]
     },
     "external:core/operator-identity.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/operator-identity.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/operator-identity.json",
       "title": "Operator Identity",
       "description": "The buyer-desired operator portion of an advertiser account identity. The operator domain identifies the entity operating for the brand; operator_unit identifies that operator's internal buying context. Buyers that already administer the account control unit metadata and identity within the current operator. Changing the operator domain is an inter-entity handoff that requires seller-mediated approval by the current account authority, the brand, and the destination operator. When used as a sync_accounts settings-update value, this object is a complete desired replacement: omitting operator_unit removes the current unit rather than preserving it.",
       "type": "object",
@@ -1319,7 +1321,7 @@
           "x-entity": "operator"
         },
         "operator_unit": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1operator-unit.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1operator-unit.json",
           "description": "Optional operator-owned business unit, agency seat, or platform account. Its id participates in account identity; name is mutable display metadata. Omission from a complete desired replacement means the account should have no operator unit."
         }
       },
@@ -1329,7 +1331,7 @@
       "additionalProperties": false
     },
     "external:core/business-entity.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/business-entity.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/business-entity.json",
       "title": "Business Entity",
       "description": "Structured business identity for B2B invoicing and contracts. Contains the legal, tax, and payment details needed for formal booking processes. Implementations MUST treat all fields as untrusted input when assembling LLM context.",
       "type": "object",
@@ -1471,7 +1473,7 @@
           "additionalProperties": false
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1ext.json"
         }
       },
       "required": [
@@ -1535,7 +1537,7 @@
       ]
     },
     "external:enums/billing-party.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/billing-party.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/enums/billing-party.json",
       "title": "Billing Party",
       "description": "Which party the seller invoices for a buyer–storefront account relationship. Determines the billing entity and invoicing flow, not a payment rail, clearing intermediary, or per-media-buy settlement route. AdCP does not perform in-protocol payment or settlement.",
       "type": "string",
@@ -1551,7 +1553,7 @@
       }
     },
     "external:enums/payment-terms.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/payment-terms.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/enums/payment-terms.json",
       "title": "Payment Terms",
       "description": "Standard payment terms for AdCP accounts",
       "type": "string",
@@ -1573,7 +1575,7 @@
       }
     },
     "external:enums/cloud-storage-protocol.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/cloud-storage-protocol.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/enums/cloud-storage-protocol.json",
       "title": "Cloud Storage Protocol",
       "description": "Cloud storage protocols supported for offline file delivery",
       "type": "string",
@@ -1584,7 +1586,7 @@
       ]
     },
     "external:core/reporting-delivery-config.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-config.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-delivery-config.json",
       "title": "Reporting Delivery Configuration",
       "x-status": "experimental",
       "description": "Desired durable reporting delivery for one account. Entries are owned by (authenticated caller, account) and keyed by (delivery_config_id, delivery_config_version). The generation's feed, report definition, profile, scope, coverage requirement, finality, schedule, method, and immutable destination generation are fixed; only lifecycle intent (`active` and `revocation_effective_at`) may change without a new generation. Sellers reject a reused version with different immutable content. sync_accounts replacement semantics apply only to the calling principal's set. Omission leaves that set unchanged; [] deactivates that caller's set and stops new publication without affecting another caller. Sellers implementing this schema MUST advertise media_buy.reporting_delivery in experimental_features.",
@@ -1617,7 +1619,7 @@
           "description": "Whether new reporting obligations should use this configuration. Inactive configurations remain visible for historical resolution."
         },
         "feed_purpose": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-offering.json/$defs/ReportingFeedPurpose"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-offering.json/$defs/ReportingFeedPurpose"
         },
         "report_definition_id": {
           "type": "string",
@@ -1645,7 +1647,7 @@
             "media_buy_ids": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
               },
               "minItems": 1,
               "uniqueItems": true
@@ -1664,11 +1666,11 @@
           "description": "Whether every package in the resolved media-buy scope must support the exact selected offering. full fails closed when any package is unsupported or unknown. allow_partial permits publication only for the explicitly covered package denominator; every revision and status response still exposes partial coverage and MUST NOT present covered-subset totals as whole-buy totals."
         },
         "required_finality": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1reporting-finality.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1reporting-finality.json",
           "description": "Finality the durable path must ultimately provide. Snapshot delivery may still precede an official requirement."
         },
         "reconciliation_mode": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-reconciliation-mode.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-reconciliation-mode.json",
           "description": "Whether producer-side delivery evidence is sufficient or the selected consumer must submit an authenticated matching receipt. A seller-authoritative billing feed MUST use consumer_receipt."
         },
         "authoritative_party": {
@@ -1681,10 +1683,10 @@
           "description": "Reserved: which party's count of this feed is authoritative. seller (the default, and the only value any 3.2 seller accepts) means the seller produces every revision and the consumer may only attest to what it consumed. consumer is reserved for the buyer-deposited billing revision task scoped to a later minor; until that task exists sellers MUST reject it with UNSUPPORTED_FEATURE. Reserving the field now keeps a future buyer-basis billing feed additive instead of breaking the billing-feed constraints. See https://github.com/adcontextprotocol/adcp/issues/7440."
         },
         "schedule": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-schedule.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-schedule.json"
         },
         "method": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-method.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-method.json"
         },
         "revocation_effective_at": {
           "type": "string",
@@ -1775,7 +1777,7 @@
       "additionalProperties": false
     },
     "external:core/reporting-delivery-offering.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-offering.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-delivery-offering.json",
       "title": "Reporting Delivery Offering",
       "x-status": "experimental",
       "description": "One atomic combination a seller can honor. Buyers MUST NOT form a cross-product from separate capability arrays; each installed configuration selects one offering_id and values within that offering. A Core API-delivered offering requires no Managed external-materialization canonicalization code or contract, but every resulting revision still carries the fixed RFC 8785/JCS revision-binding canonicalization and digest.",
@@ -1789,7 +1791,7 @@
           "x-entity": "reporting_offering"
         },
         "feed_purpose": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-offering.json/$defs/ReportingFeedPurpose"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-offering.json/$defs/ReportingFeedPurpose"
         },
         "report_definition_id": {
           "type": "string",
@@ -1855,7 +1857,7 @@
             "primary_keys": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-canonicalization-contract.json/$defs/ReportingPrimaryKey"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-canonicalization-contract.json/$defs/ReportingPrimaryKey"
               },
               "minItems": 1,
               "uniqueItems": true
@@ -1899,20 +1901,20 @@
           "additionalProperties": false
         },
         "schedule": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-schedule-offering.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-schedule-offering.json",
           "description": "Period and availability SLA this offering can honor. For example, PT1H with snapshot finality explicitly advertises hourly provisional snapshots; a separate P1D official offering advertises daily finalized reporting."
         },
         "supported_finality": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1reporting-finality.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1reporting-finality.json"
           },
           "minItems": 1,
           "uniqueItems": true,
           "description": "Finality classes available under this exact report definition, schedule, and delivery method. snapshot is an explicit provisional capability, not inferred from poll frequency. Use separate atomic offerings when snapshot and official schedules or methods differ."
         },
         "reconciliation_mode": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-reconciliation-mode.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-reconciliation-mode.json",
           "description": "Receipt contract included in this atomic offering. Billing offerings MUST require consumer_receipt."
         },
         "method": {
@@ -1920,7 +1922,7 @@
           "description": "Managed delivery method for this offering. Omit for a Core (API-delivered) offering: rows flow through existing get_media_buy_delivery and reporting_webhook transports and no destination is involved. Present only when the seller advertises managed_delivery.",
           "properties": {
             "pattern": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-offering.json/$defs/ReportingDeliveryPattern"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-offering.json/$defs/ReportingDeliveryPattern"
             },
             "transport": {
               "type": "string",
@@ -1929,7 +1931,7 @@
               "pattern": "^[a-z][a-z0-9_.-]*$"
             },
             "orchestration": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-method.json/$defs/ReportingOrchestration"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-method.json/$defs/ReportingOrchestration"
             },
             "destination_modes": {
               "type": "array",
@@ -1995,7 +1997,7 @@
                   "maxLength": 512
                 },
                 "cloud": {
-                  "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-dataset-share-destination.json/$defs/ReportingCloud"
+                  "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-dataset-share-destination.json/$defs/ReportingCloud"
                 },
                 "region": {
                   "type": "string",
@@ -2020,7 +2022,7 @@
             "reader_compatibility": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-resource.json/$defs/ReportingReaderCompatibilityItem"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-resource.json/$defs/ReportingReaderCompatibilityItem"
               },
               "uniqueItems": true
             }
@@ -2172,7 +2174,7 @@
       }
     },
     "external:core/reporting-canonicalization-contract.json": {
-      "$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.",
@@ -2198,7 +2200,7 @@
         "primary_keys": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-canonicalization-contract.json/$defs/ReportingPrimaryKey"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-canonicalization-contract.json/$defs/ReportingPrimaryKey"
           },
           "minItems": 1,
           "uniqueItems": true,
@@ -2359,7 +2361,7 @@
       }
     },
     "external:core/reporting-schedule-offering.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-schedule-offering.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-schedule-offering.json",
       "title": "Reporting Schedule Offering",
       "x-status": "experimental",
       "description": "Schedule constraint advertised by a seller. Unlike an installed reporting-schedule, an offering may resolve an account-specific upstream source timezone or let a billing-cycle configuration select its own anchor and IANA timezone.",
@@ -2370,7 +2372,7 @@
           "pattern": "^P(?=.*[1-9])(?=\\d|T)(?:\\d+Y)?(?:\\d+M)?(?:\\d+D)?(?:T(?=\\d)(?:\\d+H)?(?:\\d+M)?(?:\\d+S)?)?$"
         },
         "alignment": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-schedule.json/$defs/ReportingScheduleAlignment"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-schedule.json/$defs/ReportingScheduleAlignment"
         },
         "period_anchor_policy": {
           "type": "string",
@@ -2553,7 +2555,7 @@
       "additionalProperties": false
     },
     "external:core/reporting-schedule.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-schedule.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-schedule.json",
       "title": "Reporting Schedule",
       "x-status": "experimental",
       "description": "The period and deadline contract from which reporting obligations are created. Every elapsed period produces an obligation even when it has zero rows or production fails, so a consumer can distinguish empty from missing.",
@@ -2565,7 +2567,7 @@
           "description": "Strictly positive ISO 8601 duration of each reporting period, such as PT15M, P1D, or P1M."
         },
         "alignment": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-schedule.json/$defs/ReportingScheduleAlignment"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-schedule.json/$defs/ReportingScheduleAlignment"
         },
         "period_anchor": {
           "type": "string",
@@ -2669,7 +2671,7 @@
       }
     },
     "external:enums/reporting-finality.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/reporting-finality.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/enums/reporting-finality.json",
       "title": "Reporting Finality",
       "description": "Finality of a reporting revision. Snapshot revisions are provisional and may be superseded. An official revision is the immutable, invoice-addressable close for its reporting slice and MUST NOT be superseded; later source corrections are explicit reporting adjustments rather than silent replacement revisions.",
       "type": "string",
@@ -2683,7 +2685,7 @@
       }
     },
     "external:core/reporting-reconciliation-mode.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-reconciliation-mode.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-reconciliation-mode.json",
       "title": "Reporting Reconciliation Mode",
       "x-status": "experimental",
       "description": "Whether producer delivery evidence is sufficient or an authenticated consumer receipt is required.",
@@ -2694,7 +2696,7 @@
       ]
     },
     "external:core/reporting-delivery-method.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-method.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-delivery-method.json",
       "title": "Reporting Delivery Method",
       "x-status": "experimental",
       "description": "Provider-neutral durable reporting delivery method. The caller may request protocol-managed provisioning or reuse an existing seller-issued binding. Transport names are open so new platforms do not require an AdCP enum change. Credentials, bearer profiles, and private keys MUST NOT appear. Sellers implementing this schema MUST advertise media_buy.reporting_delivery in experimental_features.",
@@ -2717,10 +2719,10 @@
               "description": "Storage transport such as s3, gcs, azure_blob, or sftp."
             },
             "orchestration": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-method.json/$defs/ReportingOrchestration"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-method.json/$defs/ReportingOrchestration"
             },
             "destination": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-write-destination.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-write-destination.json"
             },
             "format": {
               "type": "string",
@@ -2760,10 +2762,10 @@
               "description": "Sharing transport such as delta_sharing, snowflake_secure_sharing, or bigquery_authorized_view."
             },
             "orchestration": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-method.json/$defs/ReportingOrchestration"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-method.json/$defs/ReportingOrchestration"
             },
             "destination": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-dataset-share-destination.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-dataset-share-destination.json"
             }
           },
           "required": [
@@ -2791,10 +2793,10 @@
               "description": "Warehouse or transfer transport such as bigquery, snowflake, databricks_sql, or gam_bigquery_transfer."
             },
             "orchestration": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-method.json/$defs/ReportingOrchestration"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-delivery-method.json/$defs/ReportingOrchestration"
             },
             "destination": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-write-destination.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-write-destination.json"
             }
           },
           "required": [
@@ -2820,7 +2822,7 @@
       }
     },
     "external:core/reporting-write-destination.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-write-destination.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-write-destination.json",
       "title": "Reporting Write Destination",
       "x-status": "experimental",
       "description": "Storage or warehouse destination for durable reporting. The caller either references an existing seller-issued immutable destination generation or asks the seller to validate and bind a provider-native location. A destination_ref is owned by the stable authenticated principal's relationship with this seller and may be reused across accounts; each account delivery configuration separately authorizes its feed and scope. Changing proof-bound coordinates or the accepted delivery contract produces a new destination_ref. Access grants name advertised producer identities; credentials never transit AdCP.",
@@ -2896,7 +2898,7 @@
       }
     },
     "external:core/reporting-dataset-share-destination.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-dataset-share-destination.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-dataset-share-destination.json",
       "title": "Reporting Dataset Share Destination",
       "x-status": "experimental",
       "description": "Recipient configuration for a producer-hosted reporting share. The caller either references an existing seller-issued immutable recipient/destination generation or asks the seller to provision one for the named recipient. A destination_ref is owned by the stable authenticated principal's relationship with this seller and may be reused across accounts; each account delivery configuration separately authorizes disclosure of its feed and scope. Changing proof-bound recipient coordinates or the accepted delivery contract produces a new destination_ref. No bearer profile, token, private key, password, or other credential may appear here.",
@@ -2961,7 +2963,7 @@
                   "maxLength": 512
                 },
                 "cloud": {
-                  "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-dataset-share-destination.json/$defs/ReportingCloud"
+                  "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-dataset-share-destination.json/$defs/ReportingCloud"
                 },
                 "region": {
                   "type": "string",
@@ -3010,7 +3012,7 @@
       }
     },
     "external:core/reporting-resource.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-resource.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-resource.json",
       "title": "Reporting Resource",
       "x-status": "experimental",
       "description": "Secret-free authenticated descriptor for an exact reporting materialization. The descriptor MUST select immutable bytes or a provider-native immutable snapshot/version so an exact older revision never resolves to mutable latest state. Callers resolve access through the previously validated caller/account-bound destination/share binding, never from credentials embedded here. No field, including future extensions, may contain credentials, signed URLs, bearer material, or private keys.",
@@ -3040,7 +3042,7 @@
           "description": "Non-secret provider-native object, relation, or share identifier. MUST NOT contain an activation URL, signed URL, bearer token, password, private key, or embedded credential."
         },
         "native_version_ref": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-native-version-ref.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-native-version-ref.json"
         },
         "manifest_version": {
           "type": "string",
@@ -3069,7 +3071,7 @@
           "type": "array",
           "description": "Reader features or format constraints required to consume this resource. Readiness verification MUST use a representative supported reader.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-resource.json/$defs/ReportingReaderCompatibilityItem"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-resource.json/$defs/ReportingReaderCompatibilityItem"
           },
           "uniqueItems": true
         }
@@ -3133,7 +3135,7 @@
       }
     },
     "external:core/reporting-native-version-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-native-version-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-native-version-ref.json",
       "title": "Reporting Native Version Reference",
       "x-status": "experimental",
       "description": "Credential-free, decoded provider-native immutable version reference, such as an S3 VersionId, GCS generation, table version, transaction, snapshot, manifest generation, job, or run. This is not URI-encoded or concatenated into an object_ref; URI-encode it only when constructing a provider request. The 1024-character limit accommodates a provider value of up to 1024 UTF-8 bytes because every Unicode character occupies at least one UTF-8 byte; JSON Schema maxLength counts characters rather than bytes.",
@@ -3142,7 +3144,7 @@
       "maxLength": 1024
     },
     "external:core/reporting-coverage.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-coverage.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/reporting-coverage.json",
       "title": "Reporting Coverage",
       "x-status": "experimental",
       "description": "Exact reporting-support denominator for one offering at one evaluation boundary. Coverage is independent of freshness, finality, and delivery health. It prevents a covered subset from being represented as a complete media-buy or campaign total.",
@@ -3164,7 +3166,7 @@
         "media_buy_ids": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
           },
           "uniqueItems": true,
           "description": "Exact media-buy denominator, including unsupported and unknown buys. An empty array is an explicitly evaluated zero-buy scope."
@@ -3172,35 +3174,35 @@
         "fully_covered_media_buy_ids": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
           },
           "uniqueItems": true
         },
         "partially_covered_media_buy_ids": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
           },
           "uniqueItems": true
         },
         "unsupported_media_buy_ids": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
           },
           "uniqueItems": true
         },
         "unknown_media_buy_ids": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
           },
           "uniqueItems": true
         },
         "package_ids": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingPackageId"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingPackageId"
           },
           "uniqueItems": true,
           "description": "Exact package denominator for the evaluated media buys."
@@ -3208,21 +3210,21 @@
         "covered_package_ids": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingPackageId"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingPackageId"
           },
           "uniqueItems": true
         },
         "unsupported_package_ids": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingPackageId"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingPackageId"
           },
           "uniqueItems": true
         },
         "unknown_package_ids": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingPackageId"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingPackageId"
           },
           "uniqueItems": true
         },
@@ -3243,12 +3245,12 @@
                 ]
               },
               "media_buy_id": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingMediaBuyId"
               },
               "package_ids": {
                 "type": "array",
                 "items": {
-                  "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingPackageId"
+                  "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1reporting-coverage.json/$defs/ReportingPackageId"
                 },
                 "minItems": 1,
                 "uniqueItems": true
@@ -3300,7 +3302,7 @@
       }
     },
     "external:core/notification-config.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/notification-config.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/core/notification-config.json",
       "title": "Notification Config",
       "description": "Account-level webhook subscription for notifications whose lifecycle outlives any single media buy — creative state changes, library purges, account status changes, wholesale feed change webhooks, and future account-anchored resource events after those event types are added to this schema. This is distinct from `push-notification-config.json`, which anchors at a per-resource operation (a single task or media buy). The one-shot `sync_accounts.push_notification_config` channel may report the first async result of a provisioning request, while durable account lifecycle events such as later `payment_required` or `suspended` transitions use `account.status_changed` here. An account MAY register multiple notification configs to fan a single seller's events out to multiple buyer-side endpoints; each entry filters by `event_types`. As with push-notification-config, the default signing scheme is the AdCP 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 — sellers MUST NOT echo them back in `list_accounts` responses. Sellers MUST verify endpoint control before activating a new or changed active account-level notification config; delivery-time SSRF validation still applies to every fire.",
       "type": "object",
@@ -3358,12 +3360,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` — 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. The same signed-registration downgrade-resistance rules apply to accounts[].notification_configs[].authentication. Deprecated; removed in AdCP 4.0. Credentials are write-only and MUST NOT be echoed on `list_accounts` reads.",
           "properties": {
             "schemes": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1auth-scheme.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1auth-scheme.json"
               },
               "minItems": 1,
               "maxItems": 1
@@ -3385,7 +3388,7 @@
           "description": "When false, the seller persists the configuration but suppresses fires. Use to pause a noisy subscriber without losing the registration. Sellers MUST NOT skip persisting the entry when `active: false` — the buyer's next `sync_accounts` MUST observe the same array, otherwise the buyer cannot distinguish pause from drop. 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/account/sync-accounts-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:core~1ext.json"
         }
       },
       "required": [
@@ -3493,9 +3496,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.8/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": [
@@ -3504,7 +3508,7 @@
       ]
     },
     "external:core/push-notification-config.json": {
-      "$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",
@@ -3530,13 +3534,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/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1auth-scheme.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.8/mcp/2026-07-28/account/sync-accounts-request.json#/$defs/external:enums~1auth-scheme.json"
               },
               "minItems": 1,
               "maxItems": 1
@@ -3559,7 +3564,7 @@
       ]
     },
     "external:core/context.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.8/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",