@adcp/sdk 14.0.0-rc.49 → 14.0.0-rc.50

package/dist/lib/schemas-data/3.1/core/delivery-forecast.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/delivery-forecast.json",
+  "$id": "/schemas/3.1.24/core/delivery-forecast.json",
   "title": "Delivery Forecast",
   "description": "Forecasted delivery metrics for a proposal or product allocation. Publishers attach points to help buyers evaluate expected campaign performance before purchase.",
   "type": "object",
@@ -9,16 +9,16 @@
       "type": "array",
       "description": "Forecasted delivery data points. For spend curves (default), points at ascending budget levels show how metrics scale with spend. For availability forecasts, points represent total available inventory independent of budget. See forecast_range_unit for interpretation.",
       "items": {
-        "$ref": "/schemas/3.1.18/core/forecast-point.json"
+        "$ref": "/schemas/3.1.24/core/forecast-point.json"
       },
       "minItems": 1
     },
     "forecast_range_unit": {
-      "$ref": "/schemas/3.1.18/enums/forecast-range-unit.json",
+      "$ref": "/schemas/3.1.24/enums/forecast-range-unit.json",
       "description": "How to interpret the points array. 'spend' (default when omitted): points at ascending budget levels. 'availability': total available inventory, budget omitted. 'reach_freq': points at ascending reach/frequency targets. 'weekly'/'daily': metrics are per-period values. 'clicks'/'conversions': points at ascending outcome targets. 'package': each point is a distinct inventory package."
     },
     "method": {
-      "$ref": "/schemas/3.1.18/enums/forecast-method.json",
+      "$ref": "/schemas/3.1.24/enums/forecast-method.json",
       "description": "Method used to produce this forecast"
     },
     "currency": {
@@ -26,7 +26,7 @@
       "description": "ISO 4217 currency code for monetary values in this forecast (spend, budget)"
     },
     "demographic_system": {
-      "$ref": "/schemas/3.1.18/enums/demographic-system.json",
+      "$ref": "/schemas/3.1.24/enums/demographic-system.json",
       "description": "Measurement system for the demographic field. Ensures buyer and seller agree on demographic notation."
     },
     "demographic": {
@@ -60,7 +60,7 @@
       ]
     },
     "reach_unit": {
-      "$ref": "/schemas/3.1.18/enums/reach-unit.json",
+      "$ref": "/schemas/3.1.24/enums/reach-unit.json",
       "description": "Unit of measurement for reach and audience_size metrics in this forecast. Required for cross-channel forecast comparison."
     },
     "generated_at": {
@@ -74,7 +74,7 @@
       "description": "When this forecast expires. After this time, the forecast should be refreshed. Forecast expiry does not affect proposal executability."
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/delivery-metric-aggregate.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/delivery-metric-aggregate.json",
+  "$id": "/schemas/3.1.24/core/delivery-metric-aggregate.json",
   "title": "Delivery Metric Aggregate",
   "description": "One cross-buy delivery aggregate partitioned by metric scope and qualifier. Row-symmetric with `package.committed_metrics` and delivery `missing_metrics` so buyers can reconcile by `(scope, metric_id, qualifier)`.",
   "type": "object",
@@ -16,7 +16,7 @@
           "description": "Standard metric from the closed `available-metric.json` enum."
         },
         "metric_id": {
-          "$ref": "/schemas/3.1.18/enums/available-metric.json",
+          "$ref": "/schemas/3.1.24/enums/available-metric.json",
           "description": "Identifier for the standard metric."
         },
         "qualifier": {
@@ -24,23 +24,23 @@
           "description": "Qualifier keys disambiguating this row from sibling rows under the same `metric_id`. Symmetric with `committed_metrics.qualifier` today; expected to diverge in future minors as transparency disclosures buyers don't commit to ship delivery-only. Closed (`additionalProperties: false`) — new qualifier keys ship explicitly.",
           "properties": {
             "viewability_standard": {
-              "$ref": "/schemas/3.1.18/enums/viewability-standard.json",
+              "$ref": "/schemas/3.1.24/enums/viewability-standard.json",
               "description": "Viewability standard under which this row was measured. MRC and GroupM define materially different thresholds; never sum across standards."
             },
             "completion_source": {
-              "$ref": "/schemas/3.1.18/enums/completion-source.json",
+              "$ref": "/schemas/3.1.24/enums/completion-source.json",
               "description": "Source of `completion_rate` attestation for this row — `seller_attested` from player/ad server, `vendor_attested` from a third-party measurement vendor. The two paths can yield different rates; never sum across sources."
             },
             "attribution_methodology": {
-              "$ref": "/schemas/3.1.18/enums/attribution-methodology.json",
+              "$ref": "/schemas/3.1.24/enums/attribution-methodology.json",
               "description": "Attribution methodology under which this outcome row was computed (`deterministic_purchase`, `probabilistic`, `panel_based`, `modeled`). Outcome metrics measured under different methodologies represent materially different numbers; never sum across methodologies."
             },
             "attribution_window": {
-              "$ref": "/schemas/3.1.18/core/duration.json",
+              "$ref": "/schemas/3.1.24/core/duration.json",
               "description": "Attribution window for this outcome row. Object-valued duration (`{interval, unit}`), not a shorthand string. Outcome metrics measured over different windows represent the same metric over different time periods; the partition keeps them as separate rows so buyers don't accidentally aggregate."
             },
             "lift_dimension": {
-              "$ref": "/schemas/3.1.18/enums/lift-dimension.json",
+              "$ref": "/schemas/3.1.24/enums/lift-dimension.json",
               "description": "Brand-lift dimension this row represents (awareness, consideration, favorability, purchase intent, or ad recall). Required when `metric_id` is `brand_lift`. Each dimension is a separate surveyed outcome with its own sample size and confidence interval; never sum across dimensions."
             }
           },
@@ -168,11 +168,11 @@
           "description": "Vendor-defined metric, identified by the tuple `(vendor, metric_id)`."
         },
         "vendor": {
-          "$ref": "/schemas/3.1.18/core/brand-ref.json",
+          "$ref": "/schemas/3.1.24/core/brand-ref.json",
           "description": "Vendor that defines and computes this metric. The vendor's `brand.json` `agents[type='measurement']` is the canonical anchor; metric definitions live on `get_adcp_capabilities.measurement.metrics[]`."
         },
         "metric_id": {
-          "$ref": "/schemas/3.1.18/core/vendor-metric-id.json",
+          "$ref": "/schemas/3.1.24/core/vendor-metric-id.json",
           "description": "Identifier for the metric within the vendor's vocabulary."
         },
         "qualifier": {

package/dist/lib/schemas-data/3.1/core/delivery-metrics.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/delivery-metrics.json",
+  "$id": "/schemas/3.1.24/core/delivery-metrics.json",
   "title": "Delivery Metrics",
   "description": "Standard delivery metrics that can be reported at media buy, package, or creative level",
   "type": "object",
@@ -113,7 +113,7 @@
         "type": "object",
         "properties": {
           "event_type": {
-            "$ref": "/schemas/3.1.18/enums/event-type.json",
+            "$ref": "/schemas/3.1.24/enums/event-type.json",
             "description": "The event type"
           },
           "event_source_id": {
@@ -151,7 +151,7 @@
     "reach_unit": {
       "allOf": [
         {
-          "$ref": "/schemas/3.1.18/enums/reach-unit.json"
+          "$ref": "/schemas/3.1.24/enums/reach-unit.json"
         }
       ],
       "description": "Unit of measurement for the reach field. Aligns with the reach_unit declared on optimization goals and delivery forecasts. Required when reach is present to enable cross-platform comparison."
@@ -172,7 +172,7 @@
         "period": {
           "allOf": [
             {
-              "$ref": "/schemas/3.1.18/core/duration.json"
+              "$ref": "/schemas/3.1.24/core/duration.json"
             }
           ],
           "description": "Duration of the measurement window. REQUIRED when `kind` is `period` or `rolling` — declares the snapshot length (e.g., `{\"interval\": 1, \"unit\": \"days\"}` for a daily snapshot) or the trailing-window length (e.g., `{\"interval\": 7, \"unit\": \"days\"}` for trailing-7-day rolling reach). When `kind` is `cumulative`, this field is implicit (campaign-to-date) and SHOULD be omitted."
@@ -317,7 +317,7 @@
       "description": "Viewability metrics. Viewable rate should be calculated as viewable_impressions / measurable_impressions (not total impressions), since some environments cannot measure viewability. Includes `viewed_seconds` — average in-view duration — since duration is governed by the same viewability threshold (`standard`) and shares the same `measurable_impressions` denominator. Sellers SHOULD include `standard` whenever measured viewability values are reported because MRC and GroupM rows are not interchangeable.",
       "properties": {
         "vendor": {
-          "$ref": "/schemas/3.1.18/core/brand-ref.json",
+          "$ref": "/schemas/3.1.24/core/brand-ref.json",
           "description": "Vendor that produced these viewability values. Optional but RECOMMENDED so the row is self-describing — buyer agents reading delivery in isolation can attribute the numbers without joining back to `package.committed_metrics` or `package.performance_standards`. The vendor's `brand.json` `agents[type='measurement']` is the discovery anchor; the metric definitions live on the agent's `get_adcp_capabilities.measurement.metrics[]` block. Same shape as `vendor_metric_value.vendor` for symmetry across vendor-attested surfaces."
         },
         "measurable_impressions": {
@@ -342,7 +342,7 @@
           "minimum": 0
         },
         "standard": {
-          "$ref": "/schemas/3.1.18/enums/viewability-standard.json",
+          "$ref": "/schemas/3.1.24/enums/viewability-standard.json",
           "description": "Viewability measurement standard applied to these metrics. Governs the in-view threshold for both `viewable_rate` and `viewed_seconds`."
         }
       },
@@ -411,7 +411,7 @@
         "type": "object",
         "properties": {
           "action_source": {
-            "$ref": "/schemas/3.1.18/enums/action-source.json",
+            "$ref": "/schemas/3.1.24/enums/action-source.json",
             "description": "Where the conversion occurred"
           },
           "event_source_id": {
@@ -440,7 +440,7 @@
       "type": "array",
       "description": "Reported values for vendor-defined metrics that the product's `reporting_capabilities.vendor_metrics` declared. Each entry carries the vendor (BrandRef), the metric identifier within the vendor's vocabulary, the value, optional unit, and `measurable_impressions` as the coverage denominator — vendor measurement is rarely 100% of delivered impressions, since vendors only score impressions where their SDK fires or their panel matches. When a declared vendor metric is omitted from this array, buyers infer no measurement happened (no integration). One row per `(vendor.domain, vendor.brand_id, metric_id)` per reporting period — sellers MUST de-duplicate before emission and MUST NOT emit the same vendor metric twice; buyers MAY treat duplicate rows as a seller-side conformance bug. The structured `vendor_metric_values` array is the recommended path for vendor metrics; `additionalProperties: true` on this parent object is preserved so existing free-form vendor emissions remain conformant during migration.",
       "items": {
-        "$ref": "/schemas/3.1.18/core/vendor-metric-value.json"
+        "$ref": "/schemas/3.1.24/core/vendor-metric-value.json"
       }
     }
   },

package/dist/lib/schemas-data/3.1/core/deployment.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/deployment.json",
+  "$id": "/schemas/3.1.24/core/deployment.json",
   "title": "Deployment",
   "description": "A signal deployment to a specific deployment target with activation status and key",
   "discriminator": {
@@ -28,7 +28,7 @@
           "description": "Whether signal is currently active on this deployment"
         },
         "activation_key": {
-          "$ref": "/schemas/3.1.18/core/activation-key.json",
+          "$ref": "/schemas/3.1.24/core/activation-key.json",
           "description": "The key to use for targeting. Only present if is_live=true AND requester has access to this deployment."
         },
         "estimated_activation_duration_minutes": {
@@ -71,7 +71,7 @@
           "description": "Whether signal is currently active on this deployment"
         },
         "activation_key": {
-          "$ref": "/schemas/3.1.18/core/activation-key.json",
+          "$ref": "/schemas/3.1.24/core/activation-key.json",
           "description": "The key to use for targeting. Only present if is_live=true AND requester has access to this deployment."
         },
         "estimated_activation_duration_minutes": {

package/dist/lib/schemas-data/3.1/core/destination-item.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/destination-item.json",
+  "$id": "/schemas/3.1.24/core/destination-item.json",
   "title": "Destination Item",
   "description": "A travel destination within a destination-type catalog. Carries the location, imagery, and pricing data that platforms use for destination ads and travel remarketing. Maps to Meta destination catalogs, Google travel ads, and similar formats.",
   "type": "object",
@@ -67,7 +67,7 @@
       "description": "Destination category."
     },
     "price": {
-      "$ref": "/schemas/3.1.18/core/price.json",
+      "$ref": "/schemas/3.1.24/core/price.json",
       "description": "Starting price for a trip to this destination."
     },
     "image_url": {
@@ -98,12 +98,12 @@
       "type": "array",
       "description": "Typed creative asset pools for this destination. Uses the same OfferingAssetGroup structure as offering-type catalogs. Standard group IDs: 'images_landscape' (destination hero), 'images_vertical' (9:16 for Snap, Stories), 'images_square' (1:1). Enables formats to declare typed image requirements that map unambiguously to the right asset regardless of platform.",
       "items": {
-        "$ref": "/schemas/3.1.18/core/offering-asset-group.json"
+        "$ref": "/schemas/3.1.24/core/offering-asset-group.json"
       },
       "minItems": 1
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/destination.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/destination.json",
+  "$id": "/schemas/3.1.24/core/destination.json",
   "title": "Destination",
   "description": "A deployment target where signals can be activated (DSP, sales agent, etc.)",
   "discriminator": {

package/dist/lib/schemas-data/3.1/core/diagnostic-issue.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/diagnostic-issue.json",
+  "$id": "/schemas/3.1.24/core/diagnostic-issue.json",
   "title": "Diagnostic Issue",
   "description": "An actionable issue detected during a health or readiness assessment. Used by event source health and measurement readiness to surface problems and recommendations.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/downstream-connection-requirement.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/downstream-connection-requirement.json",
+  "$id": "/schemas/3.1.24/core/downstream-connection-requirement.json",
   "title": "Downstream Connection Requirement",
   "description": "A seller/platform-side connection or grant required by a product, format, or request. This is not the AdCP caller credential: the AdCP request is still authenticated once, and the seller uses these stored downstream connections to call a platform or service on the buyer's behalf. Use this shape for platforms that require more than one downstream grant, such as an advertiser account connection plus a publisher identity or post authorization for published-post references.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/duration.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/duration.json",
+  "$id": "/schemas/3.1.24/core/duration.json",
   "title": "Duration",
   "description": "A time duration expressed as an interval and unit. Used for frequency cap windows, attribution windows, reach optimization windows, time budgets, and other time-based settings. When unit is 'campaign', interval must be 1 — the window spans the full campaign flight.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/education-item.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/education-item.json",
+  "$id": "/schemas/3.1.24/core/education-item.json",
   "title": "Education Item",
   "description": "An educational program or course within an education-type catalog. Carries the program details that platforms use for education ads and student recruitment campaigns. Maps to Google DynamicEducationAsset, schema.org Course, and similar formats.",
   "type": "object",
@@ -48,7 +48,7 @@
       "description": "Difficulty or prerequisite level."
     },
     "price": {
-      "$ref": "/schemas/3.1.18/core/price.json",
+      "$ref": "/schemas/3.1.24/core/price.json",
       "description": "Tuition or course fee."
     },
     "duration": {
@@ -99,12 +99,12 @@
       "type": "array",
       "description": "Typed creative asset pools for this program. Uses the same OfferingAssetGroup structure as offering-type catalogs. Standard group IDs: 'images_landscape' (campus/program hero), 'images_vertical' (9:16 for Stories), 'logo' (institution logo). Enables formats to declare typed image requirements that map unambiguously to the right asset regardless of platform.",
       "items": {
-        "$ref": "/schemas/3.1.18/core/offering-asset-group.json"
+        "$ref": "/schemas/3.1.24/core/offering-asset-group.json"
       },
       "minItems": 1
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/error.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/error.json",
+  "$id": "/schemas/3.1.24/core/error.json",
   "title": "Error",
   "description": "Standard error structure for task-specific errors and warnings",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/evaluator-spec.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/evaluator-spec.json",
+  "$id": "/schemas/3.1.24/core/evaluator-spec.json",
   "title": "Evaluator Spec",
   "description": "Advisory buyer-attached pointer (#5280) declaring HOW produced build_creative variants should be evaluated and ranked. The rank-side of the get_creative_features feature oracle: the chosen form is the SOURCE of feature evaluation that yields creative-feature values for each leaf, `feature_requirement` is an optional hard GATE over those values, and `rank_by` is the RANK ordering over the survivors. Informs the agent's best_of_n recommended/rank and, when the agent advertises creative.supports_evaluator, populates a per-leaf `eval` block (creative-feature-result[]) on the response.\n\nGate-then-rank pipeline (per produced leaf in a best_of_n run): the producing agent (1) evaluates the leaf via the chosen form, obtaining creative-feature values; (2) when `feature_requirement` is present, applies those predicates and DROPS any leaf that fails (internal best_of_n pruning) — survivors only; (3) orders survivors by `rank_by`. The gate operates BEFORE return: it prunes which leaves the agent recommends/returns from its own best_of_n exploration, never an AdCP-layer block of an already-produced billable leaf — what is produced and billed is governed by max_variants/max_creatives/max_spend, not by the evaluator. With no `feature_requirement`, evaluation stays advisory: every produced leaf is returned and billed and ranking is a soft preference, so `rank_by` failures rank lower but are never dropped.\n\nWhen the chosen form is `feature_agent` (or `agent_url`), the seller calls an external get_creative_features-capable agent, so the pointer is subject to the seller's `creative_policy.accepted_verifiers[]` allowlist exactly as #5280 established for provenance verify_agent: the buyer REPRESENTS which on-list agent it used, the seller (verifier-of-record) CALLS it. An off-list agent is rejected with `EVALUATOR_AGENT_NOT_ACCEPTED` (mirrors PROVENANCE_VERIFIER_NOT_ACCEPTED) before any outbound call; an on-list agent that is unreachable or unknown degrades to seller-default ranking with an advisory errors[] note (non-terminal), NOT a failure.\n\nEvaluator credentials and caller-supplied trust material are never carried in this object, `context`, `ext`, or the creative payload. The producing creative agent authenticates its outbound call to the evaluator on the transport (RFC 9421 request signing/JWKS, mTLS, or a pre-provisioned Bearer/API-key credential). Credential- or trust-material payload keys (for example `api_key`, `client_secret`, `authorization`, `jwk`, `jwks`, or `jwks_uri`) are non-conforming and should be rejected with `CREDENTIAL_IN_ARGS`.\n\nProvide exactly one of three forms; an optional `feature_requirement` gate, an optional `rank_by` ordering, an optional `feature_agent` allowlisted pointer, and a shared optional eval_budget apply to whichever form is chosen. Feature discovery uses the existing governance.creative_features catalog on get_adcp_capabilities; evaluator outputs reuse creative-feature-result[] and do not mint a parallel verdict/result surface. `evaluator_id` is not discovered from governance.creative_features: it is a pre-provisioned, account-arranged preset whose emitted feature_ids still come from that catalog.\n\nExperimental (x-status: experimental): this whole evaluator surface — the `evaluator` input, the per-leaf `eval` response block, and `creative.supports_evaluator` — is new and not yet field-tested across parties. Sellers that implement it MUST list `creative.evaluator` in `experimental_features`. Reserved 3.x follow-ons that may reshape these fields: a separate `supports_evaluator_gate` capability and a hard MUST-enforce-gate semantic. Per docs/reference/experimental-status, it MAY change between 3.x releases with notice.",
   "x-status": "experimental",
@@ -10,7 +10,7 @@
       "type": "array",
       "description": "Optional hard GATE over creative-feature values — the predicates a leaf MUST satisfy for the producing agent to recommend/return it. Reuses the feature-requirement shape (min_value/max_value for quantitative features like creative_quality_score, allowed_values for binary/categorical) — the same predicate vocabulary that gates property/audience filters, which its own schema names as an intended creative-gate reuse. A leaf that fails any predicate is DROPPED from the agent's best_of_n survivors before ranking — this is internal pruning of which leaves the agent recommends, not an AdCP-layer block of an already-produced billable leaf (what is produced/billed is governed by max_variants/max_creatives/max_spend). Distinct from `rank_by`: the gate is a pass/fail predicate (drop on fail), `rank_by` is an ordering over survivors. Each predicate's `if_not_covered` (exclude|include, default exclude) is the fail-open knob when the source cannot measure that feature. A pass/warn/fail verdict is expressed as a categorical string feature value gated via `allowed_values` (e.g. [\"pass\"] or [\"pass\",\"warn\"]) — the buyer's predicate decides whether warn passes; the verdict is derived, never stored on creative-feature-result. Omit to leave evaluation advisory (no leaf is dropped).",
       "items": {
-        "$ref": "/schemas/3.1.18/core/feature-requirement.json"
+        "$ref": "/schemas/3.1.24/core/feature-requirement.json"
       },
       "minItems": 1
     },
@@ -79,7 +79,7 @@
       "additionalProperties": true
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "oneOf": [
@@ -97,14 +97,14 @@
             "pass": {
               "type": "array",
               "items": {
-                "$ref": "/schemas/3.1.18/content-standards/artifact.json"
+                "$ref": "/schemas/3.1.24/content-standards/artifact.json"
               },
               "description": "Artifacts exemplifying variants the buyer considers good — the high end (≈1) of the calibrated prediction feature."
             },
             "fail": {
               "type": "array",
               "items": {
-                "$ref": "/schemas/3.1.18/content-standards/artifact.json"
+                "$ref": "/schemas/3.1.24/content-standards/artifact.json"
               },
               "description": "Artifacts exemplifying variants the buyer considers bad — the low end (≈0) of the calibrated prediction feature."
             }

package/dist/lib/schemas-data/3.1/core/event-custom-data.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/event-custom-data.json",
+  "$id": "/schemas/3.1.24/core/event-custom-data.json",
   "title": "Event Custom Data",
   "description": "Event-specific data for attribution and reporting",
   "type": "object",
@@ -90,7 +90,7 @@
       }
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.1/core/event-source-health.json

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/event-source-health.json",
+  "$id": "/schemas/3.1.24/core/event-source-health.json",
   "title": "Event Source Health",
   "description": "Health assessment for a configured event source. Sellers evaluate the quality, completeness, and volume of events received from this source. Sellers with native quality scores (Snap EQS, Meta EMQ) relay them in detail; sellers without native scores derive status from operational metrics (volume, error rates, tag activity).",
   "type": "object",
   "properties": {
     "status": {
-      "$ref": "/schemas/3.1.18/enums/assessment-status.json",
+      "$ref": "/schemas/3.1.24/enums/assessment-status.json",
       "description": "Overall health status. Use this for cross-seller decisions — do not rely on detail.score for comparability. 'insufficient' covers the source-offline case (zero events received over the seller's evaluation window) — disambiguate via `events_received_24h: 0` and a stale `last_event_at`. Sellers MUST surface a corresponding impairment (reason_code: source_offline) on any active media buy whose conversion goals depend on an event source that has gone offline."
     },
     "detail": {
@@ -59,7 +59,7 @@
       "type": "array",
       "description": "Actionable issues detected with this event source. Sellers should limit to the top 3-5 most actionable items. Buyer agents should sort by severity rather than relying on array position.",
       "items": {
-        "$ref": "/schemas/3.1.18/core/diagnostic-issue.json"
+        "$ref": "/schemas/3.1.24/core/diagnostic-issue.json"
       }
     }
   },

package/dist/lib/schemas-data/3.1/core/event-surface.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/event-surface.json",
+  "$id": "/schemas/3.1.24/core/event-surface.json",
   "title": "Event Surface",
   "description": "Structured context for the surface where an event source or logged event originated. Use this when the flat `action_source` is too coarse, such as a creator channel, social profile, podcast feed, newsletter list, or another owned platform property. `category` is a closed vocabulary so buyers can reason generically; `property_type` and `namespace` are open strings so new platforms and property shapes do not require a schema change. The flat `action_source` remains for backward compatibility. When `category` matches an ActionSource value, producers SHOULD set `action_source` to the same value. When `category` is `owned_property`, producers SHOULD keep the most compatible flat `action_source` for legacy consumers, commonly `system_generated` for platform-native events or `other` when no closer value applies.",
   "type": "object",
@@ -53,7 +53,7 @@
       "x-entity": "property"
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/event.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/event.json",
+  "$id": "/schemas/3.1.24/core/event.json",
   "title": "Event",
   "description": "A marketing event (conversion, engagement, or custom) for attribution and optimization",
   "type": "object",
@@ -12,7 +12,7 @@
       "maxLength": 256
     },
     "event_type": {
-      "$ref": "/schemas/3.1.18/enums/event-type.json",
+      "$ref": "/schemas/3.1.24/enums/event-type.json",
       "description": "Standard event type"
     },
     "event_time": {
@@ -21,19 +21,19 @@
       "description": "ISO 8601 timestamp when the event occurred"
     },
     "user_match": {
-      "$ref": "/schemas/3.1.18/core/user-match.json",
+      "$ref": "/schemas/3.1.24/core/user-match.json",
       "description": "User identifiers for attribution matching"
     },
     "custom_data": {
-      "$ref": "/schemas/3.1.18/core/event-custom-data.json",
+      "$ref": "/schemas/3.1.24/core/event-custom-data.json",
       "description": "Event-specific data (value, currency, items, etc.)"
     },
     "action_source": {
-      "$ref": "/schemas/3.1.18/enums/action-source.json",
+      "$ref": "/schemas/3.1.24/enums/action-source.json",
       "description": "Where the event originated"
     },
     "surface": {
-      "$ref": "/schemas/3.1.18/core/event-surface.json",
+      "$ref": "/schemas/3.1.24/core/event-surface.json",
       "description": "Optional structured surface context for the event, such as an owned channel, profile, feed, podcast, newsletter list, website, app, or store. Complements `action_source`; use it when optimization-relevant meaning would otherwise live only in platform-specific `ext` metadata."
     },
     "event_source_url": {
@@ -46,7 +46,7 @@
       "description": "Name for custom events (used when event_type is 'custom')"
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "allOf": [
@@ -69,7 +69,7 @@
           "custom_data": {
             "allOf": [
               {
-                "$ref": "/schemas/3.1.18/core/event-custom-data.json"
+                "$ref": "/schemas/3.1.24/core/event-custom-data.json"
               },
               {
                 "anyOf": [

package/dist/lib/schemas-data/3.1/core/ext.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/ext.json",
+  "$id": "/schemas/3.1.24/core/ext.json",
   "title": "Extension Object",
   "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/feature-requirement.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/feature-requirement.json",
+  "$id": "/schemas/3.1.24/core/feature-requirement.json",
   "title": "Feature Requirement",
   "description": "A feature-based requirement — a reusable predicate over a feature value. Used by property list filters today; designed for reuse in other surfaces (audience filters, creative gates) in future versions. Use min_value/max_value for quantitative features, allowed_values for binary/categorical features.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/flight-item.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/flight-item.json",
+  "$id": "/schemas/3.1.24/core/flight-item.json",
   "title": "Flight Item",
   "description": "A flight route within a flight-type catalog. Carries origin/destination, airline, pricing, and schedule data that platforms use for flight ads and dynamic travel remarketing. Maps to Google DynamicFlightsAsset, Meta flight catalogs, and similar formats.",
   "type": "object",
@@ -52,7 +52,7 @@
       "description": "Airline name or IATA airline code."
     },
     "price": {
-      "$ref": "/schemas/3.1.18/core/price.json",
+      "$ref": "/schemas/3.1.24/core/price.json",
       "description": "Ticket price or starting fare."
     },
     "description": {
@@ -91,12 +91,12 @@
       "type": "array",
       "description": "Typed creative asset pools for this flight. Uses the same OfferingAssetGroup structure as offering-type catalogs. Standard group IDs: 'images_landscape' (destination hero), 'images_vertical' (9:16 for Stories), 'images_square' (1:1). Enables formats to declare typed image requirements that map unambiguously to the right asset regardless of platform.",
       "items": {
-        "$ref": "/schemas/3.1.18/core/offering-asset-group.json"
+        "$ref": "/schemas/3.1.24/core/offering-asset-group.json"
       },
       "minItems": 1
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/forecast-dimension-audience.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/forecast-dimension-audience.json",
+  "$id": "/schemas/3.1.24/core/forecast-dimension-audience.json",
   "title": "Audience Forecast Dimension",
   "description": "An audience segment dimension for a ForecastPoint row. Variant of ForecastPoint dimensions; see forecast-point-dimensions.json for dispatch rules.",
   "type": "object",
@@ -16,7 +16,7 @@
       "x-entity": "audience"
     },
     "audience_source": {
-      "$ref": "/schemas/3.1.18/enums/audience-source.json",
+      "$ref": "/schemas/3.1.24/enums/audience-source.json",
       "description": "Origin of the audience segment."
     },
     "audience_name": {

package/dist/lib/schemas-data/3.1/core/forecast-dimension-device-platform.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/forecast-dimension-device-platform.json",
+  "$id": "/schemas/3.1.24/core/forecast-dimension-device-platform.json",
   "title": "Device Platform Forecast Dimension",
   "description": "An operating-system or platform dimension for a ForecastPoint row. Variant of ForecastPoint dimensions; see forecast-point-dimensions.json for dispatch rules.",
   "type": "object",
@@ -11,7 +11,7 @@
       "description": "Dimension family discriminator."
     },
     "device_platform": {
-      "$ref": "/schemas/3.1.18/enums/device-platform.json",
+      "$ref": "/schemas/3.1.24/enums/device-platform.json",
       "description": "Operating system or platform for this forecast row."
     }
   },

package/dist/lib/schemas-data/3.1/core/forecast-dimension-device-type.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/core/forecast-dimension-device-type.json",
+  "$id": "/schemas/3.1.24/core/forecast-dimension-device-type.json",
   "title": "Device Type Forecast Dimension",
   "description": "A device form-factor dimension for a ForecastPoint row. Variant of ForecastPoint dimensions; see forecast-point-dimensions.json for dispatch rules.",
   "type": "object",
@@ -11,7 +11,7 @@
       "description": "Dimension family discriminator."
     },
     "device_type": {
-      "$ref": "/schemas/3.1.18/enums/device-type.json",
+      "$ref": "/schemas/3.1.24/enums/device-type.json",
       "description": "Device form factor for this forecast row."
     }
   },