npm - @adcp/sdk - Versions diffs - 13.1.2 → 13.1.4 - Mend

@adcp/sdk 13.1.2 → 13.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1135) hide show

package/dist/lib/schemas-data/3.1/bundled/content-standards/get-content-standards-response.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/content-standards/get-content-standards-response.json",
+  "$id": "/schemas/3.1.30/bundled/content-standards/get-content-standards-response.json",
   "title": "Get Content Standards Response",
   "description": "Response payload with 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"
     },
     {
       "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": [
@@ -519,7 +519,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",
@@ -535,7 +535,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",
@@ -585,7 +585,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."
                   },
@@ -643,7 +643,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": [
@@ -723,7 +723,7 @@
                             "width"
                           ]
                         },
-                        "$id": "/schemas/3.1.24/core/format-id.json"
+                        "$id": "/schemas/3.1.30/core/format-id.json"
                       },
                       "url": {
                         "type": "string",
@@ -5048,10 +5048,10 @@
                         "additionalProperties": true
                       }
                     ],
-                    "$id": "/schemas/3.1.24/core/signal-pricing.json"
+                    "$id": "/schemas/3.1.30/core/signal-pricing.json"
                   }
                 ],
-                "$id": "/schemas/3.1.24/core/vendor-pricing-option.json"
+                "$id": "/schemas/3.1.30/core/vendor-pricing-option.json"
               },
               "minItems": 1
             },
@@ -5366,7 +5366,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",
@@ -5394,7 +5394,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",
@@ -5408,7 +5408,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",
@@ -5426,7 +5426,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",
@@ -5440,7 +5440,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",
@@ -5456,7 +5456,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",
@@ -5472,11 +5472,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.895Z",
+    "generatedAt": "2026-10-28T15:35:14.233Z",
     "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-media-buy-artifacts-request.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/content-standards/get-media-buy-artifacts-request.json",
+  "$id": "/schemas/3.1.30/bundled/content-standards/get-media-buy-artifacts-request.json",
   "title": "Get Media Buy Artifacts Request",
   "description": "Request parameters for retrieving content artifacts from a media buy for validation",
   "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": {
@@ -75,7 +75,7 @@
                     "nike",
                     "pampers"
                   ],
-                  "$id": "/schemas/3.1.24/core/brand-id.json"
+                  "$id": "/schemas/3.1.30/core/brand-id.json"
                 },
                 "industries": {
                   "type": "array",
@@ -187,7 +187,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",
@@ -306,7 +306,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",
@@ -372,7 +372,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",
@@ -410,7 +410,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",
@@ -474,7 +474,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",
@@ -498,7 +498,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
@@ -508,7 +508,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
@@ -581,7 +581,7 @@
                             }
                           },
                           "additionalProperties": true,
-                          "$id": "/schemas/3.1.24/core/provenance.json"
+                          "$id": "/schemas/3.1.30/core/provenance.json"
                         }
                       },
                       "required": [
@@ -591,7 +591,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",
@@ -641,7 +641,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",
@@ -687,7 +687,7 @@
           "sandbox": true
         }
       ],
-      "$id": "/schemas/3.1.24/core/account-ref.json"
+      "$id": "/schemas/3.1.30/core/account-ref.json"
     },
     "media_buy_id": {
       "type": "string",
@@ -745,7 +745,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",
@@ -758,7 +758,7 @@
     "media_buy_id"
   ],
   "_bundled": {
-    "generatedAt": "2026-09-23T15:25:22.902Z",
+    "generatedAt": "2026-10-28T15:35:14.237Z",
     "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-media-buy-artifacts-response.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/content-standards/get-media-buy-artifacts-response.json",
+  "$id": "/schemas/3.1.30/bundled/content-standards/get-media-buy-artifacts-response.json",
   "title": "Get Media Buy Artifacts Response",
   "description": "Response containing content artifacts from a media buy for validation",
   "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": [
@@ -520,7 +520,7 @@
                         "width"
                       ]
                     },
-                    "$id": "/schemas/3.1.24/core/format-id.json"
+                    "$id": "/schemas/3.1.30/core/format-id.json"
                   },
                   "url": {
                     "type": "string",
@@ -857,7 +857,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
@@ -2592,7 +2592,7 @@
             "has_more"
           ],
           "additionalProperties": false,
-          "$id": "/schemas/3.1.24/core/pagination-response.json"
+          "$id": "/schemas/3.1.30/core/pagination-response.json"
         },
         "context": {
           "title": "Context Object",
@@ -2856,7 +2856,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",
@@ -2870,7 +2870,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",
@@ -2888,7 +2888,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",
@@ -2902,7 +2902,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",
@@ -2918,7 +2918,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",
@@ -2934,11 +2934,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.905Z",
+    "generatedAt": "2026-10-28T15:35:14.241Z",
     "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/list-content-standards-request.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/bundled/content-standards/list-content-standards-request.json",
+  "$id": "/schemas/3.1.30/bundled/content-standards/list-content-standards-request.json",
   "title": "List Content Standards Request",
   "description": "Request parameters for listing content standards configurations",
   "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": {
@@ -82,7 +82,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"
       },
       "minItems": 1,
       "description": "Filter by channel"
@@ -121,26 +121,26 @@
         }
       },
       "additionalProperties": false,
-      "$id": "/schemas/3.1.24/core/pagination-request.json"
+      "$id": "/schemas/3.1.30/core/pagination-request.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",
       "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,
   "_bundled": {
-    "generatedAt": "2026-09-23T15:25:22.908Z",
+    "generatedAt": "2026-10-28T15:35:14.242Z",
     "note": "This is a bundled schema with all $ref resolved inline. For the modular version with references, use the parent directory."
   }
 }