@adcp/sdk 16.3.0 → 16.5.0

package/dist/lib/schemas-data/3.2/core/product.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/product.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/product.json",
   "title": "Product",
   "description": "Represents available advertising inventory",
   "type": "object",
@@ -24,7 +24,7 @@
       "items": {
         "allOf": [
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/publisher-property-selector.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/publisher-property-selector.json"
           },
           {
             "not": {
@@ -41,16 +41,17 @@
       "type": "array",
       "description": "Advertising channels this product is sold as. Products inherit from their properties' supported_channels but may narrow the scope. For example, a product covering YouTube properties might be sold as ['ctv'] even though those properties support ['olv', 'social', 'ctv'].",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/channels.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/channels.json"
       },
       "uniqueItems": true
     },
     "format_ids": {
       "type": "array",
       "deprecated": true,
+      "x-removed-in": "4.0.0",
       "description": "Deprecated in AdCP 3.2; removed in AdCP 4.0. Legacy named-format compatibility path. Products MUST carry `format_ids`, `format_options`, or both during the 3.x migration window. New products MUST author canonical `format_options[]`; sellers MAY additionally project those declarations to `format_ids` for legacy buyers. When both fields are present they MUST describe the same underlying formats, and buyers MUST prefer `format_options`. Do not author a new product from `format_ids` alone.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/format-id.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/format-id.json"
       }
     },
     "format_options": {
@@ -58,7 +59,7 @@
       "minItems": 1,
       "description": "Canonical format-option path: one or more inline format declarations the product accepts. Each element narrows a canonical format with parameters, slots, platform_extensions, and optional locale_policy. New 3.2 products MUST carry format_options; a seller MAY additionally project the same declarations to deprecated format_ids for older 3.x peers. A declaration carrying locale_policy is canonical-only because legacy format_ids cannot preserve locale eligibility; no product or placement format_id may project to an effective locale-constrained option.\n\nWhen placements are published, product-level format_options are the union of formats deliverable somewhere in the product and the upper bound for every placement. A placement's effective accepted set is the intersection of every applicable layer: (1) the product format_options; (2) the product placement's inline format_options, when present; and (3) for kind publisher_ref, the named publisher's adagents.json catalog narrowing. Resolve layer 3 by locating the matching placements[] entry: use its format_options when present, resolving bare format_option_id references against that same file's top-level formats[]; otherwise use top-level formats[] applicable to the placement's property_ids/property_tags. An omitted optional layer is unconstrained, but an unresolved publisher placement or format-option reference MUST fail closed. A publisher-referenced placement without inline product format_options therefore does NOT inherit the full product union when the publisher catalog supplies narrower placement or property-scoped acceptance.\n\nMatch publisher-declared options by {publisher_domain, format_option_id}, match product-local options by format_option_id when publisher_domain is omitted, and otherwise match declarations with the same format_kind whose narrower parameters satisfy the broader declaration. A product- or placement-level declaration MUST NOT introduce a format outside the product upper bound. Locale policy follows the same intersection. If the product locale policy is absent, a placement may introduce any concrete policy as a narrowing of an unconstrained option; when both are present, every placement range must be contained by a product range under RFC 4647 Basic Filtering. Locale eligibility is checked independently for every placement where an assignment may serve.\n\nFor a product or package containing multiple included placements, a single creative intended for every placement MUST lie in the intersection of every selected placement's effective set. Distinct per-placement creatives MAY use the union, but the selected creative set MUST cover every included placement; uncovered inventory MUST be rejected or refined, never silently omitted. If a product spans multiple publishers but omits placements[], there is no public routing key for per-placement creatives: its format_options MUST therefore be the common intersection accepted across every selected publisher/property scope. A seller that needs a union of publisher-specific formats MUST publish placements[] with publisher-scoped identities and narrowing. Commercial terms such as price, floor, availability, and deal eligibility are product facts, not format parameters.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/product-format-declaration.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/product-format-declaration.json"
       },
       "x-adcp-validation": {
         "verifier_constraints": {
@@ -75,7 +76,7 @@
       "type": "array",
       "description": "Optional array of specific public placements within this product. Product placements declare `kind` to distinguish publisher-catalog placements (`publisher_ref`) from sales-agent-defined placements (`seller_inline`). Publisher references use canonical `{publisher_domain, placement_id}` identity and may omit name because adagents.json resolves it. New seller-inline placements SHOULD carry `seller_agent`; legacy rows without it remain scoped to the enclosing seller and product. A seller-inline publisher_domain is inventory attribution, not authority to mint an ID in that publisher's catalog namespace. Each placement MUST declare mode: targetable or included. Creative assignments route creatives only after placement inventory is purchased.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/placement.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/placement.json"
       },
       "minItems": 1
     },
@@ -83,7 +84,7 @@
       "type": "array",
       "description": "Declared video placement types that may be included in this product, using IAB Tech Lab/OpenRTB 2.6 video.plcmt definitions with AdCP-native names. Use on OLV, CTV, and other video products when buyers need to distinguish instream, accompanying-content, interstitial, and standalone/no-content inventory. Aggregate products and ad-network products MAY declare multiple values. When `placements[]` also carry `video_placement_types`, this product-level array SHOULD be the union of the placement-level declarations the seller may deliver under the product. This is seller-declared discovery metadata, not independent verification of inventory quality or delivery context.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/video-placement-type.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/video-placement-type.json"
       },
       "uniqueItems": true,
       "minItems": 1
@@ -92,7 +93,7 @@
       "type": "array",
       "description": "Declared audio distribution types that may be included in this product, using IAB Tech Lab/OpenRTB 2.6 audio.feed definitions with AdCP-native names. Use on radio, streaming-audio, podcast, gaming, and other audio products when buyers need to distinguish music streaming services, FM/AM broadcast, podcasts, catch-up radio, web radio, video-game audio, and text-to-speech inventory without changing the buyer-facing channel or adagents.json property type. Aggregate products and ad-network products MAY declare multiple values. When `placements[]` also carry `audio_distribution_types`, this product-level array SHOULD be the union of the placement-level declarations the seller may deliver under the product. This is seller-declared discovery metadata, not independent verification of inventory quality or delivery context.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/audio-distribution-type.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/audio-distribution-type.json"
       },
       "uniqueItems": true,
       "minItems": 1
@@ -101,7 +102,7 @@
       "type": "array",
       "description": "Declared sponsored-placement types that may be included in this product, distinguishing where catalog-driven retail-media placements render on the retailer surface (sponsored search, sponsored display, or sponsored native). Use on retail-media products when buyers need to distinguish search-keyed, display, and native in-grid sponsored inventory. Aggregate products and ad-network products MAY declare multiple values. When `placements[]` also carry `sponsored_placement_types`, this product-level array SHOULD be the union of the placement-level declarations the seller may deliver under the product. This is seller-declared discovery metadata, not independent verification of inventory quality or delivery context.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/sponsored-placement-type.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/sponsored-placement-type.json"
       },
       "uniqueItems": true,
       "minItems": 1
@@ -110,32 +111,32 @@
       "type": "array",
       "description": "Declared social-placement surfaces that may be included in this product, distinguishing the in-app surface where social placements render (feed, stories, short_video, explore, or search). Use on social products when buyers need to distinguish feed, story, short-video, and discovery surfaces. Aggregate products and ad-network products MAY declare multiple values. When `placements[]` also carry `social_placement_surfaces`, this product-level array SHOULD be the union of the placement-level declarations the seller may deliver under the product. This is seller-declared discovery metadata, not independent verification of inventory quality or delivery context.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/social-placement-surface.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/social-placement-surface.json"
       },
       "uniqueItems": true,
       "minItems": 1
     },
     "delivery_type": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/delivery-type.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/delivery-type.json"
     },
     "exclusivity": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/exclusivity.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/exclusivity.json",
       "description": "Whether this product offers exclusive access to its inventory. Defaults to 'none' when absent. Most relevant for guaranteed products tied to specific collections or placements."
     },
     "pricing_options": {
       "type": "array",
       "description": "Available pricing models for this product. Fixed prices and auction floors are binding for every later targeting selection permitted by this product's overlay_support; price_guidance remains non-binding. Declaring broad overlay support alongside a binding option is therefore a uniform-price promise, not permission to calculate a different price at create time. A seller with value-dependent rates MUST return a request-specific configured product after rediscovery with concrete targeting, split the inventory into separately priced products, or expose only non-binding guidance until it can issue a binding option. The seller MUST mint a new pricing_option_id whenever a binding price, floor, currency, model, or priced applicability changes. It MUST NOT silently reprice a create request or reuse the selected option ID with different terms.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/pricing-option.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/pricing-option.json"
       },
       "minItems": 1
     },
     "forecast": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/delivery-forecast.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/delivery-forecast.json",
       "description": "Forecasted delivery metrics for this product. Concrete discovery targeting scopes the forecast to those effective values. When discovery requested only required_overlay_support for a dimension, the forecast describes the product's discovery/default scope and is not a value-specific forecast for every later selection; buyers rediscover with concrete targeting_overlay values when they need that forecast."
     },
     "outcome_measurement": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/outcome-measurement.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/outcome-measurement.json",
       "deprecated": true,
       "description": "**Deprecated as of this minor.** Outcome capabilities (incremental sales lift, brand lift, foot traffic, etc.) are now declared via `reporting_capabilities.available_metrics` (the same path used for impressions, conversions, ROAS) with `qualifier.attribution_methodology` and `qualifier.attribution_window` carrying the methodology and window on commit. New implementations SHOULD use the unified pattern; this field is retained for one-minor backwards compatibility and removed at the next major. See `outcome-measurement.json` description for migration guidance."
     },
@@ -147,7 +148,7 @@
           "type": "array",
           "description": "Measurement vendors used for this product, as structured `BrandRef` identities. Multiple entries when multiple vendors play different roles (e.g., the ad server plus a separate viewability vendor like IAS or DV; or a retail-media seller plus a third-party retail measurement vendor like Circana or NielsenIQ). Each vendor's `brand.json` `agents[type='measurement']` is the discovery anchor; metric definitions live on the agent's `get_adcp_capabilities.measurement.metrics[]` block. Distinct from `performance_standards[].vendor` which carries vendor identity for *committed* metrics with thresholds — this field carries vendor identity for the overall measurement story, including non-committed-but-reported metrics.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/brand-ref.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/brand-ref.json"
           },
           "minItems": 1
         },
@@ -163,35 +164,35 @@
       }
     },
     "measurement_terms": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/measurement-terms.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/measurement-terms.json",
       "description": "Seller's default billing measurement and makegood terms. Declares who counts the billing metric and what remedies apply when thresholds are breached. Buyers may propose different terms at media buy creation — sellers accept, reject (TERMS_REJECTED), or adjust per their policy."
     },
     "performance_standards": {
       "type": "array",
       "description": "Seller's default performance standards for this product: viewability, IVT, completion rate, brand safety, attention score. Buyers may propose different standards at media buy creation. When absent, no structured performance standards apply.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/performance-standard.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/performance-standard.json"
       },
       "minItems": 1
     },
     "cancellation_policy": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/cancellation-policy.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/cancellation-policy.json",
       "description": "Cancellation terms for this product. Declares the minimum notice period required before cancellation takes effect and any penalties for insufficient notice. Relevant for guaranteed delivery products. Buyers accept these terms by creating a media buy against the product."
     },
     "allowed_actions": {
       "type": "array",
       "description": "Actions buyers may perform on buys created against this product, scoped to statuses and modes. Advisory template — the authoritative per-buy capability is `available_actions[]` on the buy response, which resolves modes against current buy state, account tier, and negotiated terms. Buyers SHOULD use this for pre-flight product selection (\"which products let me self-serve cancel within 72hr?\") and read `available_actions[]` for runtime decisions. The array is uniquely keyed by `action` — sellers MUST NOT emit two entries with the same `action` value. Absence means the seller has not declared a structured action surface for this product — buyers fall back to `valid_actions[]` on buy responses for the flat string vocabulary.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/product-allowed-action.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/product-allowed-action.json"
       },
       "minItems": 1,
       "uniqueItems": true
     },
     "reporting_capabilities": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/reporting-capabilities.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/reporting-capabilities.json"
     },
     "creative_policy": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/creative-policy.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/creative-policy.json"
     },
     "is_custom": {
       "type": "boolean",
@@ -207,14 +208,14 @@
       "description": "Deprecated. Legacy/non-selectable metadata for data-provider signals already bundled into or associated with this product. This field does not provide buyer-selectable options, prices, or seller activation handles. Use included_signals for non-selectable product signal metadata, or signal_targeting_options for selectable package-level signal groups.",
       "deprecated": true,
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/data-provider-signal-selector.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/data-provider-signal-selector.json"
       }
     },
     "included_signals": {
       "type": "array",
       "description": "Non-selectable signal metadata for signals already included in, bundled with, or planned into this product. These signals describe what the product is; buyers do not select them in packages[].targeting_overlay.signal_targeting_groups and this field does not imply package-level signal targeting. Use signal_ref scope 'data_provider' or 'signal_source' to reference externally defined signals without redefining their name or value_type. Use signal_ref scope 'product' with name and value_type when the included signal is defined only by this product.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/signal-listing.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/signal-listing.json"
       },
       "minItems": 1
     },
@@ -222,12 +223,12 @@
       "type": "array",
       "description": "Inline seller-offered signals that may be applied to packages for this product at create_media_buy time. Each entry references a named signal definition with signal_ref scope 'product' for a product-local signal option, scope 'data_provider' for an external signal definition published in adagents.json signals[] that the seller is authorized to apply, or scope 'signal_source' for a source-native signal. Product-local options define name and value_type inline; data-provider and signal-source options may omit those fields when the referenced definition or source is authoritative. Use this field when the selectable menu is product-specific, has product-specific pricing or activation handles, is the relevant subset for a brief/refine result, or should be rendered without an additional get_signals call. Wholesale products may omit this field and rely on get_signals for the selectable signal feed. Buyers select eligible signals through packages[].targeting_overlay.signal_targeting_groups when signal_targeting_rules allow; fixed/default entries are applied by the seller and echoed on the package state. Sellers MUST set signal_targeting_allowed to true whenever this field is present. Bundled, non-selectable signal metadata belongs in included_signals; legacy data_provider_signals may appear only for backwards compatibility.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/product-signal-targeting-option.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/product-signal-targeting-option.json"
       },
       "minItems": 1
     },
     "signal_targeting_rules": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/signal-targeting-rules.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/signal-targeting-rules.json",
       "description": "Composition rules for selecting signals on this product. The selectable signal menu may come from inline signal_targeting_options or from get_signals when a wholesale product omits inline options. This is product-scoped because products may be backed by different ad servers with different Boolean targeting support and group limits."
     },
     "signal_targeting_allowed": {
@@ -236,19 +237,19 @@
       "description": "Whether this product has a package-level signal_targeting_groups surface. When false (default), signals are bundled into the product terms and cannot be selected or explicitly echoed as package signal groups. When true, eligible signals from inline signal_targeting_options or from get_signals may be buyer-selected or seller-applied according to signal_targeting_rules and are represented through packages[].targeting_overlay.signal_targeting_groups. Editability is controlled by signal_targeting_rules; fixed/default-only products still set this to true when applied signal groups are echoed."
     },
     "demographic_targeting": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/demographic-targeting-capability.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/demographic-targeting-capability.json",
       "description": "Exact demographic execution available for this product. Buyers MUST use this product-scoped declaration, not the seller-wide get_adcp_capabilities rollup, to preflight a demographic predicate."
     },
     "overlay_support": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/targeting-overlay-support.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/targeting-overlay-support.json",
       "description": "Binding product-scoped targeting dimensions the buyer may set independently on packages after discovery. Presence guarantees selectable capability subject to disclosed limits, not inventory or a forecast for every possible value. Targeting satisfied only through inherent product scope does not appear here. Returned products MUST cover every field requested through get_products.required_overlay_support. A later supported selection with no available inventory returns PRODUCT_UNAVAILABLE on create; an update outside the original priced envelope may return REQUOTE_REQUIRED."
     },
     "media_buy_support": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/media-buy-support.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/media-buy-support.json",
       "description": "Binding product participation in shared MediaBuy-level controls. This is separate from overlay_support because a root frequency cap aggregates exposures across packages rather than targeting one package. Returned products MUST cover every field requested through required_media_buy_support."
     },
     "identity": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/product-identity.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/product-identity.json",
       "x-status": "experimental",
       "x-added-in": "3.2.0"
     },
@@ -256,21 +257,21 @@
       "type": "array",
       "description": "Experimental (`media_buy.execution_requirements`). Account resources a package on this product needs before `create_media_buy` succeeds. Every entry is required. Account-independent: it does not change `cache_scope` and carries no account resource IDs or names. When present, it plus the `required_connections` of the package's selected format declarations is complete for the kinds in `product-execution-requirement.json`: a seller MUST NOT reject a package that satisfies all of them for lacking an undeclared kind. Absence means undeclared. A declaring seller MUST reject an unmet `event_source` or `catalog` entry on a buyer-supplied `create_media_buy` `packages[]` or `update_media_buy` `new_packages[]` entry, or an update that removes a satisfying binding, with `VALIDATION_ERROR`, `error.field` at the binding, and `error.details` per `error-details/execution-requirement-unmet.json`.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/product-execution-requirement.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/product-execution-requirement.json"
       },
       "minItems": 1,
       "x-status": "experimental",
       "x-added-in": "3.2.0"
     },
     "targeting_resolution": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/product-targeting-resolution.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/product-targeting-resolution.json",
       "description": "Discovery-time targeting resolution bound to this configured product. modifications sparsely disclose product-specific differences from get_products.targeting_overlay. Request-level brief interpretation is returned once on GetProductsResponse.targeting_resolution. Exact structured overlay values are not repeated. Selecting product_id accepts the disclosed modifications; product forecast and pricing MUST reflect them."
     },
     "audience_evidence": {
       "type": "array",
       "description": "Immutable population-level evidence explaining why this inventory may suit an audience. This supports discovery, comparison, and planning only. It does not imply exact demographic targeting, user-level signal membership, or legal-age verification. Sellers MUST publish each distinct snapshot with a new snapshot_id and content_digest.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/audience-evidence.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/audience-evidence.json"
       },
       "minItems": 1
     },
@@ -278,7 +279,7 @@
       "type": "array",
       "description": "Exact evidence snapshots that satisfied required eligibility or affected seller ranking for this get_products result. When audience_evidence_requirements was supplied and evidence influenced inclusion or rank, sellers MUST return the relevant selections; an absent-evidence match under evidence_presence when_available has no selection. Product selections use decision_use recommendation or eligibility.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/audience-evidence-selection.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/audience-evidence-selection.json"
       },
       "minItems": 1
     },
@@ -286,7 +287,7 @@
       "type": "array",
       "description": "Catalog types this product supports for catalog-driven campaigns. A sponsored product listing declares [\"product\"], a job board declares [\"job\", \"offering\"]. Buyers match synced catalogs to products via this field.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/catalog-type.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/catalog-type.json"
       },
       "uniqueItems": true,
       "minItems": 1
@@ -321,7 +322,7 @@
           "type": "array",
           "description": "Reach units this product can optimize for. Required when supported_metrics includes 'reach'. Buyers must set reach_unit to a value in this list on reach optimization goals — sellers reject unsupported values.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/reach-unit.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/reach-unit.json"
           },
           "minItems": 1
         },
@@ -337,7 +338,7 @@
           "type": "array",
           "description": "Viewability standards this product can optimize viewable_rate goals against. Only relevant when supported_metrics includes 'viewable_rate'. When absent, buyers cannot assume a specific standard is supported and sellers reject unsupported values. Buyers must set the goal's standard to a value in this list when it is present.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/viewability-standard.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/viewability-standard.json"
           },
           "minItems": 1,
           "uniqueItems": true
@@ -360,7 +361,7 @@
       "additionalProperties": true
     },
     "vendor_metric_optimization": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/vendor-metric-optimization.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/vendor-metric-optimization.json",
       "description": "Vendor-attested metric optimization capabilities for this product. Presence indicates the product supports `optimization_goals` with `kind: 'vendor_metric'` — the seller's bidding stack can steer delivery toward a specific vendor's measurement (e.g., DV/IAS/Adelaide attention, Scope3 emissions, Kantar brand lift, retail-media partner metrics). Distinct from `metric_optimization` (seller-native metrics with no vendor binding) and from `reporting_capabilities.vendor_metrics` (which declares what the product can *report* rather than what it can *optimize against*). A product may report a vendor metric without being able to optimize for it. Buyers MUST verify the goal's `(vendor, metric_id)` is in `supported_metrics` AND that the package's `committed_metrics[]` includes a matching `{ scope: 'vendor', vendor, metric_id }` entry — optimization without committed reporting is unverifiable and is rejected at the wire level."
     },
     "max_optimization_goals": {
@@ -369,7 +370,7 @@
       "description": "Maximum number of optimization_goals this product accepts on a package. When absent, no limit is declared. Most social platforms accept only 1 goal — buyers sending arrays longer than this value should expect the seller to use only the highest-priority (lowest priority number) goal."
     },
     "measurement_readiness": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/measurement-readiness.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/measurement-readiness.json",
       "description": "Assessment of whether the buyer's event source setup is sufficient for this product to optimize effectively. Only present when the seller can evaluate the buyer's account context. Buyers should check this before creating media buys with event-based optimization goals."
     },
     "conversion_tracking": {
@@ -380,7 +381,7 @@
           "type": "array",
           "description": "Action sources relevant to this product (e.g. a retail media product might have 'in_store' and 'website', while a display product might only have 'website')",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/action-source.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/action-source.json"
           },
           "minItems": 1
         },
@@ -452,7 +453,7 @@
       "description": "Optional standard visual card for displaying this product in user interfaces (catalog browsers, dashboards, agent UIs). Distinct from `format` — product_card describes the UI rendering of the product itself, not the ad creative the product accepts. Typed inline; no format_id indirection. Receivers render the card directly from these fields.",
       "properties": {
         "image": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/image-asset.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/image-asset.json",
           "description": "Hero image for the card. Recommended ~300x400 (4:3 portrait) for the standard card layout; receivers may scale."
         },
         "title": {
@@ -483,14 +484,14 @@
       "description": "Optional detailed card with hero + carousel + structured specifications, for rich product presentation (media-kit-style pages, full product detail views). Distinct from `format` — describes the UI rendering of the product itself, not the ad creative the product accepts. Typed inline; no format_id indirection.",
       "properties": {
         "hero_image": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/image-asset.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/image-asset.json",
           "description": "Primary hero image at the top of the detailed view."
         },
         "carousel_images": {
           "type": "array",
           "description": "Additional images for a swipeable carousel below the hero.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/image-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/image-asset.json"
           }
         },
         "title": {
@@ -535,7 +536,7 @@
           "type": "array",
           "description": "Typed seller collateral for buyer planning — coverage maps, sample renders, environment photos, media kits. Distinct from hero_image/carousel_images, which are display-oriented.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/product-card-reference-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/product-card-reference-asset.json"
           }
         }
       },
@@ -547,7 +548,7 @@
       "items": {
         "allOf": [
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/collection-selector.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/collection-selector.json"
           },
           {
             "required": [
@@ -567,7 +568,7 @@
       "type": "array",
       "description": "Product-scoped receipts for every effective property- or collection-list targeting reference. Sellers MUST return one receipt per application regardless of response field projection; exclusion applications receive a receipt even when summary.matched is zero, while zero matches for any inclusion application make the product ineligible and it is not returned. Each receipt uses the same pre-list product inventory baseline; pricing and forecast reflect inventory remaining after all effective lists are composed.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/inventory-list-application.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/inventory-list-application.json"
       },
       "minItems": 1
     },
@@ -575,7 +576,7 @@
       "type": "array",
       "description": "Specific installments included in this product. Each installment references its parent through canonical collection_ref when the product spans multiple collections or publisher namespaces; collection_id remains a deprecated single-namespace shorthand. When absent with collections present, the product covers the collections broadly (run-of-collection).",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/installment.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/installment.json"
       }
     },
     "enforced_policies": {
@@ -586,7 +587,7 @@
       }
     },
     "acceptance_policy_profile_ids": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/acceptance-policy-profile-ids.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/acceptance-policy-profile-ids.json"
     },
     "trusted_match": {
       "type": "object",
@@ -606,7 +607,7 @@
           "type": "array",
           "description": "What the publisher can accept back from context match.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/response-type.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/response-type.json"
           },
           "minItems": 1,
           "default": [
@@ -652,7 +653,7 @@
                 "type": "array",
                 "description": "Identity types this regional provider can resolve. The router filters providers whose uid_types includes the request's uid_type. Required when identity_match is true.",
                 "items": {
-                  "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/uid-type.json"
+                  "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/uid-type.json"
                 },
                 "minItems": 1
               }
@@ -696,12 +697,12 @@
           "type": "array",
           "description": "Activation capabilities available on this product, as an unordered set. Entries are usually independent options; a clean_room entry may compose with dataset_query or platform_distribution to declare how a targetable result leaves the room or reaches the buying platform.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/audience-activation-method.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/audience-activation-method.json"
           },
           "minItems": 1
         },
         "preferred_method": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/audience-activation-method.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/audience-activation-method.json",
           "description": "The seller's preferred path when the buyer supports several. MUST also appear in methods."
         },
         "notes": {
@@ -735,14 +736,14 @@
           "maxLength": 2000
         },
         "ext": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/ext.json"
         }
       },
       "minProperties": 1,
       "additionalProperties": true
     },
     "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/property-delivery-metrics.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/property-delivery-metrics.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/property-delivery-metrics.json",
   "title": "Property Delivery Metrics",
   "description": "Delivery metrics for one publisher property. The stable operational key is (publisher_domain, identifier.type, identifier.value); property_ref adds catalog identity when resolution is available.",
   "x-adcp-validation": {
@@ -10,7 +10,7 @@
   },
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/delivery-metrics.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/delivery-metrics.json"
     },
     {
       "type": "object",
@@ -21,11 +21,11 @@
           "description": "Publisher or platform authority that namespaces the operational identifier, including when the surface is not registered in adagents.json."
         },
         "identifier": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/identifier.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/identifier.json",
           "description": "Primary operational identifier of the property that delivered. Required even when catalog enrichment is unavailable."
         },
         "property_ref": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/property-ref.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/property-ref.json",
           "description": "Canonical publisher-scoped catalog identity when the delivered property resolves to adagents.json. Its publisher_domain MUST equal the row's publisher_domain."
         },
         "property_name": {

package/dist/lib/schemas-data/3.2/core/property-id.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/property-id.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/property-id.json",
   "title": "Property ID",
   "description": "Identifier for a publisher property. Must be lowercase alphanumeric with underscores only.",
   "type": "string",

package/dist/lib/schemas-data/3.2/core/property-list-ref.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/property-list-ref.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/property-list-ref.json",
   "title": "Property List Reference",
   "description": "Reference to an externally managed property list. Enables passing large property sets (50,000+) without embedding them in requests. The receiving agent fetches and caches the list independently.",
   "type": "object",

package/dist/lib/schemas-data/3.2/core/property-ref.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/property-ref.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/property-ref.json",
   "title": "Property Reference",
   "description": "Canonical reference to a publisher property. Property IDs are scoped to the adagents.json at publisher_domain, so both fields participate in identity.",
   "type": "object",
@@ -11,7 +11,7 @@
       "pattern": "^[a-z0-9]([a-z0-9-]*[a-z0-9])?(\\.[a-z0-9]([a-z0-9-]*[a-z0-9])?)*$"
     },
     "property_id": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/property-id.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/property-id.json",
       "description": "Property ID from the publisher's adagents.json property catalog."
     }
   },

package/dist/lib/schemas-data/3.2/core/property-tag.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/property-tag.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/property-tag.json",
   "title": "Property Tag",
   "description": "Tag for categorizing publisher properties. Must be lowercase alphanumeric with underscores only.",
   "type": "string",

package/dist/lib/schemas-data/3.2/core/property.json

@@ -1,16 +1,16 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/property.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/property.json",
   "title": "Property",
   "description": "An advertising property that can be validated via adagents.json",
   "type": "object",
   "properties": {
     "property_id": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/property-id.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/property-id.json",
       "description": "Unique identifier for this property (optional). Enables referencing properties by ID instead of repeating full objects."
     },
     "property_type": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/property-type.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/property-type.json",
       "description": "Type of advertising property"
     },
     "name": {
@@ -24,7 +24,7 @@
         "type": "object",
         "properties": {
           "type": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/identifier-types.json",
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/identifier-types.json",
             "description": "Type of identifier for this property"
           },
           "value": {
@@ -44,7 +44,7 @@
       "type": "array",
       "description": "Tags for categorization and grouping (e.g., network membership, content categories)",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/property-tag.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/property-tag.json"
       },
       "uniqueItems": true
     },
@@ -52,7 +52,7 @@
       "type": "array",
       "description": "Advertising channels this property supports (e.g., ['display', 'olv', 'social']). Publishers declare which channels their inventory aligns with. Properties may support multiple channels. See the Media Channel Taxonomy for definitions.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/channels.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/channels.json"
       },
       "uniqueItems": true
     },