@adcp/sdk 16.4.0 → 16.6.0

package/dist/lib/schemas-data/3.2/core/reporting-coverage.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-coverage.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-coverage.json",
   "title": "Reporting Coverage",
   "x-status": "experimental",
   "description": "Exact reporting-support denominator for one offering at one evaluation boundary. Coverage is independent of freshness, finality, and delivery health. It prevents a covered subset from being represented as a complete media-buy or campaign total.",

package/dist/lib/schemas-data/3.2/core/reporting-dataset-share-destination.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-dataset-share-destination.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-dataset-share-destination.json",
   "title": "Reporting Dataset Share Destination",
   "x-status": "experimental",
   "description": "Recipient configuration for a producer-hosted reporting share. The caller either references an existing seller-issued immutable recipient/destination generation or asks the seller to provision one for the named recipient. A destination_ref is owned by the stable authenticated principal's relationship with this seller and may be reused across accounts; each account delivery configuration separately authorizes disclosure of its feed and scope. Changing proof-bound recipient coordinates or the accepted delivery contract produces a new destination_ref. No bearer profile, token, private key, password, or other credential may appear here.",

package/dist/lib/schemas-data/3.2/core/reporting-delivery-capabilities.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-capabilities.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-capabilities.json",
   "title": "Reporting Delivery Capabilities",
   "x-status": "experimental",
   "description": "Reliable Reporting status and durable delivery support, advertised in three tiers over one data model. Core (supported: true) is the required tier: obligations, revisions, post-official adjustments, fixed RFC 8785/JCS revision-binding digests, the five health states, and get_reporting_status seller status. During the published migration window, sellers may additionally advertise sync_reporting_status consumer status over ordinary task transport; it becomes part of required Core only in the next eligible minor after the notice window. Core has no destination, materialization, bespoke webhook, or Managed external-materialization canonicalization machinery. managed_delivery adds file/dataset-share/warehouse delivery and materializations. Reconciled Billing adds canonical digests and consumer receipts for immutable billing-purpose reporting evidence/control totals only; it does not create, approve, modify, or settle invoices, calculate taxes/FX, authorize accounting entries, transfer funds, or determine legal payment obligations. Each offerings entry is an atomic supported combination; buyers MUST NOT construct an unsupported cross-product. Presence requires media_buy.reporting_delivery in experimental_features; RFC 9421 webhook signing is required only when readiness_notification, status_notification, or ledger_notification is declared. Polling get_media_buy_delivery remains the compatibility baseline when this block is absent.",
@@ -66,7 +66,7 @@
     "offerings": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-offering.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-offering.json"
       },
       "minItems": 1,
       "description": "Atomic supported feed/profile/schedule/finality/method combinations. offering_id values MUST be unique."
@@ -110,7 +110,7 @@
     "reliability_statistics": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-reliability-statistics.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-reliability-statistics.json"
       },
       "description": "Optional evidence-scoped observed performance for advertised offerings. offering_id values MUST be unique and name offerings in this capability block.",
       "uniqueItems": true

package/dist/lib/schemas-data/3.2/core/reporting-delivery-config-state.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-config-state.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-config-state.json",
   "title": "Reporting Delivery Configuration State",
   "x-status": "experimental",
   "description": "Seller-resolved state for one caller/account-owned immutable reporting delivery configuration generation. It echoes the secret-free desired configuration and adds the durable binding and setup result. The seller MUST verify that the authenticated caller may disclose the selected feeds and media-buy scope to the recipient before readiness. A setup URL is an authenticated UI/API entry point, not a bearer credential: agents MUST NOT auto-fetch it, preview it, or treat its content as instructions; it MUST use HTTPS, have no userinfo, token, or signed credential, and use an origin controlled by the seller or named provider.",
@@ -21,7 +21,7 @@
   },
   "properties": {
     "configuration": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-config.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-config.json"
     },
     "state": {
       "$ref": "#/definitions/ReportingDeliveryConfigLifecycleState"
@@ -56,7 +56,7 @@
       "description": "End of historical access to a producer-hosted share/resource for a still-authorized principal after voluntary deactivation. Inapplicable to data already written into a buyer-owned destination."
     },
     "current_coverage": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-coverage.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-coverage.json",
       "description": "Current effective product/package coverage for the selected offering and resolved account. This setup-time view may change as media buys or provider capabilities change; each period obligation later freezes its own authoritative coverage."
     },
     "setup": {
@@ -97,7 +97,7 @@
     "issues": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-status-issue.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-status-issue.json"
       },
       "minItems": 1
     }

package/dist/lib/schemas-data/3.2/core/reporting-delivery-config.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-config.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-config.json",
   "title": "Reporting Delivery Configuration",
   "x-status": "experimental",
   "description": "Desired durable reporting delivery for one account. Entries are owned by (authenticated caller, account) and keyed by (delivery_config_id, delivery_config_version). The generation's feed, report definition, profile, scope, coverage requirement, finality, schedule, method, and immutable destination generation are fixed; only lifecycle intent (`active` and `revocation_effective_at`) may change without a new generation. Sellers reject a reused version with different immutable content. sync_accounts replacement semantics apply only to the calling principal's set. Omission leaves that set unchanged; [] deactivates that caller's set and stops new publication without affecting another caller. Sellers implementing this schema MUST advertise media_buy.reporting_delivery in experimental_features.",
@@ -33,7 +33,7 @@
       "description": "Whether new reporting obligations should use this configuration. Inactive configurations remain visible for historical resolution."
     },
     "feed_purpose": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-offering.json#/definitions/ReportingFeedPurpose"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-offering.json#/definitions/ReportingFeedPurpose"
     },
     "report_definition_id": {
       "type": "string",
@@ -61,7 +61,7 @@
         "media_buy_ids": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-coverage.json#/definitions/ReportingMediaBuyId"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-coverage.json#/definitions/ReportingMediaBuyId"
           },
           "minItems": 1,
           "uniqueItems": true
@@ -80,11 +80,11 @@
       "description": "Whether every package in the resolved media-buy scope must support the exact selected offering. full fails closed when any package is unsupported or unknown. allow_partial permits publication only for the explicitly covered package denominator; every revision and status response still exposes partial coverage and MUST NOT present covered-subset totals as whole-buy totals."
     },
     "required_finality": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/reporting-finality.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/reporting-finality.json",
       "description": "Finality the durable path must ultimately provide. Snapshot delivery may still precede an official requirement."
     },
     "reconciliation_mode": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-reconciliation-mode.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-reconciliation-mode.json",
       "description": "Whether producer-side delivery evidence is sufficient or the selected consumer must submit an authenticated matching receipt. A seller-authoritative billing feed MUST use consumer_receipt."
     },
     "authoritative_party": {
@@ -97,10 +97,10 @@
       "description": "Reserved: which party's count of this feed is authoritative. seller (the default, and the only value any 3.2 seller accepts) means the seller produces every revision and the consumer may only attest to what it consumed. consumer is reserved for the buyer-deposited billing revision task scoped to a later minor; until that task exists sellers MUST reject it with UNSUPPORTED_FEATURE. Reserving the field now keeps a future buyer-basis billing feed additive instead of breaking the billing-feed constraints. See https://github.com/adcontextprotocol/adcp/issues/7440."
     },
     "schedule": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-schedule.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-schedule.json"
     },
     "method": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-method.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-method.json"
     },
     "revocation_effective_at": {
       "type": "string",

package/dist/lib/schemas-data/3.2/core/reporting-delivery-method.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-method.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-method.json",
   "title": "Reporting Delivery Method",
   "x-status": "experimental",
   "description": "Provider-neutral durable reporting delivery method. The caller may request protocol-managed provisioning or reuse an existing seller-issued binding. Transport names are open so new platforms do not require an AdCP enum change. Credentials, bearer profiles, and private keys MUST NOT appear. Sellers implementing this schema MUST advertise media_buy.reporting_delivery in experimental_features.",
@@ -38,7 +38,7 @@
           "$ref": "#/definitions/ReportingOrchestration"
         },
         "destination": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-write-destination.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-write-destination.json"
         },
         "format": {
           "type": "string",
@@ -81,7 +81,7 @@
           "$ref": "#/definitions/ReportingOrchestration"
         },
         "destination": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-dataset-share-destination.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-dataset-share-destination.json"
         }
       },
       "required": [
@@ -112,7 +112,7 @@
           "$ref": "#/definitions/ReportingOrchestration"
         },
         "destination": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-write-destination.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-write-destination.json"
         }
       },
       "required": [

package/dist/lib/schemas-data/3.2/core/reporting-delivery-offering-id.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-offering-id.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-offering-id.json",
   "title": "Reporting Delivery Offering ID",
   "description": "Identifier of one seller-advertised managed reporting-delivery offering, matching get_adcp_capabilities.media_buy.reporting_delivery.offerings[].offering_id. Shared by the legacy and canonical product reporting capabilities.",
   "type": "string",

package/dist/lib/schemas-data/3.2/core/reporting-delivery-offering.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-offering.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-offering.json",
   "title": "Reporting Delivery Offering",
   "x-status": "experimental",
   "description": "One atomic combination a seller can honor. Buyers MUST NOT form a cross-product from separate capability arrays; each installed configuration selects one offering_id and values within that offering. A Core API-delivered offering requires no Managed external-materialization canonicalization code or contract, but every resulting revision still carries the fixed RFC 8785/JCS revision-binding canonicalization and digest.",
@@ -102,7 +102,7 @@
         "primary_keys": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-canonicalization-contract.json#/definitions/ReportingPrimaryKey"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-canonicalization-contract.json#/definitions/ReportingPrimaryKey"
           },
           "minItems": 1,
           "uniqueItems": true
@@ -146,20 +146,20 @@
       "additionalProperties": false
     },
     "schedule": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-schedule-offering.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-schedule-offering.json",
       "description": "Period and availability SLA this offering can honor. For example, PT1H with snapshot finality explicitly advertises hourly provisional snapshots; a separate P1D official offering advertises daily finalized reporting."
     },
     "supported_finality": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/reporting-finality.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/reporting-finality.json"
       },
       "minItems": 1,
       "uniqueItems": true,
       "description": "Finality classes available under this exact report definition, schedule, and delivery method. snapshot is an explicit provisional capability, not inferred from poll frequency. Use separate atomic offerings when snapshot and official schedules or methods differ."
     },
     "reconciliation_mode": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-reconciliation-mode.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-reconciliation-mode.json",
       "description": "Receipt contract included in this atomic offering. Billing offerings MUST require consumer_receipt."
     },
     "method": {
@@ -176,7 +176,7 @@
           "pattern": "^[a-z][a-z0-9_.-]*$"
         },
         "orchestration": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-method.json#/definitions/ReportingOrchestration"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-method.json#/definitions/ReportingOrchestration"
         },
         "destination_modes": {
           "type": "array",
@@ -242,7 +242,7 @@
               "maxLength": 512
             },
             "cloud": {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-dataset-share-destination.json#/definitions/ReportingCloud"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-dataset-share-destination.json#/definitions/ReportingCloud"
             },
             "region": {
               "type": "string",
@@ -267,7 +267,7 @@
         "reader_compatibility": {
           "type": "array",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-resource.json#/definitions/ReportingReaderCompatibilityItem"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-resource.json#/definitions/ReportingReaderCompatibilityItem"
           },
           "uniqueItems": true
         }

package/dist/lib/schemas-data/3.2/core/reporting-delivery-ready-webhook.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-ready-webhook.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-ready-webhook.json",
   "title": "Reporting Delivery Ready Webhook",
   "x-status": "experimental",
   "description": "Compact account-anchored readiness doorbell registered through sync_accounts notification_configs using reporting.delivery_ready. Managed-delivery tier only: it names a materialization at a destination, so Core (API-delivered) configurations never fire it — Core consumers subscribe to reporting.status_changed and poll get_reporting_status. The named revision/materialization MUST already be observable through the intended consumer path. Transport retries are deduplicated by (authenticated sender, idempotency_key); downstream ingestion is deduplicated independently by reporting_revision_id and reporting_materialization_id. Ordering is unconstrained and receivers repair through authenticated get_reporting_status. The event MUST be signed using the advertised AdCP webhook-signing profile and MUST NOT contain rows, object lists, signed URLs, activation URLs, credentials, or access tokens.",
@@ -72,7 +72,7 @@
       ]
     },
     "finality": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/reporting-finality.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/reporting-finality.json"
     },
     "data_through": {
       "type": [
@@ -82,7 +82,7 @@
       "format": "date-time"
     },
     "feed_purpose": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-offering.json#/definitions/ReportingFeedPurpose"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-offering.json#/definitions/ReportingFeedPurpose"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/core/reporting-file-compression.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-file-compression.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-file-compression.json",
   "title": "Reporting File Compression",
   "x-status": "experimental",
   "description": "Physical compression applied to each data object listed by a reporting file manifest.",

package/dist/lib/schemas-data/3.2/core/reporting-file-entry.json

@@ -1,16 +1,16 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-file-entry.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-file-entry.json",
   "title": "Reporting File Entry",
   "x-status": "experimental",
   "description": "One immutable data object committed by a reporting file manifest.",
   "type": "object",
   "properties": {
     "object_ref": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-file-object-ref.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-file-object-ref.json"
     },
     "native_version_ref": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-native-version-ref.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-native-version-ref.json"
     },
     "size_bytes": {
       "type": "integer",

package/dist/lib/schemas-data/3.2/core/reporting-file-manifest.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-file-manifest.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-file-manifest.json",
   "title": "Reporting File Manifest",
   "x-status": "experimental",
   "description": "Normative manifest for one completed file-transfer materialization. Producers write every data object first and publish this manifest last. Its appearance is the commit point: consumers MUST ignore unlisted objects and MUST NOT process the materialization before a digest-valid complete manifest is visible.",
@@ -69,12 +69,12 @@
       ]
     },
     "compression": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-file-compression.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-file-compression.json"
     },
     "files": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-file-entry.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-file-entry.json"
       },
       "minItems": 1
     },
@@ -89,7 +89,7 @@
     "control_totals": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-control-total.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-control-total.json"
       },
       "uniqueItems": true
     },

package/dist/lib/schemas-data/3.2/core/reporting-file-object-ref.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-file-object-ref.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-file-object-ref.json",
   "title": "Reporting File Object Reference",
   "x-status": "experimental",
   "description": "Credential-free, destination-relative reference to one reporting data object. For an object store, this is the decoded object key relative to the configured destination, not an absolute URI and not a URI with a version query parameter. Providers URI-encode this value only when constructing their own storage request. The 1024-character limit accommodates an S3 object key of up to 1024 UTF-8 bytes because every Unicode character occupies at least one UTF-8 byte; JSON Schema maxLength counts characters rather than bytes.",

package/dist/lib/schemas-data/3.2/core/reporting-ledger-changed-webhook.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-ledger-changed-webhook.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-ledger-changed-webhook.json",
   "title": "Reporting Ledger Changed Webhook",
   "x-status": "experimental",
   "description": "Optional account-anchored invalidation fired for every newly committed reporting revision or post-official adjustment, whether or not health changes. Valid in every reporting tier. Receivers repair from their own durable changes_after checkpoint through get_reporting_status; this event is never the source of truth.",
@@ -61,7 +61,7 @@
       "x-entity": "reporting_revision"
     },
     "finality": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/reporting-finality.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/reporting-finality.json"
     },
     "reporting_adjustment_id": {
       "type": "string",
@@ -78,7 +78,7 @@
       "x-entity": "reporting_revision"
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.2/core/reporting-materialization.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-materialization.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-materialization.json",
   "title": "Reporting Materialization",
   "x-status": "experimental",
   "description": "One attempt to expose an immutable reporting revision through a configured durable delivery method. Automated retry creates a new materialization and attempt number while preserving reporting_revision_id. available is a verified producer-hosted pull/share claim; delivered is a verified recipient/destination claim. Existing per-buy inline reporting remains on its existing data API and is outside this v1 managed ledger.",
@@ -48,7 +48,7 @@
       "description": "Immutable caller-owned destination generation selected by the account-authorized obligation. It may be reused by the same caller across other independently authorized accounts."
     },
     "feed_purpose": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-offering.json#/definitions/ReportingFeedPurpose"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-offering.json#/definitions/ReportingFeedPurpose"
     },
     "method": {
       "type": "string",
@@ -95,10 +95,10 @@
       "description": "Stable safe failure classification. MUST NOT include credentials or provider response bodies."
     },
     "resource": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-resource.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-resource.json"
     },
     "verification": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-verification.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-verification.json"
     },
     "created_at": {
       "type": "string",

package/dist/lib/schemas-data/3.2/core/reporting-native-version-ref.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-native-version-ref.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-native-version-ref.json",
   "title": "Reporting Native Version Reference",
   "x-status": "experimental",
   "description": "Credential-free, decoded provider-native immutable version reference, such as an S3 VersionId, GCS generation, table version, transaction, snapshot, manifest generation, job, or run. This is not URI-encoded or concatenated into an object_ref; URI-encode it only when constructing a provider request. The 1024-character limit accommodates a provider value of up to 1024 UTF-8 bytes because every Unicode character occupies at least one UTF-8 byte; JSON Schema maxLength counts characters rather than bytes.",

package/dist/lib/schemas-data/3.2/core/reporting-obligation.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-obligation.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-obligation.json",
   "title": "Reporting Obligation",
   "x-status": "experimental",
   "description": "Period-level status joining what reporting was expected to any produced immutable revisions and delivery materializations. An obligation exists before its first revision or webhook, making missing-first-report detection possible. All nested revisions and materializations MUST match this obligation's authenticated caller/account, configuration generation, report definition, feed, period, and scope.",
@@ -32,7 +32,7 @@
       "x-entity": "reporting_definition"
     },
     "feed_purpose": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-delivery-offering.json#/definitions/ReportingFeedPurpose"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-delivery-offering.json#/definitions/ReportingFeedPurpose"
     },
     "reporting_profile": {
       "type": "string",
@@ -47,7 +47,7 @@
     "media_buy_ids": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-coverage.json#/definitions/ReportingMediaBuyId"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-coverage.json#/definitions/ReportingMediaBuyId"
       },
       "uniqueItems": true,
       "description": "Exact frozen media-buy denominator resolved for this period, including buys with zero rows. An empty array is the definitive zero-buy set; omission is never used to mean all, empty, or unknown."
@@ -58,7 +58,7 @@
       "description": "Instant at which the configured scope was resolved and frozen for this obligation. For all_media_buys, include every caller-authorized account media buy whose effective flight overlaps the half-open period and was known by this cutoff. Later-created or backdated buys do not rewrite this obligation."
     },
     "coverage": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-coverage.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-coverage.json",
       "description": "Immutable effective coverage of the exact selected offering at this period boundary. Delivery health is evaluated separately over the covered denominator."
     },
     "period": {
@@ -89,7 +89,7 @@
       "format": "date-time"
     },
     "schedule": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-schedule.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-schedule.json",
       "description": "Resolved immutable schedule generation that created this obligation."
     },
     "destination_ref": {
@@ -100,10 +100,10 @@
       "description": "Immutable caller-owned destination generation selected by this account-authorized obligation. The account/configuration join—not possession of this reusable reference—authorizes disclosure. Present when and only when the obligation’s configuration selects a managed-delivery offering; Core (API-delivered) obligations omit every destination and materialization field."
     },
     "required_finality": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/reporting-finality.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/reporting-finality.json"
     },
     "reconciliation_mode": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-reconciliation-mode.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-reconciliation-mode.json"
     },
     "reconciliation_status": {
       "type": "string",
@@ -116,7 +116,7 @@
       "description": "Consumer agreement state for the current required revision. A later superseding revision returns a receipt-required obligation to pending until that revision is accepted."
     },
     "health": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/reporting-health.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/reporting-health.json"
     },
     "production_status": {
       "type": "string",
@@ -189,7 +189,7 @@
     "issues": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-status-issue.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-status-issue.json"
       }
     },
     "resource_retained_until": {

package/dist/lib/schemas-data/3.2/core/reporting-receipt.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-receipt.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-receipt.json",
   "title": "Reporting Receipt",
   "x-status": "experimental",
   "description": "Authenticated consumer evidence for one materialization. A receipt closes the knowledge gap between producer availability and consumer reconciliation. Buyer and governance consumers submit independently; neither consumer's receipt implies acceptance by another principal.",
@@ -50,7 +50,7 @@
       ]
     },
     "verification_profile": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-verification-profile.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-verification-profile.json"
     },
     "observed_row_count": {
       "type": "integer",
@@ -59,19 +59,19 @@
     "observed_control_totals": {
       "type": "array",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-control-total.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-control-total.json"
       },
       "uniqueItems": true
     },
     "observed_canonical_content_digest": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-canonical-content-digest.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-canonical-content-digest.json"
     },
     "observed_manifest_sha256": {
       "type": "string",
       "pattern": "^[A-Fa-f0-9]{64}$"
     },
     "observed_native_version_ref": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-native-version-ref.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-native-version-ref.json"
     },
     "consumer_commit_ref": {
       "type": "string",

package/dist/lib/schemas-data/3.2/core/reporting-reconciliation-mode.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-reconciliation-mode.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-reconciliation-mode.json",
   "title": "Reporting Reconciliation Mode",
   "x-status": "experimental",
   "description": "Whether producer delivery evidence is sufficient or an authenticated consumer receipt is required.",

package/dist/lib/schemas-data/3.2/core/reporting-reliability-statistics.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-reliability-statistics.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-reliability-statistics.json",
   "title": "Reporting Reliability Statistics",
   "x-status": "experimental",
   "description": "Observed, evidence-scoped reliability for one atomic reporting offering. Counts are supplied with percentiles so buyers can compare a short, consistently met SLA with a long nominal SLA and can see how often official reports require later adjustments.",

package/dist/lib/schemas-data/3.2/core/reporting-report-definition.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-report-definition.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-report-definition.json",
   "title": "Reporting Report Definition",
   "x-status": "experimental",
   "description": "Immutable, inspectable semantic contract for how a reporting feed is produced and finalized. Its exact bytes are pinned by report_definition_sha256.",

package/dist/lib/schemas-data/3.2/core/reporting-resource.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-resource.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-resource.json",
   "title": "Reporting Resource",
   "x-status": "experimental",
   "description": "Secret-free authenticated descriptor for an exact reporting materialization. The descriptor MUST select immutable bytes or a provider-native immutable snapshot/version so an exact older revision never resolves to mutable latest state. Callers resolve access through the previously validated caller/account-bound destination/share binding, never from credentials embedded here. No field, including future extensions, may contain credentials, signed URLs, bearer material, or private keys.",
@@ -39,7 +39,7 @@
       "description": "Non-secret provider-native object, relation, or share identifier. MUST NOT contain an activation URL, signed URL, bearer token, password, private key, or embedded credential."
     },
     "native_version_ref": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-native-version-ref.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-native-version-ref.json"
     },
     "manifest_version": {
       "type": "string",