@adcp/sdk 13.0.0 → 13.0.2

package/dist/lib/schemas-data/3.1/account/list-accounts-request.json

@@ -1,17 +1,17 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/account/list-accounts-request.json",
+  "$id": "/schemas/3.1.20/account/list-accounts-request.json",
   "title": "List Accounts Request",
   "description": "Request parameters for listing accounts accessible to the authenticated agent. For upstream-managed account namespaces, this is the mandatory discovery surface for seller-assigned account_id values before account-scoped calls when a credential may access more than one account, and the preferred singleton discovery surface when a credential is bound to exactly one account.",
   "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": "Optional exact account filter. Use `account_id` to retrieve one known account from an account_id namespace, or the natural key (`brand` + `operator`, optionally `sandbox`) for buyer-declared account sellers. When present, the seller returns only matching accounts visible to the authenticated caller."
     },
     "status": {
@@ -27,17 +27,17 @@
       "description": "Filter accounts by status. Omit to return accounts in all statuses."
     },
     "pagination": {
-      "$ref": "/schemas/3.1.15/core/pagination-request.json"
+      "$ref": "/schemas/3.1.20/core/pagination-request.json"
     },
     "sandbox": {
       "type": "boolean",
       "description": "Filter by sandbox status. true returns only sandbox accounts, false returns only production accounts. Omit to return all accounts. Primarily used with account-id namespaces where sandbox accounts are pre-existing test accounts on the platform."
     },
     "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/account/list-accounts-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/account/list-accounts-response.json",
+  "$id": "/schemas/3.1.20/account/list-accounts-response.json",
   "title": "List Accounts Response",
   "description": "Response payload for list_accounts 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": {
@@ -17,24 +17,24 @@
       "type": "array",
       "description": "Array of accounts accessible to the authenticated agent. Each entry is the full Account object plus an optional `authorization` object describing what the calling agent is permitted to do on that account.",
       "items": {
-        "$ref": "/schemas/3.1.15/core/account-with-authorization.json"
+        "$ref": "/schemas/3.1.20/core/account-with-authorization.json"
       }
     },
     "errors": {
       "type": "array",
       "description": "Task-specific errors and warnings",
       "items": {
-        "$ref": "/schemas/3.1.15/core/error.json"
+        "$ref": "/schemas/3.1.20/core/error.json"
       }
     },
     "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/account/report-usage-request.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/account/report-usage-request.json",
+  "$id": "/schemas/3.1.20/account/report-usage-request.json",
   "title": "Report Usage Request",
   "description": "Reports how a vendor's service was consumed after campaign delivery. Used by orchestrators (DSPs, storefronts) to inform vendor agents (signals, governance, creative, or — when the receiving agent is the seller of the media buy itself — a sales agent for buyer-attested or vendor-attested billing reconciliation) what was used so the receiver can track earned revenue and verify billing. Records can span multiple accounts and campaigns in a single request. When the buy's `measurement_terms.billing_measurement.vendor` names a party other than the seller's own ad server, that party (or the buyer on its behalf) pushes final measurements via this task; the seller invoices against those final records. See [Billing authority](/docs/media-buy/advanced-topics/billing-authority) for the end-to-end flow.",
   "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,
@@ -16,7 +16,7 @@
       "description": "Client-generated unique key for this request. If a request with the same key has already been accepted, the server returns the original response without re-processing. MUST be unique per (seller, request) pair to prevent cross-seller correlation. Use a fresh UUID v4 for each request. Prevents duplicate billing on retries."
     },
     "reporting_period": {
-      "$ref": "/schemas/3.1.15/core/datetime-range.json",
+      "$ref": "/schemas/3.1.20/core/datetime-range.json",
       "description": "The time range covered by this usage report. Applies to all records in the request."
     },
     "usage": {
@@ -27,7 +27,7 @@
         "type": "object",
         "properties": {
           "account": {
-            "$ref": "/schemas/3.1.15/core/account-ref.json",
+            "$ref": "/schemas/3.1.20/core/account-ref.json",
             "description": "Account for this usage record."
           },
           "media_buy_id": {
@@ -122,10 +122,10 @@
       }
     },
     "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/account/report-usage-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/account/report-usage-response.json",
+  "$id": "/schemas/3.1.20/account/report-usage-response.json",
   "title": "Report Usage Response",
   "description": "Response from report_usage. Partial acceptance is valid — records that pass validation are stored even when others fail.",
   "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": {
@@ -22,7 +22,7 @@
       "type": "array",
       "description": "Validation errors for individual records. The field property identifies which record failed (e.g., 'usage[1].pricing_option_id').",
       "items": {
-        "$ref": "/schemas/3.1.15/core/error.json"
+        "$ref": "/schemas/3.1.20/core/error.json"
       }
     },
     "sandbox": {
@@ -30,10 +30,10 @@
       "description": "When true, the account is a sandbox account and no billing occurred."
     },
     "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/account/sync-accounts-request.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/account/sync-accounts-request.json",
+  "$id": "/schemas/3.1.20/account/sync-accounts-request.json",
   "title": "Sync Accounts Request",
   "description": "Sync advertiser account state with a seller. Two modes, distinguished by the key on each per-account entry:\n\n- **Provisioning mode** (`brand` + `operator` + `billing` at the entry root): the agent declares which brands it represents, who operates on each brand's behalf, and the billing model. The seller provisions or links accounts via upsert. Used when brand + operator (+ sandbox) is the durable protocol key for buyer-declared accounts (`require_operator_auth: false`). Sellers MAY echo a seller-assigned account_id, but they MUST continue accepting the natural-key AccountRef for every account provisioned this way.\n\n- **Settings-update mode** (`account` field carrying an [`AccountRef`](/schemas/core/account-ref.json)): targets an existing account by `account_id` (or by natural key for buyer-declared accounts). The seller updates the account's settable state (notification subscriptions, payment terms, billing entity refinements) — no provisioning side effects. Used for account_id namespaces only when the seller exposes this task for account settings; the account_id itself is discovered via `list_accounts` for upstream-managed namespaces or supplied out-of-band for seller-defined namespaces. Buyer-declared account sellers MAY also accept this mode for settings updates against accounts they previously provisioned.\n\nExactly one of the two key shapes is allowed per entry. Sellers that do not implement settings-update mode MUST return `UNSUPPORTED_PROVISIONING` on entries keyed by `account.account_id`; sellers that do not provision through sync_accounts MUST return `UNSUPPORTED_PROVISIONING` on entries keyed by the natural-key trio. Account-id namespace provisioning is out of scope unless a future explicit capability declares it.",
   "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,
@@ -26,11 +26,11 @@
         "description": "An advertiser account entry — either provisions/upserts a new account (natural key) or updates an existing one (AccountRef key).",
         "properties": {
           "account": {
-            "$ref": "/schemas/3.1.15/core/account-ref.json",
+            "$ref": "/schemas/3.1.20/core/account-ref.json",
             "description": "Settings-update key. When present, this entry targets an existing account by `account_id` (seller-owned account namespace) or natural key (buyer-declared account settings-update against a previously-provisioned account). Mutually exclusive with the flat `brand` + `operator` + `billing` provisioning trio. When `account` is present, the seller MUST NOT create a new account — entries that would otherwise trigger provisioning are rejected with `UNSUPPORTED_PROVISIONING`."
           },
           "brand": {
-            "$ref": "/schemas/3.1.15/core/brand-ref.json",
+            "$ref": "/schemas/3.1.20/core/brand-ref.json",
             "description": "Brand reference identifying the advertiser. Required for **provisioning mode**; MUST be absent in settings-update mode."
           },
           "operator": {
@@ -39,15 +39,15 @@
             "pattern": "^[a-z0-9]([a-z0-9-]*[a-z0-9])?(\\.[a-z0-9]([a-z0-9-]*[a-z0-9])?)*$"
           },
           "billing": {
-            "$ref": "/schemas/3.1.15/enums/billing-party.json",
+            "$ref": "/schemas/3.1.20/enums/billing-party.json",
             "description": "Who should be invoiced. Required for **provisioning mode**; MUST be absent in settings-update mode (billing is fixed at provisioning time and cannot be changed via settings-update)."
           },
           "billing_entity": {
-            "$ref": "/schemas/3.1.15/core/business-entity.json",
+            "$ref": "/schemas/3.1.20/core/business-entity.json",
             "description": "Business entity details for the party responsible for payment. The agent provides this so the seller has the legal name, tax IDs, address, and bank details needed for formal B2B invoicing. Permitted in both modes — sellers MAY accept refinements in settings-update mode (e.g., updated bank details)."
           },
           "payment_terms": {
-            "$ref": "/schemas/3.1.15/enums/payment-terms.json",
+            "$ref": "/schemas/3.1.20/enums/payment-terms.json",
             "description": "Payment terms for this account. The seller must either accept these terms or reject the account — terms are never silently remapped. When omitted, the seller applies its default terms. Permitted in both modes."
           },
           "sandbox": {
@@ -55,7 +55,7 @@
             "description": "When true, provision this as a sandbox account with no real platform calls or billing. Only applicable to buyer-declared accounts (require_operator_auth: false) in provisioning mode. For account-id namespaces, sandbox accounts are pre-existing test accounts discovered via list_accounts or supplied out-of-band."
           },
           "preferred_reporting_protocol": {
-            "$ref": "/schemas/3.1.15/enums/cloud-storage-protocol.json",
+            "$ref": "/schemas/3.1.20/enums/cloud-storage-protocol.json",
             "description": "Buyer's preferred cloud storage protocol for offline reporting delivery. The seller provisions the account's reporting_bucket using this protocol if supported. When omitted, the seller chooses from its supported offline_delivery_protocols. Only meaningful when the seller's reporting_delivery_methods includes 'offline'."
           },
           "notification_configs": {
@@ -64,7 +64,7 @@
             "items": {
               "allOf": [
                 {
-                  "$ref": "/schemas/3.1.15/core/notification-config.json"
+                  "$ref": "/schemas/3.1.20/core/notification-config.json"
                 },
                 {
                   "if": {
@@ -148,14 +148,14 @@
       "description": "When true, preview what would change without applying. Returns what would be created/updated/deactivated."
     },
     "push_notification_config": {
-      "$ref": "/schemas/3.1.15/core/push-notification-config.json",
+      "$ref": "/schemas/3.1.20/core/push-notification-config.json",
       "description": "Webhook for async notifications when account status changes (e.g., pending_approval transitions to active)."
     },
     "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/account/sync-accounts-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/account/sync-accounts-response.json",
+  "$id": "/schemas/3.1.20/account/sync-accounts-response.json",
   "title": "Sync Accounts Response",
   "description": "Response from account sync operation. Returns per-account results with status and billing, or operation-level errors on complete failure.",
   "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": [
@@ -34,7 +34,7 @@
                 "x-entity": "account"
               },
               "brand": {
-                "$ref": "/schemas/3.1.15/core/brand-ref.json",
+                "$ref": "/schemas/3.1.20/core/brand-ref.json",
                 "description": "Brand reference, echoed from the request"
               },
               "operator": {
@@ -68,15 +68,15 @@
                 "description": "Account status. active: ready for use. pending_approval: seller reviewing (credit, legal). rejected: seller declined the account request. payment_required: credit limit reached or funds depleted. suspended: was active, now paused. closed: was active, now terminated."
               },
               "billing": {
-                "$ref": "/schemas/3.1.15/enums/billing-party.json",
+                "$ref": "/schemas/3.1.20/enums/billing-party.json",
                 "description": "Who is invoiced on this account. Matches the requested billing model."
               },
               "billing_entity": {
-                "$ref": "/schemas/3.1.15/core/business-entity.json",
+                "$ref": "/schemas/3.1.20/core/business-entity.json",
                 "description": "Business entity details for the party responsible for payment, echoed from the request. Sellers MAY add fields the agent omitted (e.g., filling in registration_number from a credit check), but MUST NOT return data from a different entity. Bank details are omitted (write-only)."
               },
               "account_scope": {
-                "$ref": "/schemas/3.1.15/enums/account-scope.json"
+                "$ref": "/schemas/3.1.20/enums/account-scope.json"
               },
               "setup": {
                 "type": "object",
@@ -107,7 +107,7 @@
                 "description": "Rate card applied to this account"
               },
               "payment_terms": {
-                "$ref": "/schemas/3.1.15/enums/payment-terms.json",
+                "$ref": "/schemas/3.1.20/enums/payment-terms.json",
                 "description": "Payment terms agreed for this account. When the account is active, these are the binding terms for all invoices on this account."
               },
               "credit_limit": {
@@ -131,7 +131,7 @@
                 "type": "array",
                 "description": "Per-account errors (only present when action is 'failed')",
                 "items": {
-                  "$ref": "/schemas/3.1.15/core/error.json"
+                  "$ref": "/schemas/3.1.20/core/error.json"
                 }
               },
               "warnings": {
@@ -149,12 +149,12 @@
                 "type": "array",
                 "description": "Applied notification subscribers for this account after declarative replacement and activation-proof checks. Present on `created`, `updated`, and `unchanged` results when the buyer included `notification_configs` in the request or any persisted entries exist on the account. Entries are keyed by account-scoped `subscriber_id`; re-sending an existing `subscriber_id` replaces that subscriber's config rather than creating a duplicate. Only configs that the seller has persisted are echoed. `authentication.credentials` is omitted on every entry (write-only).",
                 "items": {
-                  "$ref": "/schemas/3.1.15/core/notification-config.json"
+                  "$ref": "/schemas/3.1.20/core/notification-config.json"
                 },
                 "maxItems": 16
               },
               "authorization": {
-                "$ref": "/schemas/3.1.15/core/account-authorization.json",
+                "$ref": "/schemas/3.1.20/core/account-authorization.json",
                 "description": "Optional. The caller's scope grant against this account after the sync operation. Vendor agents of any type (media-buy, signals, governance, creative, brand) that support scope introspection SHOULD populate this so callers can preempt RBAC errors rather than discovering scope by trial and error. Media-buy sales agents claiming the `attestation_verifier` standard scope MUST populate it. Present on `created`, `updated`, and `unchanged` results; omitted on `failed` results (where the account did not reach a usable state). Absence means the vendor agent does not advertise introspectable scope — callers MUST NOT infer access from absence."
               }
             },
@@ -168,10 +168,10 @@
           }
         },
         "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": [
@@ -193,15 +193,15 @@
           "type": "array",
           "description": "Operation-level errors (e.g., authentication failure, service unavailable)",
           "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/account/sync-governance-request.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/account/sync-governance-request.json",
+  "$id": "/schemas/3.1.20/account/sync-governance-request.json",
   "title": "Sync Governance Request",
   "description": "Sync the governance agent endpoint against specific accounts. The seller persists the governance agent and calls it for approval during media buy lifecycle events via check_governance. Uses replace semantics: each call replaces any previously synced agent on the specified accounts. The seller MUST verify that the authenticated agent has authority over each referenced account before persisting the governance agent.\n\nThe binding is **account-scoped, not plan-scoped**. Each account binds to exactly one governance agent, and that agent owns the lifecycle for every plan on the account — `plan_id` is threaded through `check_governance` calls so the agent can route internally, but governance registration does not vary per plan. Senders MUST NOT attempt to bind different governance agents to different plans on the same account; the wire offers no field for it and brand/seller implementations resolve the bound agent from the account alone.\n\nA plan is unitary — budget authority, delivery monitoring, and regulatory compliance are phases of the same evaluation (`purchase` / `modification` / `delivery` on check_governance), not specialisms held by different agents — so a single agent owns the full lifecycle. Buyers that need internal specialist review (e.g., a separate legal reviewer) compose that inside the governance agent, not at the registration layer. `governance_agents` is an array (not a scalar) because that is the shape 3.0 shipped with and existing senders MUST continue to work; the `maxItems: 1` constraint is load-bearing and not anticipated to relax. The single-agent rule is also baked into the wire below this layer (`protocol-envelope.governance_context` is singular), so loosening `maxItems` here would require a coordinated change across the envelope and every task that threads the context.",
   "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,
@@ -25,7 +25,7 @@
         "type": "object",
         "properties": {
           "account": {
-            "$ref": "/schemas/3.1.15/core/account-ref.json",
+            "$ref": "/schemas/3.1.20/core/account-ref.json",
             "description": "Account to sync governance agents for. Use account_id for account-id namespaces or brand + operator for buyer-declared accounts."
           },
           "governance_agents": {
@@ -47,7 +47,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
@@ -85,10 +85,10 @@
       "maxItems": 100
     },
     "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/account/sync-governance-response.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/account/sync-governance-response.json",
+  "$id": "/schemas/3.1.20/account/sync-governance-response.json",
   "title": "Sync Governance Response",
   "description": "Response from governance agent sync. Returns per-account results confirming sync, or operation-level errors on complete failure.",
   "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": [
@@ -25,7 +25,7 @@
             "type": "object",
             "properties": {
               "account": {
-                "$ref": "/schemas/3.1.15/core/account-ref.json",
+                "$ref": "/schemas/3.1.20/core/account-ref.json",
                 "description": "Account reference, echoed from request"
               },
               "status": {
@@ -61,7 +61,7 @@
                 "type": "array",
                 "description": "Per-account errors (only present when status is 'failed')",
                 "items": {
-                  "$ref": "/schemas/3.1.15/core/error.json"
+                  "$ref": "/schemas/3.1.20/core/error.json"
                 }
               }
             },
@@ -73,10 +73,10 @@
           }
         },
         "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": [
@@ -98,15 +98,15 @@
           "type": "array",
           "description": "Operation-level errors (e.g., authentication failure, service unavailable)",
           "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": [