@adcp/sdk 15.9.4 → 15.9.6

package/dist/lib/version.d.ts

@@ -1,7 +1,7 @@
 /**
  * AdCP SDK library version
  */
-export declare const LIBRARY_VERSION = "15.9.4";
+export declare const LIBRARY_VERSION = "15.9.6";
 /**
  * AdCP specification version this library is built for
  */
@@ -33,10 +33,10 @@ export type AdcpVersion = (typeof COMPATIBLE_ADCP_VERSIONS)[number];
  * Full version information
  */
 export declare const VERSION_INFO: {
-    readonly library: "15.9.4";
+    readonly library: "15.9.6";
     readonly adcp: "3.2.5";
     readonly compatibleVersions: readonly ["v2.5", "v2.6", "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"];
-    readonly generatedAt: "2026-10-16T23:12:08.652Z";
+    readonly generatedAt: "2026-10-19T00:18:00.760Z";
 };
 /**
  * Get the AdCP specification version this library is built for

package/dist/lib/version.js

@@ -31,7 +31,7 @@ __export(version_exports, {
   toReleasePrecisionVersion: () => toReleasePrecisionVersion
 });
 module.exports = __toCommonJS(version_exports);
-const LIBRARY_VERSION = "15.9.4";
+const LIBRARY_VERSION = "15.9.6";
 const ADCP_VERSION = "3.2.5";
 const ADCP_MAJOR_VERSION = 3;
 const COMPATIBLE_ADCP_VERSIONS = [
@@ -104,10 +104,10 @@ const COMPATIBLE_ADCP_VERSIONS = [
   "3.2.5"
 ];
 const VERSION_INFO = {
-  library: "15.9.4",
+  library: "15.9.6",
   adcp: "3.2.5",
   compatibleVersions: COMPATIBLE_ADCP_VERSIONS,
-  generatedAt: "2026-10-16T23:12:08.652Z"
+  generatedAt: "2026-10-19T00:18:00.760Z"
 };
 function getAdcpVersion() {
   return ADCP_VERSION;

package/dist/lib/version.mjs

@@ -1,4 +1,4 @@
-const LIBRARY_VERSION = "15.9.4";
+const LIBRARY_VERSION = "15.9.6";
 const ADCP_VERSION = "3.2.5";
 const ADCP_MAJOR_VERSION = 3;
 const COMPATIBLE_ADCP_VERSIONS = [
@@ -71,10 +71,10 @@ const COMPATIBLE_ADCP_VERSIONS = [
   "3.2.5"
 ];
 const VERSION_INFO = {
-  library: "15.9.4",
+  library: "15.9.6",
   adcp: "3.2.5",
   compatibleVersions: COMPATIBLE_ADCP_VERSIONS,
-  generatedAt: "2026-10-16T23:12:08.652Z"
+  generatedAt: "2026-10-19T00:18:00.760Z"
 };
 function getAdcpVersion() {
   return ADCP_VERSION;

package/docs/TYPE-SUMMARY.md

@@ -1,7 +1,7 @@
 # AdCP Type Summary
 
-> Generated at: 2026-10-16
-> @adcp/sdk v15.9.4
+> Generated at: 2026-10-19
+> @adcp/sdk v15.9.6
 
 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/CREATIVE-DELIVERY.md

@@ -131,9 +131,45 @@ checks the explicit `media_buy.features.canonical_creatives` declaration. A
 `unknown` because a 3.1 version claim does not prove the runtime accepts
 canonical creatives. For MCP peers the client then inspects the advertised
 input schema for the current tool only; support advertised by another creative
-tool is never reused. Unknown peers receive a legacy projection only when the
-selected product provides one unambiguous ref. Ambiguous or unavailable mappings throw
-`CreativeFormatProjectionError` before transport.
+tool is never reused.
+
+For a seller proven to serve AdCP 3.1, an otherwise unknown write uses canonical
+delivery when every selected option and creative is covered by the seller's own
+`format_options`. This follows the 3.1 buyer rule to prefer advertised format
+options over dual-emitted legacy IDs. Creative option references and kinds must
+match, including declared slots and dimensions. Sync assignments must all have
+matching selector containers. Explicit legacy capabilities or tool schemas take
+precedence; experimental declarations and options synthesized by the SDK from
+legacy IDs do not establish canonical support. This also works when a 3.2 buyer
+negotiates down to a 3.1 seller.
+
+Supply the selected product or the result of `packageRefsForFormatOptions()` in
+`creativeFormatProjection.selectorContainers`. Include `package_id` when using
+assignments. After serializing a selection, include `product_id` so the same
+client can recover the seller declaration from account-scoped product discovery,
+including product-cache hits. Product evidence applies to that request only.
+The seller remains responsible for full manifest validation.
+
+Canonical fallback requires affirmative evidence from this client's product
+discovery and an advertised `supported_versions` entry proving the seller serves
+3.1. The fallback uses synchronous discovery and successful conditional catalog
+revalidation. A saved product on a fresh client, including one synthesized from
+legacy IDs, cannot establish support by its shape alone. Rediscover the product
+in the current account and authorization scope first. Evidence expires after
+the discovery TTL (five minutes by default); product-cache hits do not extend
+it. Authorization changes and discovery invalidation invalidate the evidence.
+Request-scoped custom transports require explicit capability or tool-schema
+support and do not reuse this inferred product evidence.
+
+Assignment-only sync and updates containing only an existing `package_id` keep
+their existing wire behavior. Pass the matching selectors for this request to
+use the product-based fallback; package IDs alone do not establish support.
+Without assignments, each creative must match every supplied container; use
+assignments or split mixed-format batches when the products accept different kinds.
+
+Without matching product evidence, unknown peers receive a legacy projection
+only when the selected product provides one unambiguous ref. Ambiguous or
+unavailable mappings throw `CreativeFormatProjectionError` before transport.
 
 Schema inspection follows local JSON Pointer `$ref` targets, including `$defs`,
 and retains the complete listed document through shared discovery-cache reuse.
@@ -141,7 +177,7 @@ Unused definitions and annotations do not establish support. External references
 named anchors, and dynamic references are not resolved; inspection never fetches
 schema URLs. Cycles and traversal limits cannot force a guessed wire mode.
 
-Before building creatives, ask the client which mode that write will use:
+Before building creatives, inspect the tool's wire evidence:
 
 ```ts
 const mode = await agent.resolveCreativeFormatWireMode('sync_creatives');
@@ -150,13 +186,16 @@ const mode = await agent.resolveCreativeFormatWireMode('sync_creatives');
 This method is available on `AgentClient` and `SingleAgentClient`, accepts
 `sync_creatives`, `create_media_buy`, or `update_media_buy`, and shares the
 write path's capability discovery, tool-schema fallback, and buyer wire pin.
+This context-free check does not inspect a write's product options, so an
+`unknown` result can still become canonical for a matching 3.1 write as described
+above.
 It reuses fresh cached or primed evidence; cold discovery may make read calls,
 but it sends no mutation. Pass `{ signal, transport }` as the optional second
 argument to use the same cancellation and transport scope as the write.
 
 The result is `canonical`, `legacy`, or `unknown` (`CreativeFormatWireMode`).
-For older peers with insufficient evidence, `unknown` means projection still
-requires one unambiguous legacy reference. It does not promise canonical
+For older peers without matching product evidence, `unknown` means projection
+still requires one unambiguous legacy reference. It does not promise canonical
 support. Conflicting capability/schema evidence or missing release proof with
 a 3.2+ buyer pin throws `CreativeFormatCapabilityError`, as during a write.
 The standalone `resolveCreativeFormatWireMode(capabilities, version)` helper

package/docs/guides/VALIDATE-YOUR-AGENT.md

@@ -187,6 +187,40 @@ await comply(agentUrl, {
 });
 ```
 
+**Capabilities served at a newer release.** A 3.0 pin sends only
+`adcp_major_version: 3`, so a conformant agent may serve and echo its highest
+3.x release in `get_adcp_capabilities` (versioning spec, "Server echoes"). The
+runner validates that one response against the echoed release when the echo is
+the pin's major, is listed in the response's own `adcp.supported_versions`, and
+has a schema root. That covers discovery's `capabilities_response_schema_invalid`
+notices, `getAdcpCapabilities()` and every storyboard `response_schema` check on
+`get_adcp_capabilities`, even with `schemaRoot` set for the pin. Otherwise it
+validates strictly against the pin. Every other task's response, storyboard
+selection, the run's `adcp_version` and grading stay on the pin.
+
+The echoed release's schemas come from the SDK's bundle by default. A grader
+that ships its own roots per release can supply them with
+`servedReleaseSchemaRoots` (on `comply()`, `runStoryboard()` and
+`runStoryboardStep()`), keyed by AdCP version:
+
+```ts
+await comply(agentUrl, {
+  version: '3.0.27',
+  complianceDir: '/app/dist/compliance/3.0.27',
+  schemaRoot: '/app/dist/schemas/3.0.27',
+  servedReleaseSchemaRoots: {
+    '3.1.29': '/app/dist/schemas/3.1.29',
+    '3.2.5': '/app/dist/schemas/3.2.5',
+  },
+});
+```
+
+Those roots are used only for that capabilities validation. Each one is checked
+against its key once per process, and a mismatched or missing root throws
+before the run starts. Callers that validate outside `comply()` and the runner
+can scope the same map with `withServedReleaseSchemaRoots(roots, fn)` from
+`@adcp/sdk/testing`.
+
 **Multi-agent storyboards under `comply()`.** `comply()` grades one agent, so
 storyboards that declare `requires: [multi_agent]` (for example the
 governance-aware seller scenarios) skip with `requirement_unmet` and cap their

package/docs/llms.txt

@@ -1,7 +1,7 @@
 # Ad Context Protocol (AdCP)
 
-> Generated at: 2026-10-16
-> Library: @adcp/sdk v15.9.4
+> Generated at: 2026-10-19
+> Library: @adcp/sdk v15.9.6
 > 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

@@ -11,8 +11,8 @@ below as the publication/deployment gate.
 
 | Fact | Value |
 | --- | --- |
-| Exact npm package | `@adcp/sdk@15.9.4` |
-| npm integrity | registry-derived after publication; run `npm view @adcp/sdk@15.9.4 dist.integrity` |
+| Exact npm package | `@adcp/sdk@15.9.6` |
+| npm integrity | registry-derived after publication; run `npm view @adcp/sdk@15.9.6 dist.integrity` |
 | Node.js runtime | `^20.19.0 || >=22.12.0` |
 | Default AdCP wire release | `3.2.5` |
 | Maintained wire releases | `v2.5`, `v2.6`, `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` |
@@ -21,8 +21,8 @@ below as the publication/deployment gate.
 Install exact production inputs rather than a moving range or dist-tag:
 
 ```bash
-npm install --save-exact '@adcp/sdk@15.9.4'
-npm view '@adcp/sdk@15.9.4' dist.integrity
+npm install --save-exact '@adcp/sdk@15.9.6'
+npm view '@adcp/sdk@15.9.6' dist.integrity
 ```
 
 ### Required and optional peers

package/package.json

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