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

package/dist/lib/schemas-data/3.1/creative/preview-creative-response.json

@@ -1,14 +1,14 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/creative/preview-creative-response.json",
+  "$id": "/schemas/3.1.24/creative/preview-creative-response.json",
   "title": "Preview Creative Response",
   "description": "Response containing preview links for one or more creatives. Format matches the request: single preview response for single requests, batch results for batch requests.",
   "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"
     }
   ],
   "discriminator": {
@@ -39,7 +39,7 @@
                 "type": "array",
                 "description": "Array of rendered pieces for this preview variant. Most formats render as a single piece. Companion ad formats (video + banner), multi-placement formats, and adaptive formats render as multiple pieces.",
                 "items": {
-                  "$ref": "/schemas/3.1.18/creative/preview-render.json"
+                  "$ref": "/schemas/3.1.24/creative/preview-render.json"
                 },
                 "minItems": 1
               },
@@ -87,10 +87,10 @@
           "description": "ISO 8601 timestamp when preview links expire. **Optional.** Omit when preview URLs do not expire (some creative agents serve perpetually-valid preview URLs — e.g., signed asset URLs with no TTL, or session-scoped previews that the agent retires explicitly via revocation). When present, consumers MUST treat the URLs as invalid after this timestamp; when omitted, consumers MAY assume the preview URLs are valid until the creative agent revokes them out-of-band (no protocol-level revocation signal exists in 3.x — buyers requiring expiry guarantees SHOULD require sellers that publish `expires_at`)."
         },
         "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": [
@@ -140,7 +140,7 @@
                         "renders": {
                           "type": "array",
                           "items": {
-                            "$ref": "/schemas/3.1.18/creative/preview-render.json"
+                            "$ref": "/schemas/3.1.24/creative/preview-render.json"
                           },
                           "minItems": 1
                         },
@@ -191,7 +191,7 @@
                 "type": "array",
                 "description": "Errors for failed requests",
                 "items": {
-                  "$ref": "/schemas/3.1.18/core/error.json"
+                  "$ref": "/schemas/3.1.24/core/error.json"
                 },
                 "minItems": 1
               }
@@ -232,10 +232,10 @@
           "minItems": 1
         },
         "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": [
@@ -277,7 +277,7 @@
                 "type": "array",
                 "description": "Rendered pieces for this variant",
                 "items": {
-                  "$ref": "/schemas/3.1.18/creative/preview-render.json"
+                  "$ref": "/schemas/3.1.24/creative/preview-render.json"
                 },
                 "minItems": 1
               }
@@ -290,7 +290,7 @@
           "minItems": 1
         },
         "manifest": {
-          "$ref": "/schemas/3.1.18/core/creative-manifest.json",
+          "$ref": "/schemas/3.1.24/core/creative-manifest.json",
           "description": "The rendered creative manifest for this variant — the actual output that was served, not the input assets"
         },
         "expires_at": {
@@ -299,10 +299,10 @@
           "description": "ISO 8601 timestamp when preview links expire. **Optional** — omit for non-expiring preview URLs. See the top-level `PreviewCreativeResponse` branch for the full convention."
         },
         "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/creative/preview-render.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/creative/preview-render.json",
+  "$id": "/schemas/3.1.24/creative/preview-render.json",
   "title": "Preview Render",
   "description": "A single rendered piece of a creative preview with discriminated output format",
   "discriminator": {

package/dist/lib/schemas-data/3.1/creative/sync-creatives-async-response-input-required.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/creative/sync-creatives-async-response-input-required.json",
+  "$id": "/schemas/3.1.24/creative/sync-creatives-async-response-input-required.json",
   "title": "Sync Creatives - Input Required",
   "description": "Payload when sync_creatives task is paused waiting for buyer clarification or approval.",
   "type": "object",
@@ -15,10 +15,10 @@
       "description": "Reason code indicating why buyer input is needed"
     },
     "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"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.1/creative/sync-creatives-async-response-submitted.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/creative/sync-creatives-async-response-submitted.json",
+  "$id": "/schemas/3.1.24/creative/sync-creatives-async-response-submitted.json",
   "title": "Sync Creatives - Submitted",
   "description": "Async task envelope returned when the whole sync_creatives operation cannot be confirmed before the response is emitted — for example, when the seller batches ingestion or when async review must settle before per-item results can be issued. The buyer polls tasks/get with task_id or receives a webhook when the task completes; the creatives array lands on the completion artifact, not this envelope.",
   "type": "object",
@@ -24,14 +24,14 @@
       "type": "array",
       "description": "Optional advisory errors accompanying the submitted envelope. Use only for non-blocking warnings (e.g., throttled_severity advisories, governance observations). Terminal failures belong in the error branch, not here.",
       "items": {
-        "$ref": "/schemas/3.1.18/core/error.json"
+        "$ref": "/schemas/3.1.24/core/error.json"
       }
     },
     "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/creative/sync-creatives-async-response-working.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/creative/sync-creatives-async-response-working.json",
+  "$id": "/schemas/3.1.24/creative/sync-creatives-async-response-working.json",
   "title": "Sync Creatives - Working",
   "description": "Progress payload for active sync_creatives task.",
   "type": "object",
@@ -36,10 +36,10 @@
       "description": "Total number of creatives to process"
     },
     "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"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.1/creative/sync-creatives-request.json

@@ -1,25 +1,25 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/creative/sync-creatives-request.json",
+  "$id": "/schemas/3.1.24/creative/sync-creatives-request.json",
   "title": "Sync Creatives Request",
   "description": "Request parameters for syncing creative assets with upsert semantics - supports bulk operations, scoped updates, and assignment management",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/core/version-envelope.json"
+      "$ref": "/schemas/3.1.24/core/version-envelope.json"
     }
   ],
   "x-mutates-state": true,
   "properties": {
     "account": {
-      "$ref": "/schemas/3.1.18/core/account-ref.json",
+      "$ref": "/schemas/3.1.24/core/account-ref.json",
       "description": "Account that owns these creatives."
     },
     "creatives": {
       "type": "array",
       "description": "Array of creative assets to sync (create or update)",
       "items": {
-        "$ref": "/schemas/3.1.18/core/creative-asset.json"
+        "$ref": "/schemas/3.1.24/core/creative-asset.json"
       },
       "minItems": 1,
       "maxItems": 100
@@ -91,19 +91,19 @@
       "description": "When true, rehearse this sync_creatives operation without applying it. Validates the actual trafficking request in the seller's current context, including library upsert semantics, creative IDs, assignments, account-scoped gates, and seller policies, then returns what would be created/updated/deleted. This is distinct from validate_input, which only validates manifest structure against canonical/product format targets."
     },
     "validation_mode": {
-      "$ref": "/schemas/3.1.18/enums/validation-mode.json",
+      "$ref": "/schemas/3.1.24/enums/validation-mode.json",
       "default": "strict",
       "description": "Validation strictness. 'strict' fails entire sync on any validation error. 'lenient' processes valid creatives and reports errors."
     },
     "push_notification_config": {
-      "$ref": "/schemas/3.1.18/core/push-notification-config.json",
+      "$ref": "/schemas/3.1.24/core/push-notification-config.json",
       "description": "Optional webhook configuration for async sync notifications. The agent will send a webhook when sync completes if the operation takes longer than immediate response time (typically for large bulk operations or manual approval/HITL)."
     },
     "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/creative/sync-creatives-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/creative/sync-creatives-response.json",
+  "$id": "/schemas/3.1.24/creative/sync-creatives-response.json",
   "title": "Sync Creatives Response",
   "description": "Response from creative sync operation. Exactly one of three shapes: (1) synchronous success — per-creative results in the creatives array (best-effort processing with per-item status/failures); (2) terminal failure — errors array with no creatives processed; (3) submitted task envelope — status 'submitted' with task_id when the whole operation is queued (batch ingestion, async review that must settle before per-item results can be issued). The submitted branch MAY carry advisory errors for non-blocking warnings; terminal failures belong in the error branch. Final per-item results land on the task completion artifact, not this envelope. These three shapes are mutually exclusive — a response has exactly one.",
   "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"
     }
   ],
   "oneOf": [
@@ -34,15 +34,15 @@
                 "x-entity": "creative"
               },
               "account": {
-                "$ref": "/schemas/3.1.18/core/account.json",
+                "$ref": "/schemas/3.1.24/core/account.json",
                 "description": "Account that owns this creative"
               },
               "action": {
-                "$ref": "/schemas/3.1.18/enums/creative-action.json",
+                "$ref": "/schemas/3.1.24/enums/creative-action.json",
                 "description": "Action taken for this creative during this sync operation (lifecycle operation, not approval state)."
               },
               "status": {
-                "$ref": "/schemas/3.1.18/enums/creative-status.json",
+                "$ref": "/schemas/3.1.24/enums/creative-status.json",
                 "description": "Advisory review-lifecycle state of the creative after this sync — a UI hint and polling-scheduling signal, NOT a spend-authorization gate. Orthogonal to action — action says what the sync did (created, updated, ...); status says where the creative sits in review. Values come from CreativeStatus only (processing, pending_review, approved, suspended, rejected, archived) — never from CreativeAction. Sellers with async review return processing or pending_review; sellers with synchronous review MAY return a terminal value (approved, rejected) or suspended when a recoverable dependency/authorization gate prevents serving. Buyers MUST NOT gate downstream spend or package activation on status: approved from this response — a compromised or buggy seller could declare approved while bypassing content-policy review. Reconcile via list_creatives or a signed review webhook before committing spend. Authoritative state is always via list_creatives. MUST be omitted when action is failed or deleted (the creative has no meaningful review state — failure details belong in the errors array; deleted creatives are gone from the library). Omit entirely when the seller has no review lifecycle at all."
               },
               "platform_id": {
@@ -60,7 +60,7 @@
                 "type": "array",
                 "description": "Validation or processing errors (only present when action='failed')",
                 "items": {
-                  "$ref": "/schemas/3.1.18/core/error.json"
+                  "$ref": "/schemas/3.1.24/core/error.json"
                 }
               },
               "warnings": {
@@ -135,10 +135,10 @@
           "description": "When true, this response contains simulated data from sandbox mode."
         },
         "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": [
@@ -179,15 +179,15 @@
           "type": "array",
           "description": "Operation-level errors that prevented processing any creatives (e.g., authentication failure, service unavailable, invalid request format)",
           "items": {
-            "$ref": "/schemas/3.1.18/core/error.json"
+            "$ref": "/schemas/3.1.24/core/error.json"
           },
           "minItems": 1
         },
         "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": [
@@ -253,14 +253,14 @@
           "type": "array",
           "description": "Optional advisory errors accompanying the submitted envelope. Use only for non-blocking warnings (e.g., throttled_severity advisories, governance observations). Terminal failures belong in the error branch, not here.",
           "items": {
-            "$ref": "/schemas/3.1.18/core/error.json"
+            "$ref": "/schemas/3.1.24/core/error.json"
           }
         },
         "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/creative/validate-input-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/creative/validate-input-request.json",
+  "$id": "/schemas/3.1.24/creative/validate-input-request.json",
   "title": "Validate Input Request",
   "description": "Request payload for the validate_input task. Lets buyers preflight a creative manifest against canonical formats and/or specific products before committing to a render or other expensive creative-production step. It validates manifest structure and target format constraints only: slot counts, asset types, parameter ranges, and format-shape constraints. It does not rehearse a seller's library mutation, creative_id upsert semantics, package assignments, account authorization, active-delivery protections, or other trafficking-time gates. When the question is final seller acceptance for a creative that is ready to traffic, call sync_creatives directly; use dry_run: true for a non-mutating rehearsal of that operation. Used by build_creative internally to validate inputs before producing output. For genuinely nondeterministic generative platforms (Veo/Sora/Runway-class) where predictive validation is impossible, the platform's own post-synthesis QA loop applies — validate_input is the predictable-case primitive.\n\nThe `targets[]` array is a discriminated list of validation targets, mirroring the response shape on `validate-input-result.json#target`. Each entry has a `kind` (canonical | product | third_party_format) plus a kind-specific identifier. Discriminated-by-kind on both sides eliminates a wire-shape mismatch: a previous draft used `format_ids: string[]` for canonical names alongside `product_ids: string[]`, which collided with `Product.format_ids: FormatId[]` ({agent_url, id}) — codegen would emit the same field name with two different types. Discriminated `targets[]` makes the intent explicit and codegen-clean.",
   "type": "object",
@@ -9,15 +9,15 @@
   ],
   "properties": {
     "account": {
-      "$ref": "/schemas/3.1.18/core/account-ref.json",
+      "$ref": "/schemas/3.1.24/core/account-ref.json",
       "description": "Optional account scope for seller-specific product validation. Required by sellers that route product declarations by buyer account."
     },
     "brand": {
-      "$ref": "/schemas/3.1.18/core/brand-ref.json",
+      "$ref": "/schemas/3.1.24/core/brand-ref.json",
       "description": "Optional brand scope when account is omitted or the seller keys sandbox validation by brand identity."
     },
     "manifest": {
-      "$ref": "/schemas/3.1.18/core/creative-manifest.json",
+      "$ref": "/schemas/3.1.24/core/creative-manifest.json",
       "description": "Creative manifest to validate."
     },
     "targets": {

package/dist/lib/schemas-data/3.1/creative/validate-input-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/creative/validate-input-response.json",
+  "$id": "/schemas/3.1.24/creative/validate-input-response.json",
   "title": "Validate Input Response",
   "description": "Response payload for the validate_input task. Returns per-target manifest validation results — one entry per canonical, product, or third-party target requested. Each result carries a `result_kind` discriminator (`validated_pass` / `validated_fail` / `unvalidatable_nondeterministic`) so callers can branch on three meaningfully different outcomes. A pass means the manifest is structurally valid for that target; it does not mean a later sync_creatives call will be accepted, because trafficking-time gates such as account authorization, creative_id upsert state, package assignments, active-delivery protections, and seller review policy are outside validate_input's scope. The `predicted` field on violations carries the platform's pre-flight estimate (e.g., predicted audio duration from text-length analysis), NOT the actual output — there is no protocol state for orphaned out-of-spec artifacts. For nondeterministic generative platforms (Veo / Sora / Runway-class with `synthesis_nondeterministic: true`), the result_kind is `unvalidatable_nondeterministic` — predictive validation is impossible, the platform's post-synthesis QA loop applies on `build_creative`, and out-of-spec output never reaches this surface (instead `build_creative` returns task_failed with synthesis_failed reason).\n\nThe `ValidateInputResult` type is split into its own schema (`/schemas/creative/validate-input-result.json`) rather than inlined here because the same per-target shape is intended for reuse by adjacent async-validation surfaces (planned: per-batch result envelopes on `build_creative` async paths, and asynchronous canonical-against-product validation in `sync_creatives`). Producers that only need the synchronous batch shape today MAY treat the split as YAGNI, but the schema reuse anchors the violation/retry shape so downstream surfaces don't drift.",
   "type": "object",
@@ -11,7 +11,7 @@
     "results": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.1.18/creative/validate-input-result.json"
+        "$ref": "/schemas/3.1.24/creative/validate-input-result.json"
       },
       "description": "Per-target validation results."
     }
@@ -19,10 +19,10 @@
   "additionalProperties": true,
   "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"
     }
   ]
 }

package/dist/lib/schemas-data/3.1/creative/validate-input-result.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/creative/validate-input-result.json",
+  "$id": "/schemas/3.1.24/creative/validate-input-result.json",
   "title": "Validate Input Result",
   "description": "Per-target result of a validate_input call. The `result_kind` discriminator (replacing the earlier boolean `ok`) lets buyers distinguish three meaningfully different outcomes:\n\n- `validated_pass` — manifest is structurally valid against the target. This is not seller trafficking acceptance; use `sync_creatives` or `sync_creatives` with `dry_run: true` for upload/update, account, assignment, policy, and lifecycle gates.\n- `validated_fail` — manifest is structurally evaluable AND fails specific constraints. `violations[]` enumerates which. Buyers fix and retry.\n- `unvalidatable_nondeterministic` — predictive validation is impossible because the target's production pipeline is genuinely nondeterministic (Veo / Sora / Runway-class formats with `synthesis_nondeterministic: true`). The platform's own post-synthesis QA loop applies; outcome is unknowable until `build_creative` runs. Buyers MUST plan for the QA-loop semantics: submission may return `task_failed` with a `synthesis_failed` reason if the QA loop exhausts. There is no protocol state for orphaned out-of-spec artifacts.\n\nThe boolean `ok` field carried in earlier drafts is removed — it conflated `validated_fail` (a real validation result the buyer can act on) with `unvalidatable_nondeterministic` (a structural property of the target the buyer needs to handle differently). `validated_fail` returns `violations[]`; `unvalidatable_nondeterministic` does not (there's nothing to enumerate).\n\n**Scope of validation (normative).** `validate_input` validates **manifest structure** against the canonical / product / third-party format target — slot counts, asset types, parameter ranges, format-shape constraints. It does NOT predict the surface's per-impression rendering choice. This distinction matters for `composition_model: algorithmic` formats (`responsive_creative`, `agent_placement`) where the surface picks combinations or phrasing at delivery time: the buyer's asset pool can still be structurally validated (does it meet the count/size/length requirements?) → `validated_pass` or `validated_fail` with violations. What's unpredictable is the rendered output composition, and that's NOT what `validate_input` claims to predict. `unvalidatable_nondeterministic` is reserved for `synthesis_nondeterministic: true` cases where the production pipeline itself can't be evaluated upfront — distinct from algorithmic composition where the inputs ARE evaluable but the output rendering isn't. Buyers calling `validate_input` on an algorithmic-composition target SHOULD expect a structural verdict (pass/fail), not a rendering preview.",
   "type": "object",

package/dist/lib/schemas-data/3.1/creative/video-brief.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/creative/video-brief.json",
+  "$id": "/schemas/3.1.24/creative/video-brief.json",
   "title": "Video Brief",
   "description": "Structured per-segment generation brief for generative video products (Veo / Sora / Runway-class). Each `segments[]` entry declares a timed prompt the synthesis pipeline turns into a continuous shot — `order`, `duration_ms`, `prompt`, optional `vo` (voiceover line) and `caption` (on-screen text). This is a *generation* brief, not a creative-direction storyboard: there is no camera direction, shot type, mood, or reference-asset attachment. Buyers wanting to direct camera, lighting, or reference-image conditioning attach a `reference-asset.json` with `purpose: \"storyboard\"` separately — that's the visual-direction surface; video-brief is the structured prompt the model receives. Renamed from earlier `scenes` to call the shape what it is (a brief, not a scene-level production document).",
   "type": "object",

package/dist/lib/schemas-data/3.1/enums/account-scope.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/account-scope.json",
+  "$id": "/schemas/3.1.24/enums/account-scope.json",
   "title": "Account Scope",
   "description": "How the seller scoped a billing account relative to the operator and brand dimensions.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/account-status.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/account-status.json",
+  "$id": "/schemas/3.1.24/enums/account-status.json",
   "title": "Account Status",
   "description": "Advertiser account status in the account lifecycle",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/action-not-allowed-reason.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/action-not-allowed-reason.json",
+  "$id": "/schemas/3.1.24/enums/action-not-allowed-reason.json",
   "title": "Action Not Allowed Reason",
   "description": "Reason a mutation on update_media_buy was rejected with ACTION_NOT_ALLOWED. Lets buyer SDKs offer a structured recovery path without re-fetching the buy.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/action-source.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/action-source.json",
+  "$id": "/schemas/3.1.24/enums/action-source.json",
   "title": "Action Source",
   "description": "Where the conversion event originated",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/adcp-protocol.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/adcp-protocol.json",
+  "$id": "/schemas/3.1.24/enums/adcp-protocol.json",
   "title": "AdCP Protocol",
   "description": "AdCP protocols for task categorization — referenced by tasks-list-request, webhook payloads, and other task-lifecycle surfaces. Values are kebab-case. This enum shares the same axis as supported_protocols (see /schemas/protocol/get-adcp-capabilities-response.json), which uses snake_case on the wire. Compliance testing support is declared via the `capabilities.compliance_testing` block, not as a protocol value.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/adjustment-kind.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/adjustment-kind.json",
+  "$id": "/schemas/3.1.24/enums/adjustment-kind.json",
   "title": "Price Adjustment Kind",
   "description": "Categorizes how a price adjustment affects the transaction",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/advertiser-industry.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/advertiser-industry.json",
+  "$id": "/schemas/3.1.24/enums/advertiser-industry.json",
   "title": "Advertiser Industry",
   "description": "Standardized advertiser industry classification. Top-level categories classify the advertiser's primary business. Dot-notation subcategories (e.g., 'media_entertainment.podcasts') provide platform-specific precision where needed. Sellers map these to platform-native codes (Spotify ADV categories, LinkedIn industry IDs, IAB Content Taxonomy, etc.). Sellers MUST accept unknown values gracefully — treat unrecognized values as the parent category (strip the subcategory) or as uncategorized. This ensures forward compatibility as the taxonomy evolves.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/age-verification-method.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/age-verification-method.json",
+  "$id": "/schemas/3.1.24/enums/age-verification-method.json",
   "title": "Age Verification Method",
   "description": "Methods for verifying user age for compliance. Does not include 'inferred' as it is not accepted for regulatory compliance.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/assessment-status.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/assessment-status.json",
+  "$id": "/schemas/3.1.24/enums/assessment-status.json",
   "title": "Assessment Status",
   "description": "Standardized quality level for health and readiness assessments. Comparable across sellers — buyer agents should use this for cross-seller decisions.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/asset-content-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/asset-content-type.json",
+  "$id": "/schemas/3.1.24/enums/asset-content-type.json",
   "title": "Asset Content Type",
   "description": "Types of content that can be used as creative assets. Describes what KIND of content an asset contains (image, video, code, etc.), not where it displays.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/attestation-claim.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/attestation-claim.json",
+  "$id": "/schemas/3.1.24/enums/attestation-claim.json",
   "title": "Attestation Claim",
   "description": "A claim a verified identity attestation can establish about a user. Personhood and age-threshold claims are deliberately a small, closed, issuer-agnostic set: a buyer must share semantics to act on a claim, and ZK proofs are practical only for a handful of standard thresholds. Age claims are threshold-only (\"over N\") — never a date of birth or exact age — and resolve to eligibility, never crossing the wire as an attribute. The set is additive: new thresholds may be added when a real legal threshold requires one.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/attribution-methodology.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/attribution-methodology.json",
+  "$id": "/schemas/3.1.24/enums/attribution-methodology.json",
   "title": "Attribution Methodology",
   "description": "How attribution between ad exposure and outcome events was computed. Used as a `qualifier.attribution_methodology` key on `committed_metrics`, `missing_metrics`, `metric_aggregates`, and `performance-feedback.metric` to disambiguate the same outcome metric reported under different methodologies — `conversion_value` measured deterministically (matched purchase IDs) is not the same number as `conversion_value` measured probabilistically (modeled match) and should never be summed across methodologies. The retail-media closed-loop pattern typically reports under `deterministic_purchase`; MMM and clean-room outputs typically report under `modeled` or `probabilistic`; panel-based measurement (Nielsen, comScore, Edison) reports under `panel_based`.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/attribution-model.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/attribution-model.json",
+  "$id": "/schemas/3.1.24/enums/attribution-model.json",
   "title": "Attribution Model",
   "description": "Attribution model used for conversion measurement",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/audience-source.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/audience-source.json",
+  "$id": "/schemas/3.1.24/enums/audience-source.json",
   "title": "Audience Source",
   "description": "Origin of an audience segment in delivery reporting breakdowns. Only 'synced' audiences are directly targetable via the targeting overlay; other sources are informational.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/audience-status.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/audience-status.json",
+  "$id": "/schemas/3.1.24/enums/audience-status.json",
   "title": "Audience Status",
   "description": "Matching status of a synced audience on a seller platform. Present when the sync action is created, updated, or unchanged; absent when the action is deleted or failed. See the Audience Sync specialism for transition rules.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/audio-channel-layout.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/audio-channel-layout.json",
+  "$id": "/schemas/3.1.24/enums/audio-channel-layout.json",
   "title": "Audio Channel Layout",
   "description": "Audio channel configuration for audio and video assets",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/audio-distribution-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/audio-distribution-type.json",
+  "$id": "/schemas/3.1.24/enums/audio-distribution-type.json",
   "title": "Audio Distribution Type",
   "description": "Declared audio distribution classification for radio, streaming-audio, podcast, and other audio inventory, using IAB Tech Lab/OpenRTB 2.6 audio.feed definitions with AdCP-native value names. This is seller-declared discovery metadata, not independent verification of inventory quality or delivery context.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/auth-scheme.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/auth-scheme.json",
+  "$id": "/schemas/3.1.24/enums/auth-scheme.json",
   "title": "Authentication Scheme",
   "description": "Legacy authentication schemes for the webhook auth block. Bearer: token sent in Authorization header. HMAC-SHA256: legacy shared-secret signing. Both are deprecated; new integrations SHOULD omit the authentication block and use the RFC 9421 webhook signing profile (applicable on schemas where authentication is optional). Removed in AdCP 4.0.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/available-metric.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/available-metric.json",
+  "$id": "/schemas/3.1.24/enums/available-metric.json",
   "title": "Available Metric",
   "description": "Standard delivery and performance metrics available for reporting",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/billing-party.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/enums/billing-party.json",
+  "$id": "/schemas/3.1.24/enums/billing-party.json",
   "title": "Billing Party",
   "description": "Which party the seller invoices for an account. Determines the billing entity and invoicing flow.",
   "type": "string",