@adcp/sdk 15.9.3 → 15.9.4

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

@@ -6,22 +6,22 @@ Your checklist to get from "agent boots" to "agent ships." Every tool below is a
 
 ```bash
 # 1. Does it answer at all? (60s)
-npx @adcp/sdk@adcp-3.2 http://localhost:3001/mcp get_adcp_capabilities '{}'              # MCP
-npx @adcp/sdk@adcp-3.2 --protocol a2a http://localhost:3001 get_adcp_capabilities '{}'   # A2A (preview)
+npx @adcp/sdk@15.9 http://localhost:3001/mcp get_adcp_capabilities '{}'              # MCP
+npx @adcp/sdk@15.9 --protocol a2a http://localhost:3001 get_adcp_capabilities '{}'   # A2A (preview)
 
 # 2. Does it walk the golden path? (2–5 min)
-npx @adcp/sdk@adcp-3.2 storyboard run http://localhost:3001/mcp --auth $TOKEN            # MCP
-npx @adcp/sdk@adcp-3.2 storyboard run --protocol a2a http://localhost:3001 --auth $TOKEN # A2A (preview)
+npx @adcp/sdk@15.9 storyboard run http://localhost:3001/mcp --auth $TOKEN            # MCP
+npx @adcp/sdk@15.9 storyboard run --protocol a2a http://localhost:3001 --auth $TOKEN # A2A (preview)
 
 # 3. Does it crash on weird inputs? (1–3 min)
-npx @adcp/sdk@adcp-3.2 fuzz http://localhost:3001/mcp --auth-token $TOKEN
+npx @adcp/sdk@15.9 fuzz http://localhost:3001/mcp --auth-token $TOKEN
 
 # 4. Does webhook/async conformance pass? (2–5 min)
-npx @adcp/sdk@adcp-3.2 storyboard run http://localhost:3001/mcp \
+npx @adcp/sdk@15.9 storyboard run http://localhost:3001/mcp \
   --webhook-receiver --auth $TOKEN
 
 # 5. Does it survive horizontal scaling? (same as 2, two URLs)
-npx @adcp/sdk@adcp-3.2 storyboard run \
+npx @adcp/sdk@15.9 storyboard run \
   --url https://a.agent.example/mcp --url https://b.agent.example/mcp \
   sales-guaranteed --auth $TOKEN
 ```
@@ -32,7 +32,7 @@ If all five pass and your skill's specialism-specific checks below pass, you're
 
 **Working on the agent locally?** Before you reach for the remote-agent commands above, see [`VALIDATE-LOCALLY.md`](./VALIDATE-LOCALLY.md) — the same storyboards, zero tunnel setup, ten lines of code. Point `--local-agent <module>` at your handlers or call `runAgainstLocalAgent` directly from a test file.
 
-**Why `@adcp-3.2` in every `npx` command?** The tag pins the runner to the AdCP 3.2 line (SDK 14). `@latest` moves to the next protocol line when one ships, so a CI job that uses it can start grading against a different contract without a change on your side. Agents still on AdCP 3.1 should substitute `@adcp/sdk@adcp-3.1` (SDK 13, the maintained 3.1 line) in every command. The explicit tag also avoids stale `npx` cache reuse from `~/.npm/_npx/`. If an old cache is causing confusing behavior, `rm -rf ~/.npm/_npx` clears all cached CLI versions.
+**Why `@15.9` in every `npx` command?** It pins the runner to the current stable maintenance line, which is what ships the compliance caches these commands select. The `@latest` tag moves when a new line ships, so a CI job using it can start grading against a different contract with no change on your side — and the protocol-line tags (`@adcp/sdk@adcp-3.2`, `@adcp/sdk@adcp-3.1`) are frozen legacy pointers at older SDK majors that do **not** receive new caches, so pairing one with an exact `--compliance-version` below would fail. Pin the exact published SDK version in CI (for example `npx @adcp/sdk@15.9.4`) and, to see which compliance versions your install actually packages, pass an unrecognised value — `adcp storyboard list --compliance-version ?` — whose error enumerates them. The explicit pin also avoids stale `npx` cache reuse from `~/.npm/_npx/`; if an old cache is causing confusing behavior, `rm -rf ~/.npm/_npx` clears all cached CLI versions.
 
 ---
 
@@ -60,22 +60,22 @@ The main compliance entry point. Runs every storyboard that applies to your agen
 
 ```bash
 # Full capability-driven run — resolves bundles from your capabilities
-npx @adcp/sdk@adcp-3.2 storyboard run http://localhost:3001/mcp --auth $TOKEN
+npx @adcp/sdk@15.9 storyboard run http://localhost:3001/mcp --auth $TOKEN
 
 # Single bundle or storyboard by id
-npx @adcp/sdk@adcp-3.2 storyboard run http://localhost:3001/mcp sales-guaranteed --auth $TOKEN
+npx @adcp/sdk@15.9 storyboard run http://localhost:3001/mcp sales-guaranteed --auth $TOKEN
 
 # Specific tracks only (faster feedback when iterating)
-npx @adcp/sdk@adcp-3.2 storyboard run http://localhost:3001/mcp --tracks core,products --auth $TOKEN
+npx @adcp/sdk@15.9 storyboard run http://localhost:3001/mcp --tracks core,products --auth $TOKEN
 
 # Pin a specific compliance cache/spec line
-npx @adcp/sdk@adcp-3.2 storyboard run http://localhost:3001/mcp --compliance-version 3.1.24 --auth $TOKEN
+npx @adcp/sdk@15.9 storyboard run http://localhost:3001/mcp --compliance-version 3.1.29 --auth $TOKEN
 
 # Ad-hoc YAML (new storyboards under development)
-npx @adcp/sdk@adcp-3.2 storyboard run http://localhost:3001/mcp --file ./my-wip.yaml --auth $TOKEN
+npx @adcp/sdk@15.9 storyboard run http://localhost:3001/mcp --file ./my-wip.yaml --auth $TOKEN
 
 # JSON report for CI / tooling
-npx @adcp/sdk@adcp-3.2 storyboard run http://localhost:3001/mcp --json > report.json
+npx @adcp/sdk@15.9 storyboard run http://localhost:3001/mcp --json > report.json
 ```
 
 For a publisher split across sales, signals, governance, or creative tenants,
@@ -180,10 +180,10 @@ Programmatic runners can pair the two directories explicitly as well:
 import { comply } from '@adcp/sdk/testing';
 
 await comply(agentUrl, {
-  version: '3.0.12',
-  complianceDir: '/app/dist/compliance/3.0.12',
-  schemaRoot: '/app/dist/schemas/3.0.12',
-  adcpVersion: '3.0.12',
+  version: '3.1.29',
+  complianceDir: '/app/dist/compliance/3.1.29',
+  schemaRoot: '/app/dist/schemas/3.1.29',
+  adcpVersion: '3.1.29',
 });
 ```
 
@@ -240,12 +240,12 @@ test, and shared by the routed agents.
 
 ```bash
 # (a) pre-save tokens
-npx @adcp/sdk@adcp-3.2 --save-auth my-agent https://agent.example.com/mcp --oauth
-npx @adcp/sdk@adcp-3.2 storyboard run my-agent
+npx @adcp/sdk@15.9 --save-auth my-agent https://agent.example.com/mcp --oauth
+npx @adcp/sdk@15.9 storyboard run my-agent
 
 # (b) inline on first run
-npx @adcp/sdk@adcp-3.2 --save-auth my-agent https://agent.example.com/mcp --no-auth
-npx @adcp/sdk@adcp-3.2 storyboard run my-agent --oauth
+npx @adcp/sdk@15.9 --save-auth my-agent https://agent.example.com/mcp --no-auth
+npx @adcp/sdk@15.9 storyboard run my-agent --oauth
 ```
 
 Either way, subsequent runs reuse the cached tokens (auto-refresh on expiry via the stored `refresh_token`). Raw URLs don't support `--oauth` — save an alias first.
@@ -260,27 +260,27 @@ Generates schema-valid requests, calls your agent, checks every response under t
 
 ```bash
 # Tier 1 + Tier 2 stateless + referential (safe, no mutation)
-npx @adcp/sdk@adcp-3.2 fuzz http://localhost:3001/mcp --auth-token $TOKEN
+npx @adcp/sdk@15.9 fuzz http://localhost:3001/mcp --auth-token $TOKEN
 
 # Reproducible (rerun with same seed to repro a failure)
-npx @adcp/sdk@adcp-3.2 fuzz http://localhost:3001/mcp --seed 42 --auth-token $TOKEN
+npx @adcp/sdk@15.9 fuzz http://localhost:3001/mcp --seed 42 --auth-token $TOKEN
 
 # Pre-seeded ID pools for referential tools (Tier 2)
-npx @adcp/sdk@adcp-3.2 fuzz http://localhost:3001/mcp \
+npx @adcp/sdk@15.9 fuzz http://localhost:3001/mcp \
   --fixture creative_ids=cre_a,cre_b \
   --fixture media_buy_ids=mb_1
 
 # Auto-seed + Tier 3 update-tool fuzzing (mutates agent state — SANDBOX ONLY)
-npx @adcp/sdk@adcp-3.2 fuzz http://localhost:3001/mcp --auto-seed --auth-token $TOKEN
+npx @adcp/sdk@15.9 fuzz http://localhost:3001/mcp --auto-seed --auth-token $TOKEN
 
 # Uniform-error-response invariant in full cross-tenant mode
-npx @adcp/sdk@adcp-3.2 fuzz http://localhost:3001/mcp \
+npx @adcp/sdk@15.9 fuzz http://localhost:3001/mcp \
   --auto-seed \
   --auth-token            $TENANT_A_TOKEN \
   --auth-token-cross-tenant $TENANT_B_TOKEN
 
 # Inspect the tool list + tier classification
-npx @adcp/sdk@adcp-3.2 fuzz --list-tools
+npx @adcp/sdk@15.9 fuzz --list-tools
 ```
 
 See [`docs/guides/CONFORMANCE.md`](./CONFORMANCE.md) for the fixture map, tier-by-tier tool list, and failure interpretation.
@@ -326,25 +326,25 @@ A single-tenant run still produces useful signal — baseline catches a signific
 If you claim the `signed-requests` specialism, run the RFC 9421 grader. The grader signs its own requests with test keypairs from `compliance/cache/<version>/test-kits/signed-requests-runner.yaml` — no `--auth` flag; your agent's verifier must accept the runner's JWKS ahead of time.
 
 ```bash
-# All 38 vectors
-npx @adcp/sdk@adcp-3.2 grade request-signing https://sandbox.agent.example/mcp
+# All vectors (the grader prints the count for your pinned cache)
+npx @adcp/sdk@15.9 grade request-signing https://sandbox.agent.example/mcp
 
 # Skip rate-abuse (vector 020 fires cap+1 requests; skip in dev loops)
-npx @adcp/sdk@adcp-3.2 grade request-signing https://sandbox.agent.example/mcp --skip-rate-abuse
+npx @adcp/sdk@15.9 grade request-signing https://sandbox.agent.example/mcp --skip-rate-abuse
 
 # MCP transport (wraps vectors in JSON-RPC envelopes)
-npx @adcp/sdk@adcp-3.2 grade request-signing https://sandbox.agent.example/mcp --transport mcp
+npx @adcp/sdk@15.9 grade request-signing https://sandbox.agent.example/mcp --transport mcp
 
 # Isolate a single vector
-npx @adcp/sdk@adcp-3.2 grade request-signing https://sandbox.agent.example/mcp --only 016-replayed-nonce
+npx @adcp/sdk@15.9 grade request-signing https://sandbox.agent.example/mcp --only 016-replayed-nonce
 
 # Grade the authored AdCP 3.2 signing profile
-npx @adcp/sdk@adcp-3.2 grade request-signing https://sandbox.agent.example/mcp --signing-profile 3.2
+npx @adcp/sdk@15.9 grade request-signing https://sandbox.agent.example/mcp --signing-profile 3.2
 ```
 
-`--signing-profile 3.2` selects only the 3.2 profile vectors. The current
-3.2.1 compliance cache includes 11 positive and 19 negative profile
-vectors. Library callers can select
+`--signing-profile 3.2` selects only the 3.2 profile vectors. The exact counts
+move with each signed bundle, so run the command against your pinned compliance
+cache to see them rather than relying on a number here. Library callers can select
 the same set with `gradeRequestSigning(agentUrl, { signingProfileVersion: '3.2' })`.
 
 #### A2A operation-resolution vectors (`--transport a2a`)
@@ -357,17 +357,17 @@ The `signed_requests` storyboard synthesizes one step per vector and grades them
 
 ```bash
 # Per-operation HTTP endpoints instead of a single MCP mount
-npx @adcp/sdk@adcp-3.2 storyboard run https://sandbox.agent.example/adcp signed_requests \
+npx @adcp/sdk@15.9 storyboard run https://sandbox.agent.example/adcp signed_requests \
   --signing-transport raw --auth $TOKEN
 
 # Drop a vector your deployment can't satisfy, and the cap+1 flood
-npx @adcp/sdk@adcp-3.2 storyboard run https://sandbox.agent.example/mcp signed_requests \
+npx @adcp/sdk@15.9 storyboard run https://sandbox.agent.example/mcp signed_requests \
   --signing-skip-vectors 025-jwk-alg-crv-mismatch --signing-skip-rate-abuse --auth $TOKEN
 ```
 
 - **`--signing-transport` is not `--transport`.** `--transport`/`--protocol` selects how the storyboard talks to your agent; `--signing-transport` selects how the conformance vectors are framed. Mirrors `adcp grade request-signing --transport`.
 - **Leave it unset by default.** The vector transport is inferred from the resolved protocol: MCP frames each vector as a `tools/call` envelope; A2A signs the exact request emitted by the official `@a2a-js/sdk` client after Agent Card discovery.
-- **The 3.2 signing profile follows the storyboard version.** Select a 3.2 compliance cache with `--compliance-version 3.2.1`; the `signed_requests` storyboard then selects its authored 3.2 profile vectors automatically. The `request_signing` options on `comply()` control transport and filtering; profile selection follows the resolved storyboard `adcp_version`.
+- **The 3.2 signing profile follows the storyboard version.** Select a 3.2 compliance cache with `--compliance-version 3.2.5`; the `signed_requests` storyboard then selects its authored 3.2 profile vectors automatically. The `request_signing` options on `comply()` control transport and filtering; profile selection follows the resolved storyboard `adcp_version`.
 - **A2A discovery fails closed.** If the Agent Card cannot resolve to a supported JSON-RPC interface, networked vectors skip with detailed reason `signing_transport_unavailable`; the storyboard cannot pass, the `security_transport` track stays `partial`, and the command exits 3. Publish a resolvable modern or legacy Agent Card, or grade an MCP/REST binding. Do not use `--soft-fail` to dismiss actual A2A verifier failures: once discovery succeeds, they are real grades.
 - **The in-library vector remains transport-independent.** `025-jwk-alg-crv-mismatch` is decided against the SDK verifier with no wire exchange, so its result does not grade your agent.
 - **Vectors excluded on their own terms say so, on every protocol.** `026-non-ascii-host` reports `transport_ungradable` (no HTTP client can carry a non-ASCII authority — `fetch` punycodes it first). `028-unsigned-protocol-method-required` reports `capability_profile_mismatch` unless your `get_adcp_capabilities` declares `request_signing.protocol_methods_required_for` — **this applies on MCP runs too, not just A2A**: previously the storyboard dispatched 028 at every agent, so one that never claimed the JSON-RPC bucket could fail it. Declare the bucket (e.g. `['tasks/cancel']`) if you verify signatures on protocol methods; a declaration your AdCP line's schema rejects is discarded rather than treated as "not declared", so it cannot suppress the vector. Note `adcp grade request-signing` does not read your advertisement — it uses the profile you pass it — so the two commands can disagree about 028 by design.
@@ -383,7 +383,7 @@ npx @adcp/sdk@adcp-3.2 storyboard run https://sandbox.agent.example/mcp signed_r
 Exposes `(brand, account)`-scoped state that lives per-process instead of in a shared store — a class of bug that single-URL runs never catch. See [`docs/guides/MULTI-INSTANCE-TESTING.md`](./MULTI-INSTANCE-TESTING.md).
 
 ```bash
-npx @adcp/sdk@adcp-3.2 storyboard run \
+npx @adcp/sdk@15.9 storyboard run \
   --url https://a.agent.example/mcp \
   --url https://b.agent.example/mcp \
   sales-guaranteed --auth $TOKEN
@@ -608,7 +608,7 @@ Use `--invariants` to load modules that assert properties across storyboard step
 
 ```bash
 # Load ./my-invariants.js (relative path) or a bare specifier (npm package)
-npx @adcp/sdk@adcp-3.2 storyboard run http://localhost:3001/mcp \
+npx @adcp/sdk@15.9 storyboard run http://localhost:3001/mcp \
   --invariants ./assertions/idempotency.js,@my-org/adcp-invariants
 ```
 
@@ -766,18 +766,18 @@ Hints also land in machine-readable output:
 
 ```yaml
 - name: Storyboard (core + products)
-  run: npx @adcp/sdk@adcp-3.2 storyboard run $AGENT_URL --tracks core,products --auth $TOKEN
+  run: npx @adcp/sdk@15.9 storyboard run $AGENT_URL --tracks core,products --auth $TOKEN
 - name: Fuzz (fixed seed)
-  run: npx @adcp/sdk@adcp-3.2 fuzz $AGENT_URL --seed 42 --auth-token $TOKEN --format json
+  run: npx @adcp/sdk@15.9 fuzz $AGENT_URL --seed 42 --auth-token $TOKEN --format json
 ```
 
 ### Nightly (slow, broader coverage)
 
 ```yaml
 - name: Fuzz (random seed, auto-seed)
-  run: npx @adcp/sdk@adcp-3.2 fuzz $AGENT_URL --auto-seed --auth-token $TOKEN
+  run: npx @adcp/sdk@15.9 fuzz $AGENT_URL --auto-seed --auth-token $TOKEN
 - name: Full storyboard assessment
-  run: npx @adcp/sdk@adcp-3.2 storyboard run $AGENT_URL --auth $TOKEN --json > report.json
+  run: npx @adcp/sdk@15.9 storyboard run $AGENT_URL --auth $TOKEN --json > report.json
 ```
 
 Random seed on nightly broadens the surface; fixed seed on per-PR keeps reproducibility.

package/docs/llms.txt

@@ -1,7 +1,7 @@
 # Ad Context Protocol (AdCP)
 
 > Generated at: 2026-10-16
-> Library: @adcp/sdk v15.9.3
+> Library: @adcp/sdk v15.9.4
 > 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.
@@ -13,7 +13,7 @@ AdCP is an open protocol for AI agents to buy, manage, and optimize advertising
 
 ## Start here: SDK 14 and AdCP 3.2
 
-SDK 14 requires Node.js `^20.19.0 || >=22.12.0`; install it with `npm install @adcp/sdk`, or pin the AdCP 3.2 line with `@adcp/sdk@adcp-3.2`.
+SDK 14 requires Node.js `^20.19.0 || >=22.12.0`; install it with `npm install @adcp/sdk`, or pin the current stable maintenance line with `@adcp/sdk@15.9`. The `adcp-3.x` dist-tags are frozen pointers at older SDK majors and do not receive new compliance caches. To see what an install actually carries, read `adcp_version` from its `package.json`, and run `adcp storyboard list --compliance-version ?` — the error enumerates the packaged compliance caches.
 
 SDK 14 is compact-lifecycle first: `list_products → buy_products → control_media_buy`, with `request_proposals → refine_proposals → accept_proposal` when terms need negotiation.
 
@@ -1470,7 +1470,7 @@ Flow: `create_media_buy → sync_plans → sync_accounts → sync_governance →
 Flow: `create_media_buy → sync_plans → sync_accounts → sync_governance → get_products → check_governance → sync_plans → create_media_buy → check_governance → create_media_buy`
 
 **Inline media-buy creatives without sync_creatives** — Verifies that a seller advertising inline_creative_management accepts package creatives on create_media_buy and update_media_buy without requiring the Creative Protocol or sync_creatives.
-Flow: `get_adcp_capabilities → get_products → create_media_buy → update_media_buy → get_products → create_media_buy → update_media_buy → get_media_buys`
+Flow: `get_adcp_capabilities → get_products → create_media_buy → update_media_buy → get_media_buys → create_media_buy → update_media_buy → get_media_buys → create_media_buy → update_media_buy → get_media_buys → get_products → create_media_buy → update_media_buy → get_media_buys`
 
 **Seller rejects illegal state transitions and unknown references** — Validates that the seller returns structured AdCP errors (MEDIA_BUY_NOT_FOUND, PACKAGE_NOT_FOUND, NOT_CANCELLABLE) rather than 500s or undefined behavior when the buyer references missing entities or attempts forbidden state transitions.
 Flow: `update_media_buy → get_products → create_media_buy → update_media_buy`

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

@@ -11,18 +11,18 @@ below as the publication/deployment gate.
 
 | Fact | Value |
 | --- | --- |
-| Exact npm package | `@adcp/sdk@15.9.3` |
-| npm integrity | registry-derived after publication; run `npm view @adcp/sdk@15.9.3 dist.integrity` |
+| Exact npm package | `@adcp/sdk@15.9.4` |
+| npm integrity | registry-derived after publication; run `npm view @adcp/sdk@15.9.4 dist.integrity` |
 | Node.js runtime | `^20.19.0 || >=22.12.0` |
-| Default AdCP wire release | `3.2.4` |
-| 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.2.1`, `3.2`, `3.2.2`, `3.2.3`, `3.2.4` |
+| 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` |
 | Canonical migration notes | [SDK 15 OAuth](./migration-oauth-issuer-bindings.md), [issuer-binding and storage](./guides/OAUTH-ISSUER-BINDING.md); historical [13.x → 14](./migration-13-to-14.md) |
 
 Install exact production inputs rather than a moving range or dist-tag:
 
 ```bash
-npm install --save-exact '@adcp/sdk@15.9.3'
-npm view '@adcp/sdk@15.9.3' dist.integrity
+npm install --save-exact '@adcp/sdk@15.9.4'
+npm view '@adcp/sdk@15.9.4' dist.integrity
 ```
 
 ### Required and optional peers
@@ -63,7 +63,7 @@ ESM example:
 import { getCanonicalToolValidator } from '@adcp/sdk/schemas';
 
 const validate = getCanonicalToolValidator('get_reporting_status', 'sync', {
-  adcpVersion: '3.2.4',
+  adcpVersion: '3.2.5',
 });
 if (!validate) throw new Error('Requested protocol schema is unavailable');
 
@@ -86,7 +86,7 @@ CommonJS uses the same packed-artifact export:
 ```js
 const { getCanonicalToolValidator } = require('@adcp/sdk/schemas');
 const validate = getCanonicalToolValidator('get_reporting_status', 'sync', {
-  adcpVersion: '3.2.4',
+  adcpVersion: '3.2.5',
 });
 if (!validate) throw new Error('Requested protocol schema is unavailable');
 if (validate({ status: 'completed', view: 'summary' })) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adcp/sdk",
-  "version": "15.9.3",
+  "version": "15.9.4",
   "description": "AdCP SDK — client, server, and compliance harnesses for the AdContext Protocol (MCP + A2A)",
   "workspaces": [
     ".",
@@ -609,8 +609,8 @@
     "!skills/*.previous/**/*",
     ".claude-plugin/**/*",
     "compliance/cache/3.0.25/**/*",
-    "compliance/cache/3.1.24/**/*",
-    "compliance/cache/3.2.4/**/*",
+    "compliance/cache/3.1.29/**/*",
+    "compliance/cache/3.2.5/**/*",
     "ADCP_VERSION",
     "docs/README.md",
     "docs/TYPE-SUMMARY.md",
@@ -692,7 +692,7 @@
     "test:status-report": "node test/utils/final-status-report.js",
     "sync-schemas": "tsx scripts/sync-schemas.ts",
     "sync-schemas:v2.5": "tsx scripts/sync-v2-5-schemas.ts",
-    "sync-schemas:all": "npm run sync-schemas && npm run sync-schemas -- 3.1.24 && npm run sync-schemas -- 3.0.25 && npm run sync-schemas:v2.5",
+    "sync-schemas:all": "npm run sync-schemas && npm run sync-schemas -- 3.1.29 && npm run sync-schemas -- 3.0.25 && npm run sync-schemas:v2.5",
     "sync:canonical-storyboard-fixtures": "tsx scripts/sync-canonical-storyboard-fixtures.ts --update",
     "check:canonical-storyboard-fixtures": "tsx scripts/sync-canonical-storyboard-fixtures.ts --check",
     "sync-registry-schemas": "tsx scripts/generate-registry-types.ts --sync",
@@ -879,7 +879,7 @@
     },
     "minimatch": "^10.2.1"
   },
-  "adcp_version": "3.2.4",
+  "adcp_version": "3.2.5",
   "sideEffects": [
     "**/default-invariants.*"
   ]