@adcp/sdk 16.4.0 → 16.6.0

package/dist/lib/schemas-data/3.2/core/offering-asset-group.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/offering-asset-group.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/offering-asset-group.json",
   "title": "Offering Asset Group",
   "description": "A structured group of creative assets within an offering, identified by a group ID and asset type. Enables offerings to carry per-group creative pools (headlines, images, videos) using the same vocabulary as format-level asset definitions.",
   "type": "object",
@@ -10,7 +10,7 @@
       "description": "Identifies the creative role this group fills. Values are defined by each canonical format declaration's offering_asset_constraints — not protocol constants. Discover creative-agent declarations via get_adcp_capabilities creative.supported_formats[] and sales-product declarations via Product.format_options[] (e.g., 'headlines', 'images', or 'videos')."
     },
     "asset_type": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/asset-content-type.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/asset-content-type.json",
       "description": "The content type of all items in this group."
     },
     "items": {
@@ -19,43 +19,43 @@
       "items": {
         "oneOf": [
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/text-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/text-asset.json"
           },
           {
-            "$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"
           },
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/video-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/video-asset.json"
           },
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/audio-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/audio-asset.json"
           },
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/url-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/url-asset.json"
           },
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/html-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/html-asset.json"
           },
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/markdown-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/markdown-asset.json"
           },
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/vast-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/vast-asset.json"
           },
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/daast-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/daast-asset.json"
           },
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/css-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/css-asset.json"
           },
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/javascript-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/javascript-asset.json"
           },
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/zip-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/zip-asset.json"
           },
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/assets/webhook-asset.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/assets/webhook-asset.json"
           }
         ],
         "discriminator": {
@@ -65,7 +65,7 @@
       "minItems": 1
     },
     "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/offering.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/offering.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/offering.json",
   "title": "Offering",
   "description": "A promotable offering from a brand. Can represent a campaign, product promotion, service, or any other thing the brand wants to make available. Offerings carry structured asset groups for creative assembly and can be promoted via traditional creatives or conversational SI experiences (via the brand's SI agent).",
   "type": "object",
@@ -46,7 +46,7 @@
       "type": "array",
       "description": "Structured asset groups for this offering. Each group carries a typed pool of creative assets (headlines, images, videos, etc.) identified by a group ID that matches format-level vocabulary.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/offering-asset-group.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/offering-asset-group.json"
       }
     },
     "geo_targets": {
@@ -78,7 +78,7 @@
             "type": "object",
             "properties": {
               "system": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/metro-system.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/metro-system.json",
                 "description": "Metro area classification system (e.g., 'nielsen_dma', 'uk_itl2')"
               },
               "values": {
@@ -102,7 +102,7 @@
           "type": "array",
           "description": "Postal areas where this offering is relevant. Prefer the native country + postal system form. Deprecated legacy country-fused postal-system tokens remain accepted for compatibility.",
           "items": {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/postal-area.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/postal-area.json"
           },
           "minItems": 1
         }
@@ -124,7 +124,7 @@
       }
     },
     "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/operator-identity.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/operator-identity.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/operator-identity.json",
   "title": "Operator Identity",
   "description": "The buyer-desired operator portion of an advertiser account identity. The operator domain identifies the entity operating for the brand; operator_unit identifies that operator's internal buying context. Buyers that already administer the account control unit metadata and identity within the current operator. Changing the operator domain is an inter-entity handoff that requires seller-mediated approval by the current account authority, the brand, and the destination operator. When used as a sync_accounts settings-update value, this object is a complete desired replacement: omitting operator_unit removes the current unit rather than preserving it.",
   "type": "object",
@@ -12,7 +12,7 @@
       "x-entity": "operator"
     },
     "operator_unit": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/operator-unit.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/operator-unit.json",
       "description": "Optional operator-owned business unit, agency seat, or platform account. Its id participates in account identity; name is mutable display metadata. Omission from a complete desired replacement means the account should have no operator unit."
     }
   },

package/dist/lib/schemas-data/3.2/core/operator-unit.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/operator-unit.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/operator-unit.json",
   "title": "Operator Unit",
   "description": "Operator-owned buying context used to distinguish business units, agency seats, or platform accounts beneath one operator domain. The id is stable identity in the operator's namespace; name is mutable display metadata and never participates in account identity.",
   "x-entity": "operator_unit",

package/dist/lib/schemas-data/3.2/core/opportunity-context.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/opportunity-context.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/opportunity-context.json",
   "title": "Opportunity Context",
   "description": "Buyer-supplied context for one planning cycle across proposal request, decline, and media-buy creation. The opaque opportunity_id is stable within the seller and account scope; sellers associate it with proposals without treating it as proposal identity.",
   "type": "object",
@@ -33,7 +33,7 @@
       "description": "How seriously the buyer is evaluating supply in this cycle."
     },
     "planning_horizon": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/date-range.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/date-range.json",
       "description": "Inclusive calendar range in which the buyer expects the campaign to run."
     },
     "response_deadline": {

package/dist/lib/schemas-data/3.2/core/optimization-goal.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/optimization-goal.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/optimization-goal.json",
   "title": "Optimization Goal",
   "description": "A single objective function: what to maximize or optimize, in what units, and in what priority order. Used on packages to optimize delivery within one package and on seller-optimized budget allocations to allocate spend across packages. Currency-bearing execution policy belongs in BiddingPolicy in 3.2. Legacy target.cost_per and target.per_ad_spend remain accepted only on package goals for migration and are deprecated. The primary goal is the earliest array entry among goals with the lowest explicit numeric priority; goals without priority follow all explicitly prioritized goals; when all priorities are omitted, the first entry is primary. This array-order tie-break makes duplicate priorities deterministic.",
   "discriminator": {
@@ -36,7 +36,7 @@
         "standard": {
           "allOf": [
             {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/viewability-standard.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/viewability-standard.json"
             }
           ],
           "description": "Viewability standard the goal is judged against. Required when metric is 'viewable_rate'; optional for 'viewed_seconds' (seller default standard when omitted); not allowed for other metrics. Must be in metric_optimization.supported_viewability_standards when declared. A goal below a same-standard viewability performance_standard never relaxes that standard."
@@ -44,7 +44,7 @@
         "vendor": {
           "allOf": [
             {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/brand-ref.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/brand-ref.json"
             }
           ],
           "description": "Measurement vendor judging a viewable_rate or viewed_seconds goal; not allowed for other metrics. When omitted, the seller's default viewability measurement applies. Sellers MUST reject a vendor they cannot optimize against rather than substitute another."
@@ -52,7 +52,7 @@
         "reach_unit": {
           "allOf": [
             {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/reach-unit.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/reach-unit.json"
             }
           ],
           "description": "Unit for reach measurement. Required when metric is 'reach'. Must be a value declared in the product's metric_optimization.supported_reach_units."
@@ -74,7 +74,7 @@
             "window": {
               "allOf": [
                 {
-                  "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/duration.json"
+                  "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/duration.json"
                 }
               ],
               "description": "Time window over which frequency is measured (e.g. {\"interval\": 7, \"unit\": \"days\"} or {\"interval\": 1, \"unit\": \"campaign\"} for the full flight). Weekly windows are typical for brand campaigns; daily windows suit high-cadence direct response."
@@ -245,7 +245,7 @@
                 "description": "Event source to include (must be configured on this account via sync_event_sources)"
               },
               "event_type": {
-                "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/event-type.json",
+                "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/event-type.json",
                 "description": "Event type to include from this source (e.g., purchase, lead, app_install, refund)"
               },
               "custom_event_name": {
@@ -337,7 +337,7 @@
         "attribution_window": {
           "allOf": [
             {
-              "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/attribution-window.json"
+              "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/attribution-window.json"
             }
           ],
           "description": "Attribution window for this optimization goal — references the canonical `attribution-window` shape (post_click, post_view, model). Values must match an option declared in the seller's `conversion_tracking.attribution_windows` capability. Sellers MUST reject windows not in their declared capabilities. When the entire field is omitted, the seller uses their default window."
@@ -363,11 +363,11 @@
           "const": "vendor_metric"
         },
         "vendor": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/brand-ref.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/brand-ref.json",
           "description": "Vendor that defines and computes this metric. Same shape as `vendor_metric_values.vendor`, `reporting_capabilities.vendor_metrics[].vendor`, and `vendor_metric_optimization.supported_metrics[].vendor` — symmetric across discovery, capability, commitment, optimization, and reporting surfaces."
         },
         "metric_id": {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/vendor-metric-id.json",
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/vendor-metric-id.json",
           "description": "Identifier for the metric within the vendor's vocabulary (e.g., `attention_score`, `attention_seconds`, `gco2e_per_impression`, `awareness_lift`). MUST be present in the vendor's published `measurement.metrics[]` catalog and in the product's `vendor_metric_optimization.supported_metrics[]`."
         },
         "target": {

package/dist/lib/schemas-data/3.2/core/outcome-measurement.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/outcome-measurement.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/outcome-measurement.json",
   "title": "Outcome Measurement",
   "deprecated": true,
   "description": "**Deprecated as of this minor.** Predates the unified measurement-vocabulary pattern. Outcome metrics (incremental_sales_lift, brand_lift, foot_traffic, conversion_lift, brand_search_lift, attributed sales) are now expressible through the same primitives as the rest of the measurement surface:\n\n- **Outcome metric capability** → declared via `reporting_capabilities.available_metrics` on the product. Closed enum entries: `incremental_sales_lift`, `brand_lift`, `foot_traffic`, `conversion_lift`, `brand_search_lift`. Existing entries `conversions`, `conversion_value`, `roas`, `cost_per_acquisition`, `units_sold`, `new_to_brand_rate`, `new_to_brand_units`, `leads` already covered most outcome-metric needs.\n- **Attributed sales** (the retail-media value prop) → `conversion_value` with `qualifier.attribution_methodology: 'deterministic_purchase'`. **Walmart Connect's `attributedSalesIn14Days`** maps to `conversion_value` + `qualifier.attribution_methodology: 'deterministic_purchase'` + `qualifier.attribution_window: {interval: 14, unit: 'days'}`. Same pattern for Amazon DSP attributed sales, Kroger Precision attributed sales, Criteo Retail Media attributed sales — the protocol does not invent a separate `attributed_sales` metric ID because the qualifier handles the methodology split.\n- **Brand lift** → `brand_lift` metric_id PLUS `qualifier.lift_dimension` (closed enum: awareness, consideration, favorability, purchase_intent, ad_recall). Brand-lift vendors (Kantar, Upwave, Cint, DV) report each dimension separately; the qualifier ensures rows aren't combined.\n- **Attribution methodology** → `qualifier.attribution_methodology` (`deterministic_purchase`, `probabilistic`, `panel_based`, `modeled`).\n- **Attribution window** → `qualifier.attribution_window` (structured duration `{interval, unit}`, never a shorthand string).\n- **Vendor identity** (typically the seller for retail-media closed loop) → vendor-scope `committed_metrics` entries with the BrandRef anchored on the seller's measurement-agent capability (or absent when the seller is the implicit vendor). For third-party retail measurement (Circana, NielsenIQ, IRI for retail MMM; Kantar/Upwave for brand lift on retail-media inventory), use `performance_standards.vendor` to pin the third-party identity.\n- **Reporting frequency / format** → planned for a follow-up `reporting_capabilities` extension; existing `outcome_measurement.reporting` field continues to work for one minor.\n\nThis schema is retained for one-minor backwards compatibility on `product.outcome_measurement`. Removed at the next major. New implementations SHOULD declare outcome capabilities via `reporting_capabilities.available_metrics`; standard-scope delivery reconciles through `committed_metrics`, `by_package[].metric_values`, and `missing_metrics`, while vendor-scope delivery uses `by_package[].vendor_metric_values`.",
@@ -26,7 +26,7 @@
     "window": {
       "allOf": [
         {
-          "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/duration.json"
+          "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/duration.json"
         }
       ],
       "description": "Attribution window as a structured duration (e.g., {\"interval\": 30, \"unit\": \"days\"})."

package/dist/lib/schemas-data/3.2/core/outcome-target-cost-per.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/outcome-target-cost-per.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/outcome-target-cost-per.json",
   "title": "Outcome Target Cost Per",
   "description": "Average cost the buyer will pay per goal result: BiddingPolicy.cost_per plus a currency. It requires a goal expressible as a canonical optimization goal; otherwise the seller rejects with INVALID_REQUEST naming criteria.outcome_target.cost_per, since the goal stays plannable by volume. With a buyer budget (offer_filters.budget_range or the brief), the seller plans the volume it can deliver within it at or below (cap) or around (target) the cost; with volume, see volume; with neither, it MUST state the spend for the volume it can deliver at the cost in total_budget_guidance. Each proposal answers in commercial_terms.bidding.cost_per, which the buyer adopts on acceptance; it is an execution control, not an expected price, and billing stays on the selected pricing option. The answer MUST NOT carry purchase-level bidding. Under fixed or omitted budget_allocation every purchase's primary optimization goal, and under seller_optimized the primary budget_allocation.optimization_goals goal, MUST match goal and resolve to one result unit as BiddingPolicy.cost_per defines it: the same metric and result-defining qualifiers, or for an event goal every event_sources[] entry carrying the goal's event_type (and custom_event_name) with one resolved attribution_window. Seller-added qualifiers (such as view_duration_seconds or reach_unit) are permitted and visible in the proposal. For an event goal the seller fills event_sources from sources available on the buyer's account for that event, buyer-synced or seller-managed, exactly one unless it advertises conversion_tracking.multi_source_event_dedup, and states attribution_window, which SHOULD be one advertised in conversion_tracking.attribution_windows; with none available it rejects. A seller MUST NOT answer with a bidding policy outside its advertised features.bidding_policy profile for the proposal's scope and allocation mode; a declaring seller without one rejects. Rejections of a target that cannot be represented or bound (strength, currency, goal, capability) use INVALID_REQUEST naming criteria.outcome_target.cost_per; a valid target with no viable inventory is outcome 'rejected'.",
   "type": "object",
@@ -16,7 +16,7 @@
       "description": "ISO 4217 currency of amount. BiddingPolicy.cost_per has no currency because it inherits the media-buy currency, and no media buy exists at request time, so the request states it. It becomes the answer's currency: every answering proposal's purchases[].pricing.currency (which bidding amounts use) and forecast.currency MUST equal it, as MUST commercial_terms.total_budget.currency and total_budget_guidance.currency when present; sellers MUST NOT convert currency. It MUST equal offer_filters.budget_range.currency when present. The seller plans within budget_range.max when present, else at or above budget_range.min, and total_budget MUST NOT exceed max or fall below min. A seller rejects a conflict with budget_range, pricing_currencies, the account currency, or the requested products' pricing currencies with INVALID_REQUEST naming criteria.outcome_target.cost_per."
     },
     "strength": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/outcome-target-cost-strength.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/outcome-target-cost-strength.json",
       "description": "BiddingPolicy.cost_per strength: `cap` optimizes for an average at or below the amount and accepts underdelivery when necessary; `target` optimizes around the amount while balancing volume and spend. Neither is a per-result or per-auction guarantee. The answer MUST keep this strength: a cap of 3 the seller can only meet at 4.50 returns {amount: 4.50, strength: 'cap'}, never 'target'. A seller that will not plan at any amount under this strength rejects instead."
     }
   },

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/overlay.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/overlay.json",
   "title": "Overlay",
   "description": "A publisher-controlled element that renders on top of buyer creative content within the ad placement. Creative agents should avoid placing critical content (CTAs, logos, key copy) within overlay bounds.",
   "type": "object",

package/dist/lib/schemas-data/3.2/core/package-delivery-metric-value.json

@@ -1,11 +1,11 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/package-delivery-metric-value.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/package-delivery-metric-value.json",
   "title": "Package Delivery Metric Value",
   "description": "A qualified standard delivery value reported at package grain. The qualifier is required and must be non-empty; unqualified spend remains on the package's flat spend field.",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/delivery-metric-aggregate.json#/oneOf/0"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/delivery-metric-aggregate.json#/oneOf/0"
     },
     {
       "type": "object",

package/dist/lib/schemas-data/3.2/core/package-format-snapshot.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/package-format-snapshot.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/package-format-snapshot.json",
   "title": "Package Format Snapshot",
   "description": "Immutable package-time snapshot of one selected Product format declaration. Product-format fields remain flattened at the root for 3.x compatibility; product, placement, exact execution-version, and digest fields bind the seller's package-time decision. A contract-bearing snapshot is durably identified even when no preview or observation feature is offered.",
   "type": "object",
@@ -18,7 +18,7 @@
       "items": {
         "allOf": [
           {
-            "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/placement-ref.json"
+            "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/placement-ref.json"
           },
           {
             "required": [
@@ -30,11 +30,11 @@
       "description": "Nonempty, duplicate-free effective placement set, sorted by publisher_domain then placement_id using ascending UTF-8 bytes without Unicode normalization. Omission binds the product-wide common effective contract; it never means an inferred list of all current placements."
     },
     "execution_vast_version": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/vast-version.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/vast-version.json",
       "description": "Exact VAST execution version selected for first-class VAST tracker matching when no sibling delivery document supplies one. The value is immutable for the package."
     },
     "execution_daast_version": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/enums/daast-version.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/enums/daast-version.json",
       "description": "Exact DAAST execution version selected for first-class DAAST tracker matching when no sibling delivery document supplies one. The value is immutable for the package."
     },
     "tracker_execution_contract_digest": {
@@ -54,7 +54,7 @@
   ],
   "allOf": [
     {
-      "$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"
     },
     {
       "if": {

package/dist/lib/schemas-data/3.2/core/package-signal-targeting-group.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/package-signal-targeting-group.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/package-signal-targeting-group.json",
   "title": "Package Signal Targeting Group",
   "description": "A basic Boolean group of package-level signal targeting entries. 'any' means the user must match at least one signal in the group. 'none' means the user must match none of the signals in the group. Use groups for portable include/exclude composition such as (A OR B) AND NOT (C OR D).",
   "type": "object",
@@ -17,7 +17,7 @@
       "type": "array",
       "description": "Signal targeting entries evaluated by this group. Each entry uses the package signal targeting shape, including signal_ref, value expression, and optional pricing, execution-handle, or activation fields.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/package-signal-targeting.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/package-signal-targeting.json"
       },
       "minItems": 1
     }

package/dist/lib/schemas-data/3.2/core/package-signal-targeting-groups.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/package-signal-targeting-groups.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/package-signal-targeting-groups.json",
   "title": "Package Signal Targeting Groups",
   "description": "Top-level basic Boolean composition for package signal targeting. The groups-level operator is required; v1 supports operator 'all', meaning every child group must be satisfied. This represents the portable baseline: (any of include group 1) AND (any of include group 2) AND NOT (any of exclude group N).",
   "type": "object",
@@ -16,7 +16,7 @@
       "type": "array",
       "description": "Signal targeting groups to evaluate. Use operator 'any' for include groups and 'none' for exclusion groups.",
       "items": {
-        "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/package-signal-targeting-group.json"
+        "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/package-signal-targeting-group.json"
       },
       "minItems": 1
     }

package/dist/lib/schemas-data/3.2/core/package-signal-targeting.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/package-signal-targeting.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/package-signal-targeting.json",
   "title": "Package Signal Targeting",
   "description": "Buy-time selection of one seller-offered signal inside a package signal targeting group. The signal_ref uses scope 'product' for a product-local signal option, scope 'data_provider' for a signal defined in a data provider's published adagents.json signals[], or scope 'signal_source' for a source-native signal that is not published in adagents.json signals[]. The selected product's inline Product.signal_targeting_options, get_signals feed when inline options are omitted, and signal_targeting_rules define buy-time eligibility. Inclusion and exclusion are controlled by the parent group operator: use operator 'any' to include users matching the signal expression and operator 'none' to exclude users matching the signal expression. For binary signals, value MUST be true; do not use value=false for exclusion inside signal_targeting_groups. Use audience_include/audience_exclude only for buyer-managed first-party audiences registered through sync_audiences.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/signal-targeting-expression.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/signal-targeting-expression.json"
     }
   ],
   "properties": {
@@ -21,7 +21,7 @@
       "x-entity": "signal_activation_id"
     },
     "activation_key": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/activation-key.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/activation-key.json",
       "description": "Destination-specific activation key returned by get_signals or activate_signal. Usually omitted for seller-offered signals selected directly through the same seller; include only when the selected signal was separately activated and the seller requires the activation key to correlate the package selection."
     }
   },

package/dist/lib/schemas-data/3.2/core/package-targeting-resolution.json

@@ -1,16 +1,16 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.5/core/package-targeting-resolution.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.7/core/package-targeting-resolution.json",
   "title": "Package Targeting Resolution",
   "description": "Execution details for targeting accepted on a booked Package. Product discovery modifications and response-level brief interpretation are not valid here. Additional execution dimensions may be added in future minor versions.",
   "type": "object",
   "properties": {
     "demographics": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/demographic-targeting-resolution.json",
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/demographic-targeting-resolution.json",
       "description": "Canonical demographic predicate and exact seller execution details. Include whenever demographic targeting was requested or applied."
     },
     "ext": {
-      "$ref": "https://adcontextprotocol.org/schemas/3.2.5/core/ext.json"
+      "$ref": "https://adcontextprotocol.org/schemas/3.2.7/core/ext.json"
     }
   },
   "required": [