@adcp/sdk 16.0.0-beta.7 → 16.0.0-beta.9

package/dist/lib/validation/schema-loader.js

@@ -80,6 +80,12 @@ function isRuntimeSchemaDirectory(name) {
   return name !== "bundled" && !TRANSPORT_PROJECTION_DIRECTORIES.has(name);
 }
 function resolveBundleKey(version) {
+  if (/^v?2(?:\.|$)/.test(version)) {
+    throw new import_errors.ConfigurationError(
+      "AdCP 2 reached end of life on 2026-08-01; only AdCP 3 schema bundles are supported.",
+      "adcpVersion"
+    );
+  }
   const minorOnly = version.match(/^(\d+)\.(\d+)$/);
   if (minorOnly) return `${minorOnly[1]}.${minorOnly[2]}`;
   const releasePrecisionPre = version.match(/^(\d+)\.(\d+)-[0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*$/);

package/dist/lib/validation/schema-loader.mjs

@@ -24,6 +24,12 @@ function isRuntimeSchemaDirectory(name) {
   return name !== "bundled" && !TRANSPORT_PROJECTION_DIRECTORIES.has(name);
 }
 function resolveBundleKey(version) {
+  if (/^v?2(?:\.|$)/.test(version)) {
+    throw new ConfigurationError(
+      "AdCP 2 reached end of life on 2026-08-01; only AdCP 3 schema bundles are supported.",
+      "adcpVersion"
+    );
+  }
   const minorOnly = version.match(/^(\d+)\.(\d+)$/);
   if (minorOnly) return `${minorOnly[1]}.${minorOnly[2]}`;
   const releasePrecisionPre = version.match(/^(\d+)\.(\d+)-[0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*$/);

package/dist/lib/validation/schema-validator.js

@@ -26,7 +26,6 @@ __export(schema_validator_exports, {
 });
 module.exports = __toCommonJS(schema_validator_exports);
 var import_schema_loader = require('./schema-loader.js');
-var import_version = require('../version.js');
 var import_hints = require('./hints.js');
 var import_envelope_status_compat = require('../utils/envelope-status-compat.js');
 var import_diagnostic_limits = require('./diagnostic-limits.js');
@@ -310,29 +309,6 @@ function validateRequest(toolName, payload, version) {
     ...rootSchemaId && { schemaId: rootSchemaId }
   };
 }
-function stripEnvelopeNulls(payload, schema) {
-  if (payload == null || typeof payload !== "object" || Array.isArray(payload)) return payload;
-  const s = schema;
-  if (!s) return payload;
-  const properties = s.properties;
-  if (!properties) return payload;
-  const required = new Set(Array.isArray(s.required) ? s.required : []);
-  const payloadObj = payload;
-  let cloned = null;
-  for (const [key, value] of Object.entries(payloadObj)) {
-    if (value !== null) continue;
-    if (required.has(key)) continue;
-    const propSchema = properties[key];
-    if (!propSchema) continue;
-    const type = propSchema.type;
-    const isNullable = type === "null" || Array.isArray(type) && type.includes("null");
-    if (!isNullable) {
-      if (!cloned) cloned = { ...payloadObj };
-      delete cloned[key];
-    }
-  }
-  return cloned ?? payload;
-}
 function selectResponseVariant(payload) {
   if (payload && typeof payload === "object" && "status" in payload) {
     const status = payload.status;
@@ -349,8 +325,7 @@ function validateResponse(toolName, payload, version) {
   const effective = validator ?? (variant !== "sync" ? (0, import_schema_loader.getValidator)(toolName, "sync", version) : void 0);
   if (!effective) return OK;
   const rootSchema = effective.schema;
-  const isV2Bundle = version != null && (0, import_version.parseAdcpMajorVersion)(version) === 2;
-  const normalizedPayload = isV2Bundle ? stripEnvelopeNulls(compatPayload, rootSchema) : compatPayload;
+  const normalizedPayload = compatPayload;
   const valid = effective(normalizedPayload);
   const usedVariant = validator ? variant : "sync";
   const variantFallback = !validator && variant !== "sync";

package/dist/lib/validation/schema-validator.mjs

@@ -1,5 +1,4 @@
 import { getValidator, getRegisteredSchemaIds } from "./schema-loader.mjs";
-import { parseAdcpMajorVersion } from "../version.mjs";
 import { findHint } from "./hints.mjs";
 import { injectLegacyEnvelopeStatus } from "../utils/envelope-status-compat.mjs";
 import { boundValidationIssues } from "./diagnostic-limits.mjs";
@@ -283,29 +282,6 @@ function validateRequest(toolName, payload, version) {
     ...rootSchemaId && { schemaId: rootSchemaId }
   };
 }
-function stripEnvelopeNulls(payload, schema) {
-  if (payload == null || typeof payload !== "object" || Array.isArray(payload)) return payload;
-  const s = schema;
-  if (!s) return payload;
-  const properties = s.properties;
-  if (!properties) return payload;
-  const required = new Set(Array.isArray(s.required) ? s.required : []);
-  const payloadObj = payload;
-  let cloned = null;
-  for (const [key, value] of Object.entries(payloadObj)) {
-    if (value !== null) continue;
-    if (required.has(key)) continue;
-    const propSchema = properties[key];
-    if (!propSchema) continue;
-    const type = propSchema.type;
-    const isNullable = type === "null" || Array.isArray(type) && type.includes("null");
-    if (!isNullable) {
-      if (!cloned) cloned = { ...payloadObj };
-      delete cloned[key];
-    }
-  }
-  return cloned ?? payload;
-}
 function selectResponseVariant(payload) {
   if (payload && typeof payload === "object" && "status" in payload) {
     const status = payload.status;
@@ -322,8 +298,7 @@ function validateResponse(toolName, payload, version) {
   const effective = validator ?? (variant !== "sync" ? getValidator(toolName, "sync", version) : void 0);
   if (!effective) return OK;
   const rootSchema = effective.schema;
-  const isV2Bundle = version != null && parseAdcpMajorVersion(version) === 2;
-  const normalizedPayload = isV2Bundle ? stripEnvelopeNulls(compatPayload, rootSchema) : compatPayload;
+  const normalizedPayload = compatPayload;
   const valid = effective(normalizedPayload);
   const usedVariant = validator ? variant : "sync";
   const variantFallback = !validator && variant !== "sync";

package/dist/lib/version.d.mts

@@ -1,7 +1,7 @@
 /**
  * AdCP SDK library version
  */
-export declare const LIBRARY_VERSION = "16.0.0-beta.7";
+export declare const LIBRARY_VERSION = "16.0.0-beta.9";
 /**
  * AdCP specification version this library is built for
  */
@@ -19,7 +19,7 @@ export declare const ADCP_MAJOR_VERSION = 3;
  * this list by hand; bumping the AdCP pin via `npm run sync-version`
  * extends it.
  */
-export declare const COMPATIBLE_ADCP_VERSIONS: 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"];
+export declare const COMPATIBLE_ADCP_VERSIONS: readonly ["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"];
 /**
  * String literal union of every AdCP version the SDK formally supports.
  *
@@ -33,10 +33,10 @@ export type AdcpVersion = (typeof COMPATIBLE_ADCP_VERSIONS)[number];
  * Full version information
  */
 export declare const VERSION_INFO: {
-    readonly library: "16.0.0-beta.7";
+    readonly library: "16.0.0-beta.9";
     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-17T13:58:28.444Z";
+    readonly compatibleVersions: readonly ["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-19T19:41:05.601Z";
 };
 /**
  * Get the AdCP specification version this library is built for

package/dist/lib/version.d.ts

@@ -1,7 +1,7 @@
 /**
  * AdCP SDK library version
  */
-export declare const LIBRARY_VERSION = "16.0.0-beta.7";
+export declare const LIBRARY_VERSION = "16.0.0-beta.9";
 /**
  * AdCP specification version this library is built for
  */
@@ -19,7 +19,7 @@ export declare const ADCP_MAJOR_VERSION = 3;
  * this list by hand; bumping the AdCP pin via `npm run sync-version`
  * extends it.
  */
-export declare const COMPATIBLE_ADCP_VERSIONS: 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"];
+export declare const COMPATIBLE_ADCP_VERSIONS: readonly ["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"];
 /**
  * String literal union of every AdCP version the SDK formally supports.
  *
@@ -33,10 +33,10 @@ export type AdcpVersion = (typeof COMPATIBLE_ADCP_VERSIONS)[number];
  * Full version information
  */
 export declare const VERSION_INFO: {
-    readonly library: "16.0.0-beta.7";
+    readonly library: "16.0.0-beta.9";
     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-17T13:58:28.444Z";
+    readonly compatibleVersions: readonly ["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-19T19:41:05.601Z";
 };
 /**
  * Get the AdCP specification version this library is built for

package/dist/lib/version.js

@@ -31,12 +31,10 @@ __export(version_exports, {
   toReleasePrecisionVersion: () => toReleasePrecisionVersion
 });
 module.exports = __toCommonJS(version_exports);
-const LIBRARY_VERSION = "16.0.0-beta.7";
+const LIBRARY_VERSION = "16.0.0-beta.9";
 const ADCP_VERSION = "3.2.5";
 const ADCP_MAJOR_VERSION = 3;
 const COMPATIBLE_ADCP_VERSIONS = [
-  "v2.5",
-  "v2.6",
   "v3",
   "3.0.0",
   "3.0",
@@ -104,10 +102,10 @@ const COMPATIBLE_ADCP_VERSIONS = [
   "3.2.5"
 ];
 const VERSION_INFO = {
-  library: "16.0.0-beta.7",
+  library: "16.0.0-beta.9",
   adcp: "3.2.5",
   compatibleVersions: COMPATIBLE_ADCP_VERSIONS,
-  generatedAt: "2026-10-17T13:58:28.444Z"
+  generatedAt: "2026-10-19T19:41:05.601Z"
 };
 function getAdcpVersion() {
   return ADCP_VERSION;

package/dist/lib/version.mjs

@@ -1,9 +1,7 @@
-const LIBRARY_VERSION = "16.0.0-beta.7";
+const LIBRARY_VERSION = "16.0.0-beta.9";
 const ADCP_VERSION = "3.2.5";
 const ADCP_MAJOR_VERSION = 3;
 const COMPATIBLE_ADCP_VERSIONS = [
-  "v2.5",
-  "v2.6",
   "v3",
   "3.0.0",
   "3.0",
@@ -71,10 +69,10 @@ const COMPATIBLE_ADCP_VERSIONS = [
   "3.2.5"
 ];
 const VERSION_INFO = {
-  library: "16.0.0-beta.7",
+  library: "16.0.0-beta.9",
   adcp: "3.2.5",
   compatibleVersions: COMPATIBLE_ADCP_VERSIONS,
-  generatedAt: "2026-10-17T13:58:28.444Z"
+  generatedAt: "2026-10-19T19:41:05.601Z"
 };
 function getAdcpVersion() {
   return ADCP_VERSION;

package/docs/TYPE-SUMMARY.md

@@ -1,7 +1,7 @@
 # AdCP Type Summary
 
-> Generated at: 2026-10-17
-> @adcp/sdk v16.0.0-beta.7
+> Generated at: 2026-10-19
+> @adcp/sdk v16.0.0-beta.9
 
 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/development/PROTOCOL_DIFFERENCES.md

@@ -333,4 +333,4 @@ Look for messages like:
 - [MCP Specification](https://spec.modelcontextprotocol.io)
 - [A2A Protocol Documentation](https://github.com/AgentProtocol/A2A)
 - [AdCP Specification](https://github.com/adcontextprotocol/adcp)
-- [Wire-version compat playbook](https://adcontextprotocol.github.io/adcp-client/development/WIRE-VERSION-COMPAT.md) — orthogonal but commonly conflated with transport differences. Read this if you're touching how the SDK adapts requests/responses across AdCP major versions (v3 ↔ v2.5), not just MCP vs A2A.
+- [Wire-version compat playbook](https://adcontextprotocol.github.io/adcp-client/development/WIRE-VERSION-COMPAT.md) — orthogonal but commonly conflated with transport differences. Read this when adapting requests/responses across maintained AdCP 3 releases. AdCP 2 wire translation was [removed in SDK 16](../migration-drop-adcp-2.md); transport differences remain independent of the selected AdCP release.

package/docs/guides/CONFORMANCE.md

@@ -282,6 +282,31 @@ provenance manifest first. Resolve the release tag to its full commit, then use
 file and verify the release bundle's `.tgz.sha256` sidecar before updating the
 manifest. The command never accepts moving branches or unverified content.
 
+## Property-list reference credential isolation
+
+The storyboard runner implements `check: property_list_reference` and the
+`property_list_reference_runner` requirement for MCP. The protocol-authored
+`universal/property-list-reference-resolution` storyboard creates a shared list
+and a control list under the owner identity. Its probe then starts a fresh MCP
+session with only the issued reference Bearer token, follows every page, checks
+the exact identifier set, and requires authorization denials for a cross-list
+read and a name-changing update. Owner credentials, accounts, cookies, and
+signing keys are never forwarded into that session. The check needs no extra
+runner configuration beyond the storyboard's sandbox/controller setup.
+It uses the MCP endpoint already discovered by the owner client, with a fresh
+transport that does not inherit the owner's `transport.trustedFetchFn`.
+
+Evidence includes initialization, each page, and both denial probes; issued
+tokens are redacted from creation responses and diagnostic strings. Explicit
+A2A runs report `requirement_unmet` before fixture setup or task calls because
+the credential-isolated probe currently implements the MCP baseline.
+
+The storyboard is authored for the next AdCP minor release and is not in the
+bundled 3.2.5 compliance cache. Until that release, load its YAML from a local
+copy of spec PR #8289 and use `runStoryboard` with that checkout's schema root.
+
+Upstream contract: [adcp#8289](https://github.com/adcontextprotocol/adcp/pull/8289).
+
 ## Trusted Match Context router replay
 
 Context Match routers expose raw `POST /context`, not an MCP or A2A tool. A

package/docs/guides/CREATIVE-BUILD-PROBE.md

@@ -0,0 +1,156 @@
+# Creative evaluator build probes
+
+A storyboard may opt into `creative_build_probe: {context_prefix: build,
+message: "Create one sandbox creative"}`. The full runner and standalone step
+runner prepare one route/input binding before controller seeding or dispatch,
+and then enable `creative_build_probe_runner`. Author the gated steps with
+`requires_contract: creative_build_probe_runner` so older engines give no
+executed security credit.
+
+Provision the sandbox account, build entitlement, task authorization, and
+accepted evaluator endpoint separately. Complete format metadata does not prove
+these account/task prerequisites. The resolver does not issue a hidden build.
+
+`test_kit.creative_build_probes` accepts recipes `{match: [...], input: {...}}`.
+Match clauses use the existing fixture-resolution DSL against the catalog entry.
+The operator asserts that the input is valid for **every** matched route for this
+account. Input can contain message, creative_manifest, creative_id, transformer_id,
+config and legacy target_format_id; it cannot replace evaluator, account, auth or trust material. Use a
+specific capability-ID predicate when a kind-only predicate is insufficient.
+Full manifest schema validation runs before dispatch. Config requires a transformer;
+provision its live parameter values and an appropriate output route. Library IDs,
+transformers, source asset URLs, and account authorization are operator fixtures.
+
+The automatic generation path requires a unique advertised build route,
+supports_generation, technical_requirements_complete, a known non-custom kind,
+empty params, and no unhandled declaration metadata (descriptive identity/preference/channel metadata is inert).
+It supplies the brief and `{format_kind: selectedKind, assets: {}}`. Otherwise a
+matched recipe is required; omitted catalog operations still mean build and
+missing catalog IDs remain discoverable but unaddressable through capability-ID routing. Non-build entries and
+unsatisfiable routes do not prevent selecting a later satisfiable route.
+
+Resolved records use fixture_type `creative_format`, the prefix as handle, exact
+matched requirements, and seller_ids.capability_id or seller_ids.format_id. Unsatisfied whole runs have a
+fixture_unsatisfied coverage gap and zero executed security validations; standalone
+steps use skip_reason fixture_unsatisfied and canonical not_applicable, with detail
+naming creative_format:<prefix>. This does not establish producer nonconformance
+or passing security coverage. Malformed catalogs produce a structured failed validation; malformed operator recipes throw authoring errors during applicable preparation
+with the required schemas available. Unavailable catalog/schema prerequisites
+can return a zero-credit fixture gap before exhaustive recipe diagnostics. Routed and
+replicated runs currently report an explicit gap before seeding; run each agent
+independently. Unopted storyboards retain their existing behavior and counters.
+
+The protocol-side harness contract and consuming fixture are tracked in
+[adcp#8240](https://github.com/adcontextprotocol/adcp/issues/8240).
+
+## Payload-bound authorization limitation
+
+Current probe preparation requires a sandbox build fixture that does not need
+a per-request signed governance_context. The runner detects an advertised
+build_creative signed_context enforcement claim and reports fixture_unsatisfied
+with zero security credit; static recipes cannot pre-sign the fresh request.
+Other governed tasks do not disable this build probe. Preparing fresh governed
+probe authorizations is a separate runner integration, not a protocol decision.
+
+Recipe fields stay exactly as provisioned: omitting message does not add the
+storyboard's generation brief. The automatic source manifest is validated too.
+Descriptive metadata (display_name, seller_preference, experimental,
+sample_render_url, format_option_id, publisher_domain, applies_to_channels,
+canonical_formats_only) does not remove security coverage. Unknown metadata and
+constraint-bearing extensions require an operator recipe. The probe-local
+unambiguous-source/config rules do not add restrictions to build_creative wire
+requests in other modes, including refinement.
+
+Operator recipe authoring is bounded to 100,000 traversed nodes, 4 MiB of UTF-8
+string/key bytes, and the existing JSON depth bound per recipe. Repeated aliases
+count on every visit, before match normalization. These are harness configuration
+limits, not producer catalog requirements. Missing required selected-version
+validators yield a zero-credit harness gap; they never authorize a dispatch.
+
+
+## Selected-version routing
+
+The runner uses the existing guarded capabilities-echo authority for catalog
+interpretation. A same-major release-precision echo must be listed in the
+response's supported_versions and have an available bundled or supplied schema
+root. Invalid, missing, unlisted or unavailable echoes retain the pin. Supplied
+servedReleaseSchemaRoots apply to the catalog only. The runner captures build
+request, source-manifest and target-FormatID validators from the pin before
+activating any served catalog root, including overlapping version aliases.
+The public five-argument resolveCreativeBuildProbe works on an already selected
+creative catalog and uses its supplied pin only; it has no full capabilities
+response from which to select an echo. Full and standalone runners use the
+internal preparation path for guarded served-release selection.
+
+Catalog kind, parameter, ID and operation semantics follow that served release;
+build selectors and source inputs retain the request pin. Canonical route IDs
+and automatic generation require canonical routing in both releases. Otherwise
+use a provisioned legacy selector and pinned-valid input; do not synthesize a
+named format or upgrade the request. An advertised 3.2 legacy reference's density
+constraints still apply when a 3.1 request treats pixel_ratio as an opaque
+extension: the old request cannot establish a 2x parameterized binding by adding
+that field. An incompatible binding is a fixture gap, not producer failure.
+
+The reverse direction retains the older catalog's parameter rules. A 3.1
+reference cannot establish density through an omitted or opaque pixel_ratio
+field. Actual named-format requirements still apply: the published 3.1 narrowing
+rule uses an any-value baseline only where the projected legacy requirements
+impose no constraint. A provisioned, live-valid 3.2 target at 2x can
+therefore match a 3.1 reference with no ratio, even if the old payload carries
+an opaque ratio extension. The resolver does not union property sets or invent
+a 1x default for that older catalog. The operator must still provision a valid
+named-format mapping and input for the selected account.
+
+Local schema diagnostics display at most eight AJV error entries and 2048
+escaped characters. Control characters are escaped for display; producer
+catalogs and failed validation outcomes remain unchanged.
+
+Read the selected capabilities schema's format reference and selected build request
+selector. A 3.2 recipe normally binds the advertised capability ID; a provisioned legacy selector remains supported when the selected request declares it. A 3.1 recipe must supply
+an existing schema-valid `target_format_id` and assert that its discovered or
+provisioned named format maps to every matched catalog route. The resolver never
+constructs a named format from a capability ID. Missing legacy capability IDs are
+legal. Without a provisioned legacy selector there is a coverage gap; an unknown
+extra `target_capability_id` is not a valid 3.1 routing contract. Automatic generation
+is restricted to capability-ID routing. Unknown 3.1 canonical kinds remain intact
+as unsupported routes while resolution continues to understood routes. Older
+catalogs do not acquire 3.2 ID-pattern or operations-field producer requirements.
+
+Transformer-only recipes need no dummy brief/source manifest. Provision valid live
+configuration and matching transformer output_capability_ids (3.2) or
+output_format_ids (legacy). Recipe messages are trusted operator-authored input and
+remain exactly as supplied; banning a brief would not prevent a dishonest fixture
+author from biasing other input content. Credential-key and URL checks reject known
+aliases but cannot prove opaque values or custom encodings secret-free. Operators
+must provision non-secret fixture content. A malformed recipe throws an authoring
+error after the runner closes any receiver/connections it owns.
+
+
+An explicit legacy selector recipe is also supported on newer versions that retain
+`target_format_id`; bind exactly one selector. Recipes cannot override
+`canonical_formats_only: true` or contradict an advertised `v1_format_ref` pairing.
+Reference agent URLs use existing canonicalization, and declared dimensions/duration
+must agree. Incompatible pairs are unavailable; continue to another usable route.
+
+
+Resolution certifies preparation of the selected route/input, not complete catalog
+conformance. Unknown legacy kinds remain unvalidated local unsupported routes;
+the consuming storyboard must retain its required whole-response discovery schema
+validation. A standalone boundary step grades its selected probe, not unrelated
+catalog metadata. The evaluator storyboard keeps that independent required check.
+
+
+The provisioned brief is sent as `build_creative.message` to the agent under test,
+where its model may read it as instructions. Author ordinary creative direction;
+do not include instructions about evaluator behavior or expected test verdicts.
+An explicit runner `test_kit` overrides the storyboard's declared kit as a whole:
+include recipes in that override when also supplying auth. Hosted auth defaults
+preserve recipes explicitly supplied by the operator; they do not merge missing
+recipes from a separately declared brand kit.
+
+The normal hosted HTTP/UI flow does not expose arbitrary recipe uploads. Use trusted
+programmatic runner options or the local CLI for operator-provisioned recipes.
+
+The preparer checks the selected route/input binding. It does not certify all
+unselected recipe matches or remote account entitlements; narrow the operator
+match predicates when an input is valid for only one route.

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