@adcp/sdk 14.0.0-rc.49 → 14.0.0-rc.50

package/dist/lib/schemas-data/3.1/formats/canonical/responsive_creative.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/formats/canonical/responsive_creative.json",
+  "$id": "/schemas/3.1.24/formats/canonical/responsive_creative.json",
   "title": "Canonical Format: Responsive Creative",
   "description": "Buyer supplies a pool of typed assets (multiple headlines, descriptions, images, videos, logos); the surface algorithmically composes combinations per placement. **Composition is algorithmic** — surface picks combinations and reports per-asset performance breakdowns. Covers Google Responsive Display Ads (RDA), Responsive Search Ads (RSA), Performance Max (PMax), Demand Gen, and Meta Advantage+ creative. Industry term: \"Responsive\" (Google) / \"Advantage+ creative\" (Meta) / \"Dynamic Creative\" (older Meta term). Distinct from `sponsored_placement` (catalog-driven, deterministic) and `agent_placement` (AI-surface composition). The structured `slots` field below enumerates expected canonical asset_group_id slots; per-slot count/length narrowing lives in flat parameters (`headlines_min`, `headline_max_chars`, etc.).",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/formats/canonical/_base.json"
+      "$ref": "/schemas/3.1.24/formats/canonical/_base.json"
     }
   ],
   "properties": {

package/dist/lib/schemas-data/3.1/formats/canonical/sponsored_placement.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/formats/canonical/sponsored_placement.json",
+  "$id": "/schemas/3.1.24/formats/canonical/sponsored_placement.json",
   "title": "Canonical Format: Sponsored Placement (retail-media catalog-driven)",
   "description": "Catalog-driven retail-media format. Slot: `source_catalog` (catalog asset — product/SKU/ASIN/GTIN catalog reference, REQUIRED), optional `hero_asset`, optional `landing_page_url`. Buyer supplies the catalog reference; surface composes per-item or multi-item rendering using its native placement template. **Composition is deterministic** — buyer can predict per-slot rendering from the catalog item structure. Tracking model: per-item impression + click + conversion (catalog-keyed via offering_id/sku/gtin macros). Covers Amazon Sponsored Products, Criteo Sponsored Products, CitrusAd Sponsored Products, Walmart Connect Sponsored Products, Pinterest Collection (catalog-driven mode).\n\n**Scope (normative — buyer-agent routing).** This canonical is the home for catalog-driven retail-media placements ONLY. The defining feature is the `source_catalog` slot — products under this canonical compose their creative *per catalog item* using the buyer-supplied catalog feed. Without a catalog feed there is nothing to render against. Buyer agents reading `format_kind: sponsored_placement` MUST attach a catalog reference; sellers MUST require `source_catalog` in the manifest.\n\n**Not this canonical (route elsewhere):**\n- IAB in-feed native ads, content-recommendation widgets (Taboola, Outbrain, Yahoo Native, AdMob Native, in-feed sponsored cards) — use `native_in_feed` (asset-bundle composition; no catalog).\n- Algorithmic surface that picks from a buyer-supplied asset pool (Google PMax, Meta Advantage+) — use `responsive_creative`.\n- Single-image or single-video creative — use `image` or `video_hosted`.\n\nThe earlier broader framing ('any sponsored placement') was too loose for buyer-agent routing — a buyer reading `sponsored_placement` couldn't disambiguate a catalog-driven Amazon SP from an in-feed Taboola widget. As of 3.1, the canonical is narrowed to catalog-keyed retail-media; native moves to `native_in_feed`. Distinct from `responsive_creative` (algorithmic combinator from buyer pool) and `agent_placement` (text/audio AI-surface composition).",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/formats/canonical/_base.json"
+      "$ref": "/schemas/3.1.24/formats/canonical/_base.json"
     }
   ],
   "properties": {
@@ -39,7 +39,7 @@
     "supported_catalog_types": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.1.18/enums/catalog-type.json"
+        "$ref": "/schemas/3.1.24/enums/catalog-type.json"
       },
       "description": "Catalog types this product accepts."
     },

package/dist/lib/schemas-data/3.1/formats/canonical/video_hosted.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/formats/canonical/video_hosted.json",
+  "$id": "/schemas/3.1.24/formats/canonical/video_hosted.json",
   "title": "Canonical Format: Hosted Video",
   "description": "Direct video file (mp4/webm/mov) hosted by the buyer. Slot: `video_main` (video asset, file or hosted URL), optional `headline`, `brand_name`, `cta`, `companion_banner`, `landing_page_url`. Tracking model: IAB Open Measurement SDK + external impression/click/quartile pixels via universal_macros. Orientation is a parameter (vertical 9:16 / horizontal 16:9 / square 1:1); slot shape includes optional `brand_name` (typical for vertical short-form) and optional `companion_banner` (typical for horizontal instream). Distinct from `video_vast` (VAST tag, inherent VAST event tracking) — receivers fire impression and click pixels at delivery time.",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/formats/canonical/_base.json"
+      "$ref": "/schemas/3.1.24/formats/canonical/_base.json"
     }
   ],
   "properties": {

package/dist/lib/schemas-data/3.1/formats/canonical/video_vast.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/formats/canonical/video_vast.json",
+  "$id": "/schemas/3.1.24/formats/canonical/video_vast.json",
   "title": "Canonical Format: VAST Video",
   "description": "VAST-tag-delivered video creative. Slot: `vast_tag` (vast asset, URL or inline XML, VAST 2.x-4.x). Tracking model: VAST events inherent to the spec — `impression`, `firstQuartile`, `midpoint`, `thirdQuartile`, `complete`, `start`, `pause`, `resume`, `mute`, `unmute`, `expand`, `collapse`, `fullscreen`, `creativeView`, `clickTracking`, `error`. VPAID interactivity via `vpaid_enabled: true` flag. SIMID extensions for interactive video supported as VAST extensions. Orientation is a parameter (vertical / horizontal / square). Distinct from `video_hosted` (direct file with external tracking).",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/formats/canonical/_base.json"
+      "$ref": "/schemas/3.1.24/formats/canonical/_base.json"
     }
   ],
   "properties": {

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/governance/attribute-definition.json",
+  "$id": "/schemas/3.1.24/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.1/governance/audience-constraints.json

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

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

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/governance/check-governance-request.json",
+  "$id": "/schemas/3.1.24/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.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/core/version-envelope.json"
+      "$ref": "/schemas/3.1.24/core/version-envelope.json"
     }
   ],
   "x-status": "experimental",
@@ -22,7 +22,7 @@
       "description": "URL of the agent making the request."
     },
     "purchase_type": {
-      "$ref": "/schemas/3.1.18/enums/purchase-type.json",
+      "$ref": "/schemas/3.1.24/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.1.18/enums/governance-phase.json",
+      "$ref": "/schemas/3.1.24/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.1.18/core/planned-delivery.json",
+      "$ref": "/schemas/3.1.24/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.1.18/core/business-entity.json",
+      "$ref": "/schemas/3.1.24/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.1.18/core/context.json"
+      "$ref": "/schemas/3.1.24/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [

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

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/governance/check-governance-response.json",
+  "$id": "/schemas/3.1.24/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.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/core/version-envelope.json"
+      "$ref": "/schemas/3.1.24/core/version-envelope.json"
     },
     {
       "if": {
@@ -81,7 +81,7 @@
       "x-entity": "governance_check"
     },
     "verdict": {
-      "$ref": "/schemas/3.1.18/enums/governance-decision.json",
+      "$ref": "/schemas/3.1.24/enums/governance-decision.json",
       "description": "Governance verdict: approved | denied | conditions. Renamed from `status` in 3.1 to free the top-level `status` key for the envelope task-status (TaskStatus) under MCP flat-on-the-wire serialization. The enum values are unchanged; only the property name moved."
     },
     "plan_id": {
@@ -114,7 +114,7 @@
             "x-entity": "governance_plan"
           },
           "severity": {
-            "$ref": "/schemas/3.1.18/enums/escalation-severity.json"
+            "$ref": "/schemas/3.1.24/enums/escalation-severity.json"
           },
           "explanation": {
             "type": "string",
@@ -194,7 +194,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.1.18/enums/governance-mode.json",
+      "$ref": "/schemas/3.1.24/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": {
@@ -205,10 +205,10 @@
       "pattern": "^[\\x20-\\x7E]+$"
     },
     "context": {
-      "$ref": "/schemas/3.1.18/core/context.json"
+      "$ref": "/schemas/3.1.24/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [

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

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/governance/get-plan-audit-logs-request.json",
+  "$id": "/schemas/3.1.24/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.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/core/version-envelope.json"
+      "$ref": "/schemas/3.1.24/core/version-envelope.json"
     }
   ],
   "x-status": "experimental",
@@ -40,7 +40,7 @@
     "purchase_types": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.1.18/enums/purchase-type.json"
+        "$ref": "/schemas/3.1.24/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)."
@@ -51,10 +51,10 @@
       "default": false
     },
     "context": {
-      "$ref": "/schemas/3.1.18/core/context.json"
+      "$ref": "/schemas/3.1.24/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "anyOf": [

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

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/governance/get-plan-audit-logs-response.json",
+  "$id": "/schemas/3.1.24/governance/get-plan-audit-logs-response.json",
   "title": "Get Plan Audit Logs Response",
   "description": "Governance state and audit trail for one or more plans.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/core/version-envelope.json"
+      "$ref": "/schemas/3.1.24/core/version-envelope.json"
     },
     {
-      "$ref": "/schemas/3.1.18/core/protocol-envelope.json"
+      "$ref": "/schemas/3.1.24/core/protocol-envelope.json"
     }
   ],
   "x-status": "experimental",
@@ -259,7 +259,7 @@
                   "description": "The AdCP tool (present for check entries)."
                 },
                 "verdict": {
-                  "$ref": "/schemas/3.1.18/enums/governance-decision.json",
+                  "$ref": "/schemas/3.1.24/enums/governance-decision.json",
                   "description": "Governance verdict (present for check entries). Renamed from `status` in 3.1 alongside check-governance-response for vocabulary consistency."
                 },
                 "check_type": {
@@ -271,7 +271,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.1.18/enums/governance-mode.json",
+                  "$ref": "/schemas/3.1.24/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": {
@@ -306,7 +306,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.1.18/enums/escalation-severity.json"
+                        "$ref": "/schemas/3.1.24/enums/escalation-severity.json"
                       },
                       "explanation": {
                         "type": "string"
@@ -326,7 +326,7 @@
                   }
                 },
                 "outcome": {
-                  "$ref": "/schemas/3.1.18/enums/outcome-type.json",
+                  "$ref": "/schemas/3.1.24/enums/outcome-type.json",
                   "description": "Outcome type (present for outcome entries)."
                 },
                 "committed_budget": {
@@ -343,7 +343,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.1.18/enums/purchase-type.json",
+                  "$ref": "/schemas/3.1.24/enums/purchase-type.json",
                   "description": "Purchase type for this entry."
                 },
                 "outcome_status": {
@@ -370,7 +370,7 @@
                   "description": "Governance context correlating this action's lifecycle."
                 },
                 "purchase_type": {
-                  "$ref": "/schemas/3.1.18/enums/purchase-type.json",
+                  "$ref": "/schemas/3.1.24/enums/purchase-type.json",
                   "description": "Type of financial commitment."
                 },
                 "status": {
@@ -418,10 +418,10 @@
       }
     },
     "context": {
-      "$ref": "/schemas/3.1.18/core/context.json"
+      "$ref": "/schemas/3.1.24/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/governance/policy-category-definition.json",
+  "$id": "/schemas/3.1.24/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.1.18/enums/restricted-attribute.json"
+        "$ref": "/schemas/3.1.24/enums/restricted-attribute.json"
       }
     },
     "requires_human_review": {

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/governance/policy-entry.json",
+  "$id": "/schemas/3.1.24/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.1.18/enums/policy-category.json",
+      "$ref": "/schemas/3.1.24/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.1.18/enums/policy-enforcement.json",
+      "$ref": "/schemas/3.1.24/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.1.18/enums/channels.json"
+        "$ref": "/schemas/3.1.24/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.1.18/enums/governance-domain.json"
+        "$ref": "/schemas/3.1.24/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.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/governance/policy-ref.json",
+  "$id": "/schemas/3.1.24/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.1/governance/report-plan-outcome-request.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/governance/report-plan-outcome-request.json",
+  "$id": "/schemas/3.1.24/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'.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/core/version-envelope.json"
+      "$ref": "/schemas/3.1.24/core/version-envelope.json"
     }
   ],
   "x-status": "experimental",
@@ -30,12 +30,12 @@
       "pattern": "^[A-Za-z0-9_.:-]{16,255}$"
     },
     "purchase_type": {
-      "$ref": "/schemas/3.1.18/enums/purchase-type.json",
+      "$ref": "/schemas/3.1.24/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.1.18/enums/outcome-type.json",
+      "$ref": "/schemas/3.1.24/enums/outcome-type.json",
       "description": "Outcome type."
     },
     "seller_response": {
@@ -67,7 +67,7 @@
           }
         },
         "planned_delivery": {
-          "$ref": "/schemas/3.1.18/core/planned-delivery.json",
+          "$ref": "/schemas/3.1.24/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": {
@@ -148,10 +148,10 @@
       "pattern": "^[\\x20-\\x7E]+$"
     },
     "context": {
-      "$ref": "/schemas/3.1.18/core/context.json"
+      "$ref": "/schemas/3.1.24/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [

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

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/governance/report-plan-outcome-response.json",
+  "$id": "/schemas/3.1.24/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.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/core/version-envelope.json"
+      "$ref": "/schemas/3.1.24/core/version-envelope.json"
     }
   ],
   "x-status": "experimental",
@@ -38,7 +38,7 @@
             "description": "Which validation category flagged the issue."
           },
           "severity": {
-            "$ref": "/schemas/3.1.18/enums/escalation-severity.json",
+            "$ref": "/schemas/3.1.24/enums/escalation-severity.json",
             "description": "Finding severity."
           },
           "explanation": {
@@ -76,14 +76,14 @@
     },
     "replayed": {
       "type": "boolean",
-      "description": "Set to true when this response was returned from the idempotency cache rather than from a fresh execution. Set to false (or omitted) when the request was executed fresh. Buyers use this to distinguish cached replays from new executions — matters for billing reconciliation, audit logs, state-machine routing (cached state-tracking fields are historical snapshots, not current state — re-read via the resource's read endpoint), and any downstream system that assumes exactly-once event semantics. From 3.1 onward, `replayed` MAY appear on responses to any request that resolved via the idempotency cache, including read tools — universal `idempotency_key` (see security.mdx §Idempotency) means the cache holds read responses too.",
+      "description": "Set to true when this response was returned from the idempotency cache rather than from a fresh execution. Set to false (or omitted) when the request was executed fresh. Buyers use this to distinguish cached replays from new executions — matters for billing reconciliation, audit logs, state-machine routing (cached state-tracking fields are historical snapshots, not current state — re-read via the resource's read endpoint), and any downstream system that assumes exactly-once event semantics. `replayed` appears only when the request actually resolved through the idempotency cache. Pure reads may ignore an optional `idempotency_key`; when a seller voluntarily caches keyed reads, those responses use the same replay indicator and full cache contract.",
       "default": false
     },
     "context": {
-      "$ref": "/schemas/3.1.18/core/context.json"
+      "$ref": "/schemas/3.1.24/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [