@adcp/sdk 15.8.0 → 15.9.0

package/dist/lib/schemas-data/3.2/enums/macro-mapping-status.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/macro-mapping-status.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/macro-mapping-status.json",
   "title": "Macro Mapping Status",
   "description": "Evidence level connecting a dialect-local macro meaning to the AdCP universal vocabulary.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/macro-processing-operation.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/macro-processing-operation.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/macro-processing-operation.json",
   "title": "Macro Processing Operation",
   "description": "The next authorized operation on the current source token.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/macro-resolution-reason.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/macro-resolution-reason.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/macro-resolution-reason.json",
   "title": "Macro Resolution Reason",
   "description": "Structured reason for a macro preflight result.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/macro-resolver.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/macro-resolver.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/macro-resolver.json",
   "title": "Macro Processing Actor",
   "description": "Protocol role authorized to translate the token or bind its concrete value.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/macro-value-context.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/macro-value-context.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/macro-value-context.json",
   "title": "Macro Value Context",
   "description": "Syntactic occurrence context supported by the first macro contract. Substitution inside arbitrary JavaScript, JSON, or HTML text is intentionally not inferred; use `opaque` and preserve it unless a later governed context is added.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/makegood-remedy.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/makegood-remedy.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/makegood-remedy.json",
   "title": "Makegood Remedy",
   "description": "Remedy types available when a performance standard or billing measurement threshold is breached.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/markdown-flavor.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/markdown-flavor.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/markdown-flavor.json",
   "title": "Markdown Flavor",
   "description": "Markdown specification flavors supported for text assets",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/match-id-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/match-id-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/match-id-type.json",
   "title": "Match ID Type",
   "description": "Identifier types for audience match reporting. Combines hashed PII types (from audience-member.json field names) with token types from uid-type.json, including publisher-scoped PAIR identifiers.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/match-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/match-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/match-type.json",
   "title": "Match Type",
   "description": "Keyword targeting match type. broad: ads may serve on queries semantically related to the keyword. phrase: ads serve when the query contains the keyword phrase. exact: ads serve only when the query matches the keyword exactly.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/media-buy-action-mode.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/media-buy-action-mode.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/media-buy-action-mode.json",
   "title": "Media Buy Action Mode",
   "description": "How a seller honors a given action on a media buy. Buyers branch on this to decide whether to expect a synchronous response, an automatic-with-fallback flow, or seller-managed asynchronous processing. The mode is declared on each entry of `allowed_actions[]` (product, as `modes[]` array) or `available_actions[]` (buy, as singular `mode`). Requotes that fall outside the current buy envelope are not an action mode in 3.1; sellers return REQUOTE_REQUIRED from update_media_buy instead. Buyer SDKs MUST tolerate unknown future values by treating the affected action as unavailable until they re-fetch the product or buy and inspect the current `available_actions[]` / `allowed_actions[]` metadata.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/media-buy-frequency-cap-control-mode.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/media-buy-frequency-cap-control-mode.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/media-buy-frequency-cap-control-mode.json",
   "title": "Media Buy Frequency Cap Control Mode",
   "description": "The aggregate MediaBuy frequency-cap control shape supported in 3.2.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/media-buy-health.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/media-buy-health.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/media-buy-health.json",
   "title": "Media Buy Health",
   "description": "Aggregate health of a media buy based on upstream dependency state. Orthogonal to media-buy-status — a buy can be paused-and-impaired, pending-and-impaired, or active-and-impaired. Always set; defaults to 'ok' when no open impairments exist.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/media-buy-status.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/media-buy-status.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/media-buy-status.json",
   "title": "Media Buy Status",
   "description": "Status of a media buy.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/media-buy-valid-action.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/media-buy-valid-action.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/media-buy-valid-action.json",
   "title": "Media Buy Valid Action",
   "description": "Actions the buyer can perform on a media buy. Used as the action identifier in both the legacy flat `valid_actions[]` field (string array) and the structured `available_actions[]` field on buy responses, and in `allowed_actions[]` on Product. The coarse values (`update_budget`, `update_dates`, `update_packages`, `sync_creatives`) predate the finer-grained vocabulary and are retained for backwards compatibility — see `x-deprecated-enum-values`. Sellers SHOULD declare the finer-grained values where their platform distinguishes them; the coarse values roll up to the finer set per `enumMetadata[<value>].rollup`. See action-to-field mapping table in docs/media-buy/task-reference/update_media_buy.mdx for the normative binding between each action and the fields it covers on update_media_buy.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/metric-scope.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/metric-scope.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/metric-scope.json",
   "title": "Metric Scope",
   "description": "Discriminator for entries in unified metric arrays (`committed_metrics`, `missing_metrics`). `standard`: a metric from the closed `available-metric.json` enum, identified by `metric_id` alone. `vendor`: a vendor-defined metric, identified by the tuple `(vendor, metric_id)` where `vendor` is a BrandRef anchored on the vendor's `brand.json`.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/metric-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/metric-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/metric-type.json",
   "title": "Metric Type",
   "deprecated": true,
   "description": "**Deprecated as of this minor.** Legacy free-form enum mixing metrics, verification, and attribution into one list with no layer alignment. New implementations SHOULD use `performance-feedback.metric` (the discriminated `(scope, metric_id, qualifier)` row shape) instead. This enum is retained for one-minor backwards compatibility on `performance-feedback.metric_type` and is removed at the next major. Migration guidance:\n\n- `viewability` → `{ scope: 'standard', metric_id: 'viewable_rate', qualifier: { viewability_standard: 'mrc' | 'groupm' } }` (or `viewable_impressions` / `measurable_impressions` depending on what's being fed back)\n- `click_through_rate` → `{ scope: 'standard', metric_id: 'ctr' }`\n- `completion_rate` → `{ scope: 'standard', metric_id: 'completion_rate', qualifier: { completion_source: 'seller_attested' | 'vendor_attested' } }`\n- `conversion_rate` → no clean direct target. `conversions` (count) is not the same as `conversion_rate` (ratio); senders feeding back conversion-rate effectively are encouraged either to feed back `{ scope: 'standard', metric_id: 'conversions' }` with the rate in the response narrative, or to use a vendor-scope entry for an MMM/MTA conversion-rate variant. Native `conversion_rate` may graduate to `available-metric.json` in a future minor if demand materializes.\n- `brand_lift` → `{ scope: 'vendor', vendor: { domain: '...' }, metric_id: '<vendor brand lift metric>' }`\n- `brand_safety` → typically `{ scope: 'vendor', vendor: { domain: 'doubleverify.com' \\| 'integralads.com' \\| 'humansecurity.com' \\| ... } }` with `metric_id` from the vendor's measurement-agent capabilities catalog. If the buyer doesn't know the vendor's specific `metric_id`, they MAY populate the top-level `vendor` field instead and OMIT `metric` entirely — the feedback row remains attributable via `feedback_source` + `vendor` even without a structured metric reference.\n- `overall_performance` → **omit `metric` entirely**. This was a meta-bucket without defined dispatch semantics — holistic campaign feedback (a trader flagging a campaign as underperforming without a specific metric) is now expressed by populating `performance_index` and the response narrative without setting `metric`. Same for general optimization signals.\n- `cost_efficiency` → **omit `metric` entirely** for general efficiency feedback. For specific cost-per concerns, use `{ scope: 'standard', metric_id: 'cost_per_acquisition' \\| 'cost_per_click' \\| 'cost_per_completed_view' \\| 'roas' }`.",

package/dist/lib/schemas-data/3.2/enums/metro-system.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/metro-system.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/metro-system.json",
   "title": "Metro Area System",
   "description": "Metro area classification systems for geographic targeting",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/moov-atom-position.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/moov-atom-position.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/moov-atom-position.json",
   "title": "Moov Atom Position",
   "description": "Position of the moov atom in an MP4 container. 'start' enables progressive download without buffering the entire file; required for streaming ad delivery.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/motion-level.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/motion-level.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/motion-level.json",
   "title": "Creative Motion Level",
   "description": "Motion class of a rendered creative, mirroring AdCOM creative attributes 21 (Static Visual), 22 (Limited Motion / Cinemagraph), and 23 (Full-Motion Video). Sellers constrain the accepted level on a format option; buyers declare the level their creative carries. OpenRTB bridges map the value to `attr` on the bid and `battr` on the request.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/notification-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/notification-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/notification-type.json",
   "title": "Notification Type",
   "description": "Type of push notification fired by a seller agent. Media-buy-anchored cadence reports (`scheduled`, `final`, `delayed`, `adjusted`, `window_update`) fire against a media buy's `reporting_webhook`; `impairment` is media-buy-anchored but fires against `push_notification_config`. Account-anchored notifications include creative, account, product, signal, wholesale-feed, and reporting events, including `reporting.delivery_ready`, `reporting.status_changed`, and `reporting.ledger_changed`; these outlive any single media buy and fire against matching account `notification_configs[]`. The reporting events repair through `get_reporting_status`: delivery_ready is managed-delivery-only, while status_changed and ledger_changed are valid in every reporting tier. Caller-anchored notifications (`capabilities.changed`, `principal.changed`) fire against the caller-scoped subscriber set managed by `sync_principal` or the specialized `sync_agent_notification_configs` compatibility task. New notification types MUST declare their anchor (media-buy, account, or caller), logical notification_id semantics, repair key, and classification in enumDescriptions; only invalidation-only caller-eligible types flow through include_future_event_types. Account-level subscribers MUST reject media-buy- or caller-anchored event types, and persistent account- or caller-anchored types MUST NOT use push_notification_config. Caller-level entries MAY include account-anchored types only with all_authorized_accounts true; each delivery attempt, including retries, is scoped to accounts currently authorized for that caller. Caller-level entries MUST NOT include media-buy-anchored types. Caller- and account-level subscriptions to the same event are independent and receivers dedupe by logical notification_id.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/offering-availability-status.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/offering-availability-status.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/offering-availability-status.json",
   "title": "Offering Availability Status",
   "description": "Machine-readable availability state for an SI offering or a matching product. Provides a structured counterpart to the free-string availability_summary and aligns to the same vocabulary as the free-string unavailable_reason (sold_out, expired, region_restricted, inactive) plus positive in-stock states.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/outcome-target-cost-strength.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/outcome-target-cost-strength.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/outcome-target-cost-strength.json",
   "title": "Outcome Target Cost Strength",
   "description": "Strength of an outcome_target cost_per: the BiddingPolicy.cost_per strength vocabulary, kept identical to it by test. A distinct schema gives generated SDKs a distinct type instead of a second, colliding Strength.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/outcome-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/outcome-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/outcome-type.json",
   "title": "Outcome Type",
   "description": "The type of outcome reported to a campaign governance agent after a seller interaction.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/pacing.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/pacing.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/pacing.json",
   "title": "Pacing",
   "description": "Budget pacing strategy",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/payment-terms.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/payment-terms.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/payment-terms.json",
   "title": "Payment Terms",
   "description": "Standard payment terms for AdCP accounts",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/performance-baseline.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/performance-baseline.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/performance-baseline.json",
   "title": "Performance Baseline",
   "description": "The expectation represented by performance_index = 1.0. Naming the baseline makes normalized feedback interpretable without disclosing the underlying benchmark value.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/performance-standard-metric.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/performance-standard-metric.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/performance-standard-metric.json",
   "title": "Performance Standard Metric",
   "description": "Performance metrics that support rate thresholds on media buys — the verification subset of the broader metric vocabulary. Each metric specifies whether its threshold is a floor (must exceed) or ceiling (must not exceed). Shared values with `available-metric.json` mirror the delivery vocabulary (`viewability` → `viewable_rate` family, `completion_rate` → same name); verification-only values (`ivt`, `brand_safety`, `attention_score`) are typically vendor-attested and do not appear in `available-metric.json` because they're not seller-reportable scalars — they flow through `vendor_metric_values` or vendor-scope `committed_metrics` entries with the matching `performance_standard.vendor` BrandRef anchoring identity.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/pixel-tracking-event.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/pixel-tracking-event.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/pixel-tracking-event.json",
   "title": "Pixel Tracking Event",
   "description": "Closed AdCP event vocabulary for renderer-fired pixel trackers. Impression and viewability values through `viewable_video_50` map to IAB OpenRTB Native event tracker types 1-4. `audible_video_complete` is an AdCP-defined first-class event, not an assigned IAB Native event type; Native reserves 500+ for exchange-specific use. `click` represents Native click trackers and `custom` is the explicit adopter-defined extension point.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/policy-category.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/policy-category.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/policy-category.json",
   "title": "Policy Category",
   "description": "The nature of the obligation a policy represents.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/policy-enforcement.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/policy-enforcement.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/policy-enforcement.json",
   "title": "Policy Enforcement Level",
   "description": "How governance agents treat violations of a policy. Uses RFC 2119 keywords.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/postal-system.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/postal-system.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/postal-system.json",
   "title": "Postal Code System",
   "description": "Postal code system names for geographic targeting. Prefer country-local values with an explicit ISO 3166-1 alpha-2 country. Deprecated country-fused values remain in this published enum for 3.x compatibility.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/preview-output-format.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/preview-output-format.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/preview-output-format.json",
   "title": "Preview Output Format",
   "description": "Output format for creative previews",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/pricing-model.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/pricing-model.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/pricing-model.json",
   "title": "Pricing Model",
   "description": "Supported pricing models for advertising products",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/pricing-structure.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/pricing-structure.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/pricing-structure.json",
   "title": "Pricing Structure",
   "description": "How the payable price is determined. Fixed pricing has a seller-declared monetary unit price, auction pricing is established through a buyer bid, and contingent pricing is calculated from a measured business outcome after delivery.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/principal-kind.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/principal-kind.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/principal-kind.json",
   "title": "Principal Kind",
   "x-status": "experimental",
   "description": "Seller-resolved kind of the authenticated principal: an autonomous buyer-agent workload or an operator-side identity such as a person at the operator.",

package/dist/lib/schemas-data/3.2/enums/production-quality.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/production-quality.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/production-quality.json",
   "title": "Production Quality",
   "description": "Production quality tier for collection content. Maps to OpenRTB content.prodq: professional=1, prosumer=2, ugc=3. Seller-declared — no external validation.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/property-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/property-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/property-type.json",
   "title": "Property Type",
   "description": "Types of addressable advertising properties with verifiable ownership. Property types are a subset of media channels - they represent inventory surfaces that can be validated via adagents.json.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/proposal-decline-reason.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/proposal-decline-reason.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/proposal-decline-reason.json",
   "title": "Proposal Decline Reason",
   "description": "Machine-readable reason a buyer is no longer pursuing a proposal. Sellers use this only for aggregate feedback; buyers MUST NOT disclose competitor identity or confidential terms.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/proposal-refinement-reason.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/proposal-refinement-reason.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/proposal-refinement-reason.json",
   "title": "Proposal Refinement Reason",
   "description": "Machine-readable reason a proposal revision was only partially applied or could not be produced.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/proposal-status.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/proposal-status.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/proposal-status.json",
   "title": "Proposal Status",
   "description": "Lifecycle status of an immutable commercial snapshot. 'draft' is indicative, 'committed' carries firm pricing with inventory reserved until expires_at, and 'accepted' is the historical terms snapshot attached to a MediaBuy. Refining an accepted snapshot creates a new proposal ID; it never mutates or reopens the accepted snapshot.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/publisher-identifier-types.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/publisher-identifier-types.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/publisher-identifier-types.json",
   "title": "Publisher Identifier Types",
   "description": "Valid identifier types for publisher/legal entity identification",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/purchase-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/purchase-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/purchase-type.json",
   "title": "Purchase Type",
   "description": "The type of financial commitment being governed.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/reach-aggregation.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/reach-aggregation.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/reach-aggregation.json",
   "title": "Reach Aggregation",
   "description": "How reach in a cross-buy aggregate was combined. This distinction determines whether aggregate reach is a valid denominator for frequency.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/reach-unit.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/reach-unit.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/reach-unit.json",
   "title": "Reach Unit",
   "description": "Unit of measurement for reach and audience size metrics. Different channels and measurement providers count reach in fundamentally different units, making cross-channel comparison impossible without declaring the unit.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/reporting-destination-setup-state.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/reporting-destination-setup-state.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/reporting-destination-setup-state.json",
   "title": "Reporting Destination Setup State",
   "x-status": "experimental",
   "description": "Validation and setup state of a reusable reporting destination. Only ready destinations may be selected by a new account-level delivery configuration. ready is pattern-specific: file_transfer requires proven caller control of the normalized location plus a successful seller write-and-read-back probe; warehouse_materialization requires seller-verified create/commit access to the normalized locator; dataset_share requires completed recipient-side acceptance plus provider-observed recipient readability. inactive means the caller suspended the destination (active false): the seller stops initiating new deliveries to every generation within its advertised suspension interval.",

package/dist/lib/schemas-data/3.2/enums/reporting-finality.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/reporting-finality.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/reporting-finality.json",
   "title": "Reporting Finality",
   "description": "Finality of a reporting revision. Snapshot revisions are provisional and may be superseded. An official revision is the immutable, invoice-addressable close for its reporting slice and MUST NOT be superseded; later source corrections are explicit reporting adjustments rather than silent replacement revisions.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/reporting-frequency.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/reporting-frequency.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/reporting-frequency.json",
   "title": "Reporting Frequency",
   "description": "Available frequencies for delivery reports and metrics updates. Weekly and quarterly match audience-currency publication cycles in measured channels (e.g. weekly OOH/radio increments, quarterly circulation updates); post_campaign is a single report after the flight ends. Buy-side agents MUST treat a product's declared frequencies as an optimization-eligibility gate: a buyer MUST NOT make mid-flight optimization decisions against metrics whose declared cadence is quarterly or post_campaign — such data describes a period that has closed, and optimizing on it means acting on a model of the channel that is false at decision time.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/reporting-health.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/reporting-health.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/reporting-health.json",
   "title": "Reporting Health",
   "description": "Operational health for an explicitly echoed reporting scope. Aggregate precedence is action_required, delayed, then healthy. waiting applies only when no active obligation is due. action_required also applies immediately when a readable consumer-receipt revision or adjustment lacks an accepted current receipt; Reliable Reporting defines no separate receipt SLA. complete applies only when the queried scope is closed, retained coverage is complete, and every obligation has its configured required finality plus a verified readable materialization.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/representation-selection-strategy.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/representation-selection-strategy.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/representation-selection-strategy.json",
   "title": "Representation Selection Strategy",
   "description": "Deterministic strategy used after filtering a CreativeRepresentationSet against one seller destination contract. `representation_order` selects the first compatible representation in source array order. `highest_compatible_vast` is valid only when the destination format_kind is `video_vast` or `audio_vast`; it selects the compatible VAST representation with the highest exact VAST version, and equal-version ties are resolved by source array order. Using it for another format is INVALID_REQUEST and never falls back silently.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/request-signing-error-code.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/request-signing-error-code.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/request-signing-error-code.json",
   "title": "Request Signing Error Code",
   "description": "Stable request-signing transport error vocabulary returned in WWW-Authenticate: Signature error=\"<code>\" and surfaced by SDK verifiers as typed errors. These lowercase transport-profile codes are separate from the uppercase task error vocabulary in error-code.json. SDKs MUST consume enumMetadata for recovery classification instead of deriving behavior from code spelling or parsing prose.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/response-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/response-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/response-type.json",
   "title": "TMP Response Type",
   "description": "What the publisher wants back from a TMP context match. Determines the richness level of the buyer's offer response.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/restricted-attribute.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/restricted-attribute.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/restricted-attribute.json",
   "title": "Restricted Attribute",
   "description": "Personal data categories that may be restricted from use in audience targeting. Combines GDPR Article 9 special categories with US civil-rights protected classes (FHA familial_status, ADEA age). Used in two places: (1) on campaign plans via restricted_attributes to declare which categories are prohibited, and (2) on signal-definition.json via restricted_attributes to declare which categories a signal touches. Governance agents match plan restrictions against signal declarations for structural validation.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/right-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/right-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/right-type.json",
   "title": "Right Type",
   "description": "Categories of intellectual property rights that can be licensed through the brand protocol.",
   "x-status": "experimental",

package/dist/lib/schemas-data/3.2/enums/right-use.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/right-use.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/right-use.json",
   "title": "Right Use",
   "description": "Types of rights usage that can be licensed through the brand protocol. Aligned with DDEX UseType direction for interoperability with music and media rights systems.",
   "x-status": "experimental",

package/dist/lib/schemas-data/3.2/enums/rights-billing-period.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/rights-billing-period.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/rights-billing-period.json",
   "title": "Rights Billing Period",
   "description": "Billing period for brand rights pricing",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/scan-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/scan-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/scan-type.json",
   "title": "Scan Type",
   "description": "Video scan method. Modern digital delivery requires progressive scan; interlaced is retained for broadcast legacy content.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/seller-policy-decline-reason.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/seller-policy-decline-reason.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/seller-policy-decline-reason.json",
   "title": "Seller Policy Decline Reason",
   "description": "Coarse machine-readable seller-policy reason for declining a requested MediaBuy control shape. The vocabulary identifies the policy dimension without disclosing private thresholds or enforcement logic.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/si-session-status.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/si-session-status.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/si-session-status.json",
   "title": "SI Session Status",
   "description": "State of a Sponsored Intelligence session between a host and a brand agent",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/signal-catalog-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/signal-catalog-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/signal-catalog-type.json",
   "title": "Signal Availability Type",
   "description": "Commercial/provenance types for signals available for audience targeting",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/signal-source.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.3/enums/signal-source.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/signal-source.json",
   "title": "Signal Source",
   "description": "Source type for signal identifiers. Determines how the signal is referenced and whether authorization can be externally verified.",
   "type": "string",