@adcp/sdk 15.9.3 → 15.9.4

package/dist/lib/schemas-data/3.2/enums/escalation-severity.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/escalation-severity.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/escalation-severity.json",
   "title": "Escalation Severity",
   "description": "The severity level of a governance escalation.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/event-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/event-type.json",
   "title": "Event Type",
   "description": "Standard marketing event types for event logging, aligned with IAB ECAPI",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/exclusivity.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/exclusivity.json",
   "title": "Exclusivity",
   "description": "Whether a product offers exclusive access to its inventory",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/feature-check-status.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/feature-check-status.json",
   "title": "Feature Check Status",
   "description": "Per-feature evaluation outcome in content standards checks. For the two-outcome overall record verdict, see binary-verdict.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/feed-format.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/feed-format.json",
   "title": "Feed Format",
   "description": "Catalog feed formats. Determines how the platform (seller) parses items from an external feed URL. Each named value is an externally-documented feed specification a seller parses natively without buyer-supplied feed_field_mappings; values are vendor spec names (proper nouns), not semantic categories. Use `custom` + feed_field_mappings for any feed whose shape is not one of the named formats.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/feedback-source.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/feedback-source.json",
   "title": "Feedback Source",
   "description": "Source of performance feedback data",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/forecast-method.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/forecast-method.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/forecast-method.json",
   "title": "Forecast Method",
   "description": "Method used to produce a delivery forecast",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/forecast-range-unit.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/forecast-range-unit.json",
   "title": "Forecast Range Unit",
   "description": "Describes how to interpret the points array in a DeliveryForecast — what axis the curve represents",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/forecastable-metric.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/forecastable-metric.json",
   "title": "Forecastable Metric",
   "description": "Standard delivery, engagement, and availability metric names for forecasts. **Most values mirror `available-metric.json`** (the canonical closed delivery vocabulary) — `impressions`, `clicks`, `spend`, `views`, `completed_views`, `engagements`, `follows`, `saves`, `profile_visits`, `downloads`, `plays`, `reach`, `frequency`, `grps` are all shared. **Forecast-only deltas** are `audience_size`, `measured_impressions`, and `coverage_rate` — these exist here because forecasts can reasonably project them but delivery reporting today does not surface them as `available-metric` entries (delivery uses other paths: e.g., `measured_impressions` flows through `vendor_metric_values` when a third-party vendor reports it). When the industry converges on adding any of these to delivery reporting, those values graduate into `available-metric.json` and this enum's deltas shrink. For outcome/conversion forecasts (purchases, leads, app installs, etc.), use event-type enum values as metric keys instead. The ForecastPoint metrics map accepts any string key, so both forecastable-metric and event-type values can be used together.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/format-id-parameter.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/format-id-parameter.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/format-id-parameter.json",
   "title": "Format ID Parameter",
   "description": "Types of parameters that template formats accept in format_id objects to create parameterized format identifiers",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/frame-rate-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/frame-rate-type.json",
   "title": "Frame Rate Type",
   "description": "Whether the video uses a constant or variable frame rate. Broadcast and SSAI contexts require constant frame rate for seamless splicing.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/frequency-cap-control-mode.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/frequency-cap-control-mode.json",
   "title": "Frequency Cap Control Mode",
   "description": "A supported package frequency-cap control shape.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/frequency-cap-mutable-field.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/frequency-cap-mutable-field.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/frequency-cap-mutable-field.json",
   "title": "Frequency Cap Mutable Field",
   "description": "A logical frequency-cap field that a product implementation can change after creation. suppress covers the effective cooldown whether represented by suppress or the deprecated suppress_minutes alias.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/frequency-cap-scope.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/frequency-cap-scope.json",
   "title": "Frequency Cap Scope",
   "description": "Scope for frequency cap application",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/genre-taxonomy.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/genre-taxonomy.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/genre-taxonomy.json",
   "title": "Genre Taxonomy",
   "description": "Taxonomy systems for genre classification. When declared, genre values should be valid identifiers within the specified taxonomy.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/geo-level.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/geo-level.json",
   "title": "Geographic Targeting Level",
   "description": "Geographic targeting granularity levels. Some levels (metro, postal_area) require a system specification.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/gop-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/gop-type.json",
   "title": "GOP Type",
   "description": "Group of Pictures structure. SSAI and broadcast require closed GOPs for clean splice points; open GOPs may produce artifacts at ad boundaries.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/governance-decision.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/governance-decision.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/governance-decision.json",
   "title": "Governance Decision",
   "description": "Outcome of a governance check_governance call. Distinct from creative approval states (see creative-approval-status). 'conditions' is a flow-control value requiring the caller to re-call check_governance after adjusting parameters.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/governance-domain.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/governance-domain.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/governance-domain.json",
   "title": "Governance Domain",
   "description": "Governance sub-domains that a registry policy applies to. Used to indicate which types of governance agents can evaluate this policy.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/governance-mode.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/governance-mode.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/governance-mode.json",
   "title": "Governance Mode",
   "description": "Operating mode for a governance agent. Controls whether findings block execution.",
   "x-status": "experimental",

package/dist/lib/schemas-data/3.2/enums/governance-phase.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/governance-phase.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/governance-phase.json",
   "title": "Governance Phase",
   "description": "The phase of the governed action's lifecycle that triggered the governance check.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/history-entry-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/history-entry-type.json",
   "title": "History Entry Type",
   "description": "Type of entry in task execution history",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/http-method.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/http-method.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/http-method.json",
   "title": "HTTP Method",
   "description": "HTTP methods supported for webhook requests",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/identifier-types.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/identifier-types.json",
   "title": "Property Identifier Types",
   "description": "Valid identifier types for property and placement identification across different media types",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/impairment-offline-state.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/impairment-offline-state.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/impairment-offline-state.json",
   "title": "Impairment Offline State",
   "description": "Canonical offline values that may appear in impairment.transition.to. Each value is the offline endpoint of a specific resource type's lifecycle enum. The resource_type ↔ offline_state pairing is validated by the impairment.coherence assertion — not by this schema — so a single shared enum is sufficient at the field-validation layer.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/impairment-reason-code.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/impairment-reason-code.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/impairment-reason-code.json",
   "title": "Impairment Reason Code",
   "description": "Categorical reason a dependency resource entered an offline state, surfacing why a media buy is impaired. Flat shared enum across resource types — per-resource-type valid subsets are documented in enumDescriptions. Buyer agents key remediation logic off reason_code; free-text 'reason' on the impairment object carries human-readable detail.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/indicator-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/indicator-type.json",
   "title": "Indicator Type",
   "description": "A seller-asserted material risk or optimization opportunity that currently warrants buyer attention on an AdCP resource relationship. AdCP standardizes the broad meaning of each value for the protocol release; it does not standardize or version the seller's detection methodology or prescribe a universal remedy.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/installment-status.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/installment-status.json",
   "title": "Installment Status",
   "description": "Lifecycle status of an installment",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/javascript-module-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/javascript-module-type.json",
   "title": "JavaScript Module Type",
   "description": "JavaScript module format types for creative assets",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/landing-page-requirement.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/landing-page-requirement.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/landing-page-requirement.json",
   "title": "Landing Page Requirement",
   "description": "Landing page policy for creative click-through destinations",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/legacy-postal-system.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/legacy-postal-system.json",
   "title": "Country-Fused Postal Code System",
   "description": "Deprecated country-fused postal code systems for geographic targeting. Prefer postal-system with an explicit ISO 3166-1 alpha-2 country on postal area objects.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/lift-dimension.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/lift-dimension.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/lift-dimension.json",
   "title": "Lift Dimension",
   "description": "Brand-lift dimension disambiguator. Brand lift is multidimensional in production — Kantar, Upwave, Cint, DoubleVerify, and similar vendors report awareness, consideration, favorability, purchase intent, and ad recall as separate measurements with their own sample sizes and confidence intervals. Used as a `qualifier.lift_dimension` key on `committed_metrics`, `missing_metrics`, package-level delivery values (`metric_values` or `vendor_metric_values`), and `performance-feedback.metric` to disambiguate which dimension of `brand_lift` a row represents. Two `brand_lift` rows under different lift dimensions represent different surveyed outcomes and must not be combined into a single number.",
   "type": "string",

package/dist/lib/schemas-data/3.2/enums/logo-slot.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/logo-slot.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/logo-slot.json",
   "title": "Logo Slot",
   "description": "Canonical renderer-facing logo slot. Use when selecting a logo variant from brand.json for a specific UI or creative placement.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://adcontextprotocol.org/schemas/3.2.4/enums/macro-dialect.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/enums/macro-dialect.json",
   "title": "Macro Dialect Family",
   "description": "Governed family for a creative macro token. `vendor` is qualified by an authority-controlled namespace and immutable revision on the declaration/capability; AdCP does not enumerate companies as dialects. `unknown` is declaration-only and always byte-preserved.",
   "type": "string",

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.4/enums/macro-mapping-status.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/macro-processing-operation.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/macro-resolution-reason.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/macro-resolver.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/macro-value-context.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/makegood-remedy.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/markdown-flavor.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/match-id-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/match-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/media-buy-action-mode.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/media-buy-frequency-cap-control-mode.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/media-buy-health.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/media-buy-status.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/media-buy-valid-action.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/metric-scope.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/metric-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/metro-system.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/moov-atom-position.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/motion-level.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/notification-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/offering-availability-status.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/outcome-target-cost-strength.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/outcome-type.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/pacing.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/payment-terms.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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.4/enums/performance-baseline.json",
+  "$id": "https://adcontextprotocol.org/schemas/3.2.5/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",