@adcp/sdk 13.1.2 → 13.1.4

package/dist/lib/schemas-data/3.1/bundled/media-buy/sync-catalogs-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/media-buy/sync-catalogs-request.json",
+  "$id": "/schemas/3.1.30/bundled/media-buy/sync-catalogs-request.json",
   "title": "Sync Catalogs Request",
   "description": "Request parameters for syncing catalog feeds with upsert semantics. Supports bulk operations across multiple catalog types (products, inventory, stores, promotions, offerings). Existing catalogs matched by catalog_id are updated, new ones are created. When catalogs is omitted, the call is discovery-only: returns all catalogs on the account without modification.",
   "type": "object",
@@ -28,7 +28,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.24/core/version-envelope.json"
+      "$id": "/schemas/3.1.30/core/version-envelope.json"
     }
   ],
   "x-mutates-state": true,
@@ -83,7 +83,7 @@
                     "nike",
                     "pampers"
                   ],
-                  "$id": "/schemas/3.1.24/core/brand-id.json"
+                  "$id": "/schemas/3.1.30/core/brand-id.json"
                 },
                 "industries": {
                   "type": "array",
@@ -195,7 +195,7 @@
                                 "human_edits": "Content augmented, corrected, or enhanced by humans using non-generative tools",
                                 "data_driven_media": "Assembled from structured data feeds (DCO templates, product catalogs, weather-triggered variants)"
                               },
-                              "$id": "/schemas/3.1.24/enums/digital-source-type.json"
+                              "$id": "/schemas/3.1.30/enums/digital-source-type.json"
                             },
                             "ai_tool": {
                               "type": "object",
@@ -314,7 +314,7 @@
                                       "manifest_wrapper": "A provenance manifest embedded in the file container per format-specific rules (e.g., JUMBF box in JPEG, C2PATextManifestWrapper in plaintext per C2PA Section A.7). The manifest travels with the file but is tied to the file's byte structure.",
                                       "provenance_markers": "Invisible markers embedded within the content stream that encode or reference a provenance record. Designed to survive reformatting, copy-paste, CMS ingestion, and ad-server transcoding that breaks file-level bindings."
                                     },
-                                    "$id": "/schemas/3.1.24/enums/embedded-provenance-method.json"
+                                    "$id": "/schemas/3.1.30/enums/embedded-provenance-method.json"
                                   },
                                   "standard": {
                                     "type": "string",
@@ -380,7 +380,7 @@
                                       "video": "Watermark applied to video content (e.g., per-frame image watermarking, temporal watermarking)",
                                       "text": "Watermark applied to text content (e.g., synonym substitution, structural modification)"
                                     },
-                                    "$id": "/schemas/3.1.24/enums/watermark-media-type.json"
+                                    "$id": "/schemas/3.1.30/enums/watermark-media-type.json"
                                   },
                                   "provider": {
                                     "type": "string",
@@ -418,7 +418,7 @@
                                       "c2pa.watermarked.bound": "Watermark linked to a C2PA manifest for this asset. The watermark and manifest are mutually reinforcing: the manifest references the watermark, and the watermark can be used to locate the manifest.",
                                       "c2pa.watermarked.unbound": "Watermark independent of any C2PA manifest. Applied before any provenance signing event (e.g., by the AI generator at creation time) or in pipelines where no manifest is present."
                                     },
-                                    "$id": "/schemas/3.1.24/enums/c2pa-watermark-action.json"
+                                    "$id": "/schemas/3.1.30/enums/c2pa-watermark-action.json"
                                   },
                                   "embedded_at": {
                                     "type": "string",
@@ -482,7 +482,7 @@
                                               "initial": "Disclosure must appear at the start of content for a minimum duration before it may be removed. Pair with min_duration_ms in render_guidance or creative brief to specify the required duration.",
                                               "flexible": "Disclosure presence is sufficient; placement timing and duration are at the publisher's discretion"
                                             },
-                                            "$id": "/schemas/3.1.24/enums/disclosure-persistence.json"
+                                            "$id": "/schemas/3.1.30/enums/disclosure-persistence.json"
                                           },
                                           "min_duration_ms": {
                                             "type": "integer",
@@ -506,7 +506,7 @@
                                                 "pre_roll",
                                                 "companion"
                                               ],
-                                              "$id": "/schemas/3.1.24/enums/disclosure-position.json"
+                                              "$id": "/schemas/3.1.30/enums/disclosure-position.json"
                                             },
                                             "minItems": 1,
                                             "uniqueItems": true
@@ -516,7 +516,7 @@
                                             "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
                                             "type": "object",
                                             "additionalProperties": true,
-                                            "$id": "/schemas/3.1.24/core/ext.json"
+                                            "$id": "/schemas/3.1.30/core/ext.json"
                                           }
                                         },
                                         "additionalProperties": true
@@ -589,7 +589,7 @@
                             }
                           },
                           "additionalProperties": true,
-                          "$id": "/schemas/3.1.24/core/provenance.json"
+                          "$id": "/schemas/3.1.30/core/provenance.json"
                         }
                       },
                       "required": [
@@ -599,7 +599,7 @@
                         "height"
                       ],
                       "additionalProperties": true,
-                      "$id": "/schemas/3.1.24/core/assets/image-asset.json"
+                      "$id": "/schemas/3.1.30/core/assets/image-asset.json"
                     },
                     "colors": {
                       "type": "object",
@@ -649,7 +649,7 @@
                   "domain": "acme-corp.com"
                 }
               ],
-              "$id": "/schemas/3.1.24/core/brand-ref.json"
+              "$id": "/schemas/3.1.30/core/brand-ref.json"
             },
             "operator": {
               "type": "string",
@@ -695,7 +695,7 @@
           "sandbox": true
         }
       ],
-      "$id": "/schemas/3.1.24/core/account-ref.json"
+      "$id": "/schemas/3.1.30/core/account-ref.json"
     },
     "catalogs": {
       "type": "array",
@@ -733,7 +733,7 @@
               "destination",
               "app"
             ],
-            "$id": "/schemas/3.1.24/enums/catalog-type.json"
+            "$id": "/schemas/3.1.30/enums/catalog-type.json"
           },
           "url": {
             "type": "string",
@@ -764,7 +764,7 @@
               "openai_product_feed": "OpenAI Commerce product feed for ChatGPT shopping — a GMC-derived dialect adding ChatGPT-specific eligibility flags (is_eligible_search / is_eligible_checkout / is_eligible_ads). Spec: https://developers.openai.com/commerce/specs/file-upload/products",
               "custom": "A feed whose shape is not one of the named formats above. The buyer MUST supply feed_field_mappings to normalize it to the AdCP catalog item schema."
             },
-            "$id": "/schemas/3.1.24/enums/feed-format.json"
+            "$id": "/schemas/3.1.30/enums/feed-format.json"
           },
           "update_frequency": {
             "title": "Update Frequency",
@@ -776,7 +776,7 @@
               "daily",
               "weekly"
             ],
-            "$id": "/schemas/3.1.24/enums/update-frequency.json"
+            "$id": "/schemas/3.1.30/enums/update-frequency.json"
           },
           "items": {
             "type": "array",
@@ -892,7 +892,7 @@
                 "submit_application": "User submitted an application (loan, job, etc.)",
                 "custom": "Custom event type (specify in custom_event_name)"
               },
-              "$id": "/schemas/3.1.24/enums/event-type.json"
+              "$id": "/schemas/3.1.30/enums/event-type.json"
             },
             "minItems": 1,
             "uniqueItems": true
@@ -915,7 +915,7 @@
               "destination_id",
               "app_id"
             ],
-            "$id": "/schemas/3.1.24/enums/content-id-type.json"
+            "$id": "/schemas/3.1.30/enums/content-id-type.json"
           },
           "feed_field_mappings": {
             "type": "array",
@@ -1064,7 +1064,7 @@
                   }
                 }
               ],
-              "$id": "/schemas/3.1.24/core/catalog-field-mapping.json"
+              "$id": "/schemas/3.1.30/core/catalog-field-mapping.json"
             },
             "minItems": 1
           }
@@ -1194,7 +1194,7 @@
             }
           }
         ],
-        "$id": "/schemas/3.1.24/core/catalog.json"
+        "$id": "/schemas/3.1.30/core/catalog.json"
       },
       "minItems": 1,
       "maxItems": 50
@@ -1227,7 +1227,7 @@
         "strict",
         "lenient"
       ],
-      "$id": "/schemas/3.1.24/enums/validation-mode.json",
+      "$id": "/schemas/3.1.30/enums/validation-mode.json",
       "default": "strict"
     },
     "push_notification_config": {
@@ -1268,7 +1268,7 @@
                   "Bearer",
                   "HMAC-SHA256"
                 ],
-                "$id": "/schemas/3.1.24/enums/auth-scheme.json"
+                "$id": "/schemas/3.1.30/enums/auth-scheme.json"
               },
               "minItems": 1,
               "maxItems": 1
@@ -1289,14 +1289,14 @@
       "required": [
         "url"
       ],
-      "$id": "/schemas/3.1.24/core/push-notification-config.json"
+      "$id": "/schemas/3.1.30/core/push-notification-config.json"
     },
     "context": {
       "title": "Context Object",
       "description": "Opaque correlation data that is echoed unchanged in responses. Used for internal tracking, UI session IDs, trace IDs, and other caller-specific identifiers that don't affect protocol behavior. Context data is never parsed by AdCP agents - it's simply preserved and returned.",
       "type": "object",
       "additionalProperties": true,
-      "$id": "/schemas/3.1.24/core/context.json"
+      "$id": "/schemas/3.1.30/core/context.json"
     },
     "ext": {
       "title": "Extension Object",
@@ -1397,7 +1397,7 @@
     }
   ],
   "_bundled": {
-    "generatedAt": "2026-09-23T15:25:23.931Z",
+    "generatedAt": "2026-10-28T15:35:14.980Z",
     "note": "This is a bundled schema with all $ref resolved inline. For the modular version with references, use the parent directory."
   }
 }

package/dist/lib/schemas-data/3.1/bundled/media-buy/sync-catalogs-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/media-buy/sync-catalogs-response.json",
+  "$id": "/schemas/3.1.30/bundled/media-buy/sync-catalogs-response.json",
   "title": "Sync Catalogs Response",
   "description": "Response from catalog sync operation. Exactly one of three shapes: (1) synchronous success — per-catalog results in the catalogs array (best-effort processing, may include per-catalog failures); (2) terminal failure — errors array with no catalogs processed; (3) submitted task envelope — status 'submitted' with task_id when the whole operation is queued (e.g., batch catalog ingestion and deduplication). The submitted branch MAY carry advisory errors for non-blocking warnings; terminal failures belong in the error branch. These three shapes are mutually exclusive — a response has exactly one. Platforms may approve, reject, or flag individual items within each catalog (similar to Google Merchant Center product review).",
   "type": "object",
@@ -28,7 +28,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.24/core/version-envelope.json"
+      "$id": "/schemas/3.1.30/core/version-envelope.json"
     },
     {
       "title": "Protocol Envelope",
@@ -44,7 +44,7 @@
           "description": "Per-request opaque caller-supplied correlation object echoed unchanged in the response. Used for buyer-side tracking (UI session IDs, trace IDs, custom metadata) that the agent MUST preserve byte-for-byte without parsing. Distinct from `context_id` (server-managed session identifier) — `context` is caller-owned echo, `context_id` is server-owned session scope. Both MAY appear on the same response.\n\n**Relationship to per-task body-level `context` declarations.** Many task request/response schemas (147 as of 3.1) already declare a body-level `context` field that `$ref`s `/schemas/core/context.json` at the body root. Under the flat-on-the-wire MCP serialization (see `notes` below), envelope-level `context` and body-level `context` occupy the same key on the response root — they are NOT separate fields, they MUST share the same value, and they MUST both `$ref` `core/context.json`. The envelope declaration is **authoritative** for the schema definition; per-task body declarations are mirrors retained for tooling reasons (SDK codegen completeness, per-task validation against the response schema in isolation). Future versions MAY drop body-level `context` declarations from per-task schemas; conformance does not require either declaration to be present, only that the wire value `$ref`s `core/context.json`.",
           "type": "object",
           "additionalProperties": true,
-          "$id": "/schemas/3.1.24/core/context.json"
+          "$id": "/schemas/3.1.30/core/context.json"
         },
         "task_id": {
           "type": "string",
@@ -77,7 +77,7 @@
             "auth-required": "Task requires authentication to proceed",
             "unknown": "Task is in an unknown or indeterminate state"
           },
-          "$id": "/schemas/3.1.24/enums/task-status.json"
+          "$id": "/schemas/3.1.30/enums/task-status.json"
         },
         "message": {
           "type": "string",
@@ -216,7 +216,7 @@
             "message"
           ],
           "additionalProperties": true,
-          "$id": "/schemas/3.1.24/core/error.json"
+          "$id": "/schemas/3.1.30/core/error.json"
         },
         "push_notification_config": {
           "title": "Push Notification Config",
@@ -256,7 +256,7 @@
                       "Bearer",
                       "HMAC-SHA256"
                     ],
-                    "$id": "/schemas/3.1.24/enums/auth-scheme.json"
+                    "$id": "/schemas/3.1.30/enums/auth-scheme.json"
                   },
                   "minItems": 1,
                   "maxItems": 1
@@ -277,7 +277,7 @@
           "required": [
             "url"
           ],
-          "$id": "/schemas/3.1.24/core/push-notification-config.json"
+          "$id": "/schemas/3.1.30/core/push-notification-config.json"
         },
         "governance_context": {
           "type": "string",
@@ -427,7 +427,7 @@
         "`status` is REQUIRED on the conceptual envelope across all transports. On MCP and REST it appears as a sibling field at the JSON root (or `structuredContent` root for MCP); on A2A the canonical carrier is `task.status.state`, which maps 1:1 to this `status` value — receivers MUST extract A2A's `task.status.state` into the in-memory envelope `status` per the canonical extraction algorithm. The schema-level `required: [status]` enforces the post-extraction in-memory shape; the transport-native form satisfies the requirement on each wire. `payload` remains intentionally NOT required — it is a documentary grouping construct, never a required wire field. See `mcp-guide.mdx` and `a2a-guide.mdx` for the wire-level patterns receivers MUST implement.",
         "Receivers MUST handle absence of an envelope field (e.g., `replayed` omitted) as the field's documented default — see each field's `default` clause."
       ],
-      "$id": "/schemas/3.1.24/core/protocol-envelope.json"
+      "$id": "/schemas/3.1.30/core/protocol-envelope.json"
     }
   ],
   "oneOf": [
@@ -462,7 +462,7 @@
                   "failed",
                   "deleted"
                 ],
-                "$id": "/schemas/3.1.24/enums/catalog-action.json"
+                "$id": "/schemas/3.1.30/enums/catalog-action.json"
               },
               "platform_id": {
                 "type": "string",
@@ -516,7 +516,7 @@
                         "warning": "Item is approved and serving but has issues worth fixing (e.g., low-quality image, missing optional fields). The item remains eligible for delivery.",
                         "withdrawn": "Seller has removed the item from active use — inventory pulled, policy enforcement, or other seller-initiated reasons not covered by 'rejected'. Distinct lifecycle from 'rejected': no buyer-side resubmit path. Sellers MUST surface a corresponding impairment on any active media buy that targets a package referencing this catalog item. Sellers MAY return the item to 'approved' on re-publication."
                       },
-                      "$id": "/schemas/3.1.24/enums/catalog-item-status.json"
+                      "$id": "/schemas/3.1.30/enums/catalog-item-status.json"
                     },
                     "reasons": {
                       "type": "array",
@@ -731,7 +731,7 @@
           "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
           "type": "object",
           "additionalProperties": true,
-          "$id": "/schemas/3.1.24/core/ext.json"
+          "$id": "/schemas/3.1.30/core/ext.json"
         }
       },
       "required": [
@@ -1100,7 +1100,7 @@
   ],
   "properties": {},
   "_bundled": {
-    "generatedAt": "2026-09-23T15:25:23.933Z",
+    "generatedAt": "2026-10-28T15:35:14.981Z",
     "note": "This is a bundled schema with all $ref resolved inline. For the modular version with references, use the parent directory."
   }
 }

package/dist/lib/schemas-data/3.1/bundled/media-buy/sync-event-sources-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/media-buy/sync-event-sources-request.json",
+  "$id": "/schemas/3.1.30/bundled/media-buy/sync-event-sources-request.json",
   "title": "Sync Event Sources Request",
   "description": "Request parameters for configuring event sources on an account with upsert semantics. Existing event sources matched by event_source_id are updated, new ones are created. When delete_missing is true, buyer-managed event sources on the account not in this request are removed. When event_sources is omitted, the call is discovery-only: it returns all event sources on the account without modification. The response always includes both synced and seller-managed event sources for full visibility.",
   "type": "object",
@@ -28,7 +28,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.24/core/version-envelope.json"
+      "$id": "/schemas/3.1.30/core/version-envelope.json"
     }
   ],
   "x-mutates-state": true,
@@ -83,7 +83,7 @@
                     "nike",
                     "pampers"
                   ],
-                  "$id": "/schemas/3.1.24/core/brand-id.json"
+                  "$id": "/schemas/3.1.30/core/brand-id.json"
                 },
                 "industries": {
                   "type": "array",
@@ -195,7 +195,7 @@
                                 "human_edits": "Content augmented, corrected, or enhanced by humans using non-generative tools",
                                 "data_driven_media": "Assembled from structured data feeds (DCO templates, product catalogs, weather-triggered variants)"
                               },
-                              "$id": "/schemas/3.1.24/enums/digital-source-type.json"
+                              "$id": "/schemas/3.1.30/enums/digital-source-type.json"
                             },
                             "ai_tool": {
                               "type": "object",
@@ -314,7 +314,7 @@
                                       "manifest_wrapper": "A provenance manifest embedded in the file container per format-specific rules (e.g., JUMBF box in JPEG, C2PATextManifestWrapper in plaintext per C2PA Section A.7). The manifest travels with the file but is tied to the file's byte structure.",
                                       "provenance_markers": "Invisible markers embedded within the content stream that encode or reference a provenance record. Designed to survive reformatting, copy-paste, CMS ingestion, and ad-server transcoding that breaks file-level bindings."
                                     },
-                                    "$id": "/schemas/3.1.24/enums/embedded-provenance-method.json"
+                                    "$id": "/schemas/3.1.30/enums/embedded-provenance-method.json"
                                   },
                                   "standard": {
                                     "type": "string",
@@ -380,7 +380,7 @@
                                       "video": "Watermark applied to video content (e.g., per-frame image watermarking, temporal watermarking)",
                                       "text": "Watermark applied to text content (e.g., synonym substitution, structural modification)"
                                     },
-                                    "$id": "/schemas/3.1.24/enums/watermark-media-type.json"
+                                    "$id": "/schemas/3.1.30/enums/watermark-media-type.json"
                                   },
                                   "provider": {
                                     "type": "string",
@@ -418,7 +418,7 @@
                                       "c2pa.watermarked.bound": "Watermark linked to a C2PA manifest for this asset. The watermark and manifest are mutually reinforcing: the manifest references the watermark, and the watermark can be used to locate the manifest.",
                                       "c2pa.watermarked.unbound": "Watermark independent of any C2PA manifest. Applied before any provenance signing event (e.g., by the AI generator at creation time) or in pipelines where no manifest is present."
                                     },
-                                    "$id": "/schemas/3.1.24/enums/c2pa-watermark-action.json"
+                                    "$id": "/schemas/3.1.30/enums/c2pa-watermark-action.json"
                                   },
                                   "embedded_at": {
                                     "type": "string",
@@ -482,7 +482,7 @@
                                               "initial": "Disclosure must appear at the start of content for a minimum duration before it may be removed. Pair with min_duration_ms in render_guidance or creative brief to specify the required duration.",
                                               "flexible": "Disclosure presence is sufficient; placement timing and duration are at the publisher's discretion"
                                             },
-                                            "$id": "/schemas/3.1.24/enums/disclosure-persistence.json"
+                                            "$id": "/schemas/3.1.30/enums/disclosure-persistence.json"
                                           },
                                           "min_duration_ms": {
                                             "type": "integer",
@@ -506,7 +506,7 @@
                                                 "pre_roll",
                                                 "companion"
                                               ],
-                                              "$id": "/schemas/3.1.24/enums/disclosure-position.json"
+                                              "$id": "/schemas/3.1.30/enums/disclosure-position.json"
                                             },
                                             "minItems": 1,
                                             "uniqueItems": true
@@ -516,7 +516,7 @@
                                             "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
                                             "type": "object",
                                             "additionalProperties": true,
-                                            "$id": "/schemas/3.1.24/core/ext.json"
+                                            "$id": "/schemas/3.1.30/core/ext.json"
                                           }
                                         },
                                         "additionalProperties": true
@@ -589,7 +589,7 @@
                             }
                           },
                           "additionalProperties": true,
-                          "$id": "/schemas/3.1.24/core/provenance.json"
+                          "$id": "/schemas/3.1.30/core/provenance.json"
                         }
                       },
                       "required": [
@@ -599,7 +599,7 @@
                         "height"
                       ],
                       "additionalProperties": true,
-                      "$id": "/schemas/3.1.24/core/assets/image-asset.json"
+                      "$id": "/schemas/3.1.30/core/assets/image-asset.json"
                     },
                     "colors": {
                       "type": "object",
@@ -649,7 +649,7 @@
                   "domain": "acme-corp.com"
                 }
               ],
-              "$id": "/schemas/3.1.24/core/brand-ref.json"
+              "$id": "/schemas/3.1.30/core/brand-ref.json"
             },
             "operator": {
               "type": "string",
@@ -695,7 +695,7 @@
           "sandbox": true
         }
       ],
-      "$id": "/schemas/3.1.24/core/account-ref.json"
+      "$id": "/schemas/3.1.30/core/account-ref.json"
     },
     "event_sources": {
       "type": "array",
@@ -786,7 +786,7 @@
                 "submit_application": "User submitted an application (loan, job, etc.)",
                 "custom": "Custom event type (specify in custom_event_name)"
               },
-              "$id": "/schemas/3.1.24/enums/event-type.json"
+              "$id": "/schemas/3.1.30/enums/event-type.json"
             },
             "minItems": 1
           },
@@ -816,7 +816,7 @@
               "system_generated": "Event generated by an automated system",
               "other": "Other source (specify in ext)"
             },
-            "$id": "/schemas/3.1.24/enums/action-source.json"
+            "$id": "/schemas/3.1.30/enums/action-source.json"
           },
           "allowed_domains": {
             "type": "array",
@@ -889,7 +889,7 @@
               "category"
             ],
             "additionalProperties": true,
-            "$id": "/schemas/3.1.24/core/event-surface.json"
+            "$id": "/schemas/3.1.30/core/event-surface.json"
           }
         },
         "required": [
@@ -908,7 +908,7 @@
       "description": "Opaque correlation data that is echoed unchanged in responses. Used for internal tracking, UI session IDs, trace IDs, and other caller-specific identifiers that don't affect protocol behavior. Context data is never parsed by AdCP agents - it's simply preserved and returned.",
       "type": "object",
       "additionalProperties": true,
-      "$id": "/schemas/3.1.24/core/context.json"
+      "$id": "/schemas/3.1.30/core/context.json"
     },
     "ext": {
       "title": "Extension Object",
@@ -923,7 +923,7 @@
   ],
   "additionalProperties": true,
   "_bundled": {
-    "generatedAt": "2026-09-23T15:25:23.934Z",
+    "generatedAt": "2026-10-28T15:35:14.982Z",
     "note": "This is a bundled schema with all $ref resolved inline. For the modular version with references, use the parent directory."
   }
 }

package/dist/lib/schemas-data/3.1/bundled/media-buy/sync-event-sources-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/media-buy/sync-event-sources-response.json",
+  "$id": "/schemas/3.1.30/bundled/media-buy/sync-event-sources-response.json",
   "title": "Sync Event Sources Response",
   "description": "Response from event source sync operation. Returns either per-source results OR operation-level errors.",
   "type": "object",
@@ -28,7 +28,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.24/core/version-envelope.json"
+      "$id": "/schemas/3.1.30/core/version-envelope.json"
     },
     {
       "title": "Protocol Envelope",
@@ -44,7 +44,7 @@
           "description": "Per-request opaque caller-supplied correlation object echoed unchanged in the response. Used for buyer-side tracking (UI session IDs, trace IDs, custom metadata) that the agent MUST preserve byte-for-byte without parsing. Distinct from `context_id` (server-managed session identifier) — `context` is caller-owned echo, `context_id` is server-owned session scope. Both MAY appear on the same response.\n\n**Relationship to per-task body-level `context` declarations.** Many task request/response schemas (147 as of 3.1) already declare a body-level `context` field that `$ref`s `/schemas/core/context.json` at the body root. Under the flat-on-the-wire MCP serialization (see `notes` below), envelope-level `context` and body-level `context` occupy the same key on the response root — they are NOT separate fields, they MUST share the same value, and they MUST both `$ref` `core/context.json`. The envelope declaration is **authoritative** for the schema definition; per-task body declarations are mirrors retained for tooling reasons (SDK codegen completeness, per-task validation against the response schema in isolation). Future versions MAY drop body-level `context` declarations from per-task schemas; conformance does not require either declaration to be present, only that the wire value `$ref`s `core/context.json`.",
           "type": "object",
           "additionalProperties": true,
-          "$id": "/schemas/3.1.24/core/context.json"
+          "$id": "/schemas/3.1.30/core/context.json"
         },
         "task_id": {
           "type": "string",
@@ -77,7 +77,7 @@
             "auth-required": "Task requires authentication to proceed",
             "unknown": "Task is in an unknown or indeterminate state"
           },
-          "$id": "/schemas/3.1.24/enums/task-status.json"
+          "$id": "/schemas/3.1.30/enums/task-status.json"
         },
         "message": {
           "type": "string",
@@ -216,7 +216,7 @@
             "message"
           ],
           "additionalProperties": true,
-          "$id": "/schemas/3.1.24/core/error.json"
+          "$id": "/schemas/3.1.30/core/error.json"
         },
         "push_notification_config": {
           "title": "Push Notification Config",
@@ -256,7 +256,7 @@
                       "Bearer",
                       "HMAC-SHA256"
                     ],
-                    "$id": "/schemas/3.1.24/enums/auth-scheme.json"
+                    "$id": "/schemas/3.1.30/enums/auth-scheme.json"
                   },
                   "minItems": 1,
                   "maxItems": 1
@@ -277,7 +277,7 @@
           "required": [
             "url"
           ],
-          "$id": "/schemas/3.1.24/core/push-notification-config.json"
+          "$id": "/schemas/3.1.30/core/push-notification-config.json"
         },
         "governance_context": {
           "type": "string",
@@ -427,7 +427,7 @@
         "`status` is REQUIRED on the conceptual envelope across all transports. On MCP and REST it appears as a sibling field at the JSON root (or `structuredContent` root for MCP); on A2A the canonical carrier is `task.status.state`, which maps 1:1 to this `status` value — receivers MUST extract A2A's `task.status.state` into the in-memory envelope `status` per the canonical extraction algorithm. The schema-level `required: [status]` enforces the post-extraction in-memory shape; the transport-native form satisfies the requirement on each wire. `payload` remains intentionally NOT required — it is a documentary grouping construct, never a required wire field. See `mcp-guide.mdx` and `a2a-guide.mdx` for the wire-level patterns receivers MUST implement.",
         "Receivers MUST handle absence of an envelope field (e.g., `replayed` omitted) as the field's documented default — see each field's `default` clause."
       ],
-      "$id": "/schemas/3.1.24/core/protocol-envelope.json"
+      "$id": "/schemas/3.1.30/core/protocol-envelope.json"
     }
   ],
   "oneOf": [
@@ -528,7 +528,7 @@
                     "submit_application": "User submitted an application (loan, job, etc.)",
                     "custom": "Custom event type (specify in custom_event_name)"
                   },
-                  "$id": "/schemas/3.1.24/enums/event-type.json"
+                  "$id": "/schemas/3.1.30/enums/event-type.json"
                 }
               },
               "action_source": {
@@ -557,7 +557,7 @@
                   "system_generated": "Event generated by an automated system",
                   "other": "Other source (specify in ext)"
                 },
-                "$id": "/schemas/3.1.24/enums/action-source.json"
+                "$id": "/schemas/3.1.30/enums/action-source.json"
               },
               "surface": {
                 "title": "Event Surface",
@@ -616,14 +616,14 @@
                     "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
                     "type": "object",
                     "additionalProperties": true,
-                    "$id": "/schemas/3.1.24/core/ext.json"
+                    "$id": "/schemas/3.1.30/core/ext.json"
                   }
                 },
                 "required": [
                   "category"
                 ],
                 "additionalProperties": true,
-                "$id": "/schemas/3.1.24/core/event-surface.json"
+                "$id": "/schemas/3.1.30/core/event-surface.json"
               },
               "managed_by": {
                 "type": "string",
@@ -690,7 +690,7 @@
                       "good": "Meets quality thresholds for most optimization goals",
                       "excellent": "Exceeds quality thresholds across all dimensions"
                     },
-                    "$id": "/schemas/3.1.24/enums/assessment-status.json"
+                    "$id": "/schemas/3.1.30/enums/assessment-status.json"
                   },
                   "detail": {
                     "type": "object",
@@ -765,7 +765,7 @@
                         "message"
                       ],
                       "additionalProperties": true,
-                      "$id": "/schemas/3.1.24/core/diagnostic-issue.json"
+                      "$id": "/schemas/3.1.30/core/diagnostic-issue.json"
                     }
                   }
                 },
@@ -773,7 +773,7 @@
                   "status"
                 ],
                 "additionalProperties": true,
-                "$id": "/schemas/3.1.24/core/event-source-health.json"
+                "$id": "/schemas/3.1.30/core/event-source-health.json"
               },
               "errors": {
                 "type": "array",
@@ -1113,7 +1113,7 @@
   ],
   "properties": {},
   "_bundled": {
-    "generatedAt": "2026-09-23T15:25:23.936Z",
+    "generatedAt": "2026-10-28T15:35:14.983Z",
     "note": "This is a bundled schema with all $ref resolved inline. For the modular version with references, use the parent directory."
   }
 }