@adcp/sdk 15.9.6 → 15.9.7

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/feed-format.json",
+  "$id": "/schemas/3.1.30/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.1/enums/feedback-source.json

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/forecast-range-unit.json",
+  "$id": "/schemas/3.1.30/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.1/enums/forecastable-metric.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/forecastable-metric.json",
+  "$id": "/schemas/3.1.30/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.1/enums/format-id-parameter.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/format-id-parameter.json",
+  "$id": "/schemas/3.1.30/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.1/enums/frame-rate-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/frame-rate-type.json",
+  "$id": "/schemas/3.1.30/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.1/enums/frequency-cap-scope.json

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

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/genre-taxonomy.json",
+  "$id": "/schemas/3.1.30/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.1/enums/geo-level.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/geo-level.json",
+  "$id": "/schemas/3.1.30/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.1/enums/gop-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/gop-type.json",
+  "$id": "/schemas/3.1.30/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.1/enums/governance-decision.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/governance-decision.json",
+  "$id": "/schemas/3.1.30/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.1/enums/governance-domain.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/governance-domain.json",
+  "$id": "/schemas/3.1.30/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.1/enums/governance-mode.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/governance-mode.json",
+  "$id": "/schemas/3.1.30/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.1/enums/governance-phase.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/governance-phase.json",
+  "$id": "/schemas/3.1.30/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.1/enums/history-entry-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/history-entry-type.json",
+  "$id": "/schemas/3.1.30/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.1/enums/http-method.json

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/impairment-offline-state.json",
+  "$id": "/schemas/3.1.30/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.1/enums/impairment-reason-code.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/impairment-reason-code.json",
+  "$id": "/schemas/3.1.30/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.1/enums/installment-status.json

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

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/javascript-module-type.json",
+  "$id": "/schemas/3.1.30/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.1/enums/landing-page-requirement.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/landing-page-requirement.json",
+  "$id": "/schemas/3.1.30/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.1/enums/legacy-postal-system.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/legacy-postal-system.json",
+  "$id": "/schemas/3.1.30/enums/legacy-postal-system.json",
   "title": "Legacy 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.1/enums/lift-dimension.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/lift-dimension.json",
+  "$id": "/schemas/3.1.30/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`, `metric_aggregates`, 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.1/enums/logo-slot.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/logo-slot.json",
+  "$id": "/schemas/3.1.30/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.1/enums/makegood-remedy.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/makegood-remedy.json",
+  "$id": "/schemas/3.1.30/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.1/enums/markdown-flavor.json

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

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/match-id-type.json",
+  "$id": "/schemas/3.1.30/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.1/enums/match-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/match-type.json",
+  "$id": "/schemas/3.1.30/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.1/enums/media-buy-action-mode.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/media-buy-action-mode.json",
+  "$id": "/schemas/3.1.30/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 an asynchronous human approval. 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.1/enums/media-buy-health.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/media-buy-health.json",
+  "$id": "/schemas/3.1.30/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.1/enums/media-buy-status.json

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

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/media-buy-valid-action.json",
+  "$id": "/schemas/3.1.30/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.1/enums/metric-scope.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/metric-scope.json",
+  "$id": "/schemas/3.1.30/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.1/enums/metric-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/metric-type.json",
+  "$id": "/schemas/3.1.30/enums/metric-type.json",
   "title": "Metric Type (Deprecated)",
   "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' }`.",
   "type": "string",

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

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

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/moov-atom-position.json",
+  "$id": "/schemas/3.1.30/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.1/enums/notification-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/notification-type.json",
+  "$id": "/schemas/3.1.30/enums/notification-type.json",
   "title": "Notification Type",
   "description": "Type of push notification fired by a seller agent. Media-buy-anchored notifications (`scheduled`, `final`, `delayed`, `adjusted`, `impairment`) fire against a media buy's `push_notification_config`. Account-anchored notifications (`creative.status_changed`, `creative.purged`, `product.*`, `signal.*`, `wholesale_feed.bulk_change`) fire against an account's `notification_configs[]` entries whose `event_types` include the value — these outlive any single media buy and anchor at the account. Account-anchored does not mean lifecycle events for the account object itself; no `account.*` event type is currently defined. Account status changes are observed through `list_accounts` polling or the one-shot `sync_accounts.push_notification_config` async result channel. Wholesale feed notifications carry the actual change payload in `/schemas/core/wholesale-feed-webhook.json`; receivers use `get_products` / `get_signals` with `if_wholesale_feed_version` to repair or reconcile. New notification types added to this enum MUST declare their anchor (media-buy or account) and per-type `notification_id` semantics in the enumDescription. Sellers MUST reject `notification_configs[]` entries whose `event_types` include any media-buy-anchored type, and MUST reject `push_notification_config` registrations for account-anchored types.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/offering-availability-status.json",
+  "$id": "/schemas/3.1.30/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.1/enums/outcome-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/outcome-type.json",
+  "$id": "/schemas/3.1.30/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.1/enums/pacing.json

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/performance-standard-metric.json",
+  "$id": "/schemas/3.1.30/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.1/enums/policy-category.json

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

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/policy-enforcement.json",
+  "$id": "/schemas/3.1.30/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.1/enums/postal-system.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/postal-system.json",
+  "$id": "/schemas/3.1.30/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.1/enums/preview-output-format.json

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/production-quality.json",
+  "$id": "/schemas/3.1.30/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.1/enums/property-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/property-type.json",
+  "$id": "/schemas/3.1.30/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.1/enums/proposal-status.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/proposal-status.json",
+  "$id": "/schemas/3.1.30/enums/proposal-status.json",
   "title": "Proposal Status",
   "description": "Lifecycle status of a proposal. This is the per-proposal signal for whether finalization is required before create_media_buy. Absent means the proposal is ready to buy (backward compatible with pre-v3.1 proposals). 'draft' indicates indicative pricing that must be finalized before purchase. 'committed' indicates firm pricing with inventory reserved until expires_at.",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/publisher-identifier-types.json",
+  "$id": "/schemas/3.1.30/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.1/enums/purchase-type.json

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

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/reach-unit.json",
+  "$id": "/schemas/3.1.30/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.1/enums/reporting-frequency.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/reporting-frequency.json",
+  "$id": "/schemas/3.1.30/enums/reporting-frequency.json",
   "title": "Reporting Frequency",
   "description": "Available frequencies for delivery reports and metrics updates",
   "type": "string",

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/response-type.json",
+  "$id": "/schemas/3.1.30/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.1/enums/restricted-attribute.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/restricted-attribute.json",
+  "$id": "/schemas/3.1.30/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.1/enums/right-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/right-type.json",
+  "$id": "/schemas/3.1.30/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.1/enums/right-use.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.29/enums/right-use.json",
+  "$id": "/schemas/3.1.30/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.1/enums/rights-billing-period.json

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