@adcp/sdk 13.0.1 → 13.0.3

package/dist/lib/schemas-data/3.1/bundled/content-standards/list-content-standards-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/bundled/content-standards/list-content-standards-response.json",
+  "$id": "/schemas/3.1.20/bundled/content-standards/list-content-standards-response.json",
   "title": "List Content Standards Response",
   "description": "Response payload with list of content standards configurations",
   "type": "object",
@@ -28,7 +28,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.15/core/version-envelope.json"
+      "$id": "/schemas/3.1.20/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.15/core/context.json"
+          "$id": "/schemas/3.1.20/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.15/enums/task-status.json"
+          "$id": "/schemas/3.1.20/enums/task-status.json"
         },
         "message": {
           "type": "string",
@@ -216,7 +216,7 @@
             "message"
           ],
           "additionalProperties": true,
-          "$id": "/schemas/3.1.15/core/error.json"
+          "$id": "/schemas/3.1.20/core/error.json"
         },
         "push_notification_config": {
           "title": "Push Notification Config",
@@ -256,7 +256,7 @@
                       "Bearer",
                       "HMAC-SHA256"
                     ],
-                    "$id": "/schemas/3.1.15/enums/auth-scheme.json"
+                    "$id": "/schemas/3.1.20/enums/auth-scheme.json"
                   },
                   "minItems": 1,
                   "maxItems": 1
@@ -277,7 +277,7 @@
           "required": [
             "url"
           ],
-          "$id": "/schemas/3.1.15/core/push-notification-config.json"
+          "$id": "/schemas/3.1.20/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.15/core/protocol-envelope.json"
+      "$id": "/schemas/3.1.20/core/protocol-envelope.json"
     }
   ],
   "oneOf": [
@@ -521,7 +521,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.15/enums/policy-category.json"
+                      "$id": "/schemas/3.1.20/enums/policy-category.json"
                     },
                     "enforcement": {
                       "title": "Policy Enforcement Level",
@@ -537,7 +537,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.15/enums/policy-enforcement.json"
+                      "$id": "/schemas/3.1.20/enums/policy-enforcement.json"
                     },
                     "requires_human_review": {
                       "type": "boolean",
@@ -587,7 +587,7 @@
                           "creative",
                           "content_standards"
                         ],
-                        "$id": "/schemas/3.1.15/enums/governance-domain.json"
+                        "$id": "/schemas/3.1.20/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."
                     },
@@ -645,7 +645,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.15/core/ext.json"
+                      "$id": "/schemas/3.1.20/core/ext.json"
                     }
                   },
                   "required": [
@@ -725,7 +725,7 @@
                               "width"
                             ]
                           },
-                          "$id": "/schemas/3.1.15/core/format-id.json"
+                          "$id": "/schemas/3.1.20/core/format-id.json"
                         },
                         "url": {
                           "type": "string",
@@ -5050,10 +5050,10 @@
                           "additionalProperties": true
                         }
                       ],
-                      "$id": "/schemas/3.1.15/core/signal-pricing.json"
+                      "$id": "/schemas/3.1.20/core/signal-pricing.json"
                     }
                   ],
-                  "$id": "/schemas/3.1.15/core/vendor-pricing-option.json"
+                  "$id": "/schemas/3.1.20/core/vendor-pricing-option.json"
                 },
                 "minItems": 1
               },
@@ -5093,7 +5093,7 @@
             "has_more"
           ],
           "additionalProperties": false,
-          "$id": "/schemas/3.1.15/core/pagination-response.json"
+          "$id": "/schemas/3.1.20/core/pagination-response.json"
         },
         "context": {
           "title": "Context Object",
@@ -5396,7 +5396,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.15/enums/channels.json"
+      "$id": "/schemas/3.1.20/enums/channels.json"
     },
     "DigitalSourceType": {
       "title": "Digital Source Type",
@@ -5424,7 +5424,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.15/enums/digital-source-type.json"
+      "$id": "/schemas/3.1.20/enums/digital-source-type.json"
     },
     "EmbeddedProvenanceMethod": {
       "title": "Embedded Provenance Method",
@@ -5438,7 +5438,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.15/enums/embedded-provenance-method.json"
+      "$id": "/schemas/3.1.20/enums/embedded-provenance-method.json"
     },
     "WatermarkMediaType": {
       "title": "Watermark Media Type",
@@ -5456,7 +5456,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.15/enums/watermark-media-type.json"
+      "$id": "/schemas/3.1.20/enums/watermark-media-type.json"
     },
     "C2PAWatermarkAction": {
       "title": "C2PA Watermark Action",
@@ -5470,7 +5470,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.15/enums/c2pa-watermark-action.json"
+      "$id": "/schemas/3.1.20/enums/c2pa-watermark-action.json"
     },
     "DisclosurePersistence": {
       "title": "Disclosure Persistence",
@@ -5486,7 +5486,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.15/enums/disclosure-persistence.json"
+      "$id": "/schemas/3.1.20/enums/disclosure-persistence.json"
     },
     "DisclosurePosition": {
       "title": "Disclosure Position",
@@ -5502,11 +5502,11 @@
         "pre_roll",
         "companion"
       ],
-      "$id": "/schemas/3.1.15/enums/disclosure-position.json"
+      "$id": "/schemas/3.1.20/enums/disclosure-position.json"
     }
   },
   "_bundled": {
-    "generatedAt": "2026-08-16T19:12:16.523Z",
+    "generatedAt": "2026-09-02T12:43:39.252Z",
     "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/update-content-standards-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/bundled/content-standards/update-content-standards-request.json",
+  "$id": "/schemas/3.1.20/bundled/content-standards/update-content-standards-request.json",
   "title": "Update Content Standards Request",
   "description": "Request parameters for updating an existing content standards configuration. Creates a new version.",
   "type": "object",
@@ -28,7 +28,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.15/core/version-envelope.json"
+      "$id": "/schemas/3.1.20/core/version-envelope.json"
     }
   ],
   "x-mutates-state": true,
@@ -126,7 +126,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.15/enums/policy-category.json"
+            "$id": "/schemas/3.1.20/enums/policy-category.json"
           },
           "enforcement": {
             "title": "Policy Enforcement Level",
@@ -142,7 +142,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.15/enums/policy-enforcement.json"
+            "$id": "/schemas/3.1.20/enums/policy-enforcement.json"
           },
           "requires_human_review": {
             "type": "boolean",
@@ -192,7 +192,7 @@
                 "creative",
                 "content_standards"
               ],
-              "$id": "/schemas/3.1.15/enums/governance-domain.json"
+              "$id": "/schemas/3.1.20/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."
           },
@@ -250,7 +250,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.15/core/ext.json"
+            "$id": "/schemas/3.1.20/core/ext.json"
           }
         },
         "required": [
@@ -356,7 +356,7 @@
                         "width"
                       ]
                     },
-                    "$id": "/schemas/3.1.15/core/format-id.json"
+                    "$id": "/schemas/3.1.20/core/format-id.json"
                   },
                   "url": {
                     "type": "string",
@@ -4436,7 +4436,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.15/core/context.json"
+      "$id": "/schemas/3.1.20/core/context.json"
     },
     "ext": {
       "title": "Extension Object",
@@ -4591,7 +4591,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.15/enums/channels.json"
+      "$id": "/schemas/3.1.20/enums/channels.json"
     },
     "DigitalSourceType": {
       "title": "Digital Source Type",
@@ -4619,7 +4619,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.15/enums/digital-source-type.json"
+      "$id": "/schemas/3.1.20/enums/digital-source-type.json"
     },
     "EmbeddedProvenanceMethod": {
       "title": "Embedded Provenance Method",
@@ -4633,7 +4633,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.15/enums/embedded-provenance-method.json"
+      "$id": "/schemas/3.1.20/enums/embedded-provenance-method.json"
     },
     "WatermarkMediaType": {
       "title": "Watermark Media Type",
@@ -4651,7 +4651,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.15/enums/watermark-media-type.json"
+      "$id": "/schemas/3.1.20/enums/watermark-media-type.json"
     },
     "C2PAWatermarkAction": {
       "title": "C2PA Watermark Action",
@@ -4665,7 +4665,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.15/enums/c2pa-watermark-action.json"
+      "$id": "/schemas/3.1.20/enums/c2pa-watermark-action.json"
     },
     "DisclosurePersistence": {
       "title": "Disclosure Persistence",
@@ -4681,7 +4681,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.15/enums/disclosure-persistence.json"
+      "$id": "/schemas/3.1.20/enums/disclosure-persistence.json"
     },
     "DisclosurePosition": {
       "title": "Disclosure Position",
@@ -4697,11 +4697,11 @@
         "pre_roll",
         "companion"
       ],
-      "$id": "/schemas/3.1.15/enums/disclosure-position.json"
+      "$id": "/schemas/3.1.20/enums/disclosure-position.json"
     }
   },
   "_bundled": {
-    "generatedAt": "2026-08-16T19:12:16.532Z",
+    "generatedAt": "2026-09-02T12:43:39.259Z",
     "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/update-content-standards-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/bundled/content-standards/update-content-standards-response.json",
+  "$id": "/schemas/3.1.20/bundled/content-standards/update-content-standards-response.json",
   "title": "Update Content Standards Response",
   "description": "Response from updating a content standards configuration",
   "allOf": [
@@ -27,7 +27,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.15/core/version-envelope.json"
+      "$id": "/schemas/3.1.20/core/version-envelope.json"
     },
     {
       "title": "Protocol Envelope",
@@ -43,7 +43,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.15/core/context.json"
+          "$id": "/schemas/3.1.20/core/context.json"
         },
         "task_id": {
           "type": "string",
@@ -76,7 +76,7 @@
             "auth-required": "Task requires authentication to proceed",
             "unknown": "Task is in an unknown or indeterminate state"
           },
-          "$id": "/schemas/3.1.15/enums/task-status.json"
+          "$id": "/schemas/3.1.20/enums/task-status.json"
         },
         "message": {
           "type": "string",
@@ -215,7 +215,7 @@
             "message"
           ],
           "additionalProperties": true,
-          "$id": "/schemas/3.1.15/core/error.json"
+          "$id": "/schemas/3.1.20/core/error.json"
         },
         "push_notification_config": {
           "title": "Push Notification Config",
@@ -255,7 +255,7 @@
                       "Bearer",
                       "HMAC-SHA256"
                     ],
-                    "$id": "/schemas/3.1.15/enums/auth-scheme.json"
+                    "$id": "/schemas/3.1.20/enums/auth-scheme.json"
                   },
                   "minItems": 1,
                   "maxItems": 1
@@ -276,7 +276,7 @@
           "required": [
             "url"
           ],
-          "$id": "/schemas/3.1.15/core/push-notification-config.json"
+          "$id": "/schemas/3.1.20/core/push-notification-config.json"
         },
         "governance_context": {
           "type": "string",
@@ -426,7 +426,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.15/core/protocol-envelope.json"
+      "$id": "/schemas/3.1.20/core/protocol-envelope.json"
     }
   ],
   "oneOf": [
@@ -454,7 +454,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.15/core/ext.json"
+          "$id": "/schemas/3.1.20/core/ext.json"
         }
       },
       "required": [
@@ -627,7 +627,7 @@
   ],
   "properties": {},
   "_bundled": {
-    "generatedAt": "2026-08-16T19:12:16.534Z",
+    "generatedAt": "2026-09-02T12:43:39.262Z",
     "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/validate-content-delivery-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/bundled/content-standards/validate-content-delivery-request.json",
+  "$id": "/schemas/3.1.20/bundled/content-standards/validate-content-delivery-request.json",
   "title": "Validate Content Delivery Request",
   "description": "Request parameters for batch validating delivery records against content safety policies",
   "type": "object",
@@ -28,7 +28,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.15/core/version-envelope.json"
+      "$id": "/schemas/3.1.20/core/version-envelope.json"
     }
   ],
   "properties": {
@@ -119,7 +119,7 @@
                     "width"
                   ]
                 },
-                "$id": "/schemas/3.1.15/core/format-id.json"
+                "$id": "/schemas/3.1.20/core/format-id.json"
               },
               "url": {
                 "type": "string",
@@ -456,7 +456,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.15/core/ext.json"
+                                            "$id": "/schemas/3.1.20/core/ext.json"
                                           }
                                         },
                                         "additionalProperties": true
@@ -2155,7 +2155,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.15/core/context.json"
+      "$id": "/schemas/3.1.20/core/context.json"
     },
     "ext": {
       "title": "Extension Object",
@@ -2262,7 +2262,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.15/enums/digital-source-type.json"
+      "$id": "/schemas/3.1.20/enums/digital-source-type.json"
     },
     "EmbeddedProvenanceMethod": {
       "title": "Embedded Provenance Method",
@@ -2276,7 +2276,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.15/enums/embedded-provenance-method.json"
+      "$id": "/schemas/3.1.20/enums/embedded-provenance-method.json"
     },
     "WatermarkMediaType": {
       "title": "Watermark Media Type",
@@ -2294,7 +2294,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.15/enums/watermark-media-type.json"
+      "$id": "/schemas/3.1.20/enums/watermark-media-type.json"
     },
     "C2PAWatermarkAction": {
       "title": "C2PA Watermark Action",
@@ -2308,7 +2308,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.15/enums/c2pa-watermark-action.json"
+      "$id": "/schemas/3.1.20/enums/c2pa-watermark-action.json"
     },
     "DisclosurePersistence": {
       "title": "Disclosure Persistence",
@@ -2324,7 +2324,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.15/enums/disclosure-persistence.json"
+      "$id": "/schemas/3.1.20/enums/disclosure-persistence.json"
     },
     "DisclosurePosition": {
       "title": "Disclosure Position",
@@ -2340,11 +2340,11 @@
         "pre_roll",
         "companion"
       ],
-      "$id": "/schemas/3.1.15/enums/disclosure-position.json"
+      "$id": "/schemas/3.1.20/enums/disclosure-position.json"
     }
   },
   "_bundled": {
-    "generatedAt": "2026-08-16T19:12:16.537Z",
+    "generatedAt": "2026-09-02T12:43:39.265Z",
     "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/validate-content-delivery-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.15/bundled/content-standards/validate-content-delivery-response.json",
+  "$id": "/schemas/3.1.20/bundled/content-standards/validate-content-delivery-response.json",
   "title": "Validate Content Delivery Response",
   "description": "Response payload with per-record verdicts and optional feature breakdown",
   "type": "object",
@@ -28,7 +28,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.15/core/version-envelope.json"
+      "$id": "/schemas/3.1.20/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.15/core/context.json"
+          "$id": "/schemas/3.1.20/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.15/enums/task-status.json"
+          "$id": "/schemas/3.1.20/enums/task-status.json"
         },
         "message": {
           "type": "string",
@@ -216,7 +216,7 @@
             "message"
           ],
           "additionalProperties": true,
-          "$id": "/schemas/3.1.15/core/error.json"
+          "$id": "/schemas/3.1.20/core/error.json"
         },
         "push_notification_config": {
           "title": "Push Notification Config",
@@ -256,7 +256,7 @@
                       "Bearer",
                       "HMAC-SHA256"
                     ],
-                    "$id": "/schemas/3.1.15/enums/auth-scheme.json"
+                    "$id": "/schemas/3.1.20/enums/auth-scheme.json"
                   },
                   "minItems": 1,
                   "maxItems": 1
@@ -277,7 +277,7 @@
           "required": [
             "url"
           ],
-          "$id": "/schemas/3.1.15/core/push-notification-config.json"
+          "$id": "/schemas/3.1.20/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.15/core/protocol-envelope.json"
+      "$id": "/schemas/3.1.20/core/protocol-envelope.json"
     }
   ],
   "oneOf": [
@@ -477,7 +477,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.15/enums/binary-verdict.json"
+                "$id": "/schemas/3.1.20/enums/binary-verdict.json"
               },
               "features": {
                 "type": "array",
@@ -505,7 +505,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.15/enums/feature-check-status.json"
+                      "$id": "/schemas/3.1.20/enums/feature-check-status.json"
                     },
                     "policy_id": {
                       "type": "string",
@@ -547,7 +547,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.15/core/ext.json"
+          "$id": "/schemas/3.1.20/core/ext.json"
         }
       },
       "required": [
@@ -706,7 +706,7 @@
   ],
   "properties": {},
   "_bundled": {
-    "generatedAt": "2026-08-16T19:12:16.538Z",
+    "generatedAt": "2026-09-02T12:43:39.266Z",
     "note": "This is a bundled schema with all $ref resolved inline. For the modular version with references, use the parent directory."
   }
 }