@adcp/sdk 7.5.0 → 7.6.0

package/dist/lib/schemas-data/3.0/error-details/creative-rejected.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/error-details/creative-rejected.json",
+  "$id": "/schemas/3.0.12/error-details/creative-rejected.json",
   "title": "Creative Rejected Details",
   "description": "Recommended details shape for CREATIVE_REJECTED errors. Provides policy reference and rejection reasons so agents can revise.",
   "type": "object",

package/dist/lib/schemas-data/3.0/error-details/policy-violation.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/error-details/policy-violation.json",
+  "$id": "/schemas/3.0.12/error-details/policy-violation.json",
   "title": "Policy Violation Details",
   "description": "Recommended details shape for POLICY_VIOLATION errors. Provides policy reference and violated rules so agents can adjust requests.",
   "type": "object",

package/dist/lib/schemas-data/3.0/error-details/rate-limited.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/error-details/rate-limited.json",
+  "$id": "/schemas/3.0.12/error-details/rate-limited.json",
   "title": "Rate Limited Details",
   "description": "Recommended details shape for RATE_LIMITED errors. Provides rate limit window information so agents can plan request pacing.",
   "type": "object",

package/dist/lib/schemas-data/3.0/error-details/vendor-error-codes.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/error-details/vendor-error-codes.json",
+  "$id": "/schemas/3.0.12/error-details/vendor-error-codes.json",
   "title": "Vendor Error Code Registry",
   "description": "Registry of vendor-prefixed error codes (X_{VENDOR}_{CODE}). Sellers register their vendor prefix and codes here to prevent collisions. Standard error codes are in error-code.json. To register a new vendor prefix, submit a PR adding your entry to the vendors object.",
   "type": "object",

package/dist/lib/schemas-data/3.0/extensions/extension-meta.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/extensions/extension-meta.json",
+  "$id": "/schemas/3.0.12/extensions/extension-meta.json",
   "title": "AdCP Extension File Schema",
   "description": "Schema that all extension files must follow. Combines metadata (valid_from, docs_url) with the actual extension data schema. Extensions are auto-discovered from /schemas/extensions/*.json and included in versioned builds based on valid_from/valid_until.",
   "type": "object",

package/dist/lib/schemas-data/3.0/extensions/index.json

@@ -1,9 +1,9 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/extensions/index.json",
+  "$id": "/schemas/3.0.12/extensions/index.json",
   "title": "AdCP Extension Registry",
   "description": "Auto-generated registry of formal AdCP extensions. Extensions provide typed schemas for vendor-specific or domain-specific data within the ext field. Agents declare which extensions they support in their agent card.",
   "_generated": true,
-  "_generatedAt": "2026-05-11T08:45:17.889Z",
+  "_generatedAt": "2026-05-13T10:39:50.270Z",
   "extensions": {}
 }

package/dist/lib/schemas-data/3.0/governance/attribute-definition.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/attribute-definition.json",
+  "$id": "/schemas/3.0.12/governance/attribute-definition.json",
   "title": "Attribute Definition",
   "description": "Definition of a restricted personal data attribute in the policy registry. Attributes are the shared vocabulary used across campaign plans (restricted_attributes), signal definitions (restricted_attributes), and data marketplace catalogs. Each definition documents the regulatory basis, scope, and common signal patterns for the attribute category.",
   "type": "object",

package/dist/lib/schemas-data/3.0/governance/audience-constraints.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/audience-constraints.json",
+  "$id": "/schemas/3.0.12/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",
@@ -9,7 +9,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": "/schemas/3.0.11/core/audience-selector.json"
+        "$ref": "/schemas/3.0.12/core/audience-selector.json"
       },
       "minItems": 1
     },
@@ -17,7 +17,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": "/schemas/3.0.11/core/audience-selector.json"
+        "$ref": "/schemas/3.0.12/core/audience-selector.json"
       },
       "minItems": 1
     }

package/dist/lib/schemas-data/3.0/governance/check-governance-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/check-governance-request.json",
+  "$id": "/schemas/3.0.12/governance/check-governance-request.json",
   "title": "Check Governance Request",
   "description": "Universal governance check for campaign actions. The governance agent infers the check type from the fields present: tool+payload = intent check (proposed, orchestrator-side). planned_delivery = execution check (committed, seller-side). governance_context maintains lifecycle continuity across either check type — its presence alone does not determine binding. To check budget availability without a specific action, omit tool and payload.",
   "x-status": "experimental",
@@ -23,7 +23,7 @@
       "description": "URL of the agent making the request."
     },
     "purchase_type": {
-      "$ref": "/schemas/3.0.11/enums/purchase-type.json",
+      "$ref": "/schemas/3.0.12/enums/purchase-type.json",
       "description": "The type of financial commitment being checked. Determines which budget allocation (if any) to validate against. Defaults to 'media_buy' when omitted.",
       "default": "media_buy"
     },
@@ -44,12 +44,12 @@
       "pattern": "^[\\x20-\\x7E]+$"
     },
     "phase": {
-      "$ref": "/schemas/3.0.11/enums/governance-phase.json",
+      "$ref": "/schemas/3.0.12/enums/governance-phase.json",
       "description": "The phase of the governed action's lifecycle. 'purchase': initial commitment (create_media_buy, acquire_rights, activate_signal). 'modification': update to existing commitment. 'delivery': periodic delivery or usage reporting. Defaults to 'purchase' if omitted.",
       "default": "purchase"
     },
     "planned_delivery": {
-      "$ref": "/schemas/3.0.11/core/planned-delivery.json",
+      "$ref": "/schemas/3.0.12/core/planned-delivery.json",
       "description": "What the seller will actually deliver. Present on execution checks."
     },
     "delivery_metrics": {
@@ -180,14 +180,14 @@
       "maxLength": 1000
     },
     "invoice_recipient": {
-      "$ref": "/schemas/3.0.11/core/business-entity.json",
+      "$ref": "/schemas/3.0.12/core/business-entity.json",
       "description": "Invoice recipient from the purchase request. MUST be present when the tool payload includes invoice_recipient, so the governance agent can validate billing changes."
     },
     "context": {
-      "$ref": "/schemas/3.0.11/core/context.json"
+      "$ref": "/schemas/3.0.12/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.0.11/core/ext.json"
+      "$ref": "/schemas/3.0.12/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.0/governance/check-governance-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/check-governance-response.json",
+  "$id": "/schemas/3.0.12/governance/check-governance-response.json",
   "title": "Check Governance Response",
   "description": "Governance agent's response to a check request. Returns whether the action is approved under the governance plan.",
   "x-status": "experimental",
@@ -12,7 +12,7 @@
       "x-entity": "governance_check"
     },
     "status": {
-      "$ref": "/schemas/3.0.11/enums/governance-decision.json"
+      "$ref": "/schemas/3.0.12/enums/governance-decision.json"
     },
     "plan_id": {
       "type": "string",
@@ -44,7 +44,7 @@
             "x-entity": "governance_plan"
           },
           "severity": {
-            "$ref": "/schemas/3.0.11/enums/escalation-severity.json"
+            "$ref": "/schemas/3.0.12/enums/escalation-severity.json"
           },
           "explanation": {
             "type": "string",
@@ -124,7 +124,7 @@
       "description": "Policy IDs evaluated during this check. Includes registry policy IDs (resolved via the policy registry) and any inline `policy_id`s declared in the plan's `custom_policies`."
     },
     "mode": {
-      "$ref": "/schemas/3.0.11/enums/governance-mode.json",
+      "$ref": "/schemas/3.0.12/enums/governance-mode.json",
       "description": "Governance enforcement mode active when this check was evaluated. Allows counterparties, regulators, and auditors to distinguish whether a finding blocked execution (enforce) or was logged silently (audit)."
     },
     "governance_context": {
@@ -135,10 +135,10 @@
       "pattern": "^[\\x20-\\x7E]+$"
     },
     "context": {
-      "$ref": "/schemas/3.0.11/core/context.json"
+      "$ref": "/schemas/3.0.12/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.0.11/core/ext.json"
+      "$ref": "/schemas/3.0.12/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.0/governance/get-plan-audit-logs-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/get-plan-audit-logs-request.json",
+  "$id": "/schemas/3.0.12/governance/get-plan-audit-logs-request.json",
   "title": "Get Plan Audit Logs Request",
   "description": "Retrieve governance state and audit trail for one or more plans.",
   "x-status": "experimental",
@@ -41,7 +41,7 @@
     "purchase_types": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.0.11/enums/purchase-type.json"
+        "$ref": "/schemas/3.0.12/enums/purchase-type.json"
       },
       "minItems": 1,
       "description": "Filter audit entries by purchase type. Returns only checks and outcomes matching these purchase types (e.g., ['rights_license'] to see all rights activity)."
@@ -52,10 +52,10 @@
       "default": false
     },
     "context": {
-      "$ref": "/schemas/3.0.11/core/context.json"
+      "$ref": "/schemas/3.0.12/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.0.11/core/ext.json"
+      "$ref": "/schemas/3.0.12/core/ext.json"
     }
   },
   "anyOf": [

package/dist/lib/schemas-data/3.0/governance/get-plan-audit-logs-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/get-plan-audit-logs-response.json",
+  "$id": "/schemas/3.0.12/governance/get-plan-audit-logs-response.json",
   "title": "Get Plan Audit Logs Response",
   "description": "Governance state and audit trail for one or more plans.",
   "x-status": "experimental",
@@ -251,7 +251,7 @@
                   "description": "The AdCP tool (present for check entries)."
                 },
                 "status": {
-                  "$ref": "/schemas/3.0.11/enums/governance-decision.json",
+                  "$ref": "/schemas/3.0.12/enums/governance-decision.json",
                   "description": "Governance check status (present for check entries)."
                 },
                 "check_type": {
@@ -263,7 +263,7 @@
                   "description": "Whether the check was an intent check (orchestrator) or execution check (seller). Inferred from the fields present on the original check request. Present for check entries."
                 },
                 "mode": {
-                  "$ref": "/schemas/3.0.11/enums/governance-mode.json",
+                  "$ref": "/schemas/3.0.12/enums/governance-mode.json",
                   "description": "Governance mode active at the moment this specific check was evaluated. Governance agents SHOULD populate this field on check entries, recording the mode from their runtime configuration at the moment check_governance was processed — not derived from a plan field. This is a per-check value: if the operator changes mode between checks for the same governed action, each entry records the mode active for that entry. A future `governed_actions[].mode` field would describe the action's current mode, which may differ from the most recent entry's `mode` if the plan has since been re-synced. Absent for outcome entries and for pre-3.1 governance agents that do not surface mode on audit responses."
                 },
                 "explanation": {
@@ -298,7 +298,7 @@
                         "$comment": "x-entity deliberately omitted — audit log findings mirror check_governance findings and can reference either a governance_registry_policy or a governance_inline_policy (see #2685)."
                       },
                       "severity": {
-                        "$ref": "/schemas/3.0.11/enums/escalation-severity.json"
+                        "$ref": "/schemas/3.0.12/enums/escalation-severity.json"
                       },
                       "explanation": {
                         "type": "string"
@@ -318,7 +318,7 @@
                   }
                 },
                 "outcome": {
-                  "$ref": "/schemas/3.0.11/enums/outcome-type.json",
+                  "$ref": "/schemas/3.0.12/enums/outcome-type.json",
                   "description": "Outcome type (present for outcome entries)."
                 },
                 "committed_budget": {
@@ -335,7 +335,7 @@
                   "description": "Audit-layer binding to the plan revision this attestation was evaluated over — base64url_no_pad(SHA-256(JCS(plan_payload))) per Plan binding and audit in the campaign-governance specification. Present on check entries. Auditors and buyer-side compliance verify by recomputing over the retained plan revision and byte-comparing the decoded 32-byte digests."
                 },
                 "purchase_type": {
-                  "$ref": "/schemas/3.0.11/enums/purchase-type.json",
+                  "$ref": "/schemas/3.0.12/enums/purchase-type.json",
                   "description": "Purchase type for this entry."
                 },
                 "outcome_status": {
@@ -362,7 +362,7 @@
                   "description": "Governance context correlating this action's lifecycle."
                 },
                 "purchase_type": {
-                  "$ref": "/schemas/3.0.11/enums/purchase-type.json",
+                  "$ref": "/schemas/3.0.12/enums/purchase-type.json",
                   "description": "Type of financial commitment."
                 },
                 "status": {
@@ -410,10 +410,10 @@
       }
     },
     "context": {
-      "$ref": "/schemas/3.0.11/core/context.json"
+      "$ref": "/schemas/3.0.12/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.0.11/core/ext.json"
+      "$ref": "/schemas/3.0.12/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.0/governance/policy-category-definition.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/policy-category-definition.json",
+  "$id": "/schemas/3.0.12/governance/policy-category-definition.json",
   "title": "Policy Category Definition",
   "description": "Definition of a policy category in the registry. Policy categories group related regulatory regimes (e.g., 'children_directed' groups COPPA, UK AADC, GDPR Article 8). Used on campaign plans (plan.policy_categories), signal definitions (signal-definition.policy_categories), and policy entries (policy-entry.policy_categories) to connect campaigns and data to the right regulatory frameworks.",
   "type": "object",
@@ -59,7 +59,7 @@
       "type": "array",
       "description": "Restricted attribute categories that regulations in this category prohibit for targeting. Governance agents enforce these when the category is active on a plan — if a plan declares policy_categories: ['fair_housing'], the governance agent restricts targeting on these attributes.",
       "items": {
-        "$ref": "/schemas/3.0.11/enums/restricted-attribute.json"
+        "$ref": "/schemas/3.0.12/enums/restricted-attribute.json"
       }
     },
     "requires_human_review": {

package/dist/lib/schemas-data/3.0/governance/policy-entry.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/policy-entry.json",
+  "$id": "/schemas/3.0.12/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",
@@ -33,11 +33,11 @@
       "description": "Brief summary of what this policy covers."
     },
     "category": {
-      "$ref": "/schemas/3.0.11/enums/policy-category.json",
+      "$ref": "/schemas/3.0.12/enums/policy-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": "/schemas/3.0.11/enums/policy-enforcement.json",
+      "$ref": "/schemas/3.0.12/enums/policy-enforcement.json",
       "description": "How governance agents treat violations. Regulations are typically \"must\"; standards are typically \"should\"."
     },
     "requires_human_review": {
@@ -72,14 +72,14 @@
     "channels": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.0.11/enums/channels.json"
+        "$ref": "/schemas/3.0.12/enums/channels.json"
       },
       "description": "Advertising channels this policy applies to. If omitted or null, the policy applies to all channels."
     },
     "governance_domains": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.0.11/enums/governance-domain.json"
+        "$ref": "/schemas/3.0.12/enums/governance-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."
     },
@@ -133,7 +133,7 @@
       "additionalProperties": false
     },
     "ext": {
-      "$ref": "/schemas/3.0.11/core/ext.json"
+      "$ref": "/schemas/3.0.12/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.0/governance/policy-ref.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/policy-ref.json",
+  "$id": "/schemas/3.0.12/governance/policy-ref.json",
   "title": "Policy Reference",
   "description": "A reference to a policy in the policy registry. Used in brand compliance configurations to declare which registry policies apply.",
   "type": "object",

package/dist/lib/schemas-data/3.0/governance/report-plan-outcome-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/report-plan-outcome-request.json",
+  "$id": "/schemas/3.0.12/governance/report-plan-outcome-request.json",
   "title": "Report Plan Outcome Request",
   "description": "Report the outcome of an action to the governance agent. Called by the orchestrator (buyer-side agent) after a seller responds. This is the 'after' half of the governance loop. Sellers do not call this task -- they report delivery data via check_governance with phase 'delivery'.",
   "x-status": "experimental",
@@ -31,12 +31,12 @@
       "pattern": "^[A-Za-z0-9_.:-]{16,255}$"
     },
     "purchase_type": {
-      "$ref": "/schemas/3.0.11/enums/purchase-type.json",
+      "$ref": "/schemas/3.0.12/enums/purchase-type.json",
       "description": "The type of financial commitment this outcome is for. Determines which budget allocation (if any) to charge against. Defaults to 'media_buy' when omitted.",
       "default": "media_buy"
     },
     "outcome": {
-      "$ref": "/schemas/3.0.11/enums/outcome-type.json",
+      "$ref": "/schemas/3.0.12/enums/outcome-type.json",
       "description": "Outcome type."
     },
     "seller_response": {
@@ -68,7 +68,7 @@
           }
         },
         "planned_delivery": {
-          "$ref": "/schemas/3.0.11/core/planned-delivery.json",
+          "$ref": "/schemas/3.0.12/core/planned-delivery.json",
           "description": "What the seller said it will deliver. When seller-side governance is not configured, this is the governance agent's only view of the seller's delivery parameters."
         },
         "creative_deadline": {
@@ -149,10 +149,10 @@
       "pattern": "^[\\x20-\\x7E]+$"
     },
     "context": {
-      "$ref": "/schemas/3.0.11/core/context.json"
+      "$ref": "/schemas/3.0.12/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.0.11/core/ext.json"
+      "$ref": "/schemas/3.0.12/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.0/governance/report-plan-outcome-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/report-plan-outcome-response.json",
+  "$id": "/schemas/3.0.12/governance/report-plan-outcome-response.json",
   "title": "Report Plan Outcome Response",
   "description": "Response from reporting an action outcome. Only returned to the orchestrator (buyer-side agent) that manages the plan. Sellers report delivery data via check_governance with phase 'delivery', not via this task.",
   "x-status": "experimental",
@@ -33,7 +33,7 @@
             "description": "Which validation category flagged the issue."
           },
           "severity": {
-            "$ref": "/schemas/3.0.11/enums/escalation-severity.json",
+            "$ref": "/schemas/3.0.12/enums/escalation-severity.json",
             "description": "Finding severity."
           },
           "explanation": {
@@ -75,10 +75,10 @@
       "default": false
     },
     "context": {
-      "$ref": "/schemas/3.0.11/core/context.json"
+      "$ref": "/schemas/3.0.12/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.0.11/core/ext.json"
+      "$ref": "/schemas/3.0.12/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.0/governance/sync-plans-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/sync-plans-request.json",
+  "$id": "/schemas/3.0.12/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.",
   "x-status": "experimental",
@@ -32,7 +32,7 @@
             "x-entity": "governance_plan"
           },
           "brand": {
-            "$ref": "/schemas/3.0.11/core/brand-ref.json",
+            "$ref": "/schemas/3.0.12/core/brand-ref.json",
             "description": "Brand or organization being governed. For campaign plans, the governance agent resolves the brand's compliance configuration. For portfolio plans, this is the holding company or parent organization."
           },
           "objectives": {
@@ -69,7 +69,7 @@
                 "type": "object",
                 "description": "Optional budget partition across purchase types. Keys are purchase-type enum values (media_buy, rights_license, signal_activation, creative_services). When present, the governance agent validates spend against both the total and the per-type allocation. When absent, all spend counts against the single total regardless of purchase type.",
                 "propertyNames": {
-                  "$ref": "/schemas/3.0.11/enums/purchase-type.json"
+                  "$ref": "/schemas/3.0.12/enums/purchase-type.json"
                 },
                 "additionalProperties": {
                   "type": "object",
@@ -130,14 +130,14 @@
               "required": {
                 "type": "array",
                 "items": {
-                  "$ref": "/schemas/3.0.11/enums/channels.json"
+                  "$ref": "/schemas/3.0.12/enums/channels.json"
                 },
                 "description": "Channels that must be included in the media mix."
               },
               "allowed": {
                 "type": "array",
                 "items": {
-                  "$ref": "/schemas/3.0.11/enums/channels.json"
+                  "$ref": "/schemas/3.0.12/enums/channels.json"
                 },
                 "description": "Channels the orchestrator may use."
               },
@@ -214,14 +214,14 @@
             "minItems": 1
           },
           "audience": {
-            "$ref": "/schemas/3.0.11/governance/audience-constraints.json",
+            "$ref": "/schemas/3.0.12/governance/audience-constraints.json",
             "description": "Audience targeting constraints. Defines who the campaign should reach (include) and must not reach (exclude). The governance agent evaluates seller targeting against these constraints."
           },
           "restricted_attributes": {
             "type": "array",
             "description": "Personal data categories that must not be used for targeting in this campaign. Applies horizontally across all audience criteria. Used for EU DSA Article 26 compliance (prohibits targeting on GDPR Article 9 special categories) and similar regulations. The governance agent flags any audience targeting that references these attributes.",
             "items": {
-              "$ref": "/schemas/3.0.11/enums/restricted-attribute.json"
+              "$ref": "/schemas/3.0.12/enums/restricted-attribute.json"
             },
             "minItems": 1
           },
@@ -246,7 +246,7 @@
           "custom_policies": {
             "type": "array",
             "items": {
-              "$ref": "/schemas/3.0.11/governance/policy-entry.json"
+              "$ref": "/schemas/3.0.12/governance/policy-entry.json"
             },
             "description": "Bespoke policies specific to this campaign, using the same shape as registry entries. Each policy has a policy_id, enforcement (must|should), and natural-language policy text. Governance findings reference policy_id to identify which policy triggered. For quick authoring, omit version/name/category — servers default them."
           },
@@ -273,7 +273,7 @@
                   "description": "URL of the delegated agent."
                 },
                 "authority": {
-                  "$ref": "/schemas/3.0.11/enums/delegation-authority.json",
+                  "$ref": "/schemas/3.0.12/enums/delegation-authority.json",
                   "description": "Authority level granted to this agent."
                 },
                 "budget_limit": {
@@ -353,7 +353,7 @@
               "shared_exclusions": {
                 "type": "array",
                 "items": {
-                  "$ref": "/schemas/3.0.11/governance/policy-entry.json"
+                  "$ref": "/schemas/3.0.12/governance/policy-entry.json"
                 },
                 "description": "Bespoke exclusion policies applied across all member plans, using the same shape as registry entries. Authored typically as enforcement: must policies with exclusion language in the policy text (e.g., 'No advertising on properties owned by competitor holding companies')."
               }
@@ -364,7 +364,7 @@
             "additionalProperties": false
           },
           "ext": {
-            "$ref": "/schemas/3.0.11/core/ext.json"
+            "$ref": "/schemas/3.0.12/core/ext.json"
           }
         },
         "required": [
@@ -435,10 +435,10 @@
       }
     },
     "context": {
-      "$ref": "/schemas/3.0.11/core/context.json"
+      "$ref": "/schemas/3.0.12/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.0.11/core/ext.json"
+      "$ref": "/schemas/3.0.12/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.0/governance/sync-plans-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.11/governance/sync-plans-response.json",
+  "$id": "/schemas/3.0.12/governance/sync-plans-response.json",
   "title": "Sync Plans Response",
   "description": "Response from syncing campaign plans. Returns status and active validation categories for each plan.",
   "x-status": "experimental",
@@ -75,7 +75,7 @@
                   "description": "How this policy was included. 'explicit': referenced in the brand compliance configuration. 'auto_applied': matched automatically by jurisdiction or policy category."
                 },
                 "enforcement": {
-                  "$ref": "/schemas/3.0.11/enums/policy-enforcement.json",
+                  "$ref": "/schemas/3.0.12/enums/policy-enforcement.json",
                   "description": "Enforcement level for this policy."
                 },
                 "reason": {
@@ -106,10 +106,10 @@
       "default": false
     },
     "context": {
-      "$ref": "/schemas/3.0.11/core/context.json"
+      "$ref": "/schemas/3.0.12/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.0.11/core/ext.json"
+      "$ref": "/schemas/3.0.12/core/ext.json"
     }
   },
   "required": [