@adcp/sdk 15.9.7 → 15.9.8

package/dist/lib/schemas-data/3.2/media-buy/request-proposals-async-response-working.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/request-proposals-async-response-working.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/media-buy/request-proposals-async-response-working.json",
   "title": "Request Proposals - Working",
   "description": "Bounded working progress payload for request_proposals.",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/compact-task-working.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/compact-task-working.json"
     }
   ]
 }

package/dist/lib/schemas-data/3.2/media-buy/request-proposals-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/request-proposals-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/media-buy/request-proposals-request.json",
   "title": "Request Proposals Request",
   "description": "Ask a seller to create one or more indicative media-plan proposals from a brief. Provide exactly one brand source: either top-level brand or a natural-key account containing brand and operator. Each returned proposal_id identifies one immutable draft snapshot; revise or finalize it through refine_proposals, or decline it through decline_proposals.",
   "x-tool-summary": "Ask a seller to create one or more draft media-plan proposals from a campaign brief.",
@@ -14,10 +14,10 @@
   },
   "properties": {
     "adcp_version": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/version-envelope.json#/properties/adcp_version"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/version-envelope.json#/properties/adcp_version"
     },
     "adcp_major_version": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/version-envelope.json#/properties/adcp_major_version"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/version-envelope.json#/properties/adcp_major_version"
     },
     "context_id": {
       "type": "string",
@@ -27,7 +27,7 @@
     "context": {
       "allOf": [
         {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/context.json"
         }
       ],
       "x-adcp-schema-uri": "/schemas/core/context.json"
@@ -40,7 +40,7 @@
     "push_notification_config": {
       "allOf": [
         {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/push-notification-config.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/push-notification-config.json"
         }
       ],
       "x-adcp-schema-uri": "/schemas/core/push-notification-config.json"
@@ -55,13 +55,13 @@
     "account": {
       "allOf": [
         {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/canonical-account-ref.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/canonical-account-ref.json"
         }
       ],
       "description": "Alternative brand source for proposal terms. Provide either this natural-key account containing brand and operator or top-level brand, not both."
     },
     "brand": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/brand-key.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/brand-key.json",
       "description": "Alternative brand source for proposal terms. Provide either top-level brand or a natural-key account containing brand and operator, not both."
     },
     "brief": {
@@ -70,12 +70,12 @@
       "description": "Campaign goal, strategy, and requirements that are not represented in structured criteria."
     },
     "criteria": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/product-discovery-criteria.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/media-buy/product-discovery-criteria.json"
     },
     "opportunity": {
       "allOf": [
         {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/opportunity-context.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/opportunity-context.json"
         },
         {
           "properties": {
@@ -114,7 +114,7 @@
   ],
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/version-envelope.json"
     },
     {
       "not": {
@@ -133,5 +133,5 @@
       }
     }
   ],
-  "additionalProperties": false
+  "additionalProperties": true
 }

package/dist/lib/schemas-data/3.2/media-buy/request-proposals-response.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/request-proposals-response.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/media-buy/request-proposals-response.json",
   "title": "Request Proposals Response",
   "description": "One or more immutable draft media-plan proposals and compact canonical products referenced by their purchases. Products always carry product_id and name and never carry legacy named-format identifiers. During the AdCP 3.x compatibility window, an SDK projecting a valid products-only get_products brief result may instead return the deprecated products_available outcome with an explicit purchase continuation. Native 3.2 sellers MUST NOT use that compatibility outcome, and adapters MUST NOT fabricate a proposal, terms digest, or feed version.",
   "type": "object",
   "properties": {
     "adcp_version": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/version-envelope.json#/properties/adcp_version"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/version-envelope.json#/properties/adcp_version"
     },
     "outcome": {
       "type": "string",
@@ -34,7 +34,7 @@
       "items": {
         "allOf": [
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/canonical-proposal.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/canonical-proposal.json"
           },
           {
             "properties": {
@@ -62,7 +62,7 @@
       "type": "array",
       "minItems": 1,
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/canonical-product.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/canonical-product.json"
       }
     },
     "incomplete": {
@@ -87,7 +87,7 @@
             "minLength": 1
           },
           "estimated_wait": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/duration.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/duration.json"
           }
         },
         "required": [
@@ -255,7 +255,7 @@
       ]
     },
     "targeting_resolution": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/get-products-targeting-resolution.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/media-buy/get-products-targeting-resolution.json",
       "description": "Response-level confirmation of structured targeting interpreted from explicit hard requirements in the brief. Sellers MUST emit this when that interpretation materially affects eligibility, pricing, or forecasting; otherwise it remains a best practice. Product-specific changes to explicit criteria.targeting_overlay values remain on Product.targeting_resolution."
     },
     "status": {
@@ -277,14 +277,14 @@
     "errors": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/error.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/error.json"
       }
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
     },
     "replayed": {
       "type": "boolean",
@@ -475,7 +475,7 @@
       }
     },
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/compact-task-submitted.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/compact-task-submitted.json"
     }
   ],
   "not": {
@@ -499,8 +499,18 @@
         "required": [
           "wholesale_feed_version"
         ]
+      },
+      {
+        "required": [
+          "feed_version"
+        ]
+      },
+      {
+        "required": [
+          "pricing_version"
+        ]
       }
     ]
   },
-  "additionalProperties": false
+  "additionalProperties": true
 }

package/dist/lib/schemas-data/3.2/media-buy/sync-audiences-request.json

@@ -1,13 +1,13 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/sync-audiences-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/media-buy/sync-audiences-request.json",
   "title": "Sync Audiences Request",
   "description": "Request parameters for managing CRM-based audiences on an account with upsert semantics. Existing audiences matched by audience_id are updated, new ones are created. Members are specified as delta operations: add appends new members, remove drops existing ones. Recommend no more than 100,000 members per call; for larger lists, chunk and call incrementally using add/remove deltas. When delete_missing is true, buyer-managed audiences on the account not in this request are removed — do not combine with omitted audiences or all buyer-managed audiences will be deleted. When audiences is omitted, the call is discovery-only: it returns all audiences on the account without modification.",
   "x-tool-summary": "List or synchronize account audiences with upsert, member-delta, and optional replacement semantics.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/version-envelope.json"
     }
   ],
   "x-mutates-state": true,
@@ -20,7 +20,7 @@
       "pattern": "^[A-Za-z0-9_.:-]{16,255}$"
     },
     "account": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/account-ref.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/account-ref.json",
       "description": "Account to manage audiences for."
     },
     "audiences": {
@@ -65,7 +65,7 @@
             "type": "array",
             "description": "Members to add to this audience. Hashed before sending — normalize emails to lowercase+trim, phones to E.164.",
             "items": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/audience-member.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/audience-member.json"
             },
             "minItems": 1
           },
@@ -73,12 +73,12 @@
             "type": "array",
             "description": "Members to remove from this audience. If the same identifier appears in both add and remove in a single request, remove takes precedence.",
             "items": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/audience-member.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/audience-member.json"
             },
             "minItems": 1
           },
           "source": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/audience-source.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/audience-source.json",
             "description": "External source reference: the seller ingests membership from a shared dataset or vendor-distributed segment instead of inline member deltas. Mutually exclusive with add/remove — an audience is either buyer-pushed or externally sourced, and transport is fixed at creation: a cross-transport upsert (member deltas against a sourced audience, or source against a pushed one) is rejected with CONFLICT (error.field: audience_id); convert by delete-and-recreate. Only send source kinds whose activation pattern the seller declared via audience_activation (undeclared kinds are rejected with UNSUPPORTED_FEATURE). Experimental — see the media_buy.audience_activation feature."
           },
           "delete": {
@@ -86,7 +86,7 @@
             "description": "When true, delete this audience from the account entirely. All other fields on this audience object are ignored. Use this to delete a specific audience without affecting others."
           },
           "consent_basis": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/consent-basis.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/consent-basis.json",
             "description": "GDPR lawful basis for processing this audience list. Informational — not validated by the protocol, but required by some sellers operating in regulated markets (e.g. EU). When omitted, the buyer asserts they have a lawful basis appropriate to their jurisdiction."
           }
         },
@@ -120,10 +120,10 @@
       "description": "When true, buyer-managed audiences on the account not included in this sync will be removed. Does not affect seller-managed audiences. Do not combine with an omitted audiences array or all buyer-managed audiences will be deleted."
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/media-buy/sync-audiences-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/sync-audiences-response.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/media-buy/sync-audiences-response.json",
   "title": "Sync Audiences Response",
   "description": "Response from audience sync operation. Exactly one of three shapes: (1) synchronous success — per-audience results in the audiences array (best-effort processing with per-item status/failures); (2) terminal failure — errors array with no audiences processed; (3) submitted task envelope — status 'submitted' with task_id when the whole operation is queued (batch ingestion, governance-gated upload, or any flow where the seller cannot return per-audience results before the response is emitted). The submitted branch MAY carry advisory errors for non-blocking warnings; terminal failures belong in the error branch. Final per-audience results land on the task completion artifact, not this envelope. Per-audience asynchronous matching (an audience reported with status 'processing' while the rest of the sync resolves synchronously) belongs on the synchronous success branch via audience-status, NOT here — operation-level async is for when the seller has no per-item results to return yet. These three shapes are mutually exclusive — a response has exactly one.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/version-envelope.json"
     },
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/protocol-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/protocol-envelope.json"
     }
   ],
   "oneOf": [
@@ -49,7 +49,7 @@
                 "description": "Action taken for this audience. 'status' is present when action is created, updated, or unchanged. 'status' is absent when action is deleted or failed."
               },
               "status": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/audience-status.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/audience-status.json",
                 "description": "Matching status. Present when action is created, updated, or unchanged; absent when action is deleted or failed."
               },
               "uploaded_count": {
@@ -80,7 +80,7 @@
                   "type": "object",
                   "properties": {
                     "id_type": {
-                      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/match-id-type.json",
+                      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/match-id-type.json",
                       "description": "Identifier type. Combines hashed PII types (hashed_email, hashed_phone) with universal ID types (rampid, uid2, maid, etc.)."
                     },
                     "submitted": {
@@ -129,7 +129,7 @@
                     "description": "Source kind, echoed from the request."
                   },
                   "vendor": {
-                    "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/brand-ref.json",
+                    "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/brand-ref.json",
                     "description": "Vendor, echoed from the request."
                   },
                   "locator": {
@@ -172,7 +172,7 @@
                 "type": "array",
                 "description": "Errors for this audience (only present when action='failed')",
                 "items": {
-                  "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/error.json"
+                  "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/error.json"
                 }
               }
             },
@@ -209,10 +209,10 @@
           "description": "When true, this response contains simulated data from sandbox mode."
         },
         "context": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/context.json"
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
         }
       },
       "required": [
@@ -253,15 +253,15 @@
           "type": "array",
           "description": "Operation-level errors that prevented processing any audiences (e.g., authentication failure, account not found, invalid request format)",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/error.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/error.json"
           },
           "minItems": 1
         },
         "context": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/context.json"
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
         }
       },
       "required": [
@@ -322,14 +322,14 @@
           "type": "array",
           "description": "Optional advisory errors accompanying the submitted envelope. Use only for non-blocking warnings (e.g., throttled_severity advisories, governance observations). Terminal failures belong in the error branch, not here.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/error.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/error.json"
           }
         },
         "context": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/context.json"
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
         }
       },
       "required": [

package/dist/lib/schemas-data/3.2/media-buy/sync-catalogs-async-response-input-required.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/sync-catalogs-async-response-input-required.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/media-buy/sync-catalogs-async-response-input-required.json",
   "title": "Sync Catalogs - Input Required",
   "description": "Payload when sync_catalogs task is paused waiting for buyer clarification or approval.",
   "type": "object",
@@ -16,10 +16,10 @@
       "description": "Reason code indicating why buyer input is needed. APPROVAL_REQUIRED: platform requires explicit approval before activating the catalog. FEED_VALIDATION: feed URL returned unexpected format or schema errors. ITEM_REVIEW: platform flagged items for manual review. FEED_ACCESS: platform cannot access the feed URL (authentication, CORS, etc.)."
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.2/media-buy/sync-catalogs-async-response-submitted.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/sync-catalogs-async-response-submitted.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/media-buy/sync-catalogs-async-response-submitted.json",
   "title": "Sync Catalogs - Submitted",
   "description": "Async task envelope returned when sync_catalogs cannot be confirmed before the response — for example, when catalog ingestion and deduplication are queued for batch processing. The buyer invokes get_task_status with task_id or receives a webhook when the task completes; the per-catalog results land in the terminal result, not this envelope.",
   "type": "object",
@@ -24,14 +24,14 @@
       "type": "array",
       "description": "Optional advisory errors accompanying the submitted envelope. Use only for non-blocking warnings (e.g., throttled_severity advisories, governance observations). Terminal failures belong in the error branch, not here.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/error.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/error.json"
       }
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/media-buy/sync-catalogs-async-response-working.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/sync-catalogs-async-response-working.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/media-buy/sync-catalogs-async-response-working.json",
   "title": "Sync Catalogs - Working",
   "description": "Progress payload for active sync_catalogs task.",
   "type": "object",
@@ -46,10 +46,10 @@
       "description": "Total number of catalog items to process across all catalogs"
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.2/media-buy/sync-catalogs-request.json

@@ -1,13 +1,13 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/sync-catalogs-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.8/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.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/version-envelope.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/version-envelope.json"
     },
     {
       "not": {
@@ -34,14 +34,14 @@
       "pattern": "^[A-Za-z0-9_.:-]{16,255}$"
     },
     "account": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/account-ref.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/account-ref.json",
       "description": "Seller account containing these buyer-managed catalogs."
     },
     "catalogs": {
       "type": "array",
       "description": "Array of catalog feeds to sync (create or update). When omitted together with item_availability_updates and item_availability_queries, the call is discovery-only and returns all existing catalogs on the account without modification.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/catalog.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/catalog.json"
       },
       "minItems": 1,
       "maxItems": 50
@@ -50,7 +50,7 @@
       "type": "array",
       "description": "Immediate suppress or restore operations for items in buyer-managed catalogs. Sellers declaring media_buy.features.catalog_item_availability_updates MUST process these updates synchronously and MUST NOT silently ignore them or return a submitted task. A seller that does not declare the capability MUST reject the request with UNSUPPORTED_FEATURE before lookup or mutation and MUST NOT interpret it as discovery. The combined number of item_availability_updates and item_availability_queries MUST NOT exceed 1,000; excess entries are an operation-level INVALID_REQUEST before lookup or mutation. Each (catalog_id, catalog_generation, item_id) tuple MUST appear at most once in updates; a duplicate is an operation-level INVALID_REQUEST before mutation in every validation mode. For mixed catalog/update requests, the seller MUST validate and stage the entire request against the post-upsert candidate state, then commit catalog and availability changes atomically. It MUST reject before any mutation if synchronous atomic commit is unavailable. A successful suppress acknowledgement means the seller MUST stop selecting or rendering the item and every cached or pre-generated creative it materialized from the item. Seller-internal generation lineage MUST retain resolved_account_id, catalog_id, catalog_generation, and item_id. If the seller cannot enforce that guarantee, it MUST return a failed per-item result. Suppression persists across scheduled feed fetches and catalog upserts until explicit restore, expires_at, or deletion of the containing catalog. Restore removes only an existing buyer-authored overlay or tombstone in the same catalog generation and cannot override seller rejection, withdrawal, policy, rights, or inventory controls. A restore for an absent item without such prior state fails with REFERENCE_NOT_FOUND.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/catalog-item-availability-update.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/catalog-item-availability-update.json"
       },
       "minItems": 1,
       "maxItems": 1000
@@ -59,7 +59,7 @@
       "type": "array",
       "description": "Read current buyer-authored availability state. Queries require media_buy.features.catalog_item_availability_updates; a seller that does not declare it rejects with UNSUPPORTED_FEATURE before lookup. Any request containing queries is synchronous. In a mixed request the seller validates and stages catalog upserts and availability updates first, evaluates queries against that post-upsert/post-update candidate state, and atomically commits the staged mutations before returning those query results. If the mixed work cannot commit synchronously, it rejects before mutation. The seller returns exactly one item_availability_states entry per query in the same order and echoes request_index and the complete identity. Unknown, inaccessible, stale-generation, and unauthorized references use the normalized REFERENCE_NOT_FOUND shape described by validation_mode. Use a fresh idempotency_key for a current read; a replayed response is a historical snapshot.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/catalog-item-availability-ref.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/catalog-item-availability-ref.json"
       },
       "minItems": 1,
       "maxItems": 1000
@@ -85,19 +85,19 @@
       "description": "When true, preview catalog create, update, and delete changes without applying them. MUST NOT be combined with item_availability_updates."
     },
     "validation_mode": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/validation-mode.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/enums/validation-mode.json",
       "default": "strict",
       "description": "Validation strictness for semantically valid-looking catalog and item entries. In strict mode (default), an unknown, inaccessible, unauthorized, or stale-generation catalog/item reference, a known seller-managed catalog, a stale expected_overlay_revision, or another per-entry error fails the entire operation before any catalog or availability mutation. In lenient mode, the seller returns a positionally matched failed result for each such item entry and processes the remaining valid entries. Unknown, inaccessible, unauthorized, and stale-generation references MUST be observationally equivalent: code REFERENCE_NOT_FOUND, message exactly 'Catalog item not found', recovery 'correctable', and no field, suggestion, retry_after, issues, details, or resource metadata. Authorization and lookup MUST use the same externally observable failure path and SHOULD avoid materially distinguishable timing. A known seller-managed catalog may use INVALID_REQUEST only after catalog access is authorized. Request-schema failures, duplicate identity tuples, unsupported capability, batch-limit excess, dry_run conflicts, and mixed requests that cannot commit synchronously and atomically are operation-level failures before lookup or mutation in both modes. A stale revision uses CONFLICT without mutation."
     },
     "push_notification_config": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/push-notification-config.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/push-notification-config.json",
       "description": "Optional webhook configuration for async sync notifications. Publisher will send webhook when sync completes if operation takes longer than immediate response time (common for large feeds requiring platform review)."
     },
     "context": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/context.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/context.json"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.8/core/ext.json"
     }
   },
   "required": [