@adcp/sdk 15.8.1 → 16.0.0-beta.1

package/dist/lib/schemas-data/3.2/mcp/2026-07-28/media-buy/sync-catalogs-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json",
   "title": "Sync Catalogs Request",
   "description": "Request parameters for syncing buyer-managed catalog feeds, pushing immediate item availability overrides, and reading current availability state. Supports bulk operations across multiple catalog types. Existing catalogs matched by catalog_id are updated, new ones are created. When catalogs, item_availability_updates, and item_availability_queries are all omitted, the call is discovery-only.",
   "x-tool-summary": "List or synchronize buyer-managed account catalog feeds, suppress or restore specific items, and read current availability state.",
@@ -203,9 +203,9 @@
   ],
   "$defs": {
     "external:core/version-envelope.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/version-envelope.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/version-envelope.json",
       "title": "AdCP Version Envelope",
-      "description": "Release-precision AdCP protocol version negotiation fields. Composed via `allOf` into every AdCP request and response schema so the version semantics live in exactly one place. Distinct from `core/protocol-envelope.json`, which wraps responses at the transport layer (context_id / task_id / status / payload). This envelope is part of the payload itself.",
+      "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",
       "properties": {
         "adcp_version": {
@@ -229,7 +229,7 @@
       }
     },
     "external:core/account-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/account-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",
@@ -250,7 +250,7 @@
         {
           "properties": {
             "brand": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1brand-ref.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1brand-ref.json",
               "description": "Brand reference identifying the advertiser"
             },
             "operator": {
@@ -260,7 +260,7 @@
               "x-entity": "operator"
             },
             "operator_unit": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1operator-unit.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-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": {
@@ -328,7 +328,7 @@
       ]
     },
     "external:core/brand-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/brand-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",
@@ -339,7 +339,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.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1brand-id.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1brand-id.json",
           "description": "Brand identifier within the house portfolio. Optional for single-brand domains."
         },
         "countries": {
@@ -398,7 +398,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.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1assets~1image-asset.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1assets~1image-asset.json",
               "description": "Override logo asset."
             },
             "colors": {
@@ -457,7 +457,7 @@
       ]
     },
     "external:core/brand-id.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/brand-id.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",
@@ -472,7 +472,7 @@
       ]
     },
     "external:core/assets/image-asset.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/assets/image-asset.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/assets/image-asset.json",
       "title": "Image Asset",
       "description": "Image asset with URL and dimensions",
       "type": "object",
@@ -536,7 +536,7 @@
           "x-accessibility": true
         },
         "provenance": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1provenance.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1provenance.json",
           "description": "Provenance metadata for this asset, overrides manifest-level provenance"
         }
       },
@@ -549,13 +549,13 @@
       "additionalProperties": true
     },
     "external:core/provenance.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/provenance.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1digital-source-type.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1digital-source-type.json",
           "description": "IPTC-aligned classification of AI involvement in producing this content"
         },
         "synthetic_depiction": {
@@ -665,7 +665,7 @@
             "type": "object",
             "properties": {
               "method": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1embedded-provenance-method.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1embedded-provenance-method.json",
                 "description": "How provenance data is carried within the content"
               },
               "standard": {
@@ -716,7 +716,7 @@
             "type": "object",
             "properties": {
               "media_type": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1watermark-media-type.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1watermark-media-type.json",
                 "description": "Media category of the watermarked content"
               },
               "provider": {
@@ -744,7 +744,7 @@
                 "additionalProperties": false
               },
               "c2pa_action": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1c2pa-watermark-action.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1c2pa-watermark-action.json",
                 "description": "C2PA action classification for this watermark"
               },
               "embedded_at": {
@@ -795,7 +795,7 @@
                     "minProperties": 1,
                     "properties": {
                       "persistence": {
-                        "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1disclosure-persistence.json",
+                        "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1disclosure-persistence.json",
                         "description": "How long the disclosure must persist during content playback or display"
                       },
                       "min_duration_ms": {
@@ -807,13 +807,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.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1disclosure-position.json"
+                          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1disclosure-position.json"
                         },
                         "minItems": 1,
                         "uniqueItems": true
                       },
                       "ext": {
-                        "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1ext.json"
+                        "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1ext.json"
                       }
                     }
                   }
@@ -875,12 +875,12 @@
           }
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1ext.json"
         }
       }
     },
     "external:enums/digital-source-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/digital-source-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",
@@ -908,7 +908,7 @@
       }
     },
     "external:enums/embedded-provenance-method.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/embedded-provenance-method.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",
@@ -922,7 +922,7 @@
       }
     },
     "external:enums/watermark-media-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/watermark-media-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",
@@ -940,7 +940,7 @@
       }
     },
     "external:enums/c2pa-watermark-action.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/c2pa-watermark-action.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",
@@ -954,7 +954,7 @@
       }
     },
     "external:enums/disclosure-persistence.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/disclosure-persistence.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",
@@ -970,7 +970,7 @@
       }
     },
     "external:enums/disclosure-position.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/disclosure-position.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",
@@ -986,14 +986,14 @@
       ]
     },
     "external:core/ext.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/ext.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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.3/core/operator-unit.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",
@@ -1029,7 +1029,7 @@
       ]
     },
     "external:core/catalog.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/catalog.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/catalog.json",
       "title": "Catalog",
       "description": "A typed data feed. Catalogs carry the items, locations, stock levels, or pricing that publishers use to render ads. They can be synced to a platform via sync_catalogs (managed lifecycle with approval), provided inline, or fetched from an external URL. The catalog type determines the item schema and can be structural (offering, product, inventory, store, promotion) or vertical-specific (hotel, flight, job, vehicle, real_estate, education, destination, app). Selectors (ids, tags, category, query) filter items regardless of sourcing method.",
       "type": "object",
@@ -1044,7 +1044,7 @@
           "description": "Human-readable name for this catalog (e.g., 'Summer Products 2025', 'Amsterdam Store Locations')."
         },
         "type": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1catalog-type.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1catalog-type.json",
           "description": "Catalog type. Structural types: 'offering' (AdCP Offering objects), 'product' (ecommerce entries), 'inventory' (stock per location), 'store' (physical locations), 'promotion' (deals and pricing). Vertical types: 'hotel', 'flight', 'job', 'vehicle', 'real_estate', 'education', 'destination', 'app' — each with an industry-specific item schema."
         },
         "url": {
@@ -1053,11 +1053,11 @@
           "description": "URL to an external catalog feed. The platform fetches and resolves items from this URL. For offering-type catalogs, the feed contains an array of Offering objects. For other types, the feed format is determined by feed_format. When omitted with type 'product', the platform uses its synced copy of the brand's product catalog."
         },
         "feed_format": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1feed-format.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1feed-format.json",
           "description": "Format of the external feed at url. Required when url points to a non-AdCP feed (e.g., Google Merchant Center XML, Meta Product Catalog). Omit for offering-type catalogs where the feed is native AdCP JSON."
         },
         "update_frequency": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1update-frequency.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1update-frequency.json",
           "description": "How often the platform should re-fetch the feed from url. Only applicable when url is provided. Platforms may use this as a hint for polling schedules."
         },
         "items": {
@@ -1105,20 +1105,20 @@
           "type": "array",
           "description": "Event types that represent conversions for items in this catalog. Declares what events the platform should attribute to catalog items — e.g., a job catalog converts via submit_application, a product catalog via purchase. The event's content_ids field carries the item IDs that connect back to catalog items. Use content_id_type to declare what identifier type content_ids values represent.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1event-type.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1event-type.json"
           },
           "minItems": 1,
           "uniqueItems": true
         },
         "content_id_type": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1content-id-type.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1content-id-type.json",
           "description": "Identifier type that the event's content_ids field should be matched against for items in this catalog. For example, 'gtin' means content_ids values are Global Trade Item Numbers, 'sku' means retailer SKUs. Omit when using a custom identifier scheme not listed in the enum."
         },
         "feed_field_mappings": {
           "type": "array",
           "description": "Declarative normalization rules for external feeds. Maps non-standard feed field names, date formats, price encodings, and image URLs to the AdCP catalog item schema. Applied during sync_catalogs ingestion. Supports field renames, named transforms (date, divide, boolean, split), static literal injection, and assignment of image URLs to typed asset pools.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1catalog-field-mapping.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1catalog-field-mapping.json"
           },
           "minItems": 1
         }
@@ -1250,7 +1250,7 @@
       ]
     },
     "external:enums/catalog-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/catalog-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/catalog-type.json",
       "title": "Catalog Type",
       "description": "The type of catalog feed. Determines the item schema and how the platform resolves catalog items. Multiple catalog types can be synced to the same account and referenced together in creatives.",
       "type": "string",
@@ -1271,7 +1271,7 @@
       ]
     },
     "external:enums/feed-format.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/feed-format.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/feed-format.json",
       "title": "Feed Format",
       "description": "Catalog feed formats. Determines how the platform (seller) parses items from an external feed URL. Each named value is an externally-documented feed specification a seller parses natively without buyer-supplied feed_field_mappings; values are vendor spec names (proper nouns), not semantic categories. Use `custom` + feed_field_mappings for any feed whose shape is not one of the named formats.",
       "type": "string",
@@ -1297,7 +1297,7 @@
       }
     },
     "external:enums/update-frequency.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/update-frequency.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/update-frequency.json",
       "title": "Update Frequency",
       "description": "Frequency of product catalog updates",
       "type": "string",
@@ -1309,7 +1309,7 @@
       ]
     },
     "external:enums/event-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/event-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/event-type.json",
       "title": "Event Type",
       "description": "Standard marketing event types for event logging, aligned with IAB ECAPI",
       "type": "string",
@@ -1381,7 +1381,7 @@
       }
     },
     "external:enums/content-id-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/content-id-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/content-id-type.json",
       "title": "Content ID Type",
       "description": "Identifier type used in content_ids on conversion events to match back to catalog items. Omit when the identifier type is custom or not listed here.",
       "type": "string",
@@ -1401,7 +1401,7 @@
       ]
     },
     "external:core/catalog-field-mapping.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/catalog-field-mapping.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/catalog-field-mapping.json",
       "title": "Catalog Field Mapping",
       "description": "Declares how a field in an external feed maps to the AdCP catalog item schema. Used in sync_catalogs feed_field_mappings to normalize non-AdCP feeds (Google Merchant Center, LinkedIn Jobs XML, hotel XML, etc.) to the standard catalog item schema without requiring the buyer to preprocess every feed. Multiple mappings can assemble a nested object via dot notation (e.g., separate mappings for price.amount and price.currency).",
       "type": "object",
@@ -1453,7 +1453,7 @@
           "description": "Fallback value to use when feed_field is absent, null, or empty. Applied after any transform would have been applied. Allows optional feed fields to have a guaranteed baseline value."
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1ext.json"
         }
       },
       "allOf": [
@@ -1544,7 +1544,7 @@
       ]
     },
     "external:core/catalog-item-availability-update.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/catalog-item-availability-update.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/catalog-item-availability-update.json",
       "title": "Catalog Item Availability Update",
       "description": "An immediate buyer-authored availability override for an item in one immutable incarnation of a buyer-managed catalog. This overlay is distinct from seller review status: suppress makes an otherwise approved item ineligible, while restore removes only the buyer suppression and cannot override seller rejection, withdrawal, policy, rights, or inventory decisions. A suppress overlay persists across scheduled feed fetches and catalog upserts until an explicit restore, expires_at, or deletion of the containing catalog.",
       "type": "object",
@@ -1611,7 +1611,7 @@
           "description": "Optional expiry for a suppress overlay. At this instant the seller automatically removes the buyer-authored suppression as if it received restore. Valid only with action suppress; omit for an indefinite suppression. Sellers MUST reject a timestamp that is not in the future when the request is processed. On a repeated suppress, this value is complete replacement state: a changed timestamp replaces the prior expiry, and omission clears a prior expiry to make suppression indefinite. Either change returns status applied, not unchanged."
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:core~1ext.json"
         }
       },
       "required": [
@@ -1696,7 +1696,7 @@
       "additionalProperties": true
     },
     "external:core/catalog-item-availability-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/catalog-item-availability-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/catalog-item-availability-ref.json",
       "title": "Catalog Item Availability Reference",
       "description": "Unambiguous reference to an item availability overlay in one immutable incarnation of a buyer-managed catalog.",
       "type": "object",
@@ -1731,7 +1731,7 @@
       "additionalProperties": true
     },
     "external:enums/validation-mode.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/validation-mode.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/validation-mode.json",
       "title": "Validation Mode",
       "description": "Creative validation strictness levels",
       "type": "string",
@@ -1741,7 +1741,7 @@
       ]
     },
     "external:core/push-notification-config.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/push-notification-config.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",
@@ -1773,7 +1773,7 @@
               "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.3/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1auth-scheme.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/media-buy/sync-catalogs-request.json#/$defs/external:enums~1auth-scheme.json"
               },
               "minItems": 1,
               "maxItems": 1
@@ -1796,7 +1796,7 @@
       ]
     },
     "external:enums/auth-scheme.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/auth-scheme.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/auth-scheme.json",
       "title": "Authentication Scheme",
       "deprecated": true,
       "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.",
@@ -1807,7 +1807,7 @@
       ]
     },
     "external:core/context.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.3/core/context.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.4/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",