@adcp/sdk 13.0.0 → 13.0.2

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/installment.json",
+  "$id": "/schemas/3.1.20/core/installment.json",
   "title": "Installment",
   "description": "A single bookable unit within a collection — one episode, issue, event, or rotation period. The parent collection's kind indicates how to interpret each installment: TV/podcast episodes, print issues, live event airings, newsletter editions, or DOOH rotation periods. Installments inherit collection-level fields they don't override: content_rating defaults to the collection's baseline, guest_talent is additive to the collection's recurring talent, and topics add context beyond the collection's genre.",
   "type": "object",
@@ -31,7 +31,7 @@
       "description": "When the installment airs or publishes (ISO 8601)"
     },
     "status": {
-      "$ref": "/schemas/3.1.15/enums/installment-status.json",
+      "$ref": "/schemas/3.1.20/enums/installment-status.json",
       "description": "Lifecycle status of the installment"
     },
     "duration_seconds": {
@@ -49,7 +49,7 @@
       "description": "When this installment data expires and should be re-queried. Agents should re-query before committing budget to products with tentative installments."
     },
     "content_rating": {
-      "$ref": "/schemas/3.1.15/core/content-rating.json",
+      "$ref": "/schemas/3.1.20/core/content-rating.json",
       "description": "Installment-specific content rating. Overrides the collection's baseline content_rating when present."
     },
     "topics": {
@@ -60,22 +60,22 @@
       }
     },
     "special": {
-      "$ref": "/schemas/3.1.15/core/special.json",
+      "$ref": "/schemas/3.1.20/core/special.json",
       "description": "Installment-specific event context. When present, this installment is anchored to a real-world event. Overrides the collection-level special when present."
     },
     "guest_talent": {
       "type": "array",
       "description": "Installment-specific guests and talent. Additive to the collection's recurring talent.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/talent.json"
+        "$ref": "/schemas/3.1.20/core/talent.json"
       }
     },
     "ad_inventory": {
-      "$ref": "/schemas/3.1.15/core/ad-inventory-config.json",
+      "$ref": "/schemas/3.1.20/core/ad-inventory-config.json",
       "description": "Break-based ad inventory for this installment. For non-break formats (host reads, integrations), use product placements."
     },
     "deadlines": {
-      "$ref": "/schemas/3.1.15/core/installment-deadlines.json",
+      "$ref": "/schemas/3.1.20/core/installment-deadlines.json",
       "description": "Booking, cancellation, and material submission deadlines for this installment. Present when the installment has time-sensitive inventory that requires advance commitment or material delivery."
     },
     "derivative_of": {
@@ -87,7 +87,7 @@
           "description": "The source installment this content is derived from"
         },
         "type": {
-          "$ref": "/schemas/3.1.15/enums/derivative-type.json",
+          "$ref": "/schemas/3.1.20/enums/derivative-type.json",
           "description": "What kind of derivative content this is"
         }
       },
@@ -98,7 +98,7 @@
       "additionalProperties": false
     },
     "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/job-item.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/job-item.json",
+  "$id": "/schemas/3.1.20/core/job-item.json",
   "title": "Job Item",
   "description": "A job posting within a job-type catalog. Carries the position details that platforms use for job ads and recruitment campaigns. Maps to LinkedIn Jobs XML, Google DynamicJobsAsset, schema.org JobPosting, and similar formats.",
   "type": "object",
@@ -126,12 +126,12 @@
       "type": "array",
       "description": "Typed creative asset pools for this job. Uses the same OfferingAssetGroup structure as offering-type catalogs. Standard group IDs: 'images_landscape' (company/role hero), 'images_vertical' (9:16 for Stories), 'logo' (company logo). Enables formats to declare typed image requirements that map unambiguously to the right asset regardless of platform.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/offering-asset-group.json"
+        "$ref": "/schemas/3.1.20/core/offering-asset-group.json"
       },
       "minItems": 1
     },
     "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/keyword-delivery-metrics.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/keyword-delivery-metrics.json",
+  "$id": "/schemas/3.1.20/core/keyword-delivery-metrics.json",
   "title": "Keyword Delivery Metrics",
   "description": "Delivery metrics row for one keyword and match-type pair within a package.",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.15/core/delivery-metrics.json"
+      "$ref": "/schemas/3.1.20/core/delivery-metrics.json"
     },
     {
       "type": "object",
@@ -15,7 +15,7 @@
           "description": "The targeted keyword"
         },
         "match_type": {
-          "$ref": "/schemas/3.1.15/enums/match-type.json"
+          "$ref": "/schemas/3.1.20/enums/match-type.json"
         }
       },
       "required": [

package/dist/lib/schemas-data/3.1/core/limited-series.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/limited-series.json",
+  "$id": "/schemas/3.1.20/core/limited-series.json",
   "title": "Limited Series",
   "description": "A bounded content run with a defined arc. Indicates the collection has a planned beginning, end, and installment count — distinguishing it from ongoing series.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/material-deadline.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/material-deadline.json",
+  "$id": "/schemas/3.1.20/core/material-deadline.json",
   "title": "Material Deadline",
   "description": "A deadline for creative material submission. Sellers declare stages to distinguish draft materials (e.g., talking points, raw artwork) from production-ready assets (e.g., approved scripts, press-ready PDFs).",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/mcp-webhook-payload.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/mcp-webhook-payload.json",
+  "$id": "/schemas/3.1.20/core/mcp-webhook-payload.json",
   "title": "MCP Webhook Payload",
   "description": "Standard envelope for HTTP-based push notifications (MCP). This defines the wire format sent to the URL configured in `pushNotificationConfig`. NOTE: This envelope is NOT used in A2A integration, which uses native Task/TaskStatusUpdateEvent messages with the AdCP payload nested in `status.message.parts[].data`.",
   "type": "object",
@@ -29,15 +29,15 @@
       "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 that triggered this webhook. Enables webhook handlers to route to appropriate processing logic."
     },
     "protocol": {
-      "$ref": "/schemas/3.1.15/enums/adcp-protocol.json",
+      "$ref": "/schemas/3.1.20/enums/adcp-protocol.json",
       "description": "AdCP protocol this task belongs to. Helps classify the operation type at a high level."
     },
     "status": {
-      "$ref": "/schemas/3.1.15/enums/task-status.json",
+      "$ref": "/schemas/3.1.20/enums/task-status.json",
       "description": "Current task status. Webhooks are triggered for status changes after initial submission."
     },
     "timestamp": {
@@ -60,7 +60,7 @@
       "maxLength": 4096
     },
     "result": {
-      "$ref": "/schemas/3.1.15/core/async-response-data.json",
+      "$ref": "/schemas/3.1.20/core/async-response-data.json",
       "description": "Task-specific payload matching the status. For completed/failed, contains the full task response. For working/input-required/submitted, contains status-specific data. This is the data layer that AdCP specs - same structure used in A2A status.message.parts[].data."
     }
   },

package/dist/lib/schemas-data/3.1/core/measurement-readiness.json

@@ -1,19 +1,19 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/measurement-readiness.json",
+  "$id": "/schemas/3.1.20/core/measurement-readiness.json",
   "title": "Measurement Readiness",
   "description": "Per-product assessment of whether the buyer's event source setup is sufficient for the product's optimization capabilities. Sellers evaluate this in the context of the buyer's account — the same product may show different readiness for different buyers depending on their event source configuration.",
   "type": "object",
   "properties": {
     "status": {
-      "$ref": "/schemas/3.1.15/enums/assessment-status.json",
+      "$ref": "/schemas/3.1.20/enums/assessment-status.json",
       "description": "Overall measurement readiness level for this product given the buyer's event setup. 'insufficient' means the product cannot optimize effectively with the current setup."
     },
     "required_event_types": {
       "type": "array",
       "description": "Event types this product needs for effective optimization. Buyers should ensure their event sources cover these types.",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/event-type.json"
+        "$ref": "/schemas/3.1.20/enums/event-type.json"
       },
       "minItems": 1
     },
@@ -21,14 +21,14 @@
       "type": "array",
       "description": "Event types this product requires that the buyer has not configured. Empty or absent when all required types are covered.",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/event-type.json"
+        "$ref": "/schemas/3.1.20/enums/event-type.json"
       }
     },
     "issues": {
       "type": "array",
       "description": "Actionable issues preventing full measurement readiness. Sellers should limit to the top 3-5 most actionable items. Buyer agents should sort by severity rather than relying on array position.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/diagnostic-issue.json"
+        "$ref": "/schemas/3.1.20/core/diagnostic-issue.json"
       }
     },
     "notes": {

package/dist/lib/schemas-data/3.1/core/measurement-terms.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/measurement-terms.json",
+  "$id": "/schemas/3.1.20/core/measurement-terms.json",
   "title": "Measurement Terms",
   "description": "Billing measurement and makegood terms for media buys. Declares who counts the billing metric and what remedies apply when thresholds are breached. Appears on products (seller defaults), package requests (buyer proposals), and confirmed packages (agreed terms). All fields are optional — presence indicates the term is declared or proposed.",
   "type": "object",
@@ -10,7 +10,7 @@
       "description": "Which vendor's count of the billing metric governs invoicing. The billing metric is determined by the pricing_model on the selected pricing_option (e.g., impressions for CPM, completed views for CPCV).",
       "properties": {
         "vendor": {
-          "$ref": "/schemas/3.1.15/core/brand-ref.json",
+          "$ref": "/schemas/3.1.20/core/brand-ref.json",
           "description": "Vendor whose measurement of the billing metric is authoritative for invoicing (e.g., { domain: 'campaignmanager.google.com' } for buyer's DCM, { domain: 'admanager.google.com' } for seller's GAM)."
         },
         "max_variance_percent": {
@@ -52,7 +52,7 @@
           "type": "array",
           "description": "Remedy types the seller supports. Ordered by seller preference (first = preferred). Seller proposes from this list when a breach occurs; buyer accepts or disputes.",
           "items": {
-            "$ref": "/schemas/3.1.15/enums/makegood-remedy.json"
+            "$ref": "/schemas/3.1.20/enums/makegood-remedy.json"
           },
           "minItems": 1,
           "uniqueItems": true

package/dist/lib/schemas-data/3.1/core/measurement-window.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/measurement-window.json",
+  "$id": "/schemas/3.1.20/core/measurement-window.json",
   "title": "Measurement Window",
   "description": "A measurement maturation stage for any channel where billing-grade data is produced in phases rather than arriving final on day one. Each window represents an accumulation or processing stage with its own expected availability. Examples: broadcast/linear TV (live → C3 → C7 DVR accumulation), DOOH (tentative plays → post-IVT/fraud-check final), digital (raw impressions → GIVT filtered → SIVT filtered), podcast (7-day downloads → 30-day downloads), audio/radio (tentative → diary/panel-certified). Sellers whose data is final on first delivery omit this.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/media-buy-available-action.json

@@ -1,20 +1,20 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/media-buy-available-action.json",
+  "$id": "/schemas/3.1.20/core/media-buy-available-action.json",
   "title": "Media Buy Available Action",
   "description": "An action currently available on a media buy, resolved against the buy's current status, negotiated terms, account tier, and any buy-level overrides. Authoritative per-buy capability — buyer SDKs MUST read this rather than re-deriving from the product's `allowed_actions[]`, because divergence from the product template is expected (negotiated terms and IO addenda live on the deal, not the product SKU). The containing `available_actions[]` array is uniquely keyed by `action`; sellers MUST NOT emit two entries with the same `action` value (this is a contract-level invariant — JSON Schema `uniqueItems` only catches structurally identical objects, so validators MUST enforce action-uniqueness separately). Predicate evaluators consuming dotted paths like `available_actions.extend_flight.sla.response_max` MUST index by `action` rather than by array position. The `mode` and `sla` values are advisory at the moment of emission; sellers MAY resolve to a different mode by the time the mutation arrives (state can change), in which case the request is rejected with `ACTION_NOT_ALLOWED` (`reason: mode_mismatch`).",
   "type": "object",
   "properties": {
     "action": {
-      "$ref": "/schemas/3.1.15/enums/media-buy-valid-action.json",
+      "$ref": "/schemas/3.1.20/enums/media-buy-valid-action.json",
       "description": "The action identifier."
     },
     "mode": {
-      "$ref": "/schemas/3.1.15/enums/media-buy-action-mode.json",
+      "$ref": "/schemas/3.1.20/enums/media-buy-action-mode.json",
       "description": "The single mode that applies right now on this buy for this action. Singular because the buy has a concrete state, exactly one mode applies. Buyer SDKs branch on this to decide whether to expect a synchronous response, conditional handling, or an asynchronous approval callback."
     },
     "sla": {
-      "$ref": "/schemas/3.1.15/core/sla-window.json",
+      "$ref": "/schemas/3.1.20/core/sla-window.json",
       "description": "Optional SLA commitment for this action on this buy. Absence means no commitment, not zero commitment."
     },
     "terms_ref": {

package/dist/lib/schemas-data/3.1/core/media-buy-features.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/media-buy-features.json",
+  "$id": "/schemas/3.1.20/core/media-buy-features.json",
   "title": "Media Buy Features",
   "description": "Optional media-buy protocol features. Used in capability declarations (seller declares support) and product filters (buyer requires support). If a seller declares a feature as true, they MUST honor requests using that feature.",
   "type": "object",
@@ -11,7 +11,7 @@
     },
     "property_list_filtering": {
       "type": "boolean",
-      "description": "Honors property_list parameter in get_products to filter results to buyer-approved properties"
+      "description": "Honors property_list references in get_products filtering and in targeting_overlay on create_media_buy and update_media_buy"
     },
     "catalog_management": {
       "type": "boolean",

package/dist/lib/schemas-data/3.1/core/media-buy.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/media-buy.json",
+  "$id": "/schemas/3.1.20/core/media-buy.json",
   "title": "Media Buy",
   "description": "Represents a purchased advertising campaign",
   "type": "object",
@@ -11,16 +11,16 @@
       "x-entity": "media_buy"
     },
     "account": {
-      "$ref": "/schemas/3.1.15/core/account.json",
+      "$ref": "/schemas/3.1.20/core/account.json",
       "description": "Account billed for this media buy"
     },
     "status": {
-      "$ref": "/schemas/3.1.15/enums/media-buy-status.json"
+      "$ref": "/schemas/3.1.20/enums/media-buy-status.json"
     },
     "health": {
       "allOf": [
         {
-          "$ref": "/schemas/3.1.15/enums/media-buy-health.json"
+          "$ref": "/schemas/3.1.20/enums/media-buy-health.json"
         }
       ],
       "default": "ok",
@@ -30,7 +30,7 @@
       "type": "array",
       "description": "Open impairments — upstream dependency state changes that affect delivery for at least one package on this buy. Empty when health is 'ok'. Sellers MUST add an entry on next sync/poll response after a referenced resource transitions to an offline state, and MUST remove the entry (flipping health to 'ok' when the array empties) when the resource returns to a serviceable state. Staleness budget: the snapshot MUST reflect the impairment within 5 minutes of impairment.observed_at regardless of buyer poll cadence — sellers cannot rely on rare buyer polls to defer write propagation. See impairment.coherence assertion for the cross-resource invariant.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/impairment.json"
+        "$ref": "/schemas/3.1.20/core/impairment.json"
       }
     },
     "rejection_reason": {
@@ -59,7 +59,7 @@
           "description": "ISO 8601 timestamp when this media buy was canceled."
         },
         "canceled_by": {
-          "$ref": "/schemas/3.1.15/enums/canceled-by.json",
+          "$ref": "/schemas/3.1.20/enums/canceled-by.json",
           "description": "Which party initiated the cancellation. 'buyer' when canceled via update_media_buy; 'seller' when the seller cancels (e.g., policy violation, inventory withdrawal)."
         },
         "reason": {
@@ -79,15 +79,15 @@
       "type": "array",
       "description": "Array of packages within this media buy",
       "items": {
-        "$ref": "/schemas/3.1.15/core/package.json"
+        "$ref": "/schemas/3.1.20/core/package.json"
       }
     },
     "context": {
-      "$ref": "/schemas/3.1.15/core/context.json",
+      "$ref": "/schemas/3.1.20/core/context.json",
       "description": "Opaque media-buy-level correlation data echoed unchanged from the create_media_buy request. Sellers MUST include persisted context on read surfaces such as get_media_buys when the media buy was created through AdCP with context, so buyers can reconcile seller-assigned media_buy_id values with their own tracking state. Sellers MAY omit context for media buys created outside AdCP or created without context. Sellers MUST NOT parse this object for business logic."
     },
     "invoice_recipient": {
-      "$ref": "/schemas/3.1.15/core/business-entity.json",
+      "$ref": "/schemas/3.1.20/core/business-entity.json",
       "description": "Per-buy override for who receives the invoice. When provided, the seller invoices this entity instead of the account's default billing_entity. The seller MUST validate the invoice recipient is authorized for this account. When governance_agents are configured, the seller MUST include invoice_recipient in the check_governance request."
     },
     "creative_deadline": {
@@ -111,7 +111,7 @@
       "description": "Last update timestamp"
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "allOf": [

package/dist/lib/schemas-data/3.1/core/missing-metric.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/missing-metric.json",
+  "$id": "/schemas/3.1.20/core/missing-metric.json",
   "title": "Missing Metric",
   "description": "One metric the binding reporting contract declared but that is not populated in a delivery report. Symmetric with `committed_metrics` and discriminated by `scope`.",
   "type": "object",
@@ -15,26 +15,26 @@
           "const": "standard"
         },
         "metric_id": {
-          "$ref": "/schemas/3.1.15/enums/available-metric.json"
+          "$ref": "/schemas/3.1.20/enums/available-metric.json"
         },
         "qualifier": {
           "type": "object",
           "description": "Mirrors the qualifier on `committed_metrics` so the missing entry preserves the contract distinction (e.g., flagging MRC viewability as missing when only GroupM was reported, vendor-attested completion as missing when only seller-attested was reported, or deterministic_purchase attribution as missing when only probabilistic was reported). MUST match the qualifier on the corresponding `committed_metrics` entry the missing flag refers to.",
           "properties": {
             "viewability_standard": {
-              "$ref": "/schemas/3.1.15/enums/viewability-standard.json"
+              "$ref": "/schemas/3.1.20/enums/viewability-standard.json"
             },
             "completion_source": {
-              "$ref": "/schemas/3.1.15/enums/completion-source.json"
+              "$ref": "/schemas/3.1.20/enums/completion-source.json"
             },
             "attribution_methodology": {
-              "$ref": "/schemas/3.1.15/enums/attribution-methodology.json"
+              "$ref": "/schemas/3.1.20/enums/attribution-methodology.json"
             },
             "attribution_window": {
-              "$ref": "/schemas/3.1.15/core/duration.json"
+              "$ref": "/schemas/3.1.20/core/duration.json"
             },
             "lift_dimension": {
-              "$ref": "/schemas/3.1.15/enums/lift-dimension.json"
+              "$ref": "/schemas/3.1.20/enums/lift-dimension.json"
             }
           },
           "additionalProperties": false
@@ -53,10 +53,10 @@
           "const": "vendor"
         },
         "vendor": {
-          "$ref": "/schemas/3.1.15/core/brand-ref.json"
+          "$ref": "/schemas/3.1.20/core/brand-ref.json"
         },
         "metric_id": {
-          "$ref": "/schemas/3.1.15/core/vendor-metric-id.json"
+          "$ref": "/schemas/3.1.20/core/vendor-metric-id.json"
         }
       },
       "required": [

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/notification-config.json",
+  "$id": "/schemas/3.1.20/core/notification-config.json",
   "title": "Notification Config",
   "description": "Account-level webhook subscription for notifications whose lifecycle outlives any single media buy — creative state changes, library purges, wholesale feed change webhooks, and future account-anchored resource events after those event types are added to notification-type.json. This surface does not currently carry lifecycle events for the account object itself (for example, there is no `account.status_changed` event type); account status changes are observed through `list_accounts` polling or the one-shot `sync_accounts.push_notification_config` async result channel. Distinct from `push-notification-config.json`, which anchors at a per-resource operation (a single task or media buy). An account MAY register multiple notification configs to fan a single seller's events out to multiple buyer-side endpoints; each entry filters by `event_types`. As with push-notification-config, the default signing scheme is the AdCP RFC 9421 webhook profile against the seller's brand.json `agents[]` JWKS; the optional `authentication` block opts into the deprecated Bearer / HMAC-SHA256 fallback for compatibility. Credentials and shared secrets in `authentication.credentials` are write-only — sellers MUST NOT echo them back in `list_accounts` responses. Sellers MUST verify endpoint control before activating a new or changed active account-level notification config; delivery-time SSRF validation still applies to every fire.",
   "type": "object",
@@ -21,7 +21,7 @@
       "type": "array",
       "description": "Notification types this subscriber wishes to receive on the registered `url`. The seller MUST NOT fire other types against this endpoint, and MUST NOT silently widen the filter when new types are added to `notification-type.json`. When omitted, the seller MUST default to a no-fire policy and surface an `errors[]` entry on `sync_accounts` so the buyer notices the missing filter. Values are drawn from `notification-type.json`, but only types whose contract anchors at the account scope are valid here — creative lifecycle events and wholesale feed change payloads are valid; media-buy-anchored types (`scheduled`, `final`, `delayed`, `adjusted`, `impairment`) and account-lifecycle names not present in the enum (for example, `account.status_changed`) are invalid on this surface; sellers MUST reject those entries as per-account validation failures with `INVALID_REQUEST` or `VALIDATION_ERROR` and `error.field` pointing at the invalid `event_types` entry rather than silently dropping them.",
       "items": {
-        "$ref": "/schemas/3.1.15/enums/notification-type.json"
+        "$ref": "/schemas/3.1.20/enums/notification-type.json"
       },
       "minItems": 1,
       "uniqueItems": true
@@ -33,7 +33,7 @@
         "schemes": {
           "type": "array",
           "items": {
-            "$ref": "/schemas/3.1.15/enums/auth-scheme.json"
+            "$ref": "/schemas/3.1.20/enums/auth-scheme.json"
           },
           "minItems": 1,
           "maxItems": 1
@@ -55,7 +55,7 @@
       "description": "When false, the seller persists the configuration but suppresses fires. Use to pause a noisy subscriber without losing the registration. Sellers MUST NOT skip persisting the entry when `active: false` — the buyer's next `sync_accounts` MUST observe the same array, otherwise the buyer cannot distinguish pause from drop. Paused configs may skip only the outbound proof challenge while inactive; sellers MUST still enforce URL parsing, HTTPS, hostname normalization, and reserved-range rejection at write time. Reactivation requires full SSRF validation with connect pinning plus proof-of-control for any tuple without current valid proof."
     },
     "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/offering-asset-group.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/offering-asset-group.json",
+  "$id": "/schemas/3.1.20/core/offering-asset-group.json",
   "title": "Offering Asset Group",
   "description": "A structured group of creative assets within an offering, identified by a group ID and asset type. Enables offerings to carry per-group creative pools (headlines, images, videos) using the same vocabulary as format-level asset definitions.",
   "type": "object",
@@ -10,7 +10,7 @@
       "description": "Identifies the creative role this group fills. Values are defined by each format's offering_asset_constraints — not protocol constants. Discover them via list_creative_formats (e.g., a format might declare 'headlines', 'images', or 'videos')."
     },
     "asset_type": {
-      "$ref": "/schemas/3.1.15/enums/asset-content-type.json",
+      "$ref": "/schemas/3.1.20/enums/asset-content-type.json",
       "description": "The content type of all items in this group."
     },
     "items": {
@@ -19,43 +19,43 @@
       "items": {
         "oneOf": [
           {
-            "$ref": "/schemas/3.1.15/core/assets/text-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/text-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/image-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/image-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/video-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/video-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/audio-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/audio-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/url-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/url-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/html-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/html-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/markdown-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/markdown-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/vast-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/vast-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/daast-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/daast-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/css-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/css-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/javascript-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/javascript-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/zip-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/zip-asset.json"
           },
           {
-            "$ref": "/schemas/3.1.15/core/assets/webhook-asset.json"
+            "$ref": "/schemas/3.1.20/core/assets/webhook-asset.json"
           }
         ],
         "discriminator": {
@@ -65,7 +65,7 @@
       "minItems": 1
     },
     "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/offering.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/core/offering.json",
+  "$id": "/schemas/3.1.20/core/offering.json",
   "title": "Offering",
   "description": "A promotable offering from a brand. Can represent a campaign, product promotion, service, or any other thing the brand wants to make available. Offerings carry structured asset groups for creative assembly and can be promoted via traditional creatives or conversational SI experiences (via the brand's SI agent).",
   "type": "object",
@@ -46,7 +46,7 @@
       "type": "array",
       "description": "Structured asset groups for this offering. Each group carries a typed pool of creative assets (headlines, images, videos, etc.) identified by a group ID that matches format-level vocabulary.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/offering-asset-group.json"
+        "$ref": "/schemas/3.1.20/core/offering-asset-group.json"
       }
     },
     "geo_targets": {
@@ -78,7 +78,7 @@
             "type": "object",
             "properties": {
               "system": {
-                "$ref": "/schemas/3.1.15/enums/metro-system.json",
+                "$ref": "/schemas/3.1.20/enums/metro-system.json",
                 "description": "Metro area classification system (e.g., 'nielsen_dma', 'uk_itl2')"
               },
               "values": {
@@ -102,7 +102,7 @@
           "type": "array",
           "description": "Postal areas where this offering is relevant. Prefer the native country + postal system form. Deprecated legacy country-fused postal-system tokens remain accepted for compatibility.",
           "items": {
-            "$ref": "/schemas/3.1.15/core/postal-area.json"
+            "$ref": "/schemas/3.1.20/core/postal-area.json"
           },
           "minItems": 1
         }
@@ -124,7 +124,7 @@
       }
     },
     "ext": {
-      "$ref": "/schemas/3.1.15/core/ext.json"
+      "$ref": "/schemas/3.1.20/core/ext.json"
     }
   },
   "required": [