@adcp/sdk 17.0.0-beta.6 → 17.0.0-beta.8

package/dist/lib/version.mjs

@@ -1,4 +1,4 @@
-const LIBRARY_VERSION = "17.0.0-beta.6";
+const LIBRARY_VERSION = "17.0.0-beta.8";
 const ADCP_VERSION = "3.3.0-beta.1";
 const ADCP_MAJOR_VERSION = 3;
 const COMPATIBLE_ADCP_VERSIONS = [
@@ -73,10 +73,10 @@ const COMPATIBLE_ADCP_VERSIONS = [
   "3.3-beta.1"
 ];
 const VERSION_INFO = {
-  library: "17.0.0-beta.6",
+  library: "17.0.0-beta.8",
   adcp: "3.3.0-beta.1",
   compatibleVersions: COMPATIBLE_ADCP_VERSIONS,
-  generatedAt: "2026-10-29T19:03:50.550Z"
+  generatedAt: "2026-10-30T04:24:20.449Z"
 };
 function getAdcpVersion() {
   return ADCP_VERSION;

package/docs/TYPE-SUMMARY.md

@@ -1,7 +1,7 @@
 # AdCP Type Summary
 
-> Generated at: 2026-10-29
-> @adcp/sdk v17.0.0-beta.6
+> Generated at: 2026-10-30
+> @adcp/sdk v17.0.0-beta.8
 
 Curated reference of the types that matter for using the AdCP client. For full generated types see `src/lib/types/tools.generated.ts` and `src/lib/types/core.generated.ts`.
 

package/docs/guides/WHOLESALE-PAGE-COLLECTION.md

@@ -0,0 +1,67 @@
+# Collecting a wholesale product feed in a storyboard
+
+Set `collect_product_pages: true` on a `get_products` wholesale step when its
+checks need products beyond the seller's first page. Ordinary steps continue to
+make one request. Declare the intrinsic runtime requirement so an older runner
+reports missing coverage before fixture setup instead of ignoring the new flag:
+
+```yaml
+requires: [collect_product_pages_runner]
+phases:
+  - id: discovery
+    steps:
+      - id: complete_catalog
+        task: get_products
+        collect_product_pages: true
+        sample_request:
+          buying_mode: wholesale
+          pagination: { max_results: 25 }
+          account: { account_id: seller-issued-account }
+        validations:
+          - check: field_contains
+            path: products[*].product_id
+            value: expected-product
+```
+
+The first request is unconditional and must omit a continuation cursor. The
+runner preserves account, filters, fields, context, extensions,
+and the authored page size on each continuation. It follows every cursor,
+validates every response, rejects duplicate identities and broken cursors, and
+restarts when the feed identity changes. It permits at most three restarts,
+1,000 physical requests, 100,000 products, and 100,000 advisory errors. Exhausting a budget fails the
+logical read and never publishes a successful partial snapshot.
+
+Collection requires fresh reads without `idempotency_key`. An authored key or
+runtime-injected key is rejected before dispatch; the runner never silently
+rewrites or removes a key. Each cursor page and restarted read has a different
+request body, so reusing a key could conflict with a seller's optional read
+replay protection. The SDK does not automatically add a key to these wholesale
+reads. Ordinary one-page steps keep their existing key behavior.
+
+Per-page validation still requires the response schema's required Product
+fields. Forwarding `fields` does not relax schema validation for projections.
+
+Authored field checks and context captures use
+`product_page_collection.logical_response`. Its products and advisory errors
+combine all pages of the final stable enumeration, including pages beyond the
+response-retention limit. A restart discards their abandoned counterparts. Other
+envelope fields are representative metadata from the first stable page; this
+feature does not merge arbitrary response fields or extension definitions. The ordinary `response` and
+`response_record` retain an actual physical page; they never masquerade as a
+merged seller response. Each page has its own request, response, extraction,
+schema disposition, and restart number under `product_page_collection.pages`.
+Logical-check pointers are prefixed with
+`/product_page_collection/logical_response`. Physical schema and invariant
+failures cite the actual page exchange instead.
+
+Every physical page runs the step's enabled invariants before response-evidence
+retention limits apply, including pages later abandoned during a restart. The
+report retains the first 16 page responses and every request. Later responses
+carry an explicit retention marker; failing checks still retain their actual
+page evidence. Unknown or custom pricing remains visibly unproven under its
+existing invariant contract.
+
+Expected-error probes, raw authentication probes, parallel dispatch, conditional
+feed reads, and response-derived skip gates cannot be combined with collection.
+Credentialed functional steps through the official protocol client remain
+supported. `runStoryboardStep` exposes the same complete view and page checks.

package/docs/llms.txt

@@ -1,7 +1,7 @@
 # Ad Context Protocol (AdCP)
 
-> Generated at: 2026-10-29
-> Library: @adcp/sdk v17.0.0-beta.6
+> Generated at: 2026-10-30
+> Library: @adcp/sdk v17.0.0-beta.8
 > AdCP major version: 3
 > Canonical URL: https://adcontextprotocol.github.io/adcp-client/llms.txt
 > Note: the `Library` stamp reflects the package.json version at doc-generation time. The narrative below describes the surface that lands on the next-published minor — including any 6.7 helpers documented here ahead of the release tag.

package/docs/migration-14.x-rc-worksheet.md

@@ -16,8 +16,8 @@ pin using `ADCP_VERSION` inside that tarball.
 
 | Fact | Value |
 | --- | --- |
-| Checkout `package.json` version | `@adcp/sdk@17.0.0-beta.6` |
-| npm integrity | registry-derived after publication; run `npm view @adcp/sdk@17.0.0-beta.6 dist.integrity` |
+| Checkout `package.json` version | `@adcp/sdk@17.0.0-beta.8` |
+| npm integrity | registry-derived after publication; run `npm view @adcp/sdk@17.0.0-beta.8 dist.integrity` |
 | Node.js runtime | `^20.19.0 || >=22.12.0` |
 | Default AdCP wire release | `3.3.0-beta.1` |
 | Maintained wire releases | `v3`, `3.0.0`, `3.0`, `3.0.1`, `3.0.2`, `3.0.3`, `3.0.4`, `3.0.5`, `3.0.6`, `3.0.7`, `3.0.8`, `3.0.9`, `3.0.10`, `3.0.11`, `3.0.12`, `3.0.13`, `3.0.14`, `3.0.15`, `3.0.16`, `3.0.17`, `3.0.18`, `3.0.19`, `3.0.20`, `3.0.21`, `3.0.22`, `3.0.23`, `3.0.24`, `3.0.25`, `3.1.0`, `3.1`, `3.1.1`, `3.1.2`, `3.1.3`, `3.1.4`, `3.1.5`, `3.1.6`, `3.1.7`, `3.1.8`, `3.1.9`, `3.1.10`, `3.1.11`, `3.1.12`, `3.1.13`, `3.1.14`, `3.1.15`, `3.1.16`, `3.1.17`, `3.1.18`, `3.1.19`, `3.1.20`, `3.1.21`, `3.1.22`, `3.1.23`, `3.1.24`, `3.1.25`, `3.1.26`, `3.1.27`, `3.1.28`, `3.1.29`, `3.2.1`, `3.2`, `3.2.2`, `3.2.3`, `3.2.4`, `3.2.5`, `3.2.6`, `3.2.7`, `3.3.0-beta.1`, `3.3-beta.1` |
@@ -26,8 +26,8 @@ pin using `ADCP_VERSION` inside that tarball.
 For a checkout at the published release commit, install the exact package version:
 
 ```bash
-npm install --save-exact '@adcp/sdk@17.0.0-beta.6'
-npm view '@adcp/sdk@17.0.0-beta.6' dist.integrity
+npm install --save-exact '@adcp/sdk@17.0.0-beta.8'
+npm view '@adcp/sdk@17.0.0-beta.8' dist.integrity
 ```
 
 ### Required and optional peers

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adcp/sdk",
-  "version": "17.0.0-beta.6",
+  "version": "17.0.0-beta.8",
   "description": "AdCP SDK — client, server, and compliance harnesses for the AdContext Protocol (MCP + A2A)",
   "workspaces": [
     ".",