@adcp/sdk 13.0.1 → 13.0.3

package/dist/lib/schemas-data/3.1/protocol/list-tasks-request.json

@@ -1,17 +1,17 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/protocol/list-tasks-request.json",
+  "$id": "/schemas/3.1.20/protocol/list-tasks-request.json",
   "title": "List Tasks Request",
   "description": "Request parameters for the list_tasks AdCP tool. This is a 3.x protocol-namespace alias for the legacy AdCP tasks/list reconciliation surface, not a transport-native MCP/A2A tasks/* method. It lists and filters AdCP application-layer async tasks for state reconciliation while preserving the legacy 3.x payload shape.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.15/core/version-envelope.json"
+      "$ref": "/schemas/3.1.20/core/version-envelope.json"
     }
   ],
   "properties": {
     "account": {
-      "$ref": "/schemas/3.1.15/core/account-ref.json",
+      "$ref": "/schemas/3.1.20/core/account-ref.json",
       "description": "Account scope for task reconciliation. Sellers MUST only return tasks created for the caller's authenticated account + principal pair. When omitted, the seller MAY use the credential-bound singleton account, but multi-account credentials SHOULD require an explicit account."
     },
     "filters": {
@@ -19,38 +19,38 @@
       "description": "Filter criteria for querying tasks",
       "properties": {
         "protocol": {
-          "$ref": "/schemas/3.1.15/enums/adcp-protocol.json",
+          "$ref": "/schemas/3.1.20/enums/adcp-protocol.json",
           "description": "Filter by single AdCP protocol"
         },
         "protocols": {
           "type": "array",
           "description": "Filter by multiple AdCP protocols",
           "items": {
-            "$ref": "/schemas/3.1.15/enums/adcp-protocol.json"
+            "$ref": "/schemas/3.1.20/enums/adcp-protocol.json"
           },
           "minItems": 1
         },
         "status": {
-          "$ref": "/schemas/3.1.15/enums/task-status.json",
+          "$ref": "/schemas/3.1.20/enums/task-status.json",
           "description": "Filter by single task status"
         },
         "statuses": {
           "type": "array",
           "description": "Filter by multiple task statuses",
           "items": {
-            "$ref": "/schemas/3.1.15/enums/task-status.json"
+            "$ref": "/schemas/3.1.20/enums/task-status.json"
           },
           "minItems": 1
         },
         "task_type": {
-          "$ref": "/schemas/3.1.15/enums/task-type.json",
+          "$ref": "/schemas/3.1.20/enums/task-type.json",
           "description": "Filter by single task type"
         },
         "task_types": {
           "type": "array",
           "description": "Filter by multiple task types",
           "items": {
-            "$ref": "/schemas/3.1.15/enums/task-type.json"
+            "$ref": "/schemas/3.1.20/enums/task-type.json"
           },
           "minItems": 1
         },
@@ -111,7 +111,7 @@
           "description": "Field to sort by"
         },
         "direction": {
-          "$ref": "/schemas/3.1.15/enums/sort-direction.json",
+          "$ref": "/schemas/3.1.20/enums/sort-direction.json",
           "default": "desc",
           "description": "Sort direction"
         }
@@ -119,7 +119,7 @@
       "additionalProperties": true
     },
     "pagination": {
-      "$ref": "/schemas/3.1.15/core/pagination-request.json"
+      "$ref": "/schemas/3.1.20/core/pagination-request.json"
     },
     "include_history": {
       "type": "boolean",
@@ -127,10 +127,10 @@
       "description": "Include full conversation history for each task (may significantly increase response size)"
     },
     "context": {
-      "$ref": "/schemas/3.1.15/core/context.json"
+      "$ref": "/schemas/3.1.20/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "additionalProperties": true,

package/dist/lib/schemas-data/3.1/protocol/list-tasks-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/protocol/list-tasks-response.json",
+  "$id": "/schemas/3.1.20/protocol/list-tasks-response.json",
   "title": "List Tasks Response",
   "description": "Response from the list_tasks AdCP tool, a 3.x protocol-namespace alias for legacy AdCP tasks/list. Contains filtered AdCP application-layer task results and reconciliation data while preserving the legacy 3.x domain field shape; distinct from transport-native MCP/A2A task responses.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.15/core/version-envelope.json"
+      "$ref": "/schemas/3.1.20/core/version-envelope.json"
     },
     {
-      "$ref": "/schemas/3.1.15/core/protocol-envelope.json"
+      "$ref": "/schemas/3.1.20/core/protocol-envelope.json"
     }
   ],
   "properties": {
@@ -101,7 +101,7 @@
             "x-entity": "task"
           },
           "task_type": {
-            "$ref": "/schemas/3.1.15/enums/task-type.json",
+            "$ref": "/schemas/3.1.20/enums/task-type.json",
             "description": "Type of AdCP operation"
           },
           "domain": {
@@ -114,7 +114,7 @@
             ]
           },
           "status": {
-            "$ref": "/schemas/3.1.15/enums/task-status.json",
+            "$ref": "/schemas/3.1.20/enums/task-status.json",
             "description": "Current task status"
           },
           "created_at": {
@@ -149,13 +149,13 @@
       }
     },
     "pagination": {
-      "$ref": "/schemas/3.1.15/core/pagination-response.json"
+      "$ref": "/schemas/3.1.20/core/pagination-response.json"
     },
     "context": {
-      "$ref": "/schemas/3.1.15/core/context.json"
+      "$ref": "/schemas/3.1.20/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/registries/v1-canonical-mapping.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/registries/v1-canonical-mapping.json",
+  "$id": "/schemas/3.1.20/registries/v1-canonical-mapping.json",
   "title": "v1 → v2 Canonical Format Mapping Registry",
   "description": "Authoritative AAO-published mapping from v1 named formats to v2 canonical declarations. Used by SDKs to project the v1 wire shape into v2 canonical declarations during the migration window.\n\n**Direction of truth (normative).** This registry is authoritative for **v1 → v2 projection only**. v2 → v1 projection MUST rely on `v1_format_ref` on the v2 `ProductFormatDeclaration` — sellers assert the v1 pairing explicitly. SDKs MUST NOT synthesize a v1 `format_id` from the registry by inverting structural matches: the registry's `id` slugs lack the `agent_url` half of a `FormatId`, and registry entries with `format_id_glob: '*'` or pure-structural matches have no single literal to invert to. SDKs that synthesize unilaterally produce inter-SDK divergence on structurally-equal values (different SDKs pick different `agent_url` and `id` patterns for the same v2 declaration). When a v2 declaration carries no `v1_format_ref` and a v1-only buyer queries the product, the SDK reports the canonical as v1-unreachable via `FORMAT_DECLARATION_V1_AMBIGUOUS` and lets the buyer surface it to the seller; the seller's path is to add `v1_format_ref` to disambiguate.\n\nBest-effort inversion is available only from this registry's non-wildcarded literal format_id_glob entries. Structural matches remain family-level and are not invertible to a specific v1 format_id. SDKs MAY do best-effort inversion for non-wildcarded literals only, AND only when the seller hasn't authored a contradicting `v1_format_ref` — even then, the projection is non-normative and downstream consumers MUST NOT depend on it.\n\n**Resolution order** (per RFC #3305 amendment #3767, normative):\n1. **Authoritative v2→v1 link**: if any v2 `ProductFormatDeclaration` on the same product carries `v1_format_ref` pointing at this v1 format_id, use that v2 declaration. Highest priority — seller asserts the link directly. SDKs SHOULD run the *narrows* check (canonical-formats.mdx 'Narrows — formal definition') between the v2 declaration's `params` and the referenced v1 format's `requirements`; on conflict, surface `FORMAT_DECLARATION_DIVERGENT` on the `get_products` response `errors[]`. Without the narrowing check, `v1_format_ref` is a hint rather than a contract.\n2. **Seller-asserted on the v1 file**: if the v1 format declaration carries an explicit `canonical` field, use it. (Note: `canonical_parameters` on the v1 file is deprecated for 3.1; SDKs reading 3.1 catalogs MUST still honor it when present, but `v1_format_ref` is the path forward.)\n3. **Registry glob**: look up `format_id` in this registry's `format_id_glob` entries.\n4. **Structural match**: attempt structural match against this registry's `structural` entries. A successful structural match yields a *family-level* identification only (e.g., 'this is a `video_vast`') — it does NOT yield a specific v1 `format_id`. SDKs use structural match for v1 → v2 projection (the inbound direction) but MUST NOT invert it to a v1 `format_id` on the outbound path.\n5. **Ambiguous family**: if step 4 succeeded but the matched entries are family-only (pure structural, no invertible literal), the canonical is **v1-unreachable for THIS specific product** unless the seller authors `v1_format_ref`. SDKs MUST surface `FORMAT_DECLARATION_V1_AMBIGUOUS` via `errors[]` augmentation rather than synthesize a plausible-but-arbitrary v1 `format_id`. Distinct from canonical-level v1-unreachability (a canonical with `v1_translatable: false` — `agent_placement`, `sponsored_placement`, `responsive_creative`, `image_carousel` — never has any v1 form regardless of registry coverage).\n6. **Fail closed**: SDK MUST NOT emit `format_options` for products carrying this format. SDKs MUST augment the response's `errors[]` array with an entry carrying `source: \"sdk\"`, `sdk_id: \"<package>@<version>\"`, `code: \"FORMAT_PROJECTION_FAILED\"`, `field: \"products[N].format_ids[K]\"`, and `error.details: { format_id, product_id, resolution_failure: \"no_explicit_canonical\" | \"no_registry_match\" | \"no_structural_match\" }`. Single mandated surface (`errors[]` augmentation) — lint-output channels are NOT acceptable; the multi-hop agent network needs warnings to propagate across SDK boundaries via the wire response. Logger-only warnings die in DEBUG. The advisory is non-fatal: the response stays 200/success, the product is still valid on the v1 path, only the v2 `format_options` projection is absent. Consumer-side counterpart to the producer SHOULD (sellers should add a v2 declaration with `v1_format_ref`, an explicit `canonical` field, or file a registry PR).\n\n**Match modes:**\n- `format_id_glob` — exact / glob match against the v1 `format_id.id`. Published non-wildcarded literals cover independently observed legacy conventions whose names carry semantic narrowing (duration, dimensions, or VAST delivery) that slot shape alone cannot recover. Each literal mapping preserves those constraints in canonical parameters; AAO-catalog-published formats with explicit canonical annotations still project via resolution-order step 2. Glob syntax: `*` matches any segment.\n- `structural` — match against the format's slot shape, asset types, and version constraints. The PRIMARY fallback for v1 wire traffic — catches custom v1 formats (a publisher's `acme_homepage_300x250` is structurally an IAB MREC) without enumerating every possible v1 name. v1 sellers in the wild naming things their own way are handled here, not by literal globs.\n\n**Alias collision precedence (normative).** When a v1 format's `assets[i]` carries multiple `asset_group_id` aliases that resolve to the same canonical asset_group (e.g., two slots both aliasing to `landing_page_url`), the SDK MUST resolve deterministically: the v1 format's `assets[*]` array order is authoritative — the first slot in declaration order wins, subsequent collisions are dropped from the projected v2 manifest and surfaced via `FORMAT_PROJECTION_FAILED` with `error.details: { collision_kind: \"asset_group_id_alias\", asset_group_id, winning_slot_id, dropped_slot_ids }`. SDKs MUST NOT silently pick one and discard the other without surfacing — silent picking creates inter-SDK divergence. Producers SHOULD avoid the collision by deduplicating aliased slots or using distinct `asset_group_id` values when both slots are semantically meaningful.\n\n**Pixel-density version boundary (normative).** In AdCP 3.1.x, `pixel_ratios` and `required_pixel_ratios` inside this registry are opaque forward-projection metadata. A 3.1.x SDK MUST preserve these members unchanged when it copies or re-emits registry-derived metadata, but MUST NOT interpret them as 3.1 constraints, validate creatives against them, or emit pixel-density validation errors. Seller-authored canonical declarations selected by resolution-order step 1 or 2 are authoritative; SDKs MUST NOT merge registry slot or pixel-ratio defaults into them. For this registry, `3.2-aware` describes the active operation, not merely SDK capability: an SDK is 3.2-aware only while projecting or validating against the AdCP 3.2 canonical model. A binary that supports 3.2 but is processing a negotiated 3.1 exchange MUST follow the 3.1 preservation-only behavior. The complete typed contract begins in AdCP 3.2. Under that contract, ratios are unique positive JSON numbers (fractions are valid); top-level `image.params.pixel_ratios` and slot-level `pixel_ratios` are both authoritative constraints and their intersection is the effective accepted set; `required_pixel_ratios` MUST be a subset of that effective set. A 3.2-aware SDK reports `required_pixel_ratio_missing`, `pixel_ratio_duplicate`, `pixel_ratio_not_accepted`, `pixel_ratio_dimension_mismatch`, `pixel_ratio_ambiguous`, `pixel_ratio_intersection_empty`, or `required_pixel_ratio_not_accepted` as specified by the canonical image reference and its test vectors.\n\n**Image rendition-set exception (AdCP 3.2+, normative).** This specific rule takes precedence over the generic alias-collision rule above only when an SDK projects the matched mapping into, and validates it against, the AdCP 3.2 canonical model. When the mapping declares an image slot with `required_pixel_ratios`, v1 image assets sharing that slot's `asset_group_id` are intentional renditions rather than collisions. The SDK MUST validate each asset against a distinct accepted density and collect them, in v1 declaration order, into the canonical slot array. Missing or duplicate required densities fail under the rendition-set rules; only remaining same-group assets enter ordinary collision handling.\n\n**Governance**: same vocabulary-governance rules as `asset-group-vocabulary.json` and `format-shape-vocabulary.json` — additions land via PR with rationale + ≥1 reference adopter; AAO maintainer review; versioned + content-digested. Entries are additive; once published they are not removed (they may be marked `deprecated: true` if superseded).\n\n**Scope**: 7 structural fallback entries cover VAST 4.x / legacy VAST, DAAST 1.x, HTML5 zip bundles, hosted video, hosted audio, and url-shaped display tags. Literal entries cover independently observed legacy duration-, dimension-, and VAST-token naming conventions. Durationless placement ids video_pre_roll and video_mid_roll are deliberately omitted: projecting either to video_hosted without duration_ms_exact would resolve to an untraffickable format and defer failure until ad-server line-item creation. Failing closed during discovery is safer. Platform-specific formats (Meta Reels, TikTok Spark Ads, etc.) project via structural fallback or via the platform's own adagents.json `formats[]` block (#4620). The full v1-format audit dataset (~76% of formats from the 12-platform / 86-format audit in #3305) seeds the long-term roadmap and informs future literal-entry decisions.\n\nDigest the file content (sha256) when emitting in capabilities responses or referencing from SDK output. Buyers cache by `version` + `digest`.",
   "version": "1.3.1",
@@ -99,7 +99,7 @@
             ],
             "properties": {
               "canonical": {
-                "$ref": "/schemas/3.1.15/core/canonical-format-kind.json",
+                "$ref": "/schemas/3.1.20/core/canonical-format-kind.json",
                 "description": "v2 canonical format the v1 pattern projects to."
               },
               "parameters": {

package/dist/lib/schemas-data/3.1/signals/activate-signal-request.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/signals/activate-signal-request.json",
+  "$id": "/schemas/3.1.20/signals/activate-signal-request.json",
   "title": "Activate Signal Request",
   "description": "Request parameters for activating or deactivating a signal on deployment targets",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.15/core/version-envelope.json"
+      "$ref": "/schemas/3.1.20/core/version-envelope.json"
     }
   ],
   "x-mutates-state": true,
@@ -29,7 +29,7 @@
       "type": "array",
       "description": "Target destination(s) for activation. If the authenticated caller matches one of these destinations, activation keys will be included in the response.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/destination.json"
+        "$ref": "/schemas/3.1.20/core/destination.json"
       },
       "minItems": 1
     },
@@ -46,7 +46,7 @@
       "pattern": "^[\\x20-\\x7E]+$"
     },
     "account": {
-      "$ref": "/schemas/3.1.15/core/account-ref.json",
+      "$ref": "/schemas/3.1.20/core/account-ref.json",
       "description": "Account for this activation. Associates with a commercial relationship established via sync_accounts."
     },
     "idempotency_key": {
@@ -57,10 +57,10 @@
       "pattern": "^[A-Za-z0-9_.:-]{16,255}$"
     },
     "context": {
-      "$ref": "/schemas/3.1.15/core/context.json"
+      "$ref": "/schemas/3.1.20/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/signals/activate-signal-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/signals/activate-signal-response.json",
+  "$id": "/schemas/3.1.20/signals/activate-signal-response.json",
   "title": "Activate Signal Response",
   "description": "Response payload for activate_signal task. Returns either complete success data OR error information, never both. This enforces atomic operation semantics - the signal is either fully activated or not activated at all.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.15/core/version-envelope.json"
+      "$ref": "/schemas/3.1.20/core/version-envelope.json"
     },
     {
-      "$ref": "/schemas/3.1.15/core/protocol-envelope.json"
+      "$ref": "/schemas/3.1.20/core/protocol-envelope.json"
     }
   ],
   "oneOf": [
@@ -22,7 +22,7 @@
           "type": "array",
           "description": "Array of deployment results for each deployment target",
           "items": {
-            "$ref": "/schemas/3.1.15/core/deployment.json"
+            "$ref": "/schemas/3.1.20/core/deployment.json"
           }
         },
         "sandbox": {
@@ -30,10 +30,10 @@
           "description": "When true, this response contains simulated data from sandbox mode."
         },
         "context": {
-          "$ref": "/schemas/3.1.15/core/context.json"
+          "$ref": "/schemas/3.1.20/core/context.json"
         },
         "ext": {
-          "$ref": "/schemas/3.1.15/core/ext.json"
+          "$ref": "/schemas/3.1.20/core/ext.json"
         }
       },
       "required": [
@@ -55,15 +55,15 @@
           "type": "array",
           "description": "Array of errors explaining why activation failed (e.g., platform connectivity issues, signal definition problems, authentication failures)",
           "items": {
-            "$ref": "/schemas/3.1.15/core/error.json"
+            "$ref": "/schemas/3.1.20/core/error.json"
           },
           "minItems": 1
         },
         "context": {
-          "$ref": "/schemas/3.1.15/core/context.json"
+          "$ref": "/schemas/3.1.20/core/context.json"
         },
         "ext": {
-          "$ref": "/schemas/3.1.15/core/ext.json"
+          "$ref": "/schemas/3.1.20/core/ext.json"
         }
       },
       "required": [

package/dist/lib/schemas-data/3.1/signals/get-signals-async-response-submitted.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/signals/get-signals-async-response-submitted.json",
+  "$id": "/schemas/3.1.20/signals/get-signals-async-response-submitted.json",
   "title": "Get Signals - Submitted",
   "description": "Async task envelope returned when get_signals cannot be confirmed before the response — for example, when semantic discovery depends on slow provider queries or review. This envelope is valid only for `discovery_mode: \"brief\"`; `discovery_mode: \"wholesale\"` is a synchronous wholesale signals feed read and MUST NOT use the Submitted arm. The caller can always poll `get_task_status` (legacy `tasks/get`) with `task_id`. If the originating request carried `push_notification_config`, the agent also delivers at least the terminal completion/failure notification to that webhook URL; intermediate progress notifications are MAY. The signals array lands on the completion artifact, not this envelope.",
   "type": "object",
@@ -29,14 +29,14 @@
       "type": "array",
       "description": "Optional advisory errors accompanying the submitted envelope. Use only for non-blocking warnings (e.g., throttled_severity advisories or partial provider unavailability). Terminal failures belong in the error branch, not here.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/error.json"
+        "$ref": "/schemas/3.1.20/core/error.json"
       }
     },
     "context": {
-      "$ref": "/schemas/3.1.15/core/context.json"
+      "$ref": "/schemas/3.1.20/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/signals/get-signals-async-response-working.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/signals/get-signals-async-response-working.json",
+  "$id": "/schemas/3.1.20/signals/get-signals-async-response-working.json",
   "title": "Get Signals - Working",
   "description": "Progress payload for an active get_signals task after a submitted semantic discovery request has started processing. Valid only for `discovery_mode: \"brief\"`; wholesale signals feed reads report partial completion via `incomplete[]`, not async task progress.",
   "type": "object",
@@ -24,10 +24,10 @@
       "description": "Current step number (1-indexed)."
     },
     "context": {
-      "$ref": "/schemas/3.1.15/core/context.json"
+      "$ref": "/schemas/3.1.20/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.1/signals/get-signals-request.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/signals/get-signals-request.json",
+  "$id": "/schemas/3.1.20/signals/get-signals-request.json",
   "title": "Get Signals Request",
   "description": "Request parameters for discovering and refining signals. Use signal_spec for natural language discovery, signal_refs for exact lookups, both together to refine previous results, or discovery_mode: 'wholesale' to enumerate the agent's full priced signals feed (symmetric with get_products buying_mode: 'wholesale'). The legacy signal_ids field is deprecated.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.15/core/version-envelope.json"
+      "$ref": "/schemas/3.1.20/core/version-envelope.json"
     },
     {
       "description": "Conditional wholesale feed version requests are only valid for wholesale signals feed reads.",
@@ -47,7 +47,7 @@
       "description": "Declares caller intent for this request. 'brief' (default): semantic discovery — signal_spec, signal_refs, or legacy signal_ids is required and the agent performs inference/RAG. 'wholesale': raw wholesale signals feed enumeration — signal_spec, signal_refs, and signal_ids MUST NOT be provided and the agent returns its full priced signals feed, paginated, scoped by filters/account/destinations/countries when present. Sellers receiving requests from pre-v3.1 clients without discovery_mode MUST default to 'brief'. Timing semantics: 'wholesale' is a wholesale signals feed read — agents SHOULD respond synchronously and MUST NOT route a 'wholesale' request through the async/Submitted arm; partial completion is signalled via the response's incomplete[] field, not via a task-handoff envelope. Agents that do not implement wholesale enumeration MAY return INVALID_REQUEST for wholesale calls; callers SHOULD probe via get_adcp_capabilities (signals.discovery_modes) first."
     },
     "account": {
-      "$ref": "/schemas/3.1.15/core/account-ref.json",
+      "$ref": "/schemas/3.1.20/core/account-ref.json",
       "description": "Account for this request. When provided, the signals agent returns per-account pricing options if configured. In 'wholesale' mode, this is the rate-card scope: when omitted in wholesale mode, agents return their default rate-card pricing or omit pricing_options entirely."
     },
     "signal_spec": {
@@ -58,7 +58,7 @@
       "type": "array",
       "description": "Specific signals to look up by reference. Returns exact matches for the requested SignalRef values. When combined with signal_spec, these signals anchor the starting set and signal_spec guides adjustments. MUST NOT be provided when discovery_mode is 'wholesale'.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/signal-ref.json"
+        "$ref": "/schemas/3.1.20/core/signal-ref.json"
       },
       "minItems": 1
     },
@@ -67,7 +67,7 @@
       "description": "DEPRECATED. Use signal_refs instead. Legacy exact lookup field using SignalId objects. MUST NOT be provided when discovery_mode is 'wholesale'.",
       "deprecated": true,
       "items": {
-        "$ref": "/schemas/3.1.15/core/signal-id.json"
+        "$ref": "/schemas/3.1.20/core/signal-id.json"
       },
       "minItems": 1
     },
@@ -75,7 +75,7 @@
       "type": "array",
       "description": "Filter signals to those activatable on specific agents/platforms. When omitted, returns all signals available on the current agent. If the authenticated caller matches one of these destinations, activation keys will be included in the response.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/destination.json"
+        "$ref": "/schemas/3.1.20/core/destination.json"
       },
       "minItems": 1
     },
@@ -89,7 +89,7 @@
       "minItems": 1
     },
     "filters": {
-      "$ref": "/schemas/3.1.15/core/signal-filters.json"
+      "$ref": "/schemas/3.1.20/core/signal-filters.json"
     },
     "fields": {
       "type": "array",
@@ -140,11 +140,11 @@
       "minimum": 1
     },
     "pagination": {
-      "$ref": "/schemas/3.1.15/core/pagination-request.json",
+      "$ref": "/schemas/3.1.20/core/pagination-request.json",
       "description": "Pagination parameters. Use pagination.max_results (max: 100, default: 50) and pagination.cursor for cursor-based page walks. When the deprecated top-level max_results field is also present, pagination.max_results takes precedence."
     },
     "push_notification_config": {
-      "$ref": "/schemas/3.1.15/core/push-notification-config.json",
+      "$ref": "/schemas/3.1.20/core/push-notification-config.json",
       "description": "Optional webhook configuration for async terminal completion/failure notifications on semantic signal discovery. Meaningful only for `discovery_mode: \"brief\"` requests that enter the async lifecycle. Submitted envelopes with `task_id` remain pollable through `get_task_status` (legacy `tasks/get`) whether or not this field is present. If a brief request includes this field and the agent returns a Submitted envelope, the agent MUST deliver at least the terminal completion/failure notification to the configured URL; intermediate progress notifications are MAY. If the agent cannot honor the webhook channel, it MUST reject the request with a structured error instead of silently accepting. This field does not change wholesale timing semantics: agents MUST NOT route `discovery_mode: \"wholesale\"` requests through the async/Submitted arm or emit async delivery solely because `push_notification_config` is present; partial wholesale completion is reported via `incomplete[]`."
     },
     "if_wholesale_feed_version": {
@@ -156,10 +156,10 @@
       "description": "Opaque pricing_version token from a prior get_signals response. MUST only be sent together with if_wholesale_feed_version — pricing version has no structural baseline to compare against on its own. Evaluation order: (1) if_wholesale_feed_version mismatch → agent returns the full payload; (2) if_wholesale_feed_version matches but if_pricing_version mismatches → agent returns the full payload so the caller sees updated pricing_options; (3) both match → agent MAY return unchanged: true. Agents that don't track pricing separately ignore this and fall back to if_wholesale_feed_version semantics."
     },
     "context": {
-      "$ref": "/schemas/3.1.15/core/context.json"
+      "$ref": "/schemas/3.1.20/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "if": {

package/dist/lib/schemas-data/3.1/signals/get-signals-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/signals/get-signals-response.json",
+  "$id": "/schemas/3.1.20/signals/get-signals-response.json",
   "title": "Get Signals Response",
   "description": "Response payload for get_signals task",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.15/core/version-envelope.json"
+      "$ref": "/schemas/3.1.20/core/version-envelope.json"
     },
     {
-      "$ref": "/schemas/3.1.15/core/protocol-envelope.json"
+      "$ref": "/schemas/3.1.20/core/protocol-envelope.json"
     }
   ],
   "properties": {
@@ -20,20 +20,20 @@
         "type": "object",
         "allOf": [
           {
-            "$ref": "/schemas/3.1.15/core/signal-listing.json"
+            "$ref": "/schemas/3.1.20/core/signal-listing.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/signal-definition-enrichment.json"
+            "$ref": "/schemas/3.1.20/core/signal-definition-enrichment.json"
           }
         ],
         "properties": {
           "signal_id": {
-            "$ref": "/schemas/3.1.15/core/signal-id.json",
+            "$ref": "/schemas/3.1.20/core/signal-id.json",
             "description": "DEPRECATED. Use signal_ref instead. Legacy SignalId retained for compatibility with older Signals Protocol clients.",
             "deprecated": true
           },
           "signal_ref": {
-            "$ref": "/schemas/3.1.15/core/signal-ref.json",
+            "$ref": "/schemas/3.1.20/core/signal-ref.json",
             "description": "Canonical signal reference for discovery, activation, and media-buy targeting. Provider-published signals use scope 'data_provider'. Source-native custom signals that are not published in adagents.json signals[] use scope 'signal_source'. Product-local refs are only meaningful when the response is explicitly scoped to a product context."
           },
           "signal_agent_segment_id": {
@@ -50,7 +50,7 @@
             "description": "Detailed signal description"
           },
           "value_type": {
-            "$ref": "/schemas/3.1.15/enums/signal-value-type.json",
+            "$ref": "/schemas/3.1.20/enums/signal-value-type.json",
             "description": "The data type of this signal's values (binary, categorical, numeric)"
           },
           "categories": {
@@ -80,7 +80,7 @@
             "additionalProperties": false
           },
           "signal_type": {
-            "$ref": "/schemas/3.1.15/enums/signal-catalog-type.json",
+            "$ref": "/schemas/3.1.20/enums/signal-catalog-type.json",
             "description": "Commercial/provenance type of signal (marketplace, custom, owned)"
           },
           "data_provider": {
@@ -95,21 +95,21 @@
             "deprecated": true
           },
           "coverage_forecast": {
-            "$ref": "/schemas/3.1.15/core/signal-coverage-forecast.json",
+            "$ref": "/schemas/3.1.20/core/signal-coverage-forecast.json",
             "description": "Optional forecast-shaped signal availability guidance. When present, this is authoritative for signal-level discovery coverage. Use this to disclose the denominator, bucket semantics, not-present bucket, aggregate present bucket, and per-value coverage distribution for the signal."
           },
           "deployments": {
             "type": "array",
             "description": "Array of deployment targets",
             "items": {
-              "$ref": "/schemas/3.1.15/core/deployment.json"
+              "$ref": "/schemas/3.1.20/core/deployment.json"
             }
           },
           "pricing_options": {
             "type": "array",
             "description": "Pricing options available for this signal when it has an incremental price. The buyer selects one and passes its pricing_option_id in report_usage or package-level signal_targeting_groups for billing verification. Omit when pricing is unavailable to the caller, bundled into the destination product, or has no incremental cost.",
             "items": {
-              "$ref": "/schemas/3.1.15/core/vendor-pricing-option.json"
+              "$ref": "/schemas/3.1.20/core/vendor-pricing-option.json"
             },
             "minItems": 1
           }
@@ -140,7 +140,7 @@
       "type": "array",
       "description": "Task-specific errors and warnings (e.g., signal discovery or pricing issues)",
       "items": {
-        "$ref": "/schemas/3.1.15/core/error.json"
+        "$ref": "/schemas/3.1.20/core/error.json"
       }
     },
     "incomplete": {
@@ -166,7 +166,7 @@
           "estimated_wait": {
             "allOf": [
               {
-                "$ref": "/schemas/3.1.15/core/duration.json"
+                "$ref": "/schemas/3.1.20/core/duration.json"
               }
             ],
             "description": "How much additional time would resolve this scope. Allows the caller to decide whether to retry with a larger time_budget."
@@ -211,17 +211,17 @@
       "description": "Present and `true` ONLY on wholesale-mode responses when the request carried if_wholesale_feed_version (and/or if_pricing_version) matching the agent's current version for the caller's cache_scope, in which case signals[] MUST be omitted; wholesale_feed_version (echoed), cache_scope (echoed), and pricing_version (echoed when used) MUST still be present. Callers receiving unchanged: true MUST NOT mutate their local wholesale signals mirror. **One shape per state:** agents MUST NOT emit `unchanged: false` — the absence of the field IS the signal that the response carries signals."
     },
     "pagination": {
-      "$ref": "/schemas/3.1.15/core/pagination-response.json"
+      "$ref": "/schemas/3.1.20/core/pagination-response.json"
     },
     "sandbox": {
       "type": "boolean",
       "description": "When true, this response contains simulated data from sandbox mode."
     },
     "context": {
-      "$ref": "/schemas/3.1.15/core/context.json"
+      "$ref": "/schemas/3.1.20/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "if": {

package/dist/lib/schemas-data/3.1/sponsored-intelligence/si-capabilities.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/sponsored-intelligence/si-capabilities.json",
+  "$id": "/schemas/3.1.20/sponsored-intelligence/si-capabilities.json",
   "title": "SI Capabilities",
   "description": "Capabilities that a brand agent declares or a host supports",
   "x-status": "experimental",

package/dist/lib/schemas-data/3.1/sponsored-intelligence/si-context-use.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/sponsored-intelligence/si-context-use.json",
+  "$id": "/schemas/3.1.20/sponsored-intelligence/si-context-use.json",
   "title": "SI Context Use",
   "description": "Declared use mode for sponsored context crossing into a Sponsored Intelligence host boundary. This is a boundary declaration, not a claim that AdCP can inspect hidden model reasoning after the host receives the context.",
   "x-status": "experimental",

package/dist/lib/schemas-data/3.1/sponsored-intelligence/si-get-offering-request.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/sponsored-intelligence/si-get-offering-request.json",
+  "$id": "/schemas/3.1.20/sponsored-intelligence/si-get-offering-request.json",
   "title": "SI Get Offering Request",
   "description": "Get offering details and availability before session handoff. Returns offering information, availability status, and optionally matching products based on context.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.15/core/version-envelope.json"
+      "$ref": "/schemas/3.1.20/core/version-envelope.json"
     }
   ],
   "x-status": "experimental",
@@ -21,7 +21,7 @@
       "description": "Optional natural language description of user intent for personalized results (e.g., 'mens size 14 near Cincinnati'). Must be anonymous - no PII."
     },
     "context": {
-      "$ref": "/schemas/3.1.15/core/context.json"
+      "$ref": "/schemas/3.1.20/core/context.json"
     },
     "include_products": {
       "type": "boolean",
@@ -36,7 +36,7 @@
       "description": "Maximum number of matching products to return"
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "required": [