@adcp/sdk 6.6.0 → 6.7.0

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.1/core/education-item.json",
+  "$id": "/schemas/3.0.5/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.0.1/core/price.json",
+      "$ref": "/schemas/3.0.5/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.0.1/core/offering-asset-group.json"
+        "$ref": "/schemas/3.0.5/core/offering-asset-group.json"
       },
       "minItems": 1
     },
     "ext": {
-      "$ref": "/schemas/3.0.1/core/ext.json"
+      "$ref": "/schemas/3.0.5/core/ext.json"
     }
   },
   "required": [

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.1/core/error.json",
+  "$id": "/schemas/3.0.5/core/error.json",
   "title": "Error",
   "description": "Standard error structure for task-specific errors and warnings",
   "type": "object",
@@ -17,7 +17,7 @@
     },
     "field": {
       "type": "string",
-      "description": "Field path associated with the error (e.g., 'packages[0].targeting')"
+      "description": "Field path associated with the error in JSONPath-lite format (e.g., 'packages[0].targeting'). When `issues[]` is also present, sellers MUST set this to `issues[0].pointer` translated from RFC 6901 to JSONPath-lite (e.g., '/packages/0/targeting' → 'packages[0].targeting') so pre-3.1 consumers reading `field` only get deterministic behavior. Will be deprecated in a future major version in favor of `issues[].pointer`."
     },
     "suggestion": {
       "type": "string",
@@ -29,9 +29,40 @@
       "minimum": 1,
       "maximum": 3600
     },
+    "issues": {
+      "type": "array",
+      "description": "Structured list of validation failures. Primary use is `VALIDATION_ERROR`, where multi-field rejections are common and `field` (singular) cannot carry the full pointer map. MAY appear on other error codes that reject multiple fields at once. When `issues` is present, sellers MUST also populate `field` from `issues[0]` for backward compatibility with pre-3.1 consumers that read `field` only — translating the RFC 6901 `pointer` format to the JSONPath-lite format `field` uses (e.g., `/packages/0/targeting` → `packages[0].targeting`). MUST (not SHOULD) so consumers reading `field` get deterministic behavior across sellers — the cost is one line of dual-write per seller; the cost of SHOULD is a long tail of seller-A-vs-seller-B inconsistency. Future major versions will deprecate `field` in favor of `issues[].pointer`.",
+      "items": {
+        "type": "object",
+        "properties": {
+          "pointer": {
+            "type": "string",
+            "description": "RFC 6901 JSON Pointer to the offending field in the request payload (e.g., '/packages/0/targeting/geo_countries/2'). Format chosen to match Ajv's native validation output (`instancePath`); standardized and unambiguous on keys containing `/` or `~`. NOTE: this differs from the legacy top-level `field` which uses JSONPath-lite (`packages[0].targeting.geo_countries[2]`). When sellers populate `field` from `issues[0].pointer` for backward compatibility (see `field` description), they MUST translate the format — `/packages/0/x` → `packages[0].x`. Future major versions will deprecate `field` in favor of `issues[].pointer`."
+          },
+          "message": {
+            "type": "string",
+            "description": "Human-readable description of why this specific field was rejected."
+          },
+          "keyword": {
+            "type": "string",
+            "description": "Schema keyword that rejected the payload, drawn from the JSON Schema vocabulary (e.g., 'required', 'type', 'format', 'enum', 'pattern', 'minimum', 'maxLength'). Matches the keyword names emitted by JSON Schema validators (Ajv, jsonschema, etc.) so agents can pattern-match on rejection class without parsing message text. Implementers SHOULD use the validator's native keyword name; do not invent custom values here."
+          },
+          "schemaPath": {
+            "type": "string",
+            "description": "Optional. Path inside the schema that rejected the payload (e.g., '#/properties/packages/items/properties/targeting/oneOf/1'). Sellers SHOULD NOT emit on production-facing endpoints — `schemaPath` leaks which `oneOf` branch the validator selected before semantic rejection, which is a probe oracle for adversarial callers crafting payloads against polymorphic unions. Sellers MAY emit in dev/sandbox modes where the diagnostic value outweighs the fingerprinting risk."
+          }
+        },
+        "required": [
+          "pointer",
+          "message",
+          "keyword"
+        ],
+        "additionalProperties": true
+      }
+    },
     "details": {
       "type": "object",
-      "description": "Additional task-specific error details",
+      "description": "Additional task-specific error details. Sellers MAY mirror `issues[]` here as `details.issues` for backward compatibility with pre-3.1 consumers reading from `details`; new consumers SHOULD prefer the top-level `issues` field.",
       "additionalProperties": true
     },
     "recovery": {

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

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

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

@@ -1,12 +1,12 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.1/core/event-source-health.json",
+  "$id": "/schemas/3.0.5/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.0.1/enums/assessment-status.json",
+      "$ref": "/schemas/3.0.5/enums/assessment-status.json",
       "description": "Overall health status. Use this for cross-seller decisions — do not rely on detail.score for comparability."
     },
     "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.0.1/core/diagnostic-issue.json"
+        "$ref": "/schemas/3.0.5/core/diagnostic-issue.json"
       }
     }
   },

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.1/core/event.json",
+  "$id": "/schemas/3.0.5/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.0.1/enums/event-type.json",
+      "$ref": "/schemas/3.0.5/enums/event-type.json",
       "description": "Standard event type"
     },
     "event_time": {
@@ -21,15 +21,15 @@
       "description": "ISO 8601 timestamp when the event occurred"
     },
     "user_match": {
-      "$ref": "/schemas/3.0.1/core/user-match.json",
+      "$ref": "/schemas/3.0.5/core/user-match.json",
       "description": "User identifiers for attribution matching"
     },
     "custom_data": {
-      "$ref": "/schemas/3.0.1/core/event-custom-data.json",
+      "$ref": "/schemas/3.0.5/core/event-custom-data.json",
       "description": "Event-specific data (value, currency, items, etc.)"
     },
     "action_source": {
-      "$ref": "/schemas/3.0.1/enums/action-source.json",
+      "$ref": "/schemas/3.0.5/enums/action-source.json",
       "description": "Where the event originated"
     },
     "event_source_url": {
@@ -42,7 +42,7 @@
       "description": "Name for custom events (used when event_type is 'custom')"
     },
     "ext": {
-      "$ref": "/schemas/3.0.1/core/ext.json"
+      "$ref": "/schemas/3.0.5/core/ext.json"
     }
   },
   "required": [

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

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.1/core/ext.json",
+  "$id": "/schemas/3.0.5/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.0/core/feature-requirement.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.1/core/feature-requirement.json",
+  "$id": "/schemas/3.0.5/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.0/core/flight-item.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.1/core/flight-item.json",
+  "$id": "/schemas/3.0.5/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.0.1/core/price.json",
+      "$ref": "/schemas/3.0.5/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.0.1/core/offering-asset-group.json"
+        "$ref": "/schemas/3.0.5/core/offering-asset-group.json"
       },
       "minItems": 1
     },
     "ext": {
-      "$ref": "/schemas/3.0.1/core/ext.json"
+      "$ref": "/schemas/3.0.5/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.0/core/forecast-point.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.1/core/forecast-point.json",
+  "$id": "/schemas/3.0.5/core/forecast-point.json",
   "title": "Forecast Point",
   "description": "A forecast data point. When budget is present, the point pairs a spend level with expected delivery — multiple points at ascending budgets form a curve. When budget is omitted, the point represents total available inventory for the requested targeting and dates, independent of spend.",
   "type": "object",
@@ -25,56 +25,56 @@
       "description": "Forecasted metric values. Keys are forecastable-metric enum values for delivery/engagement or event-type enum values for outcomes. Values are ForecastRange objects (low/mid/high). Use { \"mid\": value } for point estimates. When budget is present, these are the expected metrics at that spend level. When budget is omitted, these represent total available inventory — use spend to express the estimated cost. Additional keys beyond the documented properties are allowed for event-type values (purchase, lead, app_install, etc.).",
       "properties": {
         "audience_size": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "reach": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "frequency": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "impressions": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "clicks": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "spend": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "views": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "completed_views": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "grps": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "engagements": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "follows": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "saves": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "profile_visits": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "measured_impressions": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "downloads": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         },
         "plays": {
-          "$ref": "/schemas/3.0.1/core/forecast-range.json"
+          "$ref": "/schemas/3.0.5/core/forecast-range.json"
         }
       },
       "additionalProperties": {
-        "$ref": "/schemas/3.0.1/core/forecast-range.json"
+        "$ref": "/schemas/3.0.5/core/forecast-range.json"
       }
     }
   },

package/dist/lib/schemas-data/3.0/core/forecast-range.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.1/core/forecast-range.json",
+  "$id": "/schemas/3.0.5/core/forecast-range.json",
   "title": "Forecast Range",
   "description": "A forecast value with optional confidence bounds. Either mid (point estimate) or both low and high (range) must be provided. mid represents the most likely outcome. low and high represent conservative and optimistic estimates. All three can be provided together.",
   "type": "object",

package/dist/lib/schemas-data/3.0/core/format-id.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.0.1/core/format-id.json",
+  "$id": "/schemas/3.0.5/core/format-id.json",
   "title": "Format Reference (Structured Object)",
   "description": "A JSON object — never a plain string — that identifies a creative format by its declaring agent and local slug. Required properties: agent_url (URI of the agent that owns the format) and id (slug matching [a-zA-Z0-9_-]+). Example: {\"agent_url\": \"https://creative.adcontextprotocol.org\", \"id\": \"display_300x250\"}. Can reference: (1) a concrete format with fixed dimensions (id only), (2) a template format without parameters (id only), or (3) a template format with parameters (id + dimensions/duration). Template formats accept parameters in format_id while concrete formats have fixed dimensions in their definition. Parameterized format IDs create unique, specific format variants. Using a plain string here is a schema violation.",
   "x-entity": "creative_format",