@adcp/sdk 13.0.1 → 13.0.3

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

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/catalog-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/catalog-requirements.json",
   "title": "Catalog Requirements",
   "description": "Format-level declaration of what catalog feeds a creative needs. Formats that render product listings, store locators, or promotional content declare which catalog types must be synced and what fields each catalog must provide. Buyers use this to ensure the right catalogs are synced before submitting creatives.",
   "type": "object",
   "properties": {
     "catalog_type": {
-      "$ref": "/schemas/3.1.15/enums/catalog-type.json",
+      "$ref": "/schemas/3.1.20/enums/catalog-type.json",
       "description": "The catalog type this requirement applies to"
     },
     "required": {
@@ -37,7 +37,7 @@
       "type": "array",
       "description": "Accepted feed formats for this catalog type. When specified, the synced catalog must use one of these formats. When omitted, any format is accepted.",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/feed-format.json"
+        "$ref": "/schemas/3.1.20/enums/feed-format.json"
       },
       "minItems": 1,
       "uniqueItems": true
@@ -46,7 +46,7 @@
       "type": "array",
       "description": "Per-item creative asset requirements. Declares what asset groups (headlines, images, videos) each catalog item must provide in its assets array, along with count bounds and per-asset technical constraints. Applicable to 'offering' and all vertical catalog types (hotel, flight, job, etc.) whose items carry typed assets.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/requirements/offering-asset-constraint.json"
+        "$ref": "/schemas/3.1.20/core/requirements/offering-asset-constraint.json"
       },
       "minItems": 1,
       "uniqueItems": true
@@ -55,7 +55,7 @@
       "type": "array",
       "description": "Explicit mappings from format template slots to catalog item fields or typed asset pools. Optional — creative agents can infer mappings without them, but bindings make the relationship self-describing and enable validation. Covers scalar fields (asset_id → catalog_field), asset pools (asset_id → asset_group_id on the catalog item), and repeatable groups that iterate over catalog items.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/requirements/catalog-field-binding.json"
+        "$ref": "/schemas/3.1.20/core/requirements/catalog-field-binding.json"
       },
       "minItems": 1,
       "uniqueItems": true

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/css-asset-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/css-asset-requirements.json",
   "title": "CSS Asset Requirements",
   "description": "Requirements for CSS creative assets.",
   "type": "object",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/daast-asset-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/daast-asset-requirements.json",
   "title": "DAAST Asset Requirements",
   "description": "Requirements for DAAST (Digital Audio Ad Serving Template) creative assets.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/requirements/html-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/html-asset-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/html-asset-requirements.json",
   "title": "HTML Asset Requirements",
   "description": "Requirements for HTML creative assets. These define the execution environment constraints that the HTML must be compatible with.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/requirements/image-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/image-asset-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/image-asset-requirements.json",
   "title": "Image Asset Requirements",
   "description": "Requirements for image creative assets. These define the technical constraints for image files.",
   "type": "object",
@@ -26,7 +26,7 @@
       "description": "Maximum height. Interpretation depends on unit (default: pixels). For exact dimensions, set min_height = max_height."
     },
     "unit": {
-      "$ref": "/schemas/3.1.15/enums/dimension-unit.json",
+      "$ref": "/schemas/3.1.20/enums/dimension-unit.json",
       "description": "Unit of measurement for width/height values. Defaults to 'px' when absent. Print formats use 'inches' or 'cm'."
     },
     "aspect_ratio": {

package/dist/lib/schemas-data/3.1/core/requirements/javascript-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/javascript-asset-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/javascript-asset-requirements.json",
   "title": "JavaScript Asset Requirements",
   "description": "Requirements for JavaScript creative assets. These define the execution environment constraints that the JavaScript must be compatible with.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/requirements/markdown-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/markdown-asset-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/markdown-asset-requirements.json",
   "title": "Markdown Asset Requirements",
   "description": "Requirements for markdown creative assets.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/requirements/offering-asset-constraint.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/offering-asset-constraint.json",
+  "$id": "/schemas/3.1.20/core/requirements/offering-asset-constraint.json",
   "title": "Offering Asset Constraint",
   "description": "Declares per-group creative requirements that each offering must satisfy. Allows formats to specify what asset groups (headlines, images, videos) offerings must provide, along with count and per-asset technical constraints.",
   "type": "object",
@@ -10,7 +10,7 @@
       "description": "The asset group this constraint applies to. Values are format-defined vocabulary — each format chooses its own group IDs (e.g., 'headlines', 'images', 'videos'). Buyers discover them via list_creative_formats."
     },
     "asset_type": {
-      "$ref": "/schemas/3.1.15/enums/asset-content-type.json",
+      "$ref": "/schemas/3.1.20/enums/asset-content-type.json",
       "description": "The expected content type for this group."
     },
     "required": {
@@ -29,11 +29,11 @@
       "description": "Maximum number of items allowed in this group."
     },
     "asset_requirements": {
-      "$ref": "/schemas/3.1.15/core/requirements/asset-requirements.json",
+      "$ref": "/schemas/3.1.20/core/requirements/asset-requirements.json",
       "description": "Technical requirements for each item in this group (e.g., max_length for text, min_width/aspect_ratio for images). Applies uniformly to all items in the group."
     },
     "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/core/requirements/text-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/text-asset-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/text-asset-requirements.json",
   "title": "Text Asset Requirements",
   "description": "Requirements for text creative assets such as headlines, body copy, and CTAs.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/requirements/url-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/url-asset-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/url-asset-requirements.json",
   "title": "URL Asset Requirements",
   "description": "Requirements for URL assets such as click-through URLs, tracking pixels, and landing pages.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/requirements/vast-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/vast-asset-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/vast-asset-requirements.json",
   "title": "VAST Asset Requirements",
   "description": "Requirements for VAST (Video Ad Serving Template) creative assets.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/requirements/video-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/video-asset-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/video-asset-requirements.json",
   "title": "Video Asset Requirements",
   "description": "Requirements for video creative assets. These define the technical constraints for video files.",
   "type": "object",
@@ -97,15 +97,15 @@
       "description": "Whether the video must include an audio track"
     },
     "frame_rate_type": {
-      "$ref": "/schemas/3.1.15/enums/frame-rate-type.json",
+      "$ref": "/schemas/3.1.20/enums/frame-rate-type.json",
       "description": "Required frame rate type. Broadcast and SSAI require constant frame rate for seamless splicing."
     },
     "scan_type": {
-      "$ref": "/schemas/3.1.15/enums/scan-type.json",
+      "$ref": "/schemas/3.1.20/enums/scan-type.json",
       "description": "Required scan type. Modern delivery requires progressive scan."
     },
     "gop_type": {
-      "$ref": "/schemas/3.1.15/enums/gop-type.json",
+      "$ref": "/schemas/3.1.20/enums/gop-type.json",
       "description": "Required GOP structure. SSAI and broadcast require closed GOPs for clean splice points."
     },
     "min_gop_interval_seconds": {
@@ -119,7 +119,7 @@
       "description": "Maximum keyframe interval in seconds. SSAI typically requires 1-2 second intervals."
     },
     "moov_atom_position": {
-      "$ref": "/schemas/3.1.15/enums/moov-atom-position.json",
+      "$ref": "/schemas/3.1.20/enums/moov-atom-position.json",
       "description": "Required moov atom position in MP4 container. 'start' enables progressive download without buffering the entire file."
     },
     "audio_codecs": {
@@ -150,7 +150,7 @@
     "audio_channels": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/audio-channel-layout.json"
+        "$ref": "/schemas/3.1.20/enums/audio-channel-layout.json"
       },
       "description": "Accepted audio channel configurations"
     },

package/dist/lib/schemas-data/3.1/core/requirements/webhook-asset-requirements.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/requirements/webhook-asset-requirements.json",
+  "$id": "/schemas/3.1.20/core/requirements/webhook-asset-requirements.json",
   "title": "Webhook Asset Requirements",
   "description": "Requirements for webhook creative assets.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/response-payload-jws-envelope.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/response-payload-jws-envelope.json",
+  "$id": "/schemas/3.1.20/core/response-payload-jws-envelope.json",
   "title": "Response Payload JWS Envelope",
   "description": "Decoded-payload JWS envelope for the closed designated-task response-signing profile. The protected member is the base64url-encoded JWS protected header; payload is the decoded signed payload that verifiers canonicalize with RFC 8785/JCS and base64url-encode before checking the ordinary JWS signature.",
   "type": "object",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/response.json",
+  "$id": "/schemas/3.1.20/core/response.json",
   "title": "Protocol Response",
   "description": "Protocol-level response wrapper (MCP/A2A) - contains AdCP task data plus protocol fields",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/rights-constraint.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/rights-constraint.json",
+  "$id": "/schemas/3.1.20/core/rights-constraint.json",
   "title": "Rights Constraint",
   "description": "Rights metadata attached to a creative manifest. Each entry represents constraints from a single rights holder. A creative may combine multiple rights constraints (e.g., talent likeness + music license). For v1, rights constraints are informational metadata — the buyer/orchestrator manages creative lifecycle against these terms.",
   "type": "object",
@@ -42,7 +42,7 @@
       "type": "array",
       "description": "Rights uses covered by this constraint",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/right-use.json"
+        "$ref": "/schemas/3.1.20/enums/right-use.json"
       },
       "minItems": 1
     },
@@ -68,7 +68,7 @@
       "description": "Maximum total impressions allowed for the full validity period (valid_from to valid_until). This is the absolute cap across all creatives using this rights grant, not a per-creative or per-period limit."
     },
     "right_type": {
-      "$ref": "/schemas/3.1.15/enums/right-type.json",
+      "$ref": "/schemas/3.1.20/enums/right-type.json",
       "description": "Type of rights (talent, music, etc.). Helps identify constraints when a creative combines multiple rights types."
     },
     "approval_status": {
@@ -86,7 +86,7 @@
       "description": "URL where downstream supply chain participants can verify this rights grant is active. Returns HTTP 200 with the current grant status, or 404 if revoked. Enables SSPs and verification vendors to confirm rights before serving."
     },
     "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/core/seller-agent-ref.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/seller-agent-ref.json",
+  "$id": "/schemas/3.1.20/core/seller-agent-ref.json",
   "title": "Seller Agent Reference",
   "description": "Structured reference to a seller agent. The canonical identifier is the agent's URL as declared in the property publisher's adagents.json `authorized_agents[].url`. The optional `id` slot is reserved for a future registry-assigned stable identifier; it is not used today. This shape mirrors `format-id` and `ProviderEntry` — URL-first, with an ID slot for forward compatibility.",
   "x-status": "experimental",

package/dist/lib/schemas-data/3.1/core/signal-coverage-forecast.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-coverage-forecast.json",
+  "$id": "/schemas/3.1.20/core/signal-coverage-forecast.json",
   "title": "Signal Coverage Forecast",
   "description": "Forecast-shaped availability guidance for a signal. Use this when a seller or signal source can expose how much of a declared inventory denominator has a signal present, absent, or present with specific values. This object intentionally omits DeliveryForecast.currency because signal coverage can be unitless.",
   "x-adcp-validation": {
@@ -20,7 +20,7 @@
       "items": {
         "allOf": [
           {
-            "$ref": "/schemas/3.1.15/core/forecast-point.json"
+            "$ref": "/schemas/3.1.20/core/forecast-point.json"
           },
           {
             "required": [
@@ -57,7 +57,7 @@
       "description": "How to interpret the points array. Signal coverage forecasts always use 'availability' because the points describe available inventory or population coverage, not spend curves or temporal pacing."
     },
     "method": {
-      "$ref": "/schemas/3.1.15/enums/forecast-method.json",
+      "$ref": "/schemas/3.1.20/enums/forecast-method.json",
       "description": "Method used to produce this coverage forecast."
     },
     "scope": {
@@ -103,7 +103,7 @@
           "minItems": 1
         },
         "date_range": {
-          "$ref": "/schemas/3.1.15/core/date-range.json",
+          "$ref": "/schemas/3.1.20/core/date-range.json",
           "description": "Historical or planned date window used to compute the denominator."
         }
       },
@@ -140,7 +140,7 @@
       "description": "When this coverage forecast expires."
     },
     "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/core/signal-definition-enrichment.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-definition-enrichment.json",
+  "$id": "/schemas/3.1.20/core/signal-definition-enrichment.json",
   "title": "Signal Definition Enrichment",
   "description": "Optional signal-definition enrichment fields that may be projected inline on signal listings when requested through get_signals.fields. This schema intentionally excludes signal identity and required definition fields so source-native, private, or compact listings can include typed partial disclosure without becoming a full adagents.json signal definition.",
   "type": "object",
@@ -9,7 +9,7 @@
       "type": "array",
       "description": "Restricted attribute categories this signal touches.",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/restricted-attribute.json"
+        "$ref": "/schemas/3.1.20/enums/restricted-attribute.json"
       },
       "minItems": 1
     },
@@ -240,7 +240,7 @@
       "type": "array",
       "minItems": 1,
       "items": {
-        "$ref": "/schemas/3.1.15/enums/consent-basis.json"
+        "$ref": "/schemas/3.1.20/enums/consent-basis.json"
       },
       "description": "Data provider's declared GDPR Article 6 lawful basis or consent basis for the underlying signal definition, projected into this get_signals response row when requested. Sellers and federating agents that pass through another provider's signal MUST NOT substitute their own processing basis for the provider-declared basis."
     },
@@ -307,7 +307,7 @@
           ]
         },
         "disclosure": {
-          "$ref": "/schemas/3.1.15/core/signal-modeling-disclosure.json"
+          "$ref": "/schemas/3.1.20/core/signal-modeling-disclosure.json"
         }
       },
       "required": [

package/dist/lib/schemas-data/3.1/core/signal-definition.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-definition.json",
+  "$id": "/schemas/3.1.20/core/signal-definition.json",
   "title": "Signal Definition",
   "description": "Definition of a signal in published adagents.json signals[]. The publishing domain supplies the namespace, so this definition carries a local id rather than a signal_ref. Media-buy products reference this definition with signal_ref scope 'data_provider', data_provider_domain set to the publishing domain, and signal_id set to this id. Some constraints use JSON Schema draft-07 conditional keywords such as if/then and contains; SDK generators that drop those keywords need equivalent runtime guards.",
   "type": "object",
@@ -22,7 +22,7 @@
       "maxLength": 2000
     },
     "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"
     },
     "tags": {
@@ -45,7 +45,7 @@
       "type": "array",
       "description": "Restricted attribute categories this signal touches. Data providers SHOULD declare these so governance agents can structurally match signals against a plan's restricted_attributes without relying on semantic inference from the signal name or description.",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/restricted-attribute.json"
+        "$ref": "/schemas/3.1.20/enums/restricted-attribute.json"
       },
       "minItems": 1
     },
@@ -375,7 +375,7 @@
       "type": "array",
       "minItems": 1,
       "items": {
-        "$ref": "/schemas/3.1.15/enums/consent-basis.json"
+        "$ref": "/schemas/3.1.20/enums/consent-basis.json"
       },
       "description": "Declared GDPR Article 6 lawful basis or consent basis under which this signal's data is processed. For non-GDPR regimes, use countries, policy_categories, and disclosure fields to describe jurisdiction-specific obligations unless a future enum value applies."
     },
@@ -445,7 +445,7 @@
           "description": "EU AI Act risk classification self-declared by the provider. Prohibited-risk modeled signals must not be published as AdCP signal definitions."
         },
         "disclosure": {
-          "$ref": "/schemas/3.1.15/core/signal-modeling-disclosure.json",
+          "$ref": "/schemas/3.1.20/core/signal-modeling-disclosure.json",
           "description": "Signal/modeling-specific disclosure requirements and jurisdictional notes. This is not creative provenance render guidance."
         }
       },

package/dist/lib/schemas-data/3.1/core/signal-filters.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-filters.json",
+  "$id": "/schemas/3.1.20/core/signal-filters.json",
   "title": "Signal Filters",
   "description": "Filters to refine signal discovery results",
   "type": "object",
@@ -9,7 +9,7 @@
       "type": "array",
       "description": "Filter by catalog type",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/signal-catalog-type.json"
+        "$ref": "/schemas/3.1.20/enums/signal-catalog-type.json"
       },
       "minItems": 1
     },
@@ -39,7 +39,7 @@
       "maximum": 100
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json",
+      "$ref": "/schemas/3.1.20/core/ext.json",
       "description": "Vendor-namespaced extension parameters for seller- or platform-specific signal filter criteria not covered by standard fields. Keys MUST be namespaced under a vendor or platform key (e.g., ext.gam, ext.platform_x). Sellers MUST treat all values as untrusted buyer input; avoid unbounded logging or labels, and do not interpolate values into caller-visible error strings, LLM prompts, SQL queries, or system commands without sanitization. Persistent use of an extension key across multiple buyers is a signal to propose standardization."
     }
   },

package/dist/lib/schemas-data/3.1/core/signal-id.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-id.json",
+  "$id": "/schemas/3.1.20/core/signal-id.json",
   "title": "Signal ID",
   "description": "DEPRECATED. Use SignalRef for new discovery, activation, and media-buy signal identity surfaces. Legacy universal signal identifier used by older Signals Protocol clients. Uses 'source' as discriminator: 'catalog' for signals from a data provider's published catalog (verifiable), or 'agent' for signals native to a signal source identified by agent_url.",
   "deprecated": true,

package/dist/lib/schemas-data/3.1/core/signal-listing.json

@@ -1,16 +1,16 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-listing.json",
+  "$id": "/schemas/3.1.20/core/signal-listing.json",
   "title": "Signal Listing",
   "description": "Shared signal identity and definition metadata used when a signal is listed outside its authoritative definition. New listings carry signal_ref; legacy listings may carry deprecated signal_id during the SignalRef migration window. Product-local signals use the listing as the definition boundary and MUST include name and value_type. Data-provider and signal-source refs MAY omit definition metadata when the buyer can resolve it from the referenced provider-published definition or source; any supplied name, description, value_type, categories, range, methodology_url, or last_updated is product/account/source context and does not replace the authoritative definition.",
   "type": "object",
   "properties": {
     "signal_ref": {
-      "$ref": "/schemas/3.1.15/core/signal-ref.json",
+      "$ref": "/schemas/3.1.20/core/signal-ref.json",
       "description": "Canonical signal reference. Use scope 'product' for a product-local signal defined by this listing; use scope 'data_provider' with data_provider_domain for a signal defined in a data provider's published adagents.json signals[]; use scope 'signal_source' with signal_source_url for a source-native signal."
     },
     "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
     },
@@ -33,7 +33,7 @@
       "description": "When this listing record was last updated. This indicates freshness of the listing record, not an attestation that the underlying data or model was refreshed at that time."
     },
     "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. Required when signal_ref.scope is 'product'."
     },
     "categories": {

package/dist/lib/schemas-data/3.1/core/signal-modeling-disclosure.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-modeling-disclosure.json",
+  "$id": "/schemas/3.1.20/core/signal-modeling-disclosure.json",
   "title": "Signal Modeling Disclosure",
   "description": "Disclosure requirements and jurisdictional notes for modeled data signals. This schema is intentionally separate from core/provenance.json because creative provenance is about generated content, render guidance, and asset-level chain of custody, while signal modeling disclosure is about data-segment methodology and data-use transparency.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/signal-pricing-option.json

@@ -1,7 +1,7 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-pricing-option.json",
+  "$id": "/schemas/3.1.20/core/signal-pricing-option.json",
   "title": "Signal Pricing Option",
   "description": "Deprecated — use vendor-pricing-option.json for new implementations. This alias is retained for backward compatibility.",
-  "$ref": "/schemas/3.1.15/core/vendor-pricing-option.json"
+  "$ref": "/schemas/3.1.20/core/vendor-pricing-option.json"
 }

package/dist/lib/schemas-data/3.1/core/signal-pricing.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-pricing.json",
+  "$id": "/schemas/3.1.20/core/signal-pricing.json",
   "title": "Vendor Pricing",
   "description": "Pricing model for a vendor service. Discriminated by model: 'cpm' (fixed CPM), 'percent_of_media' (percentage of spend with optional CPM cap), 'flat_fee' (fixed charge per reporting period), 'per_unit' (fixed price per unit of work), or 'custom' (escape hatch for models not covered by the enumerated forms — requires a description and structured metadata).",
   "type": "object",
@@ -28,7 +28,7 @@
           "pattern": "^[A-Z]{3}$"
         },
         "ext": {
-          "$ref": "/schemas/3.1.15/core/ext.json"
+          "$ref": "/schemas/3.1.20/core/ext.json"
         }
       },
       "required": [
@@ -64,7 +64,7 @@
           "pattern": "^[A-Z]{3}$"
         },
         "ext": {
-          "$ref": "/schemas/3.1.15/core/ext.json"
+          "$ref": "/schemas/3.1.20/core/ext.json"
         }
       },
       "required": [
@@ -104,7 +104,7 @@
           "pattern": "^[A-Z]{3}$"
         },
         "ext": {
-          "$ref": "/schemas/3.1.15/core/ext.json"
+          "$ref": "/schemas/3.1.20/core/ext.json"
         }
       },
       "required": [
@@ -139,7 +139,7 @@
           "pattern": "^[A-Z]{3}$"
         },
         "ext": {
-          "$ref": "/schemas/3.1.15/core/ext.json"
+          "$ref": "/schemas/3.1.20/core/ext.json"
         }
       },
       "required": [
@@ -183,7 +183,7 @@
           "pattern": "^[A-Z]{3}$"
         },
         "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/core/signal-ref.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-ref.json",
+  "$id": "/schemas/3.1.20/core/signal-ref.json",
   "title": "Signal Ref",
   "description": "Reference to a named signal definition. Uses scope as discriminator: 'data_provider' for a signal resolved through published adagents.json signals[], 'signal_source' for a source-native signal resolved through the issuing signal source, or 'product' for a product-local signal option. Scope is the resolution path, not provenance; authoritative enrichment lives on the seller, signal source, or data-provider signal definition, not on this reference.",
   "x-entity": "signal",

package/dist/lib/schemas-data/3.1/core/signal-selection-group-rule.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-selection-group-rule.json",
+  "$id": "/schemas/3.1.20/core/signal-selection-group-rule.json",
   "title": "Signal Selection Group Rule",
   "description": "Product-scoped override for one ProductSignalTargetingOption.selection_group value. Use this when a product has mixed signal-selection behavior, such as fixed suppressions plus a required pick-one include tier.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/signal-targeting-expression.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/signal-targeting-expression.json",
+  "$id": "/schemas/3.1.20/core/signal-targeting-expression.json",
   "title": "Signal Targeting Expression",
   "description": "Predicate over a named signal definition. Signals are typed dimensions, similar to feature values: binary signals match true, categorical signals match one of a set of values, and numeric signals match a range. In package signal targeting groups, include/exclude semantics are controlled by the parent group operator, not by negating the expression.",
   "discriminator": {
@@ -12,7 +12,7 @@
       "description": "Binary signal expression. In grouped package targeting, value is always true; use a parent group with operator 'none' for exclusion.",
       "properties": {
         "signal_ref": {
-          "$ref": "/schemas/3.1.15/core/signal-ref.json",
+          "$ref": "/schemas/3.1.20/core/signal-ref.json",
           "description": "Named signal being targeted."
         },
         "value_type": {
@@ -38,7 +38,7 @@
       "description": "Categorical signal expression - target users with one of the listed values.",
       "properties": {
         "signal_ref": {
-          "$ref": "/schemas/3.1.15/core/signal-ref.json",
+          "$ref": "/schemas/3.1.20/core/signal-ref.json",
           "description": "Named signal being targeted."
         },
         "value_type": {
@@ -67,7 +67,7 @@
       "description": "Numeric signal expression - target users within a value range. At least one of min_value or max_value is required. If both min_value and max_value are provided, min_value MUST be <= max_value.",
       "properties": {
         "signal_ref": {
-          "$ref": "/schemas/3.1.15/core/signal-ref.json",
+          "$ref": "/schemas/3.1.20/core/signal-ref.json",
           "description": "Named signal being targeted."
         },
         "value_type": {