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

package/docs/guides/MEDIA-BUY-3.2-COMPATIBILITY.md

@@ -280,7 +280,7 @@ authoritative completion reconciliation after restart.
 
 ### Tokenless catalog and products-only legacy continuations
 
-An established 2.5, 3.0, or 3.1 seller may return purchasable catalog products
+An established 3.0 or 3.1 seller may return purchasable catalog products
 without a wholesale feed token, or answer a brief with products but no
 proposal. The SDK never invents a proposal, terms digest, or feed fence. When
 `principalScope`, an account, and stable seller-session binding are available,
@@ -301,7 +301,7 @@ invocation receives a fresh continuation even when the catalog is unchanged:
 const continuations = createInMemoryLegacyPurchaseContinuationStore();
 const lifecycle = await agent.negotiateMediaBuyLifecycle({
   principalScope: authenticatedPrincipalId,
-  // Required for established 2.5, 3.0, and 3.1 sellers that provide no server
+  // Required for established 3.0 and 3.1 sellers that provide no server
   // context ID. Persist this non-secret authenticated session ID across rehydration.
   legacyPurchaseSellerSessionScope: authenticatedSellerSessionId,
   legacyPurchaseContinuationStore: continuations,
@@ -331,9 +331,9 @@ after accepting the exact returned loss set. If the application requires an
 enforceable observed catalog/pricing fence, do not accept the continuation;
 the tokenless catalog is read-only for that policy.
 
-On 2.5 the loss set also includes `mutation_idempotency_not_guaranteed`. On 3.0
-and 3.1 it includes that loss whenever the seller does not advertise a usable
-replay TTL. All tokenless catalog continuations include
+On 3.0 and 3.1 the loss set includes `mutation_idempotency_not_guaranteed`
+whenever the seller does not advertise a usable replay TTL. All tokenless
+catalog continuations include
 `feed_version_not_atomic` and `pricing_version_not_atomic`.
 
 The in-memory store is a single-process reference implementation. Production
@@ -462,13 +462,12 @@ issued. It must be a stable, non-secret ID derived by the application from the
 authenticated seller/account session—not a bearer token. Persist and reuse it
 with the continuation store so a restarted coordinator can redeem or replay
 the same operation without making the token portable to another credentialed
-session. This applies to 2.5, 3.0, and 3.1; endpoint identity is not an
+session. This applies to 3.0 and 3.1; endpoint identity is not an
 authenticated session identity. URL userinfo and presigned URLs are rejected
 before the discovered payload can enter durable storage.
 
-Every 2.5 continuation declares `mutation_idempotency_not_guaranteed`.
-3.0/3.1 continuations declare the same loss whenever the seller does not
-advertise a usable replay TTL; accepting an idempotency key alone is not treated
+3.0/3.1 continuations declare `mutation_idempotency_not_guaranteed` whenever
+the seller does not advertise a usable replay TTL; accepting an idempotency key alone is not treated
 as evidence that a mutation can be replayed safely. Submitted completions are
 accepted only for the exact seller task ID recorded at dispatch. Unstructured
 or SDK-synthetic terminal errors remain ambiguous and retain the durable fence.
@@ -584,15 +583,17 @@ mutating prior state.
 
 ## Buyer projection policy
 
+All compatibility lanes require AdCP 3. AdCP 2 agents are rejected during discovery before a coordinator operation can dispatch; see the [AdCP 2 retirement guide](../migration-drop-adcp-2.md).
+
 | Coordinator operation | Compact tool | Established projection | Boundary |
 |---|---|---|---|
-| `listProducts` | `list_products` | `get_products(buying_mode='wholesale')` | Representable `criteria.offer_filters` map field-by-field through the negotiated legacy offer-filter schema; country remains `filters.countries` and is never recast as delivery targeting. Other structured criteria report their exact unsupported field before dispatch. Actual `wholesale_feed_version` is renamed to `feed_version`; no value is invented. An eligible tokenless catalog may expose the SDK-local `purchase_continuation` described above while `raw` remains the canonical SDK source object. The stable response exposes `next_cursor` and `unchanged` in both lanes. The established request includes `pagination` only when the caller supplies a cursor or `max_results`; the SDK does not fabricate a page-size default. v2.5 pagination/field selection, pre-3.1 conditional feed/pricing reads, and response-field names absent from the negotiated enum are typed unsupported. |
+| `listProducts` | `list_products` | `get_products(buying_mode='wholesale')` | Representable `criteria.offer_filters` map field-by-field through the negotiated legacy offer-filter schema; country remains `filters.countries` and is never recast as delivery targeting. Other structured criteria report their exact unsupported field before dispatch. Actual `wholesale_feed_version` is renamed to `feed_version`; no value is invented. An eligible tokenless catalog may expose the SDK-local `purchase_continuation` described above while `raw` remains the canonical SDK source object. The stable response exposes `next_cursor` and `unchanged` in both lanes. The established request includes `pagination` only when the caller supplies a cursor or `max_results`; the SDK does not fabricate a page-size default. Pre-3.1 conditional feed/pricing reads and response-field names absent from the negotiated enum are typed unsupported. |
 | `requestProposals` | `request_proposals` | `get_products(buying_mode='brief')` | Only offer-filter fields and metric values defined by the negotiated release map field-by-field, plus policy IDs. Compact catalog selection lacks the complete legacy catalog metadata and fails closed. Targeting-overlay requirements are forwarded only to a 3.2 established surface; 3.0/3.1 cannot represent them. Product-ID filters, compact-only offer prerequisites, `ext`, opportunity, and governance context fail preflight. |
 | `refineProposals` | `refine_proposals` | `get_products(buying_mode='refine')` | Ask and product include/omit map for revisions. Finalize maps only when it contains no additional refinement fields. Hard constraints, alternatives, criteria, amendment kinds, and finalize extras fail before dispatch. |
 | `declineProposals` | `decline_proposals` | proposal-scoped legacy omit | Rejected by default because omit is not a terminal decline and cannot carry the required compact reason/detail. Explicit opt-in reports `proposal_decline_not_terminal` and `proposal_decline_reason_not_forwarded`. |
-| `buyProducts` | `buy_products` | `create_media_buy` | Feed/pricing fencing is not atomic. Rejected by default; explicit opt-in names `feed_version_not_atomic` and, when present, `pricing_version_not_atomic`. A missing `feed_version` remains unsupported here; tokenless catalogs use the separate SDK-local `continueLegacyPurchase()` handoff. Shared package fields and nested targeting/reporting enums map against the negotiated schema, including 3.1+ `format_option_refs`; newer targeting, metric, and postal shapes fail closed. v2.5 also rejects non-empty compact targeting and push notification configuration. A direct compact `total_budget` and fields introduced on the 3.2 established surface—including allocation, budget-cap, bidding, governance, opportunity, and newer package controls—map only on a negotiated 3.2 established lane. Compact `catalog_ids` and resolved `pricing` remain typed unsupported. |
+| `buyProducts` | `buy_products` | `create_media_buy` | Feed/pricing fencing is not atomic. Rejected by default; explicit opt-in names `feed_version_not_atomic` and, when present, `pricing_version_not_atomic`. A missing `feed_version` remains unsupported here; tokenless catalogs use the separate SDK-local `continueLegacyPurchase()` handoff. Shared package fields and nested targeting/reporting enums map against the negotiated schema, including 3.1+ `format_option_refs`; newer targeting, metric, and postal shapes fail closed. A direct compact `total_budget` and fields introduced on the 3.2 established surface—including allocation, budget-cap, bidding, governance, opportunity, and newer package controls—map only on a negotiated 3.2 established lane. Compact `catalog_ids` and resolved `pricing` remain typed unsupported. |
 | `acceptProposal` | `accept_proposal` | `create_media_buy(proposal_id=...)` | A compact-shaped proposal retains strict digest, immutable-snapshot, account-scope, kind/status, and expiry checks. Caller values cannot override digest-bound budget, budget-cap, timezone, or purchase-order terms. An honest 3.0/3.1 proposal remains executable with its ordinary `proposal_id` semantics only after explicit opt-in to `proposal_terms_digest_not_enforced`, `proposal_terms_digest_unavailable`, and `proposal_snapshot_not_immutable` (plus `proposal_hold_not_verifiable` when it has no expiry). The caller supplies the original brand/flight as `established_fallback`; the SDK does not claim those values came from the seller or synthesize a digest. |
-| `controlMediaBuy` | `control_media_buy` | `update_media_buy` | Account, media-buy ID, and a positive revision are required. Revision and identically shaped fields present in the negotiated established schema map directly; `name` maps on the 3.2 established surface and fails closed on 3.0/3.1, whose update schemas do not define it. v2.5 requires explicit `revision_not_atomic` opt-in and rejects cancellation plus v3-only package controls. Pre-3.2 lanes reject the broader compact optimization-goal union and nested targeting/keyword shapes they cannot represent. Compact `catalog_ids` cannot be cast to established `catalogs` objects, so it fails closed in every established lane. |
+| `controlMediaBuy` | `control_media_buy` | `update_media_buy` | Account, media-buy ID, and a positive revision are required. Revision and identically shaped fields present in the negotiated established schema map directly; `name` maps on the 3.2 established surface and fails closed on 3.0/3.1, whose update schemas do not define it. Pre-3.2 lanes reject the broader compact optimization-goal union and nested targeting/keyword shapes they cannot represent. Compact `catalog_ids` cannot be cast to established `catalogs` objects, so it fails closed in every established lane. |
 | Readback | shared tools | `get_media_buys`, `get_media_buy_delivery` | Same public calls and canonical creative projection in every lane. Versioned request additions fail closed: webhook-activity and delivery-window/granularity options require 3.1+, while `indicator_types`, demographic breakdowns, and spot breakdowns require 3.2. Native postal reporting shapes require 3.1+. |
 
 Lossy mutations are fail-closed. An adopter may opt into only the exact named
@@ -735,8 +736,7 @@ trusted namespaces, never a buyer-supplied proposal ID alone.
 
 | Buyer surface | Seller surface | Expected path | Guarantee |
 |---|---|---|---|
-| Established `getProducts` / `createMediaBuy` / `updateMediaBuy` | AdCP 2.5–3.1 or a dual-surface 3.2 seller | Established tools are called directly | Existing application behavior remains unchanged; the compact coordinator is not involved. |
-| Compact-first coordinator | AdCP 2.5 | `list_products` → `get_products`; purchase → `create_media_buy`; supported control → `update_media_buy` | The direct common subset remains usable. Proposal objects/binding, media-buy readback, pagination, cancellation, v3-only top-level/package fields, and update reporting-webhook changes are typed unsupported rather than sent into v2.5's permissive additional-properties boundary. Feed fencing and optimistic revision enforcement require their named loss opt-ins. |
+| Established `getProducts` / `createMediaBuy` / `updateMediaBuy` | AdCP 3.0/3.1 or a dual-surface 3.2 seller | Established tools are called directly | Existing application behavior remains unchanged; the compact coordinator is not involved. |
 | Compact-first coordinator | AdCP 3.0, 3.1, or 3.2 legacy-only | `list_products` → `get_products`; proposal discovery/refinement → `get_products`; control → `update_media_buy`; purchase → `create_media_buy` only when its named loss policy permits it | Common-subset reads and control are lossless. Atomic feed/pricing fencing, digest enforcement, and terminal decline are not representable and fail before mutation by default. |
 | Compact-first coordinator | AdCP 3.2 dual-surface | Compact tools are preferred; `preferredLifecycle: 'established'` exercises the compatibility facade | Native by default; the forced established lane has the same explicit boundaries as older sellers. |
 | Compact-first coordinator | AdCP 3.2 compact-only | Compact lifecycle tools | Native compact guarantees. |
@@ -749,7 +749,7 @@ that a 3.0 seller can enforce a 3.2-only atomicity or digest guarantee. The SDK
 must reject that case or report the exact explicitly accepted loss; it must
 never label the weaker mutation as equivalent.
 
-The coordinator test matrix covers SDK 14 compact-first callers against v2.5,
+The coordinator test matrix covers compact-first callers against
 3.0, 3.1, 3.2 legacy-only, 3.2 dual-surface (compact preferred and established
 forced), and 3.2 compact-only discovery. The dual-surface MCP lane also holds
 the maximum at 3.2 while defaulting unversioned discovery and dispatch to 3.1,
@@ -761,9 +761,6 @@ validating every request and response against the corresponding cached wire
 bundle. Those lanes assert canonical format projection, pagination,
 feed/pricing provenance, account/brand/context/currency continuity, exact
 replay, changed-payload conflict, no duplicate mutation, control, and shared
-readback. The honest v2.5 fixture executes its complete representable direct
-subset, validates exact legacy wire, and asserts typed failures for pagination,
-proposals, cancellation, unsupported create/update fields, and media-buy
 readback. Versioned MCP fixtures also preserve submitted and input-required
 proposal states without inventing completed outcomes. A normal 3.2 server
 profile is exercised by 3.0 and 3.1 buyers through hidden established routes,

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

@@ -835,3 +835,8 @@ Random seed on nightly broadens the surface; fixed seed on per-PR keeps reproduc
 - [`MULTI-INSTANCE-TESTING.md`](./MULTI-INSTANCE-TESTING.md) — horizontal scaling bug hunt
 - [`BUILD-AN-AGENT.md`](./BUILD-AN-AGENT.md) — server-side implementation
 - `skills/build-*-agent/SKILL.md` — per-specialism obligations and storyboard IDs
+
+
+For creative evaluator security fixtures, see
+[Creative evaluator build probes](CREATIVE-BUILD-PROBE.md) for valid route/input
+preparation, provisioned legacy selectors and explicit coverage gaps.

package/docs/llms.txt

@@ -1,7 +1,7 @@
 # Ad Context Protocol (AdCP)
 
-> Generated at: 2026-10-18
-> Library: @adcp/sdk v16.0.0-beta.8
+> Generated at: 2026-10-19
+> Library: @adcp/sdk v16.0.0-beta.9
 > 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-13-to-14.md

@@ -929,10 +929,12 @@ acceptance, caller-supplied budget,
 budget-cap, timezone, or purchase-order values must match any digest-bound
 seller terms; a conflict fails before `create_media_buy`.
 
-For v2.5 specifically, proposal operations, `get_media_buys`, pagination,
-cancellation, and v3-only package controls return typed unsupported errors.
-Supported pause/resume updates require explicit `revision_not_atomic` opt-in
-because v2.5 has no optimistic revision token.
+Historically, the SDK 14 v2.5 lane rejected proposal operations,
+`get_media_buys`, pagination, cancellation, and v3-only package controls with
+typed unsupported errors. Pause/resume updates required explicit
+`revision_not_atomic` opt-in because v2.5 has no optimistic revision token.
+SDK 16 removes that lane and rejects AdCP 2 agents before dispatch; see the
+[AdCP 2 retirement guide](./migration-drop-adcp-2.md).
 
 Run the same compact CLI storyboards against established sellers with
 `--media-buy-lifecycle-compat`. Use `--media-buy-compat-losses` only for the
@@ -1171,18 +1173,20 @@ configuration error; a tool or response variant absent from an installed
 bundle returns `undefined`. Neither case silently falls back to the current
 schema.
 
-Every `TaskResult.metadata` now exposes the selected seller wire generation as
-`serverVersion: 'v2' | 'v3'`. `serverVersionSynthetic` distinguishes an
-authoritative capability declaration (`false`) from the SDK's compatibility
-fallback (`true`). Both fields survive submitted/deferred continuations and
-durable restart recovery. `adcpVersion` remains the distinct, release-precision
-value echoed by a seller response.
-
-The v2.5 `get_products` response adapter also accepts explicitly zoned legacy
-forecast timestamps, including offset variants and single `$date`/`value`
-wrappers. It converts them to UTC RFC 3339 without losing fractional precision;
-ambiguous or unzoned values remain untouched, and the preserved seller wire
-object is not mutated.
+In SDK 14, every `TaskResult.metadata` exposed the selected seller wire
+generation as `serverVersion: 'v2' | 'v3'`. `serverVersionSynthetic`
+distinguishes an authoritative capability declaration (`false`) from the SDK's
+compatibility fallback (`true`). Both fields survive submitted/deferred
+continuations and durable restart recovery. `adcpVersion` remains the distinct,
+release-precision value echoed by a seller response. SDK 16 only dispatches
+AdCP 3 and rejects stored AdCP 2 continuations before resuming them; see the
+[AdCP 2 retirement guide](./migration-drop-adcp-2.md).
+
+The SDK 14 v2.5 `get_products` response adapter also accepted explicitly zoned
+legacy forecast timestamps, including offset variants and single `$date`/`value`
+wrappers. It converted them to UTC RFC 3339 without losing fractional precision;
+ambiguous or unzoned values remained untouched, and the preserved seller wire
+object was not mutated. That AdCP 2 adapter was removed in SDK 16.
 
 SDK 14 also adds semantic refinements to public object schemas. Behavior when
 composing a refined schema varies across supported Zod 4 releases: `.extend()`

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

@@ -16,18 +16,18 @@ pin using `ADCP_VERSION` inside that tarball.
 
 | Fact | Value |
 | --- | --- |
-| Checkout `package.json` version | `@adcp/sdk@16.0.0-beta.8` |
-| npm integrity | registry-derived after publication; run `npm view @adcp/sdk@16.0.0-beta.8 dist.integrity` |
+| Checkout `package.json` version | `@adcp/sdk@16.0.0-beta.9` |
+| npm integrity | registry-derived after publication; run `npm view @adcp/sdk@16.0.0-beta.9 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` |
+| 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` |
 | 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) |
 
 For a checkout at the published release commit, install the exact package version:
 
 ```bash
-npm install --save-exact '@adcp/sdk@16.0.0-beta.8'
-npm view '@adcp/sdk@16.0.0-beta.8' dist.integrity
+npm install --save-exact '@adcp/sdk@16.0.0-beta.9'
+npm view '@adcp/sdk@16.0.0-beta.9' dist.integrity
 ```
 
 ### Required and optional peers

package/docs/migration-4.x-to-5.x.md

@@ -882,13 +882,18 @@ steps for a 4.x upgrader and are omitted here:
 
 ## v2 sunset
 
-AdCP v2 went unsupported on 2026-04-20 as part of the 3.0 GA cutover
-([adcp#2220](https://github.com/adcontextprotocol/adcp/issues/2220)). The
-client still executes v2 code paths — no functional break — but emits a
-one-time `console.warn` the first time a client instance sees v2
-capabilities from an agent. Suppress with `ADCP_ALLOW_V2=1` or `adcp
---allow-v2` if you're knowingly running against a legacy holdout.
-Synthetic capabilities don't fire the warning.
+AdCP v2 became unsupported at the April 2026 3.0 GA cutover and reached
+full end of life on August 1, 2026; see the protocol's
+[v2 sunset policy](https://github.com/adcontextprotocol/adcp/blob/main/docs/reference/v2-sunset.mdx).
+In SDK 5.x, the client still executed v2 code paths and emitted a one-time
+`console.warn` when a client instance saw explicit v2 capabilities. That
+historical warning could be suppressed with `ADCP_ALLOW_V2=1` or
+`adcp --allow-v2`; synthetic capabilities did not fire it.
+
+**SDK 16 update:** AdCP 2 compatibility, `ADCP_ALLOW_V2`, and `--allow-v2`
+have been removed. Agents must support AdCP 3 discovery before business-tool
+dispatch. Follow the [AdCP 2 retirement guide](./migration-drop-adcp-2.md)
+for current behavior and the last supporting SDK pins.
 
 ## Webhook HMAC legacy deprecation
 

package/docs/migration-drop-adcp-2.md

@@ -0,0 +1,25 @@
+# Removing AdCP 2 compatibility
+
+AdCP 2.5 reached end of life on August 1, 2026. The SDK now supports AdCP 3 agents only. This is an SDK major release change. Integrations that still require AdCP 2 can pin the last supporting beta, `npm install @adcp/sdk@16.0.0-beta.8`, or stay on the stable SDK 15 line (`npm install @adcp/sdk@15.9.6`) while upgrading their agents.
+
+Upgrade agents to AdCP 3 before upgrading the SDK. An agent must expose `get_adcp_capabilities`. Its `adcp.supported_versions` determines its supported majors; `adcp.major_versions` is the legacy fallback. Omitting both fields no longer selects AdCP 2.
+
+Agents that declare only AdCP 2 and agents missing capability discovery fail with `VersionUnsupportedError` (`code: 'VERSION_UNSUPPORTED'`) before a business tool is dispatched. AdCP 2 constructor pins fail with `ConfigurationError`, even if an old schema cache remains on disk.
+
+The release removes:
+
+- `allowV2`, `ADCP_ALLOW_V2`, and the CLI `--allow-v2` flag.
+- `SingleAgentClient.isSyntheticV2()` and the v2 `buildSyntheticCapabilities()` helper.
+- The `2` argument to `SingleAgentClient.supportsVersion()` and `AgentClient.supportsVersion()`; the maintained query is `supportsVersion(3)`.
+- The `@adcp/sdk/types/v2-5` export and AdCP 2 schema bundles.
+- Outbound AdCP 2 adapters: `adaptGetProductsRequestForV2`, `adaptPricingOptionForV2`, `adaptProductPricingForV2`, `adaptSyncCreativesRequestForV2`, `adaptPackageRequestForV2`, `adaptCreateMediaBuyRequestForV2`, and `adaptUpdateMediaBuyRequestForV2`.
+- AdCP 2 creative/format/preview detectors: `usesV2CreativeIds`, `usesV2Dimensions`, and `usesV2RenderFields`, plus their v2-only structural types (`PackageRequestV2`, `PackageResponseV2`, `PackageAdapterContext`, `FormatV2`, and `PreviewRenderV2`).
+- The `sync-schemas:v2.5` and `generate-types:v2.5` scripts.
+
+Submit canonical AdCP 3 `creative_assignments`, format `renders`, and preview `render_id` / `role` fields. The maintained read helpers (`getCreativeIds`, `getCreativeAssignments`, `getFormatRenders`, `getPrimaryRender`, `getFormatDimensions`, `getRenderId`, `getRenderRole`, and preview URL/HTML accessors) still inspect valid AdCP 3 data. Their normalizers preserve that data; they no longer promote `creative_ids`, top-level format dimensions, or `output_id` into AdCP 3 fields.
+
+Seller applications using `createAdcpServer` or `createAdcpServerFromPlatform` must remove AdCP 2 from `capabilities.major_versions` and `capabilities.supported_versions`. Startup rejects a declaration such as `[2, 3]` because this SDK no longer implements the advertised AdCP 2 surface. A buyer can still call an external agent that genuinely implements both majors: when its discovery includes AdCP 3, the SDK negotiates AdCP 3.
+
+AdCP 3.0 and 3.1 compatibility remains available. Creative-model v2 projections and MCP v2 transport names refer to separate version schemes and remain supported.
+
+See the protocol's [v2 sunset policy](https://github.com/adcontextprotocol/adcp/blob/main/docs/reference/v2-sunset.mdx) and [FAQ](https://github.com/adcontextprotocol/adcp/blob/main/docs/faq.mdx).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adcp/sdk",
-  "version": "16.0.0-beta.8",
+  "version": "16.0.0-beta.9",
   "description": "AdCP SDK — client, server, and compliance harnesses for the AdContext Protocol (MCP + A2A)",
   "workspaces": [
     ".",
@@ -81,16 +81,6 @@
         "default": "./dist/lib/enums.js"
       }
     },
-    "./types/v2-5": {
-      "import": {
-        "types": "./dist/lib/types/v2-5/index.d.mts",
-        "default": "./dist/lib/types/v2-5/index.mjs"
-      },
-      "require": {
-        "types": "./dist/lib/types/v2-5/index.d.ts",
-        "default": "./dist/lib/types/v2-5/index.js"
-      }
-    },
     "./types/*": {
       "types": "./dist/lib/types/*.d.ts"
     },
@@ -448,9 +438,6 @@
       "types": [
         "dist/lib/types/index.d.ts"
       ],
-      "types/v2-5": [
-        "dist/lib/types/v2-5/index.d.ts"
-      ],
       "wholesale-feed-sync": [
         "dist/lib/wholesale-feed-sync/index.d.ts"
       ],
@@ -652,8 +639,7 @@
     "test:protocol-comparison": "node test/utils/comprehensive-protocol-comparison.js",
     "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.29 && 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",
     "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",
@@ -662,8 +648,7 @@
     "generate-types": "tsx scripts/generate-types.ts && tsx scripts/generate-enum-arrays.ts && tsx scripts/generate-inline-enum-arrays.ts && tsx scripts/generate-manifest-derived.ts && tsx scripts/generate-entity-hydration.ts && tsx scripts/generate-media-buy-update-fields.ts && tsx scripts/generate-media-buy-action-metadata.ts",
     "generate-manifest-derived": "tsx scripts/generate-manifest-derived.ts",
     "generate-entity-hydration": "tsx scripts/generate-entity-hydration.ts",
-    "generate-types:v2.5": "tsx scripts/generate-v2-5-types.ts",
-    "generate-types:all": "npm run generate-types && npm run generate-types:v2.5",
+    "generate-types:all": "npm run generate-types",
     "generate-registry-types": "tsx scripts/generate-registry-types.ts",
     "generate-enum-arrays": "tsx scripts/generate-enum-arrays.ts",
     "generate-inline-enum-arrays": "tsx scripts/generate-inline-enum-arrays.ts",

package/skills/call-adcp-agent/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: call-adcp-agent
 description: Wire-level invariants for any AdCP buyer call — idempotency_key replay semantics, account `oneOf` variants, async `status:'submitted'`+`task_id` polling, error recovery from `adcp_error.issues[]`. Load before any per-protocol task skill (adcp-media-buy, adcp-creative, adcp-signals, adcp-governance, adcp-si, adcp-brand) when calling an AdCP agent as a buyer.
-adcp_version: "3.x"
+adcp_version: '3.x'
 type: cross-cutting
 ---
 
@@ -32,7 +32,7 @@ Walk these in order on first contact:
 
 1. **Agent card** (A2A) or **`tools/list`** (MCP): returns tool NAMES. Most AdCP MCP servers publish passthrough schemas in `tools/list` by default — everything shows `{type: 'object', properties: {}}`. Some servers opt into `exposeToolSchemas: true` and publish shallow top-level key hints there; treat those as call hints, not as the canonical schema.
 2. **`get_adcp_capabilities`**: returns supported protocols (`media_buy`, `signals`, `creative`, …), AdCP major versions, feature flags. Tells you WHICH tools this agent supports, not how to call them.
-3. **`get_schema(tool_name)`** *(when the agent exposes it — pending standardization in [#3057](https://github.com/adcontextprotocol/adcp/issues/3057), not yet universal)*: returns the JSON Schema for a tool's request/response. Preferred over reading bundled schemas when available.
+3. **`get_schema(tool_name)`** _(when the agent exposes it — pending standardization in [#3057](https://github.com/adcontextprotocol/adcp/issues/3057), not yet universal)_: returns the JSON Schema for a tool's request/response. Preferred over reading bundled schemas when available.
 4. **Bundled schemas** (offline, authoritative): every SDK ships the AdCP JSON Schemas locally. Path differs by SDK — spec repo source uses `dist/schemas/<version>/bundled/`, `@adcp/client` puts them at `schemas/cache/<version>/bundled/` after `npm run sync-schemas`, Python and Go SDKs use their own conventions. **Don't hardcode a path** — let the SDK's loader find them, or ask the developer. Each schema is `<protocol>/<tool>-{request,response}.json` once you locate the bundle. The canonical source for every SDK is `https://adcontextprotocol.org/protocol/<version>.tgz`.
 
 ## Non-obvious rules every buyer must follow
@@ -119,7 +119,7 @@ Every validation failure produces:
         "keyword": "oneOf",
         "message": "must match exactly one schema in oneOf",
         "variants": [
-          { "index": 0, "required": ["account_id"],        "properties": ["account_id"] },
+          { "index": 0, "required": ["account_id"], "properties": ["account_id"] },
           { "index": 1, "required": ["brand", "operator"], "properties": ["brand", "operator", "sandbox"] }
         ]
       },
@@ -226,9 +226,7 @@ Returns `{ signals: [{ signal_agent_segment_id, match_rate, pricing, ... }] }`.
 {
   "idempotency_key": "<uuid>",
   "signal_agent_segment_id": "sig_premium_ctv_sports",
-  "destinations": [
-    { "type": "platform", "platform": "the-trade-desk" }
-  ]
+  "destinations": [{ "type": "platform", "platform": "the-trade-desk" }]
 }
 ```
 
@@ -254,25 +252,25 @@ Both transports share: idempotency, error shape, schema enforcement, and handler
 
 Quick lookup before reading the full envelope. Match what you see in `adcp_error.issues[*]`, apply the fix:
 
-| Symptom | What it means | Fix |
-|---|---|---|
-| `keyword: 'oneOf'` with `variants[]` | Discriminated union — you sent fields from multiple variants, or none | Pick ONE variant from `variants[]`. Send only its `required` fields. |
-| `discriminator: [{field, value}]` on a `required` issue | Validator inferred which branch you targeted; you missed required fields IN that branch | Read the `discriminator` pair, fill the missing required fields at the same level (don't nest under the discriminator field name). |
-| `hint:` field present on the issue | SDK matched a curated shape-gotcha rule | Apply the hint directly — it's the validated fix path. |
-| 2-3 `additionalProperties` errors at the same pointer | You merged `oneOf` variants ({account_id, brand, operator, …}) | Drop to one variant. Don't keep "extra" fields "for completeness". |
-| `keyword: 'required'`, `pointer: '/idempotency_key'` | Mutating tool, no UUID | Generate fresh UUID per logical operation. Reuse it on retries. |
-| `keyword: 'type'` or `additionalProperties` at `/budget` | Sent `{amount, currency}` | `budget` is a number. Currency is implied by `pricing_option_id`. |
-| `additionalProperties` at `/format_id` (string passed) | Sent `"format_id": "video_..."` | `format_id` is `{agent_url, id}` — always an object. |
-| `keyword: 'enum'` at `/destinations/*/type` | Made-up destination type | Use `'platform'` (with `platform`) or `'agent'` (with `agent_url`). |
-| Response carries `status: 'submitted'` and `task_id` | Async — work is queued, NOT done | Poll via `tasks/get` (A2A) or the MCP async task extension using `task_id`. |
-| `recovery: 'transient'` (rate limit, 5xx, timeout) | Server-side, retry-safe | Retry with the **same** `idempotency_key`. |
-| `recovery: 'correctable'` | Buyer-side fix | Read `issues[]`, patch the pointers, resend. Most cases close in one attempt. |
-| `recovery: 'terminal'` (account suspended, payment required, …) | Requires human action | Don't retry. Surface to the user. |
-| `[adcp] Warning: agent … does not expose get_adcp_capabilities` (one-shot per client, `@adcp/client` only) | Seller didn't ship v3 discovery — routed through the v2 adapter with idempotency-TTL guarantee unknown | Branch on `client.isSyntheticV2()` before dispatch. Tighten retry policy (lower attempt cap, longer backoff) or fall back to natural-key recovery for these sellers. Same predicate also flags synthetic v3 caveat — see `isSyntheticV2()` JSDoc. |
-| `adcp_error.code: 'AUTH_MISSING'` | No credential was presented | Escalate by default. Retry only if you own a credential supply or refresh path; otherwise surface re-auth to a human. |
-| `adcp_error.code: 'AUTH_INVALID'` | Credential was presented but rejected or revoked | Do not retry blindly. Refresh once only if you own a valid refresh grant and the rejection is token-expiry-shaped; otherwise surface to a human to rotate credentials. |
-| `adcp_error.code: 'AUTH_REQUIRED'` | Legacy compatibility code; older sellers and some SDK helper paths still use it for missing or rejected credentials | Treat as auth escalation by default. Retry only if your agent owns a credential-refresh path; otherwise surface to a human. |
-| HTTP 401 with `WWW-Authenticate` header | Transport auth challenge; may be missing credentials, wrong scheme, rejected credentials, or required request signing | Follow the challenge scheme. `Bearer` means send/refresh an OAuth-style `Authorization: Bearer ...` token. `Basic` means configure basic auth (`auth: { type: 'basic', username, password }` or `--auth user:pass --auth-scheme basic`) — `Bearer` will never succeed against that gateway. `Signature` means enable RFC 9421 request signing with an AdCP signing key, not an `Authorization` retry. **Saved aliases**: if registered with `--auth-scheme basic`, the scheme persists in `~/.adcp/config.json` and auto-applies on every later invocation — don't redundantly repeat the flag on each call. |
+| Symptom                                                                    | What it means                                                                                                             | Fix                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `keyword: 'oneOf'` with `variants[]`                                       | Discriminated union — you sent fields from multiple variants, or none                                                     | Pick ONE variant from `variants[]`. Send only its `required` fields.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `discriminator: [{field, value}]` on a `required` issue                    | Validator inferred which branch you targeted; you missed required fields IN that branch                                   | Read the `discriminator` pair, fill the missing required fields at the same level (don't nest under the discriminator field name).                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `hint:` field present on the issue                                         | SDK matched a curated shape-gotcha rule                                                                                   | Apply the hint directly — it's the validated fix path.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| 2-3 `additionalProperties` errors at the same pointer                      | You merged `oneOf` variants ({account_id, brand, operator, …})                                                            | Drop to one variant. Don't keep "extra" fields "for completeness".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `keyword: 'required'`, `pointer: '/idempotency_key'`                       | Mutating tool, no UUID                                                                                                    | Generate fresh UUID per logical operation. Reuse it on retries.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `keyword: 'type'` or `additionalProperties` at `/budget`                   | Sent `{amount, currency}`                                                                                                 | `budget` is a number. Currency is implied by `pricing_option_id`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `additionalProperties` at `/format_id` (string passed)                     | Sent `"format_id": "video_..."`                                                                                           | `format_id` is `{agent_url, id}` — always an object.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `keyword: 'enum'` at `/destinations/*/type`                                | Made-up destination type                                                                                                  | Use `'platform'` (with `platform`) or `'agent'` (with `agent_url`).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| Response carries `status: 'submitted'` and `task_id`                       | Async — work is queued, NOT done                                                                                          | Poll via `tasks/get` (A2A) or the MCP async task extension using `task_id`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `recovery: 'transient'` (rate limit, 5xx, timeout)                         | Server-side, retry-safe                                                                                                   | Retry with the **same** `idempotency_key`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `recovery: 'correctable'`                                                  | Buyer-side fix                                                                                                            | Read `issues[]`, patch the pointers, resend. Most cases close in one attempt.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `recovery: 'terminal'` (account suspended, payment required, …)            | Requires human action                                                                                                     | Don't retry. Surface to the user.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `VersionUnsupportedError` / `code: 'VERSION_UNSUPPORTED'` from `@adcp/sdk` | Seller cannot meet the configured AdCP 3 version or required capability guarantees; read the error's `reason` and message | Stop and report the incompatibility before business-tool dispatch. For end-of-life AdCP 2 or missing discovery, upgrade the seller to AdCP 3 with `get_adcp_capabilities`; if the application must retain AdCP 2 temporarily, use the exact older SDK pins in the [AdCP 2 migration guide](https://github.com/adcontextprotocol/adcp-client/blob/main/docs/migration-drop-adcp-2.md). Retrying or changing idempotency keys cannot fix protocol incompatibility.                                                                                                                                             |
+| `adcp_error.code: 'AUTH_MISSING'`                                          | No credential was presented                                                                                               | Escalate by default. Retry only if you own a credential supply or refresh path; otherwise surface re-auth to a human.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `adcp_error.code: 'AUTH_INVALID'`                                          | Credential was presented but rejected or revoked                                                                          | Do not retry blindly. Refresh once only if you own a valid refresh grant and the rejection is token-expiry-shaped; otherwise surface to a human to rotate credentials.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `adcp_error.code: 'AUTH_REQUIRED'`                                         | Legacy compatibility code; older sellers and some SDK helper paths still use it for missing or rejected credentials       | Treat as auth escalation by default. Retry only if your agent owns a credential-refresh path; otherwise surface to a human.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| HTTP 401 with `WWW-Authenticate` header                                    | Transport auth challenge; may be missing credentials, wrong scheme, rejected credentials, or required request signing     | Follow the challenge scheme. `Bearer` means send/refresh an OAuth-style `Authorization: Bearer ...` token. `Basic` means configure basic auth (`auth: { type: 'basic', username, password }` or `--auth user:pass --auth-scheme basic`) — `Bearer` will never succeed against that gateway. `Signature` means enable RFC 9421 request signing with an AdCP signing key, not an `Authorization` retry. **Saved aliases**: if registered with `--auth-scheme basic`, the scheme persists in `~/.adcp/config.json` and auto-applies on every later invocation — don't redundantly repeat the flag on each call. |
 
 If your symptom isn't here, fall through to the next section.
 

package/dist/lib/adapters/legacy/v2-5/create_media_buy.d.mts

@@ -1,3 +0,0 @@
-import type { CreateMediaBuyRequest, CreateMediaBuyResponse } from '../../../types/v2-5/index.mjs';
-import type { AdapterPair } from './types.mjs';
-export declare const createMediaBuyAdapter: AdapterPair<unknown, CreateMediaBuyRequest, CreateMediaBuyResponse, unknown>;

package/dist/lib/adapters/legacy/v2-5/create_media_buy.d.ts

@@ -1,3 +0,0 @@
-import type { CreateMediaBuyRequest, CreateMediaBuyResponse } from '../../../types/v2-5';
-import type { AdapterPair } from './types';
-export declare const createMediaBuyAdapter: AdapterPair<unknown, CreateMediaBuyRequest, CreateMediaBuyResponse, unknown>;

package/dist/lib/adapters/legacy/v2-5/create_media_buy.js

@@ -1,33 +0,0 @@
-"use strict";
-var __defProp = Object.defineProperty;
-var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
-var __getOwnPropNames = Object.getOwnPropertyNames;
-var __hasOwnProp = Object.prototype.hasOwnProperty;
-var __export = (target, all) => {
-  for (var name in all)
-    __defProp(target, name, { get: all[name], enumerable: true });
-};
-var __copyProps = (to, from, except, desc) => {
-  if (from && typeof from === "object" || typeof from === "function") {
-    for (let key of __getOwnPropNames(from))
-      if (!__hasOwnProp.call(to, key) && key !== except)
-        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
-  }
-  return to;
-};
-var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
-var create_media_buy_exports = {};
-__export(create_media_buy_exports, {
-  createMediaBuyAdapter: () => createMediaBuyAdapter
-});
-module.exports = __toCommonJS(create_media_buy_exports);
-var import_creative_adapter = require('../../../utils/creative-adapter.js');
-const createMediaBuyAdapter = {
-  toolName: "create_media_buy",
-  adaptRequest: import_creative_adapter.adaptCreateMediaBuyRequestForV2,
-  normalizeResponse: import_creative_adapter.normalizeMediaBuyResponse
-};
-// Annotate the CommonJS export names for ESM import in node:
-0 && (module.exports = {
-  createMediaBuyAdapter
-});

package/dist/lib/adapters/legacy/v2-5/create_media_buy.mjs

@@ -1,9 +0,0 @@
-import { adaptCreateMediaBuyRequestForV2, normalizeMediaBuyResponse } from "../../../utils/creative-adapter.mjs";
-const createMediaBuyAdapter = {
-  toolName: "create_media_buy",
-  adaptRequest: adaptCreateMediaBuyRequestForV2,
-  normalizeResponse: normalizeMediaBuyResponse
-};
-export {
-  createMediaBuyAdapter
-};

package/dist/lib/adapters/legacy/v2-5/get_products.d.mts

@@ -1,8 +0,0 @@
-import type { GetProductsRequest, GetProductsResponse } from '../../../types/v2-5/index.mjs';
-import type { AdapterPair } from './types.mjs';
-/**
- * v3 ↔ v2.5 adapter pair for `get_products`. Wraps the existing scattered
- * adapter helpers so the registry pattern lands without behavior change;
- * a focused refactor of the underlying implementation can follow.
- */
-export declare const getProductsAdapter: AdapterPair<unknown, GetProductsRequest, GetProductsResponse, unknown>;

package/dist/lib/adapters/legacy/v2-5/get_products.d.ts

@@ -1,8 +0,0 @@
-import type { GetProductsRequest, GetProductsResponse } from '../../../types/v2-5';
-import type { AdapterPair } from './types';
-/**
- * v3 ↔ v2.5 adapter pair for `get_products`. Wraps the existing scattered
- * adapter helpers so the registry pattern lands without behavior change;
- * a focused refactor of the underlying implementation can follow.
- */
-export declare const getProductsAdapter: AdapterPair<unknown, GetProductsRequest, GetProductsResponse, unknown>;

package/dist/lib/adapters/legacy/v2-5/get_products.js

@@ -1,33 +0,0 @@
-"use strict";
-var __defProp = Object.defineProperty;
-var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
-var __getOwnPropNames = Object.getOwnPropertyNames;
-var __hasOwnProp = Object.prototype.hasOwnProperty;
-var __export = (target, all) => {
-  for (var name in all)
-    __defProp(target, name, { get: all[name], enumerable: true });
-};
-var __copyProps = (to, from, except, desc) => {
-  if (from && typeof from === "object" || typeof from === "function") {
-    for (let key of __getOwnPropNames(from))
-      if (!__hasOwnProp.call(to, key) && key !== except)
-        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
-  }
-  return to;
-};
-var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
-var get_products_exports = {};
-__export(get_products_exports, {
-  getProductsAdapter: () => getProductsAdapter
-});
-module.exports = __toCommonJS(get_products_exports);
-var import_pricing_adapter = require('../../../utils/pricing-adapter.js');
-const getProductsAdapter = {
-  toolName: "get_products",
-  adaptRequest: import_pricing_adapter.adaptGetProductsRequestForV2,
-  normalizeResponse: import_pricing_adapter.normalizeGetProductsResponse
-};
-// Annotate the CommonJS export names for ESM import in node:
-0 && (module.exports = {
-  getProductsAdapter
-});

package/dist/lib/adapters/legacy/v2-5/get_products.mjs

@@ -1,9 +0,0 @@
-import { adaptGetProductsRequestForV2, normalizeGetProductsResponse } from "../../../utils/pricing-adapter.mjs";
-const getProductsAdapter = {
-  toolName: "get_products",
-  adaptRequest: adaptGetProductsRequestForV2,
-  normalizeResponse: normalizeGetProductsResponse
-};
-export {
-  getProductsAdapter
-};

package/dist/lib/adapters/legacy/v2-5/index.d.mts

@@ -1,34 +0,0 @@
-/**
- * Registry of legacy v2.5 adapter pairs, one per AdCP tool.
- *
- * The SDK's current pin (v3 today) is implicit — this module describes
- * what the buyer sends to and receives from a v2.5 seller, regardless of
- * which v3.x patch the SDK itself speaks. When the SDK pin moves to v4,
- * this directory continues to hold the v2.5 compat shim and a sibling
- * `legacy/v3/` would join for v3 sellers.
- *
- * Add a new tool by:
- *   1. Drop a per-tool module in this directory exporting an
- *      `AdapterPair<V3Req, V25Req, V25Res, V3Res>`.
- *   2. Register it below.
- *   3. Add a fixture to `test/lib/adapter-v2-5-conformance.test.js`.
- *
- * Naming intentionally matches `legacy/<seller-version>/`, NOT
- * `<sdk-version>-to-<seller-version>/`. Real ad-tech compat layers carry
- * N=1 active legacy shim with a deprecation runway (OpenRTB, Prebid, GAM
- * all behave this way) — the directory tree should reflect "exceptional,
- * time-boxed" rather than encoding a matrix nobody will staff.
- */
-import type { AdapterPair } from './types.mjs';
-export type { AdapterPair } from './types.mjs';
-/**
- * Look up the legacy adapter pair for a given AdCP tool when targeting
- * a v2.5 seller. Returns `undefined` for tools without a registered pair
- * — caller should pass the request through unchanged.
- */
-export declare function getV25Adapter(toolName: string): AdapterPair | undefined;
-/**
- * Names of tools registered for v2.5 adaptation. Used by the conformance
- * test suite as the authoritative list.
- */
-export declare function listV25AdapterTools(): string[];