@adcp/sdk 15.9.5 → 15.9.7

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/scan-type.json",
+  "$id": "/schemas/3.1.30/enums/scan-type.json",
   "title": "Scan Type",
   "description": "Video scan method. Modern digital delivery requires progressive scan; interlaced is retained for broadcast legacy content.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/si-session-status.json",
+  "$id": "/schemas/3.1.30/enums/si-session-status.json",
   "title": "SI Session Status",
   "description": "State of a Sponsored Intelligence session between a host and a brand agent",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/signal-catalog-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/signal-catalog-type.json",
+  "$id": "/schemas/3.1.30/enums/signal-catalog-type.json",
   "title": "Signal Availability Type",
   "description": "Commercial/provenance types for signals available for audience targeting",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/signal-source.json",
+  "$id": "/schemas/3.1.30/enums/signal-source.json",
   "title": "Signal Source",
   "description": "Source type for signal identifiers. Determines how the signal is referenced and whether authorization can be externally verified.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/signal-value-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/signal-value-type.json",
+  "$id": "/schemas/3.1.30/enums/signal-value-type.json",
   "title": "Signal Value Type",
   "description": "The data type of a signal's values, determining how it can be targeted",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/snapshot-unavailable-reason.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/snapshot-unavailable-reason.json",
+  "$id": "/schemas/3.1.30/enums/snapshot-unavailable-reason.json",
   "title": "Snapshot Unavailable Reason",
   "description": "Machine-readable reason a delivery snapshot was requested but could not be returned. Present only when include_snapshot was true and snapshot data is unavailable.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/social-placement-surface.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/social-placement-surface.json",
+  "$id": "/schemas/3.1.30/enums/social-placement-surface.json",
   "title": "Social Placement Surface",
   "description": "Declared social-placement surface classification for social inventory, distinguishing the in-app surface where a social placement renders. Values name the semantic surface, not platform brands. 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/sort-direction.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/sort-direction.json",
+  "$id": "/schemas/3.1.30/enums/sort-direction.json",
   "title": "Sort Direction",
   "description": "Sort direction for list queries",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/sort-metric.json",
+  "$id": "/schemas/3.1.30/enums/sort-metric.json",
   "title": "Sort Metric",
   "description": "Numeric delivery metrics available for sorting breakdown rows. Subset of delivery-metrics fields that are flat numeric values (excludes nested objects like quartile_data, dooh_metrics, viewability, by_event_type, by_action_source).",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/special-category.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/special-category.json",
+  "$id": "/schemas/3.1.30/enums/special-category.json",
   "title": "Special Category",
   "description": "Category of special or event-anchored content",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/specialism.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/specialism.json",
+  "$id": "/schemas/3.1.30/enums/specialism.json",
   "title": "AdCP Specialism",
   "description": "Specialized capability claims an agent can make. Each specialism maps to a compliance storyboard bundle published at /compliance/{version}/specialisms/{id}/. An agent asserts specialisms it supports in get_adcp_capabilities; the AAO compliance runner executes the matching storyboards to verify the claim.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/sponsored-placement-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/sponsored-placement-type.json",
+  "$id": "/schemas/3.1.30/enums/sponsored-placement-type.json",
   "title": "Sponsored Placement Type",
   "description": "Declared sponsored-placement classification for catalog-driven retail-media inventory, distinguishing where the sponsored placement renders on the retailer surface. 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/talent-role.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/talent-role.json",
+  "$id": "/schemas/3.1.30/enums/talent-role.json",
   "title": "Talent Role",
   "description": "Role of a person associated with a collection or installment",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/task-status.json",
+  "$id": "/schemas/3.1.30/enums/task-status.json",
   "title": "Task Status",
   "description": "Standardized task status values based on A2A TaskState enum. Indicates the current state of any AdCP operation.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/task-type.json",
+  "$id": "/schemas/3.1.30/enums/task-type.json",
   "title": "Task Type",
   "description": "Valid AdCP task types across all domains. These represent the complete set of operations that can be tracked via the task management system.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/transport-mode.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/transport-mode.json",
+  "$id": "/schemas/3.1.30/enums/transport-mode.json",
   "title": "Transport Mode",
   "description": "Transportation modes for isochrone-based catchment area calculations. Determines how travel time translates to geographic reach.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/travel-time-unit.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/travel-time-unit.json",
+  "$id": "/schemas/3.1.30/enums/travel-time-unit.json",
   "title": "Travel Time Unit",
   "description": "Time unit for isochrone (travel-time catchment) calculations.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/uid-type.json",
+  "$id": "/schemas/3.1.30/enums/uid-type.json",
   "title": "UID Type",
   "description": "Type of user identifier. Used in audience sync, event logging, and TMP identity match requests to tell the receiver how to interpret and resolve the identifier; some types, including PAIR, are publisher-scoped rather than universal identity-graph tokens.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/universal-macro.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/universal-macro.json",
+  "$id": "/schemas/3.1.30/enums/universal-macro.json",
   "title": "Universal Macro",
   "description": "Standardized macro placeholders for dynamic value substitution in creative tracking URLs. Macros are replaced with actual values at impression time. See docs/creative/universal-macros.mdx for detailed documentation.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/update-frequency.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/update-frequency.json",
+  "$id": "/schemas/3.1.30/enums/update-frequency.json",
   "title": "Update Frequency",
   "description": "Frequency of product catalog updates",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/url-asset-type.json",
+  "$id": "/schemas/3.1.30/enums/url-asset-type.json",
   "title": "URL Asset Type",
   "description": "Types of URL assets for tracking and click-through purposes",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/validation-mode.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/validation-mode.json",
+  "$id": "/schemas/3.1.30/enums/validation-mode.json",
   "title": "Validation Mode",
   "description": "Creative validation strictness levels",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/vast-tracking-event.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/vast-tracking-event.json",
+  "$id": "/schemas/3.1.30/enums/vast-tracking-event.json",
   "title": "VAST Tracking Event",
   "description": "Tracking events for video ads. Includes the IAB VAST 4.2 `Tracking@event` enumeration (vast_4.2.xsd `TrackingEvents_type`, lines 112–136), plus AdCP-flattened representations of the `Impression`, `Error`, `VideoClicks`, and `ViewableImpression` elements (which live in dedicated VAST elements, not under `<TrackingEvents>` — they are surfaced here so a single declared list can cover everything a measurement vendor wants to track). `fullscreen` / `exitFullscreen` are retained for VAST 2.x / 3.x compatibility (VAST 4.0+ replaced them with `playerExpand` / `playerCollapse`). `measurableImpression` is an AdCP extension for MRC measurability signals.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/vast-version.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/vast-version.json",
+  "$id": "/schemas/3.1.30/enums/vast-version.json",
   "title": "VAST Version",
   "description": "Supported VAST (Video Ad Serving Template) specification versions",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/video-placement-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/video-placement-type.json",
+  "$id": "/schemas/3.1.30/enums/video-placement-type.json",
   "title": "Video Placement Type",
   "description": "Declared video placement classification for OLV and other video inventory, using the IAB Tech Lab/OpenRTB 2.6 video.plcmt 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/viewability-standard.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/viewability-standard.json",
+  "$id": "/schemas/3.1.30/enums/viewability-standard.json",
   "title": "Viewability Standard",
   "description": "Viewability measurement standard applied to determine whether an impression qualifies as viewable. These are materially different thresholds and should not be compared across standards.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/watermark-media-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/watermark-media-type.json",
+  "$id": "/schemas/3.1.30/enums/watermark-media-type.json",
   "title": "Watermark Media Type",
   "description": "Media category of a content watermark. Identifies what kind of content the watermark is applied to, which determines the detection and verification methods required.",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/wcag-level.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/wcag-level.json",
+  "$id": "/schemas/3.1.30/enums/wcag-level.json",
   "title": "WCAG Level",
   "description": "Web Content Accessibility Guidelines conformance level",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/webhook-response-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/webhook-response-type.json",
+  "$id": "/schemas/3.1.30/enums/webhook-response-type.json",
   "title": "Webhook Response Type",
   "description": "Expected response content type from webhook endpoints",
   "type": "string",

package/dist/lib/schemas-data/3.1/enums/webhook-security-method.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/webhook-security-method.json",
+  "$id": "/schemas/3.1.30/enums/webhook-security-method.json",
   "title": "Webhook Security Method",
   "description": "Security methods for authenticating webhook requests",
   "type": "string",

package/dist/lib/schemas-data/3.1/error-details/account-setup-required.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/error-details/account-setup-required.json",
+  "$id": "/schemas/3.1.30/error-details/account-setup-required.json",
   "title": "Account Setup Required Details",
   "description": "Recommended details shape for ACCOUNT_SETUP_REQUIRED errors. Provides setup URL and remaining steps.",
   "type": "object",

package/dist/lib/schemas-data/3.1/error-details/action-not-allowed.json

@@ -1,23 +1,23 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/error-details/action-not-allowed.json",
+  "$id": "/schemas/3.1.30/error-details/action-not-allowed.json",
   "title": "Action Not Allowed Details",
   "description": "Details payload for ACTION_NOT_ALLOWED errors. Lets buyer SDKs offer a structured recovery path without a separate get_media_buys round-trip.",
   "type": "object",
   "properties": {
     "attempted_action": {
-      "$ref": "/schemas/3.1.29/enums/media-buy-valid-action.json",
+      "$ref": "/schemas/3.1.30/enums/media-buy-valid-action.json",
       "description": "The action the request mapped to, per the normative action-to-field mapping in update_media_buy task-reference."
     },
     "reason": {
-      "$ref": "/schemas/3.1.29/enums/action-not-allowed-reason.json",
+      "$ref": "/schemas/3.1.30/enums/action-not-allowed-reason.json",
       "description": "Why the action was rejected. Buyer SDKs branch on this to choose a recovery path."
     },
     "currently_available_actions": {
       "type": "array",
       "description": "Echo of the buy's resolved `available_actions[]` at rejection time. Buyer SDKs render this to the caller as the recovery option set.",
       "items": {
-        "$ref": "/schemas/3.1.29/core/media-buy-available-action.json"
+        "$ref": "/schemas/3.1.30/core/media-buy-available-action.json"
       },
       "uniqueItems": true
     }

package/dist/lib/schemas-data/3.1/error-details/agent-permission-denied.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/error-details/agent-permission-denied.json",
+  "$id": "/schemas/3.1.30/error-details/agent-permission-denied.json",
   "title": "Agent Permission Denied Details",
   "description": "Recommended details shape for `PERMISSION_DENIED` errors when the gate that fired is a non-status per-agent provisioning constraint (`scope: \"agent\"` plus a registered `reason`) — distinct from generic credential-shaped permission failures (no `scope`), from per-account/per-task authorization failures (`SCOPE_INSUFFICIENT`, `READ_ONLY_SCOPE`, `FIELD_NOT_PERMITTED`), and from per-agent commercial-status rejections (`AGENT_SUSPENDED` / `AGENT_BLOCKED`, which are their own discriminator codes and do NOT carry an explicit `scope` field). The shape carries a registered `reason` value identifying the gate; `additionalProperties: false` clamps it so adopters cannot invent ad-hoc per-agent state keys (rate cards, payment terms, credit limit, billing entity, custom reason strings) — full disclosure of the agent's commercial state in a single probe is a per-agent oracle the clamp prevents. New `reason` values MUST be registered in the schema's enum so cross-language SDKs can dispatch without parsing prose; future per-agent state additions belong on new dedicated codes (each with its own clamped details shape), NOT by relaxing this shape. The cross-tenant onboarding oracle clamp and its full channel-coverage requirements are normative in `error-handling.mdx` Per-Agent Authorization Gate — this schema description does not restate them to avoid drift.",
   "type": "object",

package/dist/lib/schemas-data/3.1/error-details/audience-too-small.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/error-details/audience-too-small.json",
+  "$id": "/schemas/3.1.30/error-details/audience-too-small.json",
   "title": "Audience Too Small Details",
   "description": "Recommended details shape for AUDIENCE_TOO_SMALL errors. Provides size thresholds so agents can broaden targeting.",
   "type": "object",

package/dist/lib/schemas-data/3.1/error-details/authorization-required.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/error-details/authorization-required.json",
+  "$id": "/schemas/3.1.30/error-details/authorization-required.json",
   "title": "Authorization Required Details",
   "description": "Recommended details shape for AUTHORIZATION_REQUIRED errors. The caller's AdCP credential was accepted, but the seller cannot complete the requested action until one or more downstream platform connections or grants are completed, restored, or refreshed.",
   "type": "object",
@@ -8,14 +8,14 @@
     "required_connections": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.1.29/core/downstream-connection-requirement.json"
+        "$ref": "/schemas/3.1.30/core/downstream-connection-requirement.json"
       },
       "description": "Complete set of downstream connections known to be required for the relevant product, format, or request."
     },
     "missing_connections": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.1.29/core/downstream-connection-requirement.json"
+        "$ref": "/schemas/3.1.30/core/downstream-connection-requirement.json"
       },
       "description": "Subset of downstream connections that blocked the current request. Sellers SHOULD populate this array when the caller needs to route a human through a connections flow. Entries with `status` of `missing`, `pending`, `expired`, or `revoked` MUST include either `provider` or `authorization_url` so the buyer can route the remediation unambiguously."
     },

package/dist/lib/schemas-data/3.1/error-details/billing-not-permitted-for-agent.json

@@ -1,16 +1,16 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/error-details/billing-not-permitted-for-agent.json",
+  "$id": "/schemas/3.1.30/error-details/billing-not-permitted-for-agent.json",
   "title": "Billing Not Permitted For Agent Details",
   "description": "Recommended details shape for BILLING_NOT_PERMITTED_FOR_AGENT errors. Returned when the seller's declared `supported_billing` capability accepts the requested value but the calling buyer agent's commercial relationship with the seller does not (e.g., the agent is onboarded as passthrough-only — no payments relationship — so `agent` and `advertiser` reject). The shape is deliberately minimal: it returns the value that was rejected and at most one suggested retry value (typically `operator`). It MUST NOT carry the agent's full permitted-billing subset, the agent's other commercial state (rate cards, payment terms, credit limit, billing entity), or any per-account state — those are commercial-state oracles. Sellers MUST NOT add ad-hoc keys to this object: any field carrying per-agent commercial state is forbidden, even if `additionalProperties` would permit it. The recovery contract is: if `suggested_billing` is present, the agent MAY retry autonomously with that value; if absent, the rejection is terminal-pending-onboarding and the agent MUST surface to a human at the buyer to complete payments-relationship onboarding with the seller offline.",
   "type": "object",
   "properties": {
     "rejected_billing": {
-      "$ref": "/schemas/3.1.29/enums/billing-party.json",
+      "$ref": "/schemas/3.1.30/enums/billing-party.json",
       "description": "The `billing` value the seller rejected — echoed verbatim from the request for caller-side reconciliation."
     },
     "suggested_billing": {
-      "$ref": "/schemas/3.1.29/enums/billing-party.json",
+      "$ref": "/schemas/3.1.30/enums/billing-party.json",
       "description": "A single billing value the calling buyer agent MAY retry with autonomously. Typically `operator` for passthrough-only agents. Sellers MAY omit this field when no retryable value exists for this agent's commercial relationship — in that case the rejection is terminal-pending-onboarding and the buyer MUST complete offline payments-relationship onboarding before any value other than the original request will succeed. Sellers MUST NOT populate this field with the full subset of values the agent may use; the field surfaces at most one canonical retry."
     }
   },

package/dist/lib/schemas-data/3.1/error-details/billing-not-supported.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/error-details/billing-not-supported.json",
+  "$id": "/schemas/3.1.30/error-details/billing-not-supported.json",
   "title": "Billing Not Supported Details",
   "description": "Recommended details shape for BILLING_NOT_SUPPORTED errors. Returned when the seller declines the requested `billing` value either at the seller-wide capability level or at the per-account-relationship level. The shape lets callers dispatch on the gate that fired without parsing prose. The `scope` field MUST be omitted when the seller is responding on the unauthenticated/unestablished-identity path required by the uniform-response rule for `BILLING_NOT_PERMITTED_FOR_AGENT` — emitting `scope: \"account\"` to a caller whose agent identity is not established would itself act as a per-account-relationship oracle (same shape the uniform-response rule closes for the per-agent code).",
   "type": "object",
@@ -17,7 +17,7 @@
       "type": "array",
       "description": "Echoed copy of the seller's `supported_billing` capability for the caller's convenience — saves a `get_adcp_capabilities` round-trip when `scope` is `\"capability\"`. Sellers MAY omit this field; callers MUST treat absence as \"call `get_adcp_capabilities`\" rather than \"any value is permitted.\"",
       "items": {
-        "$ref": "/schemas/3.1.29/enums/billing-party.json"
+        "$ref": "/schemas/3.1.30/enums/billing-party.json"
       },
       "minItems": 1
     }

package/dist/lib/schemas-data/3.1/error-details/budget-too-low.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/error-details/budget-too-low.json",
+  "$id": "/schemas/3.1.30/error-details/budget-too-low.json",
   "title": "Budget Too Low Details",
   "description": "Recommended details shape for BUDGET_TOO_LOW errors. Provides the seller's minimum budget so agents can adjust.",
   "type": "object",

package/dist/lib/schemas-data/3.1/error-details/conflict.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/error-details/conflict.json",
+  "$id": "/schemas/3.1.30/error-details/conflict.json",
   "title": "Conflict Details",
   "description": "Recommended details shape for CONFLICT errors. Provides version information so agents can re-read the resource and retry.",
   "type": "object",

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

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

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

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

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

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

package/dist/lib/schemas-data/3.1/error-details/stale-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/error-details/stale-response.json",
+  "$id": "/schemas/3.1.30/error-details/stale-response.json",
   "title": "Stale Response Details",
   "description": "Recommended `error.details` shape for STALE_RESPONSE errors. Emitted alongside a populated success payload when the seller served cached data past its freshness target because an upstream or sub-agent fetch failed. Lets buyer agents dispatch on cache age and identify the stale upstream without parsing prose. One details entry per affected upstream — when multiple upstreams are stale, the seller emits one STALE_RESPONSE error per upstream rather than aggregating.",
   "type": "object",

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

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

package/dist/lib/schemas-data/3.1/error-details/version-unsupported.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/error-details/version-unsupported.json",
+  "$id": "/schemas/3.1.30/error-details/version-unsupported.json",
   "title": "Version Unsupported Details",
   "description": "Recommended details shape for VERSION_UNSUPPORTED errors. Returned when the buyer's declared `adcp_version` (release) or `adcp_major_version` (integer) is not supported by the seller. Provides the seller's supported versions so the buyer can re-pin and retry without a separate capabilities round-trip.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.29/core/version-envelope.json"
+      "$ref": "/schemas/3.1.30/core/version-envelope.json"
     }
   ],
   "properties": {

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

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

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

@@ -1,9 +1,9 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/extensions/index.json",
+  "$id": "/schemas/3.1.30/extensions/index.json",
   "title": "AdCP Extension Registry",
   "description": "Auto-generated registry of formal AdCP extensions. Extensions provide typed schemas for vendor-specific or domain-specific data within the ext field. Agents declare which extensions they support in their agent card.",
   "_generated": true,
-  "_generatedAt": "2026-10-16T17:35:36.372Z",
+  "_generatedAt": "2026-10-28T15:35:14.074Z",
   "extensions": {}
 }

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/formats/canonical/_base.json",
+  "$id": "/schemas/3.1.30/formats/canonical/_base.json",
   "title": "Canonical Format Base",
   "description": "Shared parameter fields that apply across canonical formats. Each canonical format extends this base with format-specific parameters (dimensions, durations, codecs, slot constraints).",
   "type": "object",
@@ -46,7 +46,7 @@
       "type": "array",
       "description": "Platform-specific extensions narrowing the canonical (pixel ID shapes, conversion event taxonomies, platform-specific CTAs/destinations). Each extension is a URI+digest reference resolved against the bundled `extensions` map in get_products responses or fetched directly.\n\n**Collision precedence (normative).** When two or more `platform_extensions[]` entries on the same declaration extend the same target (e.g., both extend `tracking`) with overlapping field names, **array order is authoritative — later entries override earlier ones on a per-field basis** (last-in-array-wins). SDKs MUST surface the overlap via the `errors[]` array on the `get_products` response with a structured code (`FORMAT_DECLARATION_DIVERGENT` is appropriate when the overlap appears across dual-emitted shapes; a producer-self-emitted overlap on a single declaration SHOULD use the same code with `error.details: { collision_kind: \"platform_extension_field\", target, overlapping_fields, winning_extension_uri }`). Producers SHOULD avoid the collision by emitting one extension per target or by partitioning fields across extensions; the deterministic precedence is for last-resort consistency across SDK implementations, not a sanctioned merging strategy.",
       "items": {
-        "$ref": "/schemas/3.1.29/core/platform-extension-ref.json"
+        "$ref": "/schemas/3.1.30/core/platform-extension-ref.json"
       }
     },
     "synthesis_nondeterministic": {
@@ -123,7 +123,7 @@
           "logo_slots": {
             "type": "array",
             "items": {
-              "$ref": "/schemas/3.1.29/enums/logo-slot.json"
+              "$ref": "/schemas/3.1.30/enums/logo-slot.json"
             },
             "uniqueItems": true,
             "description": "When `asset_group_id` is `logo`, renderer-facing brand.json logo slots acceptable for this format slot. Producers selecting from brand.json SHOULD prefer `logos[]` entries whose `slots[]` intersects this list, then apply `visual_guidelines.logo_usage_rules[]`."
@@ -131,7 +131,7 @@
           "required_logo_slots": {
             "type": "array",
             "items": {
-              "$ref": "/schemas/3.1.29/enums/logo-slot.json"
+              "$ref": "/schemas/3.1.30/enums/logo-slot.json"
             },
             "uniqueItems": true,
             "description": "Subset of `logo_slots` for which this format expects explicit logo coverage. A manifest or brand-derived logo pool SHOULD include at least one usable logo for each required slot; if coverage is missing, builders SHOULD surface a validation warning or approval mapping instead of guessing from prose."
@@ -277,7 +277,7 @@
     "required_connections": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.1.29/core/downstream-connection-requirement.json"
+        "$ref": "/schemas/3.1.30/core/downstream-connection-requirement.json"
       },
       "description": "Downstream platform connections or grants required to use this format declaration. These are in addition to the single AdCP caller credential. Use this when a platform product requires multiple downstream grants, such as an advertiser account connection plus a publisher identity or post authorization for published-post references."
     },

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

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/formats/canonical/agent_placement.json",
+  "$id": "/schemas/3.1.30/formats/canonical/agent_placement.json",
   "title": "Canonical Format: Agent Placement (AI-surface sponsored placement)",
   "description": "**3.2-track canonical.** The structural shape (algorithmic composition + brand-context input + optional offering/landing_page) is captured here so adopters can declare against it in 3.1 catalogs, but the **mention-level tracking contract is intentionally underspecified for 3.1**: no normative macro vocabulary, no postback shape, no cross-surface dedup model. Adopters claiming `agent_placement` in 3.1 ship private tracking integrations and SHOULD leave `experimental: true` on the product declaration that references this canonical; buyer agents MUST treat agent_placement attribution as adapter-defined until the 3.2 tracking-macro spec lands. The canonical promotes to a normatively-buyer-callable surface in 3.2 (or later) once the tracking contract is specified.\n\nSponsored placement integrated into an AI-surface's response to a user. Buyer supplies a `BrandRef` (resolving brand.json for context), an optional `offering_ref` to focus the mention on a specific offering, and an optional `landing_page_url` the surface MAY attach as a citation. The surface (LLM, voice assistant, sponsored-search ranker) composes a natural-language mention, sponsored card, or audio snippet within its response to a user query. **Composition is algorithmic** — the agent chooses phrasing and presentation. Output asset_type varies by surface: `text` for chat UIs and sponsored search snippets; `audio` (synthesized) for voice assistants; `card` for structured AI-surface result cards. Tracking model: mention-level impression + attribution events; per-mention id keys back to brand and offering — but see the 3.2-track note above; the wire shape of these events is not yet specified. Distinct from `si_chat` (which is the user-converses-with-brand's-agent pattern — brand owns the conversational surface) and from `sponsored_placement` (retail-media catalog-driven). Parallels `sponsored_placement` structurally: both are surface-composed placements; agent_placement is for AI/agentic surfaces, sponsored_placement is for retail media.",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.29/formats/canonical/_base.json"
+      "$ref": "/schemas/3.1.30/formats/canonical/_base.json"
     }
   ],
   "properties": {

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

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/formats/canonical/audio_daast.json",
+  "$id": "/schemas/3.1.30/formats/canonical/audio_daast.json",
   "title": "Canonical Format: DAAST Audio",
   "description": "DAAST-tag-delivered audio creative (audio analog of VAST). Slot: `daast_tag` (daast asset, URL or inline XML). Tracking model: DAAST events inherent to the spec — `impression`, `firstQuartile`, `midpoint`, `thirdQuartile`, `complete`, `start`, `pause`, `resume`, `mute`, `unmute`, `clickTracking`, `error`. Distinct from `audio_hosted` (direct file with external tracking).",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.29/formats/canonical/_base.json"
+      "$ref": "/schemas/3.1.30/formats/canonical/_base.json"
     }
   ],
   "properties": {