@adcp/sdk 13.1.2 → 13.1.4

package/dist/lib/schemas-data/3.1/content-standards/validate-content-delivery-request.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/content-standards/validate-content-delivery-request.json",
+  "$id": "/schemas/3.1.30/content-standards/validate-content-delivery-request.json",
   "title": "Validate Content Delivery Request",
   "description": "Request parameters for batch validating delivery records against content safety policies",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.24/core/version-envelope.json"
+      "$ref": "/schemas/3.1.30/core/version-envelope.json"
     }
   ],
   "properties": {
@@ -36,7 +36,7 @@
             "description": "When the delivery occurred"
           },
           "artifact": {
-            "$ref": "/schemas/3.1.24/content-standards/artifact.json",
+            "$ref": "/schemas/3.1.30/content-standards/artifact.json",
             "description": "Artifact where ad was delivered"
           },
           "country": {
@@ -82,10 +82,10 @@
       "description": "Include passed records in results"
     },
     "context": {
-      "$ref": "/schemas/3.1.24/core/context.json"
+      "$ref": "/schemas/3.1.30/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.24/core/ext.json"
+      "$ref": "/schemas/3.1.30/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/content-standards/validate-content-delivery-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/content-standards/validate-content-delivery-response.json",
+  "$id": "/schemas/3.1.30/content-standards/validate-content-delivery-response.json",
   "title": "Validate Content Delivery Response",
   "description": "Response payload with per-record verdicts and optional feature breakdown",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.24/core/version-envelope.json"
+      "$ref": "/schemas/3.1.30/core/version-envelope.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/protocol-envelope.json"
+      "$ref": "/schemas/3.1.30/core/protocol-envelope.json"
     }
   ],
   "oneOf": [
@@ -48,7 +48,7 @@
                 "description": "Which delivery record was evaluated"
               },
               "verdict": {
-                "$ref": "/schemas/3.1.24/enums/binary-verdict.json"
+                "$ref": "/schemas/3.1.30/enums/binary-verdict.json"
               },
               "features": {
                 "type": "array",
@@ -61,7 +61,7 @@
                       "description": "Which feature was evaluated. Data features come from the content-standards feature catalog (e.g., 'brand_safety', 'brand_suitability', 'image_dpi'). Record-level structural checks use reserved namespaces: 'record:malformed_artifact', 'delivery:authorization'. Reserved prefixes: 'record:', 'delivery:'."
                     },
                     "status": {
-                      "$ref": "/schemas/3.1.24/enums/feature-check-status.json"
+                      "$ref": "/schemas/3.1.30/enums/feature-check-status.json"
                     },
                     "policy_id": {
                       "type": "string",
@@ -93,10 +93,10 @@
           }
         },
         "context": {
-          "$ref": "/schemas/3.1.24/core/context.json"
+          "$ref": "/schemas/3.1.30/core/context.json"
         },
         "ext": {
-          "$ref": "/schemas/3.1.24/core/ext.json"
+          "$ref": "/schemas/3.1.30/core/ext.json"
         }
       },
       "required": [
@@ -111,14 +111,14 @@
         "errors": {
           "type": "array",
           "items": {
-            "$ref": "/schemas/3.1.24/core/error.json"
+            "$ref": "/schemas/3.1.30/core/error.json"
           }
         },
         "context": {
-          "$ref": "/schemas/3.1.24/core/context.json"
+          "$ref": "/schemas/3.1.30/core/context.json"
         },
         "ext": {
-          "$ref": "/schemas/3.1.24/core/ext.json"
+          "$ref": "/schemas/3.1.30/core/ext.json"
         }
       },
       "required": [

package/dist/lib/schemas-data/3.1/core/account-authorization.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/account-authorization.json",
+  "$id": "/schemas/3.1.30/core/account-authorization.json",
   "title": "Account Authorization",
   "description": "The authenticated caller's grant against a specific account: which tasks are callable, which request fields are modifiable, and the named scope (if any) the grant maps to. Attached to per-account entries in sync_accounts and list_accounts responses when the vendor agent supports scope introspection. APPLIES TO EVERY AGENT TYPE: media-buy sales agents, signals agents, governance agents, creative agents, and brand agents all use the same authorization shape on their sync_accounts / list_accounts responses — the accounts protocol is shared, and so is the scope-introspection mechanism. The standard scope `attestation_verifier` is Media Buy Protocol-specific (it binds to the AAO Verified (Live) qualifier), but the mechanism itself is protocol-neutral: a signals agent can declare a `custom:activation_only` scope, a governance agent can declare a `custom:audit_viewer` scope, and so on. ABSENCE IS SILENCE, NOT DENIAL: the vendor agent simply does not advertise introspectable scope. Callers MUST NOT infer access (or absence of access) from the absence of this object — discover scope by attempting tasks and reading the authz error codes (SCOPE_INSUFFICIENT, READ_ONLY_SCOPE, FIELD_NOT_PERMITTED) when introspection is unavailable. Conceptually analogous to RFC 7662 OAuth 2.0 Token Introspection, specialized for AdCP's task-and-field authorization model. IDENTITY BINDING: the authorization object is implicitly scoped to the (caller identity, account_id) tuple at read time — the same account returned to a different authenticated caller MAY return a different authorization object. Vendor agents MUST resolve 'caller identity' from the authenticated request (not from any client-supplied field) and MUST bind the returned authorization to that identity. CONSISTENCY: for a given (caller identity, account_id) tuple, sequential reads within the refresh window (below) MUST return identical authorization objects, modulo operator-initiated scope changes. Flicker from load-balanced or eventually-consistent backends is non-conformant — compliance engines rely on scope stability for state tracking. REFRESH WINDOW: callers SHOULD re-read authorization at least every 300 seconds of active use against the account. Vendor agents MUST reflect operator-initiated scope changes in sync_accounts / list_accounts responses within 300 seconds of the change being made; a reader that polls every 300s MUST see operator changes within at most one refresh cycle. Vendor agents MAY cache the authorization object briefly but MUST NOT cache past 300 seconds without revalidation.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/account-ref.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/account-ref.json",
+  "$id": "/schemas/3.1.30/core/account-ref.json",
   "title": "Account Reference",
   "description": "Reference to an account by seller-assigned ID or natural key. Use account_id when the seller or upstream platform owns the canonical account namespace: either a seller-defined account supplied out-of-band, or an upstream-managed namespace discovered with list_accounts before account-scoped calls. If a credential may access more than one account, the seller MUST expose list_accounts; if a credential is bound to exactly one account, the seller SHOULD expose list_accounts returning that singleton and MAY omit it only when the same explicit account_id is provided through another declared path or out-of-band onboarding. Use the natural key (brand + operator) when brand + operator (+ sandbox) is the durable protocol key for buyer-declared accounts provisioned through sync_accounts (require_operator_auth: false). For sandbox: account_id namespaces use pre-existing test accounts discovered via list_accounts or supplied out-of-band; buyer-declared accounts use the natural key with sandbox: true.",
   "type": "object",
@@ -21,7 +21,7 @@
     {
       "properties": {
         "brand": {
-          "$ref": "/schemas/3.1.24/core/brand-ref.json",
+          "$ref": "/schemas/3.1.30/core/brand-ref.json",
           "description": "Brand reference identifying the advertiser"
         },
         "operator": {

package/dist/lib/schemas-data/3.1/core/account-with-authorization.json

@@ -1,17 +1,17 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/account-with-authorization.json",
+  "$id": "/schemas/3.1.30/core/account-with-authorization.json",
   "title": "Account With Authorization",
   "description": "List-accounts response item: the full Account object plus optional caller-specific authorization metadata. Named separately so SDKs can generate a stable response item type instead of inventing local wrappers for `Account` plus inline `authorization`.",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.24/core/account.json"
+      "$ref": "/schemas/3.1.30/core/account.json"
     },
     {
       "type": "object",
       "properties": {
         "authorization": {
-          "$ref": "/schemas/3.1.24/core/account-authorization.json",
+          "$ref": "/schemas/3.1.30/core/account-authorization.json",
           "description": "Optional. The caller's scope grant against this account. Vendor agents of any type (media-buy, signals, governance, creative, brand) that support scope introspection SHOULD populate this so callers can preempt SCOPE_INSUFFICIENT / FIELD_NOT_PERMITTED errors rather than discovering scope by trial and error. Media-buy sales agents claiming the `attestation_verifier` standard scope MUST populate it. Absence means the vendor agent does not advertise introspectable scope for this account — callers MUST NOT infer access from absence, and fall back to error-driven discovery via the RBAC error codes."
         }
       }

package/dist/lib/schemas-data/3.1/core/account.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/account.json",
+  "$id": "/schemas/3.1.30/core/account.json",
   "title": "Account",
   "description": "A billing account representing the relationship between a buyer and seller. The account determines rate cards, payment terms, and billing entity.",
   "type": "object",
@@ -23,11 +23,11 @@
       "description": "Optional intermediary who receives invoices on behalf of the advertiser (e.g., agency)"
     },
     "status": {
-      "$ref": "/schemas/3.1.24/enums/account-status.json",
+      "$ref": "/schemas/3.1.30/enums/account-status.json",
       "description": "Account lifecycle status. See the Accounts Protocol overview for the operations matrix showing which tasks are permitted in each state."
     },
     "brand": {
-      "$ref": "/schemas/3.1.24/core/brand-ref.json",
+      "$ref": "/schemas/3.1.30/core/brand-ref.json",
       "description": "Brand reference identifying the advertiser"
     },
     "operator": {
@@ -37,11 +37,11 @@
       "x-entity": "operator"
     },
     "billing": {
-      "$ref": "/schemas/3.1.24/enums/billing-party.json",
+      "$ref": "/schemas/3.1.30/enums/billing-party.json",
       "description": "Who is invoiced on this account. See billing_entity for the invoiced party's business details."
     },
     "billing_entity": {
-      "$ref": "/schemas/3.1.24/core/business-entity.json",
+      "$ref": "/schemas/3.1.30/core/business-entity.json",
       "description": "Business entity details for the party responsible for payment. Contains the legal name, tax IDs, address, and bank details needed for formal B2B invoicing. Corresponds to whoever billing points to (operator, agent, or advertiser). When this account appears in a response, bank details MUST be omitted (write-only)."
     },
     "rate_card": {
@@ -49,7 +49,7 @@
       "description": "Identifier for the rate card applied to this account"
     },
     "payment_terms": {
-      "$ref": "/schemas/3.1.24/enums/payment-terms.json",
+      "$ref": "/schemas/3.1.30/enums/payment-terms.json",
       "description": "Payment terms agreed for this account. Binding for all invoices when the account is active."
     },
     "credit_limit": {
@@ -95,7 +95,7 @@
       "additionalProperties": true
     },
     "account_scope": {
-      "$ref": "/schemas/3.1.24/enums/account-scope.json"
+      "$ref": "/schemas/3.1.30/enums/account-scope.json"
     },
     "governance_agents": {
       "type": "array",
@@ -123,7 +123,7 @@
       "description": "Cloud storage bucket where the seller delivers offline reporting files for this account. Seller provisions a dedicated bucket or a per-account prefix within a shared bucket, and grants the buyer read access out-of-band. Access MUST be scoped at the IAM layer so each account can only read its own prefix — bucket-wide grants are non-compliant even with per-account prefixes. Seller MUST revoke access when the account's status transitions to inactive, suspended, or closed. See security considerations for offline delivery in docs/media-buy/media-buys/optimization-reporting. Only present when the seller supports offline delivery (reporting_delivery_methods includes 'offline' in capabilities).",
       "properties": {
         "protocol": {
-          "$ref": "/schemas/3.1.24/enums/cloud-storage-protocol.json",
+          "$ref": "/schemas/3.1.30/enums/cloud-storage-protocol.json",
           "description": "Cloud storage protocol"
         },
         "bucket": {
@@ -206,12 +206,12 @@
       "type": "array",
       "description": "Account-level webhook subscriptions for notifications whose lifecycle outlives any single media buy (e.g., `creative.status_changed`, `creative.purged`, wholesale feed change payloads). This is an account-scoped delivery surface, not an account-object lifecycle event stream; account status changes are observed through `list_accounts` polling or the one-shot `sync_accounts.push_notification_config` async result channel. Distinct from `push_notification_config` on individual operations, which anchors at a per-resource scope. Buyers register and update entries via `sync_accounts`; sellers echo the applied state here on `list_accounts` reads so buyers can verify what's active. The set is keyed by account-scoped `subscriber_id`; re-registering the same `subscriber_id` replaces that subscriber's config. `authentication.credentials` is write-only — sellers MUST NOT echo legacy auth credentials in this response. When two or more entries register the same `event_types`, each receives an independent fire — see #3009 multi-subscriber composition.",
       "items": {
-        "$ref": "/schemas/3.1.24/core/notification-config.json"
+        "$ref": "/schemas/3.1.30/core/notification-config.json"
       },
       "maxItems": 16
     },
     "ext": {
-      "$ref": "/schemas/3.1.24/core/ext.json"
+      "$ref": "/schemas/3.1.30/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/activation-key.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/activation-key.json",
+  "$id": "/schemas/3.1.30/core/activation-key.json",
   "title": "Activation Key",
   "description": "Universal identifier for using a signal on a destination platform. Can be either a segment ID or a key-value pair depending on the platform's targeting mechanism.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/ad-inventory-config.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/ad-inventory-config.json",
+  "$id": "/schemas/3.1.30/core/ad-inventory-config.json",
   "title": "Ad Inventory Configuration",
   "description": "Break-based ad inventory configuration for an installment. Describes the ad breaks available within the content. For non-break ad formats (host reads, integrations, sponsorships), use product placements instead.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/agent-encryption-key.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/agent-encryption-key.json",
+  "$id": "/schemas/3.1.30/core/agent-encryption-key.json",
   "title": "Agent Encryption Key",
   "description": "X25519 public key for HPKE encryption. Used for TMPX exposure token encryption with HPKE mode_base.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/agent-signing-key.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/agent-signing-key.json",
+  "$id": "/schemas/3.1.30/core/agent-signing-key.json",
   "title": "Agent Signing Key",
   "description": "Publisher-attested public key material for an authorized agent. Buyers use these keys to verify signed agent responses against the trust anchor published in adagents.json rather than trusting key discovery from the agent domain alone.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/app-item.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/app-item.json",
+  "$id": "/schemas/3.1.30/core/app-item.json",
   "title": "App Item",
   "description": "A mobile application within an app-type catalog. Carries the app metadata and store identifiers that platforms use for app install campaigns and re-engagement ads. Maps to Google App Campaigns, Apple Search Ads, Meta App Ads, TikTok App Campaigns, and Snapchat App Install Ads. Each item represents one app on one platform — iOS and Android variants are separate items.",
   "type": "object",
@@ -72,7 +72,7 @@
       "description": "Deep link URI for re-engagement campaigns targeting existing users. Use Universal Links (iOS) or App Links (Android) where available (e.g., 'https://acmegames.com/app/level/5'). Falls back to URI scheme (e.g., 'acmegames://level/5') when universal links are not configured."
     },
     "price": {
-      "$ref": "/schemas/3.1.24/core/price.json",
+      "$ref": "/schemas/3.1.30/core/price.json",
       "description": "App download price. Set amount to 0 for free apps."
     },
     "rating": {
@@ -102,12 +102,12 @@
       "type": "array",
       "description": "Typed creative asset pools for this app. Uses the same OfferingAssetGroup structure as offering-type catalogs. Standard group IDs: 'images_landscape' (promotional hero), 'images_vertical' (9:16 for Snap, Stories), 'images_square' (1:1 for display), 'video' (gameplay or demo video). Supplements icon_url and screenshots for platform-specific format requirements.",
       "items": {
-        "$ref": "/schemas/3.1.24/core/offering-asset-group.json"
+        "$ref": "/schemas/3.1.30/core/offering-asset-group.json"
       },
       "minItems": 1
     },
     "ext": {
-      "$ref": "/schemas/3.1.24/core/ext.json"
+      "$ref": "/schemas/3.1.30/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/asset-group-vocabulary.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/asset-group-vocabulary.json",
+  "$id": "/schemas/3.1.30/core/asset-group-vocabulary.json",
   "title": "AdCP Asset Group Vocabulary Registry",
   "description": "Canonical registry of asset_group_id values used in offering asset groups (OfferingAssetGroup) and in v2 product format declarations. Non-canonical IDs remain valid for platform-specific extensions; this registry codifies the recommended canonical set so that buyers and sellers share a vocabulary for the most common slot roles. Validators may emit soft warnings on non-canonical IDs to encourage convergence.\n\nThe registry covers everything the buyer ships in the manifest's `assets` map — both directly-rendered creative content (image, video, audio) AND content the seller consumes for production (script, creative_brief, video_brief). The seller dispatches per the format's slot declaration. There is no separate \"inputs\" map on the manifest; everything is an asset.\n\n**Two-tier boundary (normative).** This registry is the *canonical, portable* tier — IAB-aligned, platform-agnostic slot roles every adopter shares (`headline`, `body_text`, `main_image`, `cta`, `landing_page_url`, etc.). Platform-specific asset identifiers (e.g., YouTube video IDs, Pinterest pin IDs, TikTok video IDs, Snap attachment IDs, Meta Advantage+ creative IDs) MUST NOT be added here — they live on the canonical's `platform_extensions[]` (URI+digest reference to the platform's extension schema) so the canonical registry stays portable. Earlier drafts carried `youtube_video_id` and `pin_id` here; they were dropped in 3.1 GA precisely because adding them set precedent for every platform's identifier vocabulary to leak into the canonical tier, defeating the registry's portability purpose. Adopters needing to reference an existing platform-hosted asset attach a `platform_extensions[]` entry on the format declaration whose extension schema defines the platform-specific ID slot.",
   "version": "1.3.0",

package/dist/lib/schemas-data/3.1/core/assets/asset-union.json

@@ -1,69 +1,69 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/assets/asset-union.json",
+  "$id": "/schemas/3.1.30/core/assets/asset-union.json",
   "title": "AssetVariant",
   "description": "Canonical union of all asset variant schemas. Referenced from creative-asset.json and creative-manifest.json to ensure a single named type is emitted by schema-to-TypeScript tooling. Add new asset types here and to the creative/asset-types registry.",
   "type": "object",
   "oneOf": [
     {
-      "$ref": "/schemas/3.1.24/core/assets/image-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/image-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/video-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/video-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/audio-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/audio-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/vast-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/vast-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/text-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/text-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/url-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/url-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/html-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/html-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/javascript-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/javascript-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/zip-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/zip-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/webhook-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/webhook-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/css-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/css-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/daast-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/daast-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/markdown-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/markdown-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/brief-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/brief-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/catalog-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/catalog-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/published-post-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/published-post-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/card-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/card-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/pixel-tracker-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/pixel-tracker-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/vast-tracker-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/vast-tracker-asset.json"
     },
     {
-      "$ref": "/schemas/3.1.24/core/assets/daast-tracker-asset.json"
+      "$ref": "/schemas/3.1.30/core/assets/daast-tracker-asset.json"
     }
   ],
   "discriminator": {

package/dist/lib/schemas-data/3.1/core/assets/audio-asset.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/assets/audio-asset.json",
+  "$id": "/schemas/3.1.30/core/assets/audio-asset.json",
   "title": "Audio Asset",
   "description": "Audio asset with URL and technical specifications",
   "type": "object",
@@ -38,7 +38,7 @@
       "description": "Sampling rate in Hz (e.g., 44100, 48000, 96000)"
     },
     "channels": {
-      "$ref": "/schemas/3.1.24/enums/audio-channel-layout.json",
+      "$ref": "/schemas/3.1.30/enums/audio-channel-layout.json",
       "description": "Channel configuration"
     },
     "bit_depth": {
@@ -70,7 +70,7 @@
       "x-accessibility": true
     },
     "provenance": {
-      "$ref": "/schemas/3.1.24/core/provenance.json",
+      "$ref": "/schemas/3.1.30/core/provenance.json",
       "description": "Provenance metadata for this asset, overrides manifest-level provenance"
     }
   },

package/dist/lib/schemas-data/3.1/core/assets/brief-asset.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/assets/brief-asset.json",
+  "$id": "/schemas/3.1.30/core/assets/brief-asset.json",
   "title": "Brief Asset",
   "description": "Campaign-level creative context as an asset. Carries the creative brief through the manifest so it travels with the creative through regeneration, resizing, and auditing.",
   "type": "object",
@@ -16,7 +16,7 @@
   ],
   "allOf": [
     {
-      "$ref": "/schemas/3.1.24/core/creative-brief.json"
+      "$ref": "/schemas/3.1.30/core/creative-brief.json"
     }
   ]
 }

package/dist/lib/schemas-data/3.1/core/assets/card-asset.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/assets/card-asset.json",
+  "$id": "/schemas/3.1.30/core/assets/card-asset.json",
   "title": "Card Asset",
   "description": "A single card in a multi-card creative (image_carousel, future composed carousels). Carries: `media` (an image OR video asset), optional `headline` (short text), optional `description` (longer text), optional `cta` (call-to-action label), optional `landing_page_url` (url asset with `url_type: \"clickthrough\"`).\n\nCovers the multi-card patterns across Meta carousel, Pinterest sponsored pin, Snap Collection, TikTok carousel, and AI-surface result cards. The two-field text shape (`headline` + `description`) reflects how almost every adopter splits short labels from longer copy; Pinterest pin description and Meta per-card description both go in `description`.\n\nUsed as the array element type for the `cards` slot on image_carousel canonicals. Adopters MUST NOT invent per-card key conventions like `card_0_headline` / `cards.0.headline` — the manifest's `assets.cards` value is an array of card-asset objects, period. Per-card platform extensions (e.g., Meta-specific carousel attributes, Pinterest rich-pin metadata, Snap Collection price tags) attach via the `platform_extensions` field, never via inline non-canonical keys.",
   "type": "object",
@@ -18,10 +18,10 @@
       "description": "The card's primary visual asset. Either an `image` or `video` asset, matching the parent format's `allowed_card_media_asset_types` parameter.",
       "oneOf": [
         {
-          "$ref": "/schemas/3.1.24/core/assets/image-asset.json"
+          "$ref": "/schemas/3.1.30/core/assets/image-asset.json"
         },
         {
-          "$ref": "/schemas/3.1.24/core/assets/video-asset.json"
+          "$ref": "/schemas/3.1.30/core/assets/video-asset.json"
         }
       ],
       "discriminator": {
@@ -41,18 +41,18 @@
       "description": "Optional per-card call-to-action label (e.g., 'SHOP_NOW', 'LEARN_MORE'). When the parent format declares `cta_values` (allowed CTA labels), the per-card `cta` MUST be one of those values. Lets a Meta or TikTok carousel show different CTAs per card."
     },
     "landing_page_url": {
-      "$ref": "/schemas/3.1.24/core/assets/url-asset.json",
+      "$ref": "/schemas/3.1.30/core/assets/url-asset.json",
       "description": "Optional per-card click-through URL. URL asset with `url_type: \"clickthrough\"`."
     },
     "platform_extensions": {
       "type": "array",
       "description": "Per-card platform-specific extensions (URI+digest references). Same hosting model as format-level platform_extensions. Use this for Meta carousel-card attributes, Pinterest pin overrides, etc. — NEVER inline non-canonical keys on the card object directly.",
       "items": {
-        "$ref": "/schemas/3.1.24/core/platform-extension-ref.json"
+        "$ref": "/schemas/3.1.30/core/platform-extension-ref.json"
       }
     },
     "provenance": {
-      "$ref": "/schemas/3.1.24/core/provenance.json",
+      "$ref": "/schemas/3.1.30/core/provenance.json",
       "description": "Provenance metadata for this card, overrides manifest-level provenance."
     }
   },

package/dist/lib/schemas-data/3.1/core/assets/catalog-asset.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/assets/catalog-asset.json",
+  "$id": "/schemas/3.1.30/core/assets/catalog-asset.json",
   "title": "Catalog Asset",
   "description": "A typed data feed as a creative asset. Carries catalog context (products, stores, jobs, etc.) within the manifest's assets map.",
   "type": "object",
@@ -16,7 +16,7 @@
   ],
   "allOf": [
     {
-      "$ref": "/schemas/3.1.24/core/catalog.json"
+      "$ref": "/schemas/3.1.30/core/catalog.json"
     }
   ]
 }

package/dist/lib/schemas-data/3.1/core/assets/css-asset.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/assets/css-asset.json",
+  "$id": "/schemas/3.1.30/core/assets/css-asset.json",
   "title": "CSS Asset",
   "description": "CSS stylesheet asset",
   "type": "object",
@@ -19,7 +19,7 @@
       "description": "CSS media query context (e.g., 'screen', 'print')"
     },
     "provenance": {
-      "$ref": "/schemas/3.1.24/core/provenance.json",
+      "$ref": "/schemas/3.1.30/core/provenance.json",
       "description": "Provenance metadata for this asset, overrides manifest-level provenance"
     }
   },

package/dist/lib/schemas-data/3.1/core/assets/daast-asset.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/assets/daast-asset.json",
+  "$id": "/schemas/3.1.30/core/assets/daast-asset.json",
   "title": "DAAST Asset",
   "description": "DAAST (Digital Audio Ad Serving Template) tag for third-party audio ad serving",
   "type": "object",
@@ -11,7 +11,7 @@
       "description": "Discriminator identifying this as a DAAST asset. See /schemas/creative/asset-types for the registry."
     },
     "daast_version": {
-      "$ref": "/schemas/3.1.24/enums/daast-version.json",
+      "$ref": "/schemas/3.1.30/enums/daast-version.json",
       "description": "DAAST specification version"
     },
     "duration_ms": {
@@ -22,7 +22,7 @@
     "tracking_events": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/daast-tracking-event.json"
+        "$ref": "/schemas/3.1.30/enums/daast-tracking-event.json"
       },
       "description": "Tracking events supported by this DAAST tag"
     },
@@ -37,7 +37,7 @@
       "x-accessibility": true
     },
     "provenance": {
-      "$ref": "/schemas/3.1.24/core/provenance.json",
+      "$ref": "/schemas/3.1.30/core/provenance.json",
       "description": "Provenance metadata for this asset, overrides manifest-level provenance"
     }
   },
@@ -53,9 +53,8 @@
           "description": "Discriminator indicating DAAST is delivered via URL endpoint"
         },
         "url": {
-          "type": "string",
-          "format": "uri-template",
-          "description": "URL endpoint that returns DAAST XML. May carry unsubstituted ad-server macros — DAAST/VAST-style `[MACRO]` and `${MACRO}` placeholders are accepted as-is (RFC 6570 syntax); buyers MUST NOT pre-encode macro delimiters, since players match the literal token at substitution time."
+          "$ref": "/schemas/3.1.30/core/macro-bearing-url.json",
+          "description": "URL endpoint that returns DAAST XML. May carry unsubstituted ad-server macros — DAAST/VAST-style `[MACRO]`, `${MACRO}`, and `%%MACRO%%` placeholders are accepted as-is; buyers MUST NOT pre-encode macro delimiters, since players match the literal token at substitution time."
         }
       },
       "required": [

package/dist/lib/schemas-data/3.1/core/assets/daast-tracker-asset.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/assets/daast-tracker-asset.json",
+  "$id": "/schemas/3.1.30/core/assets/daast-tracker-asset.json",
   "title": "DAAST Tracker Asset",
   "description": "A single tracker URL bound to a DAAST `TrackingEvents` event. Audio-side analogue of vast-tracker-asset. The `Impression` URL MUST be modeled as a `url` asset with `url_type: \"tracker_pixel\"`, not as a daast_tracker with `daast_event: \"impression\"`.",
   "type": "object",
@@ -13,7 +13,7 @@
     "daast_event": {
       "allOf": [
         {
-          "$ref": "/schemas/3.1.24/enums/daast-tracking-event.json"
+          "$ref": "/schemas/3.1.30/enums/daast-tracking-event.json"
         },
         {
           "not": {
@@ -34,8 +34,7 @@
       "description": "The DAAST tracking event this URL fires on. MUST NOT be `impression` (model as `url` asset with `url_type: \"tracker_pixel\"`), `clickTracking` / `customClick` (click-tracking trackers go on their own URL asset), `error`, or any of the `ViewableImpression`-element children (`viewable`, `notViewable`, `viewUndetermined`, `measurableImpression`, `viewableImpression`)."
     },
     "url": {
-      "type": "string",
-      "format": "uri-template",
+      "$ref": "/schemas/3.1.30/core/macro-bearing-url.json",
       "description": "Tracker URL that fires when `daast_event` occurs. May carry AdCP universal macros; the sales agent or ad server URL-encodes substituted values at serve time. See docs/creative/universal-macros.mdx."
     },
     "offset": {
@@ -53,7 +52,7 @@
       "description": "Which DAAST creative element this tracker scopes to — `linear` for `<Linear>/<TrackingEvents>` (DAAST 1.1 §3.2.1.7), `companion` for `<CompanionAds>/<Companion>/<TrackingEvents>` (DAAST 1.1 §3.2.2.7, where the only valid event is `creativeView`). DAAST has no `<NonLinearAds>` element. Defaults to `linear`. Sales agents use this to place the tracker in the correct location during DAAST assembly."
     },
     "provenance": {
-      "$ref": "/schemas/3.1.24/core/provenance.json",
+      "$ref": "/schemas/3.1.30/core/provenance.json",
       "description": "Provenance metadata for this asset, overrides manifest-level provenance."
     }
   },