@adcp/sdk 15.9.3 → 15.9.4

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

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json",
   "title": "Sync Plans Request",
   "description": "Push campaign plans to the governance agent. A plan defines the authorized parameters for a campaign -- budget limits, channels, flight dates, and authorized markets.",
   "type": "object",
@@ -469,7 +469,7 @@
   "additionalProperties": true,
   "$defs": {
     "external:core/version-envelope.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/version-envelope.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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",
@@ -495,7 +495,7 @@
       }
     },
     "external:core/brand-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/brand-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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",
@@ -506,7 +506,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.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1brand-id.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1brand-id.json",
           "description": "Brand identifier within the house portfolio. Optional for single-brand domains."
         },
         "countries": {
@@ -565,7 +565,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.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1assets~1image-asset.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1assets~1image-asset.json",
               "description": "Override logo asset."
             },
             "colors": {
@@ -624,7 +624,7 @@
       ]
     },
     "external:core/brand-id.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/brand-id.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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",
@@ -639,7 +639,7 @@
       ]
     },
     "external:core/assets/image-asset.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/assets/image-asset.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/image-asset.json",
       "title": "Image Asset",
       "description": "Image asset with URL and dimensions",
       "type": "object",
@@ -703,7 +703,7 @@
           "x-accessibility": true
         },
         "provenance": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1provenance.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1provenance.json",
           "description": "Provenance metadata for this asset, overrides manifest-level provenance"
         }
       },
@@ -716,13 +716,13 @@
       "additionalProperties": true
     },
     "external:core/provenance.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/provenance.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1digital-source-type.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1digital-source-type.json",
           "description": "IPTC-aligned classification of AI involvement in producing this content"
         },
         "synthetic_depiction": {
@@ -832,7 +832,7 @@
             "type": "object",
             "properties": {
               "method": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1embedded-provenance-method.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1embedded-provenance-method.json",
                 "description": "How provenance data is carried within the content"
               },
               "standard": {
@@ -883,7 +883,7 @@
             "type": "object",
             "properties": {
               "media_type": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1watermark-media-type.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1watermark-media-type.json",
                 "description": "Media category of the watermarked content"
               },
               "provider": {
@@ -911,7 +911,7 @@
                 "additionalProperties": false
               },
               "c2pa_action": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1c2pa-watermark-action.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1c2pa-watermark-action.json",
                 "description": "C2PA action classification for this watermark"
               },
               "embedded_at": {
@@ -962,7 +962,7 @@
                     "minProperties": 1,
                     "properties": {
                       "persistence": {
-                        "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1disclosure-persistence.json",
+                        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1disclosure-persistence.json",
                         "description": "How long the disclosure must persist during content playback or display"
                       },
                       "min_duration_ms": {
@@ -974,13 +974,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.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1disclosure-position.json"
+                          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1disclosure-position.json"
                         },
                         "minItems": 1,
                         "uniqueItems": true
                       },
                       "ext": {
-                        "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
+                        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
                       }
                     }
                   }
@@ -1042,12 +1042,12 @@
           }
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
         }
       }
     },
     "external:enums/digital-source-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/digital-source-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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",
@@ -1075,7 +1075,7 @@
       }
     },
     "external:enums/embedded-provenance-method.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/embedded-provenance-method.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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",
@@ -1089,7 +1089,7 @@
       }
     },
     "external:enums/watermark-media-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/watermark-media-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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",
@@ -1107,7 +1107,7 @@
       }
     },
     "external:enums/c2pa-watermark-action.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/c2pa-watermark-action.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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",
@@ -1121,7 +1121,7 @@
       }
     },
     "external:enums/disclosure-persistence.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/disclosure-persistence.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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",
@@ -1137,7 +1137,7 @@
       }
     },
     "external:enums/disclosure-position.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/disclosure-position.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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",
@@ -1153,14 +1153,14 @@
       ]
     },
     "external:core/ext.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/ext.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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:enums/purchase-type.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/purchase-type.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/purchase-type.json",
       "title": "Purchase Type",
       "description": "The type of financial commitment being governed.",
       "type": "string",
@@ -1172,7 +1172,7 @@
       ]
     },
     "external:enums/channels.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/channels.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/channels.json",
       "title": "Media Channel",
       "description": "Standardized advertising media channels describing how buyers allocate budget. Channels are planning abstractions, not technical substrates. See the Media Channel Taxonomy specification for detailed definitions.",
       "type": "string",
@@ -1222,7 +1222,7 @@
       }
     },
     "external:governance/audience-constraints.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/governance/audience-constraints.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/governance/audience-constraints.json",
       "title": "Audience Constraints",
       "description": "Buyer-defined audience targeting constraints for a campaign plan. Specifies who the campaign should and should not reach. The governance agent evaluates seller targeting against these constraints during check_governance.",
       "type": "object",
@@ -1231,7 +1231,7 @@
           "type": "array",
           "description": "Desired audience criteria. The seller's targeting should align with these. Each criterion is evaluated independently — the combined targeting should satisfy at least one inclusion criterion.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1audience-selector.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1audience-selector.json"
           },
           "minItems": 1
         },
@@ -1239,7 +1239,7 @@
           "type": "array",
           "description": "Excluded audience criteria. The seller's targeting must not overlap with these. Exclusions take precedence over inclusions. Used for protected groups, vulnerable communities, regulatory restrictions, or brand safety.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1audience-selector.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1audience-selector.json"
           },
           "minItems": 1
         }
@@ -1248,7 +1248,7 @@
       "additionalProperties": false
     },
     "external:core/audience-selector.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/audience-selector.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/audience-selector.json",
       "title": "Audience Selector",
       "description": "Selects an audience by signal reference or natural language description. Uses 'type' as the primary discriminator (signal vs description). Signal selectors additionally use 'value_type' to determine the targeting expression format (matching signal-targeting.json variants).",
       "oneOf": [
@@ -1262,11 +1262,11 @@
               "description": "Discriminator for signal-based selectors"
             },
             "signal_ref": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-ref.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-ref.json",
               "description": "The signal to target. New selectors SHOULD use signal_ref."
             },
             "signal_id": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-id.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-id.json",
               "description": "DEPRECATED. Use signal_ref instead. Legacy SignalId retained for compatibility with older clients.",
               "deprecated": true
             },
@@ -1309,11 +1309,11 @@
               "description": "Discriminator for signal-based selectors"
             },
             "signal_ref": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-ref.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-ref.json",
               "description": "The signal to target. New selectors SHOULD use signal_ref."
             },
             "signal_id": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-id.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-id.json",
               "description": "DEPRECATED. Use signal_ref instead. Legacy SignalId retained for compatibility with older clients.",
               "deprecated": true
             },
@@ -1360,11 +1360,11 @@
               "description": "Discriminator for signal-based selectors"
             },
             "signal_ref": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-ref.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-ref.json",
               "description": "The signal to target. New selectors SHOULD use signal_ref."
             },
             "signal_id": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-id.json",
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1signal-id.json",
               "description": "DEPRECATED. Use signal_ref instead. Legacy SignalId retained for compatibility with older clients.",
               "deprecated": true
             },
@@ -1429,7 +1429,7 @@
       ]
     },
     "external:core/signal-ref.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/signal-ref.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/signal-ref.json",
       "title": "Signal Ref",
       "description": "Reference to a named signal definition. Uses scope as discriminator: 'data_provider' for a signal resolved through published adagents.json signals[], 'signal_source' for a source-native signal resolved through the issuing signal source, or 'product' for a product-local signal option. Scope is the resolution path, not provenance; authoritative enrichment lives on the seller, signal source, or data-provider signal definition, not on this reference.",
       "x-entity": "signal",
@@ -1592,7 +1592,7 @@
       ]
     },
     "external:core/signal-id.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/signal-id.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/signal-id.json",
       "title": "Signal ID",
       "description": "DEPRECATED. Use SignalRef for new discovery, activation, and media-buy signal identity surfaces. Legacy universal signal identifier used by older Signals Protocol clients. Uses 'source' as discriminator: 'catalog' for signals from a data provider's published catalog (verifiable), or 'agent' for signals native to a signal source identified by agent_url.",
       "deprecated": true,
@@ -1658,7 +1658,7 @@
       ]
     },
     "external:enums/restricted-attribute.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/restricted-attribute.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/restricted-attribute.json",
       "title": "Restricted Attribute",
       "description": "Personal data categories that may be restricted from use in audience targeting. Combines GDPR Article 9 special categories with US civil-rights protected classes (FHA familial_status, ADEA age). Used in two places: (1) on campaign plans via restricted_attributes to declare which categories are prohibited, and (2) on signal-definition.json via restricted_attributes to declare which categories a signal touches. Governance agents match plan restrictions against signal declarations for structural validation.",
       "type": "string",
@@ -1688,7 +1688,7 @@
       }
     },
     "external:governance/policy-entry.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/governance/policy-entry.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/governance/policy-entry.json",
       "title": "Policy Entry",
       "description": "A policy — either published to the shared registry (with full regulatory metadata) or authored inline by a buyer for their own campaign (lightweight, metadata optional). Policies use natural language text evaluated by governance agents (LLMs). Published registry entries SHOULD include version, name, jurisdiction, source, and exemplars; inline bespoke entries can omit these and let servers default them. Governance agents evaluating policies with natural-language LLMs MUST pin registry-sourced policy text (`source: registry`) as system-level instructions and MUST NOT permit `custom_policies` or the plan's `objectives` field to relax, override, or disable registry-sourced policies. Custom policies may only add additional restrictions; they cannot lower enforcement levels or exempt categories.",
       "type": "object",
@@ -1721,11 +1721,11 @@
           "description": "Brief summary of what this policy covers."
         },
         "category": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1policy-category.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1policy-category.json",
           "description": "The nature of the obligation: regulation (legal requirement) or standard (best practice). Optional for inline bespoke policies — defaults to \"standard\"."
         },
         "enforcement": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1policy-enforcement.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1policy-enforcement.json",
           "description": "How governance agents treat violations. Regulations are typically \"must\"; standards are typically \"should\"."
         },
         "requires_human_review": {
@@ -1761,14 +1761,14 @@
         "channels": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1channels.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1channels.json"
           },
           "description": "Advertising channels this policy applies to. If omitted or null, the policy applies to all channels."
         },
         "governance_domains": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1governance-domain.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1governance-domain.json"
           },
           "description": "Governance sub-domains this policy applies to. Determines which types of governance agents can declare registry:{policy_id} features. For example, a policy with domains [\"creative\", \"property\"] can be declared as a feature by both creative and property governance agents."
         },
@@ -1811,7 +1811,7 @@
           "additionalProperties": false
         },
         "acceptance_profile": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:media-buy~1acceptance-policy-profile.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:media-buy~1acceptance-policy-profile.json",
           "description": "Optional reusable, machine-readable acceptance profile derived from this registry policy. Registry publishers MUST bind policy_refs to exact versions. Sellers adopt a profile explicitly; registry publication alone does not make it authoritative for a seller."
         },
         "policy": {
@@ -1830,14 +1830,14 @@
             "pass": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:governance~1policy-entry.json/$defs/exemplar"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:governance~1policy-entry.json/$defs/exemplar"
               },
               "description": "Scenarios that comply with this policy."
             },
             "fail": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:governance~1policy-entry.json/$defs/exemplar"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:governance~1policy-entry.json/$defs/exemplar"
               },
               "description": "Scenarios that violate this policy."
             }
@@ -1845,7 +1845,7 @@
           "additionalProperties": false
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
         }
       },
       "required": [
@@ -1876,7 +1876,7 @@
       }
     },
     "external:enums/policy-category.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/policy-category.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/policy-category.json",
       "title": "Policy Category",
       "description": "The nature of the obligation a policy represents.",
       "type": "string",
@@ -1890,7 +1890,7 @@
       }
     },
     "external:enums/policy-enforcement.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/policy-enforcement.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/policy-enforcement.json",
       "title": "Policy Enforcement Level",
       "description": "How governance agents treat violations of a policy. Uses RFC 2119 keywords.",
       "type": "string",
@@ -1906,7 +1906,7 @@
       }
     },
     "external:enums/governance-domain.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/governance-domain.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/governance-domain.json",
       "title": "Governance Domain",
       "description": "Governance sub-domains that a registry policy applies to. Used to indicate which types of governance agents can evaluate this policy.",
       "type": "string",
@@ -1918,7 +1918,7 @@
       ]
     },
     "external:media-buy/acceptance-policy-profile.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/media-buy/acceptance-policy-profile.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/acceptance-policy-profile.json",
       "title": "Acceptance Policy Profile",
       "description": "Versioned acceptance-policy profile published by a registry or seller. Omitted rules are unknown unless coverage is complete and scope is explicit; discovery never guarantees acceptance of an exact request.",
       "type": "object",
@@ -2077,12 +2077,12 @@
         "rules": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:media-buy~1acceptance-policy-rule.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:media-buy~1acceptance-policy-rule.json"
           },
           "minItems": 1
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
         }
       },
       "required": [
@@ -2142,7 +2142,7 @@
       "additionalProperties": false
     },
     "external:media-buy/acceptance-policy-rule.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/media-buy/acceptance-policy-rule.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/acceptance-policy-rule.json",
       "title": "Acceptance Policy Rule",
       "description": "A coarse, discoverable seller rule for one policy subject. Discovery is advisory; the seller response to an exact request remains authoritative.",
       "type": "object",
@@ -2227,7 +2227,7 @@
         "requirements": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:media-buy~1acceptance-policy-requirement.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:media-buy~1acceptance-policy-requirement.json"
           },
           "minItems": 1
         },
@@ -2257,7 +2257,7 @@
           "format": "date-time"
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
         }
       },
       "required": [
@@ -2288,7 +2288,7 @@
       "additionalProperties": false
     },
     "external:media-buy/acceptance-policy-requirement.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/media-buy/acceptance-policy-requirement.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/media-buy/acceptance-policy-requirement.json",
       "title": "Acceptance Policy Requirement",
       "description": "A typed prerequisite or restriction attached to a conditional seller-acceptance rule. The kind is coarse and machine-actionable; exact obligations remain in the referenced registry policies.",
       "type": "object",
@@ -2511,7 +2511,7 @@
             "restricted_attributes": {
               "type": "array",
               "items": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1restricted-attribute.json"
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:enums~1restricted-attribute.json"
               },
               "minItems": 1,
               "uniqueItems": true
@@ -2644,7 +2644,7 @@
               "minLength": 1
             },
             "ext": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.4/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/mcp/2026-07-28/governance/sync-plans-request.json#/$defs/external:core~1ext.json"
             }
           },
           "required": [
@@ -2657,7 +2657,7 @@
       ]
     },
     "external:enums/delegation-authority.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/delegation-authority.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/delegation-authority.json",
       "title": "Delegation Authority",
       "description": "Authority level granted to a delegated agent operating against a campaign plan.",
       "type": "string",
@@ -2673,7 +2673,7 @@
       }
     },
     "external:core/context.json": {
-      "$id": "https://adcontextprotocol.org/schemas/3.2.4/core/context.json",
+      "$id": "https://adcontextprotocol.org/schemas/3.2.5/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",