@adcp/sdk 13.1.3 → 13.1.4

package/dist/lib/schemas-data/3.1/bundled/content-standards/calibrate-content-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/content-standards/calibrate-content-request.json",
+  "$id": "/schemas/3.1.30/bundled/content-standards/calibrate-content-request.json",
   "title": "Calibrate Content Request",
   "description": "Request parameters for evaluating content during calibration. Multi-turn dialogue is handled at the protocol layer via contextId.",
   "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,
@@ -99,7 +99,7 @@
               "width"
             ]
           },
-          "$id": "/schemas/3.1.24/core/format-id.json"
+          "$id": "/schemas/3.1.30/core/format-id.json"
         },
         "url": {
           "type": "string",
@@ -436,7 +436,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
@@ -2100,7 +2100,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",
@@ -2208,7 +2208,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"
     },
     "EmbeddedProvenanceMethod": {
       "title": "Embedded Provenance Method",
@@ -2222,7 +2222,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"
     },
     "WatermarkMediaType": {
       "title": "Watermark Media Type",
@@ -2240,7 +2240,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"
     },
     "C2PAWatermarkAction": {
       "title": "C2PA Watermark Action",
@@ -2254,7 +2254,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"
     },
     "DisclosurePersistence": {
       "title": "Disclosure Persistence",
@@ -2270,7 +2270,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"
     },
     "DisclosurePosition": {
       "title": "Disclosure Position",
@@ -2286,11 +2286,11 @@
         "pre_roll",
         "companion"
       ],
-      "$id": "/schemas/3.1.24/enums/disclosure-position.json"
+      "$id": "/schemas/3.1.30/enums/disclosure-position.json"
     }
   },
   "_bundled": {
-    "generatedAt": "2026-09-23T15:25:22.850Z",
+    "generatedAt": "2026-10-28T15:35:14.209Z",
     "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/content-standards/calibrate-content-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/content-standards/calibrate-content-response.json",
+  "$id": "/schemas/3.1.30/bundled/content-standards/calibrate-content-response.json",
   "title": "Calibrate Content Response",
   "description": "Response payload with verdict and detailed explanations for collaborative calibration",
   "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": [
@@ -447,7 +447,7 @@
             "pass": "The evaluated record meets all applicable content standards",
             "fail": "The evaluated record failed one or more content standard checks"
           },
-          "$id": "/schemas/3.1.24/enums/binary-verdict.json"
+          "$id": "/schemas/3.1.30/enums/binary-verdict.json"
         },
         "confidence": {
           "type": "number",
@@ -485,7 +485,7 @@
                   "warning": "Feature is within tolerance but approaching a threshold — informational, not blocking",
                   "unevaluated": "Feature was not assessed in this evaluation run (e.g., required data not present)"
                 },
-                "$id": "/schemas/3.1.24/enums/feature-check-status.json"
+                "$id": "/schemas/3.1.30/enums/feature-check-status.json"
               },
               "policy_id": {
                 "type": "string",
@@ -520,7 +520,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": [
@@ -678,7 +678,7 @@
   ],
   "properties": {},
   "_bundled": {
-    "generatedAt": "2026-09-23T15:25:22.853Z",
+    "generatedAt": "2026-10-28T15:35:14.210Z",
     "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/content-standards/create-content-standards-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/content-standards/create-content-standards-request.json",
+  "$id": "/schemas/3.1.30/bundled/content-standards/create-content-standards-request.json",
   "title": "Create Content Standards Request",
   "description": "Request parameters for creating a new content standards configuration",
   "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,
@@ -125,7 +125,7 @@
               "regulation": "Legal requirement with jurisdiction scope. Violations have legal consequences. Enforcement is hard (must).",
               "standard": "Industry best practice, voluntary but recommended. Protects brand value and campaign effectiveness. Enforcement is soft (should)."
             },
-            "$id": "/schemas/3.1.24/enums/policy-category.json"
+            "$id": "/schemas/3.1.30/enums/policy-category.json"
           },
           "enforcement": {
             "title": "Policy Enforcement Level",
@@ -141,7 +141,7 @@
               "should": "Best practice. Governance agents warn on violations but do not block.",
               "may": "Recommendation. Governance agents log for informational purposes only."
             },
-            "$id": "/schemas/3.1.24/enums/policy-enforcement.json"
+            "$id": "/schemas/3.1.30/enums/policy-enforcement.json"
           },
           "requires_human_review": {
             "type": "boolean",
@@ -191,7 +191,7 @@
                 "creative",
                 "content_standards"
               ],
-              "$id": "/schemas/3.1.24/enums/governance-domain.json"
+              "$id": "/schemas/3.1.30/enums/governance-domain.json"
             },
             "description": "Governance sub-domains this policy applies to. Determines which types of governance agents can declare registry:{policy_id} features. For example, a policy with domains [\"creative\", \"property\"] can be declared as a feature by both creative and property governance agents."
           },
@@ -249,7 +249,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": [
@@ -355,7 +355,7 @@
                         "width"
                       ]
                     },
-                    "$id": "/schemas/3.1.24/core/format-id.json"
+                    "$id": "/schemas/3.1.30/core/format-id.json"
                   },
                   "url": {
                     "type": "string",
@@ -4442,7 +4442,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",
@@ -4602,7 +4602,7 @@
         "product_placement": "Product placement, branded content, and sponsorship integrations",
         "sponsored_intelligence": "Sponsored Intelligence — advertising within AI assistants, AI search, and generative AI experiences via the reversed data flow"
       },
-      "$id": "/schemas/3.1.24/enums/channels.json"
+      "$id": "/schemas/3.1.30/enums/channels.json"
     },
     "DigitalSourceType": {
       "title": "Digital Source Type",
@@ -4630,7 +4630,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"
     },
     "EmbeddedProvenanceMethod": {
       "title": "Embedded Provenance Method",
@@ -4644,7 +4644,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"
     },
     "WatermarkMediaType": {
       "title": "Watermark Media Type",
@@ -4662,7 +4662,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"
     },
     "C2PAWatermarkAction": {
       "title": "C2PA Watermark Action",
@@ -4676,7 +4676,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"
     },
     "DisclosurePersistence": {
       "title": "Disclosure Persistence",
@@ -4692,7 +4692,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"
     },
     "DisclosurePosition": {
       "title": "Disclosure Position",
@@ -4708,11 +4708,11 @@
         "pre_roll",
         "companion"
       ],
-      "$id": "/schemas/3.1.24/enums/disclosure-position.json"
+      "$id": "/schemas/3.1.30/enums/disclosure-position.json"
     }
   },
   "_bundled": {
-    "generatedAt": "2026-09-23T15:25:22.872Z",
+    "generatedAt": "2026-10-28T15:35:14.221Z",
     "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/content-standards/create-content-standards-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/content-standards/create-content-standards-response.json",
+  "$id": "/schemas/3.1.30/bundled/content-standards/create-content-standards-response.json",
   "title": "Create Content Standards Response",
   "description": "Response payload for creating a content standards configuration",
   "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": [
@@ -450,7 +450,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": [
@@ -612,7 +612,7 @@
   ],
   "properties": {},
   "_bundled": {
-    "generatedAt": "2026-09-23T15:25:22.879Z",
+    "generatedAt": "2026-10-28T15:35:14.226Z",
     "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/content-standards/get-content-standards-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/content-standards/get-content-standards-request.json",
+  "$id": "/schemas/3.1.30/bundled/content-standards/get-content-standards-request.json",
   "title": "Get Content Standards Request",
   "description": "Request parameters for retrieving content safety policies",
   "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"
     }
   ],
   "properties": {
@@ -41,21 +41,21 @@
       "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",
       "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": [
     "standards_id"
   ],
   "_bundled": {
-    "generatedAt": "2026-09-23T15:25:22.880Z",
+    "generatedAt": "2026-10-28T15:35:14.226Z",
     "note": "This is a bundled schema with all $ref resolved inline. For the modular version with references, use the parent directory."
   }
 }