feat: adopt signed AdCP 3.3.0-beta.3 and serve the reporting-subscription surface

.changeset/reporting-subscription-beta3.md

@@ -0,0 +1,18 @@
+---
+'@adcp/sdk': minor
+---
+
+**Beta-channel break:** this SDK advertises and negotiates only the AdCP `3.3-beta.3` preview and no longer packages or advertises `3.3-beta.2`. A buyer or seller still on beta.2 (SDK 17.0.0-beta.10) will not select the 3.3 preview with this release; the pair negotiates a shared stable release (3.2.7, 3.1.31 or 3.0.25) instead. Upgrade both sides together to keep exercising 3.3 preview features. An explicit `adcpVersion: '3.3.0-beta.2'` pin now fails with a configuration error.
+
+Adopt the signed AdCP 3.3.0-beta.3 bundle, replacing 3.3.0-beta.2. Public types, Zod schemas, tool metadata and the packaged compliance corpus are regenerated from the beta.3 release.
+
+- Every 3.3 task response composes the protocol envelope (adcp#8547): `status` is required on every response, and the generated response types no longer restate envelope fields.
+- Account requests (adcp#8620): resolved `matched`/`created` records carry `account` with its money terms, an `updated` money change carries `effective_at`, and a change that `created` a separate account carries `not_carried_over`.
+- Experimental live creative updates: `creative.live_updates` types, `CREATIVE_LIVE_UPDATE_UNSUPPORTED`, and the `creative.staged_update_changed` notification type, which joins `ACCOUNT_NOTIFICATION_TYPES`.
+- Reporting subscriptions: `authorization.regranted_at` joins the account authorization fields (`toWireAccount` and `windDownGrant` keep it); media buys carry `cancellation_effective_at` and `flight_history`, packages `reporting_delivery_offering_ids`, offerings `available_from`/`withdrawn_at`, billing obligations `stub`, and `subscription_coverage[].status` is served as `inactive` with `deactivated_at`. Readbacks list at most 16 `prior_versions` and carry `prior_versions_count`, `accounts_with_exceptions_count` and `accounts_unauthorized_count`. A subscription response served without a negotiated release uses the pinned release, as in the Python SDK.
+
+**Removed from `@adcp/sdk/reporting/advanced`:** the hand-modelled wire types `ReportingDeliveryOfferingWithDimensionsV1`, `ReportingSubscriptionCoverageWithOfferingsV1`, `ReportingSubscriptionExclusionEntryV1`, `ReportingSubscriptionGapV1`, `ReportingSubscriptionInactiveIntervalV1`, `ReportingSubscriptionStateWithIntervalsV1` and `ReportingSubscriptionTimezoneCutoverV1`. The generated `ReportingDeliveryOffering`, `ReportingSubscriptionCoverage` and `ReportingSubscriptionState` carry every field; `ReportingSubscriptionOfferingV1` is now an alias of `ReportingDeliveryOffering`.
+
+Codegen follows the beta.3 envelope layout: the `request_proposals`, `refine_proposals` and `decline_proposals` submitted arms keep `status: 'submitted'` and the required `task_id` (folded from `core/task-submitted.json`), and generated Zod response schemas keep the `adcp_version`, `adcp_major_version`, `task_id` and `message` constraints they inherit through the composed envelopes.
+
+A terminal task webhook's `result` is the task's full response, so on 3.1+ it now carries the task `status` (`completed` or `rejected`) like a synchronous response, and a media-buy lifecycle value a platform returned in `status` moves to `media_buy_status`, as on the synchronous path. A 3.2 `list_products` / `decline_proposals` result and a 3.0 result are left as returned.

ADCP_VERSION

@@ -1 +1 @@
-3.3.0-beta.2
+3.3.0-beta.3

AGENTS.md

@@ -265,7 +265,7 @@ npm run generate-zod-schemas  # Generate runtime validation
 
 ### Wire-version compat (v3 SDK ↔ legacy sellers)
 
-The SDK speaks one AdCP major (`ADCP_VERSION` in `src/lib/version.ts`, currently `3.3.0-beta.2`) on its public surface and adapts to legacy sellers underneath. AdCP 2 support has been removed following its August 1, 2026 end of life. Maintained AdCP 3 compatibility and the policy for future major-version support are documented in [`docs/development/WIRE-VERSION-COMPAT.md`](https://github.com/adcontextprotocol/adcp-client/blob/main/docs/development/WIRE-VERSION-COMPAT.md). Touch that doc whenever you add to `src/lib/adapters/legacy/`, `src/lib/types/v*-*/`, or `schemas/cache/<version>/`.
+The SDK speaks one AdCP major (`ADCP_VERSION` in `src/lib/version.ts`, currently `3.3.0-beta.3`) on its public surface and adapts to legacy sellers underneath. AdCP 2 support has been removed following its August 1, 2026 end of life. Maintained AdCP 3 compatibility and the policy for future major-version support are documented in [`docs/development/WIRE-VERSION-COMPAT.md`](https://github.com/adcontextprotocol/adcp-client/blob/main/docs/development/WIRE-VERSION-COMPAT.md). Touch that doc whenever you add to `src/lib/adapters/legacy/`, `src/lib/types/v*-*/`, or `schemas/cache/<version>/`.
 
 ## Testing Strategies
 

README.md

@@ -30,12 +30,12 @@ AdCP operations are **distributed and asynchronous by default**. An agent might:
 
 ```bash
 npm install @adcp/sdk              # 16.x, AdCP 3.2
-npm install @adcp/sdk@beta         # 17.x beta, AdCP 3.3.0-beta.2 (development/staging)
+npm install @adcp/sdk@beta         # 17.x beta, AdCP 3.3.0-beta.3 (development/staging)
 npm install @adcp/sdk@adcp-3.1     # 13.x, maintained AdCP 3.1 line
 npm install @adcp/sdk@adcp-3.0     # 7.11.x, AdCP 3.0
 ```
 
-SDK 17 beta adopts the signed AdCP `3.3.0-beta.2` bundle and includes the breaking
+SDK 17 beta adopts the signed AdCP `3.3.0-beta.3` bundle and includes the breaking
 HTML-markup `display_tag` mapping. See the [beta release notes](./docs/releases/17.0.0-beta.0.md)
 and [16 → 17 migration guide](./docs/migration-16-to-17.md). Keep production on SDK 16.
 

bin/adcp.js

@@ -2079,7 +2079,7 @@ RUN OPTIONS (full assessment):
   --storyboards IDS   Comma-separated storyboard/bundle IDs to run
   --compliance-version VERSION
                       Select a compliance cache version, e.g. 3.1.31 or
-                      3.3.0-beta.2. The runner uses this cache for
+                      3.3.0-beta.3. The runner uses this cache for
                       storyboard resolution and wire-version defaults. When
                       --test-kit points into a compliance cache, its version is
                       selected automatically; an explicit mismatch is rejected.

docs/TYPE-SUMMARY.md

@@ -1,6 +1,6 @@
 # AdCP Type Summary
 
-> Generated at: 2026-10-30
+> Generated at: 2026-10-31
 > @adcp/sdk v17.0.0-beta.10
 
 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`.
@@ -575,7 +575,7 @@ Request parameters for get_task_status, the 3.
 _Request:_
 ```
 {
-  task_id: string  // required
+  task_id: Task Id  // required
   account: Account Ref
   include_history: boolean
   include_result: boolean
@@ -586,10 +586,8 @@ _Request:_
 _Response (success branch):_
 ```
 {
-  task_id: string  // required
   task_type: Task Type  // required
   protocol: Adcp Protocol  // required
-  status: Task Status  // required
   created_at: string  // required
   updated_at: string  // required
   completed_at: string
@@ -684,6 +682,7 @@ Read caller-scoped connection configuration, version, and destination setup stat
 _Request:_
 ```
 {
+  reporting_subscription_page: object
   context: Context
 }
 ```
@@ -998,12 +997,10 @@ _Response (success branch):_
   products: Canonical Product[]  // required
   feed_version: string  // required
   cache_scope: 'public' | 'account'  // required
-  adcp_version: string
   collections: Response Collection[]
   next_cursor: string
   pricing_version: string
   incomplete: object[]
-  replayed: 'true'
   context: Context
 }
 ```
@@ -1038,7 +1035,6 @@ _Response (success branch):_
   proposals: object[]  // required
   opportunities: object[]  // required
   next_cursor: string
-  replayed: 'true'
   context: Context
 }
 ```
@@ -1069,7 +1065,6 @@ _Response (success branch):_
   collections_version: string  // required
   cache_scope: 'public' | 'account'  // required
   pagination: Pagination Response
-  replayed: 'true'
   context: Context
 }
 ```
@@ -1102,16 +1097,13 @@ _Response (success branch):_
   outcome: 'proposed'  // required
   proposals: Canonical Proposal[]  // required
   products: Canonical Product[]  // required
-  adcp_version: string
   collections: Response Collection[]
   incomplete: object[]
   targeting_resolution: Get Products Targeting Resolution
   later_proposals: Later Proposals State
-  status: 'completed'
-  message: string
   errors: Error[]
   context: Context
-  replayed: 'true'
+  status: 'completed'
 }
 ```
 
@@ -1138,13 +1130,10 @@ _Response (success branch):_
 {
   results: union[]  // required
   products: Canonical Product[]  // required
-  adcp_version: string
   collections: Response Collection[]
-  status: 'completed'
-  message: string
   errors: Error[]
   context: Context
-  replayed: 'true'
+  status: 'completed'
 }
 ```
 
@@ -1170,10 +1159,9 @@ _Response (success branch):_
 ```
 {
   results: object[]  // required
-  message: string
   errors: Error[]
   context: Context
-  replayed: 'true'
+  status: 'completed'
 }
 ```
 
@@ -1289,7 +1277,6 @@ _Response (success branch):_
   available_actions: Canonical Media Buy Action[]
   warnings: Warning[]
   context: Context
-  replayed: 'true'
 }
 ```
 
@@ -1688,7 +1675,6 @@ _Response (success branch):_
   outcome: 'recorded'  // required
   issue: Media Buy Issue  // required
   context: Context
-  replayed: boolean
 }
 ```
 
@@ -1716,7 +1702,6 @@ _Response (success branch):_
   outcome: 'found'  // required
   issue: Media Buy Issue  // required
   context: Context
-  replayed: boolean
 }
 ```
 
@@ -2100,7 +2085,7 @@ _Request:_
   include_webhook_activity: boolean
   webhook_activity_limit: integer
   account: Account Ref
-  fields: ('creative_id' | 'name' | 'format_id' | 'format_kind' | 'format_option_ref' | 'assets' | 'status' | 'created_date' | 'updated_date' | 'tags' | 'provenance' | 'rights' | 'rights_attestation_evaluations' | 'localization' | 'localization_unavailable' | 'assignments' | 'snapshot' | 'items' | 'variables' | 'concept' | 'pricing_options')[]
+  fields: ('creative_id' | 'name' | 'format_id' | 'format_kind' | 'format_option_ref' | 'assets' | 'status' | 'created_date' | 'updated_date' | 'tags' | 'provenance' | 'rights' | 'rights_attestation_evaluations' | 'localization' | 'localization_unavailable' | 'assignments' | 'snapshot' | 'items' | 'variables' | 'concept' | 'pricing_options' | 'staged_update')[]
   context: Context
 }
 ```
@@ -2268,7 +2253,6 @@ _Response (success branch):_
 {
   list: Property List  // required
   auth_token: string  // required
-  replayed: boolean
   context: Context
 }
 ```
@@ -2297,7 +2281,6 @@ _Response (success branch):_
 ```
 {
   list: Property List  // required
-  replayed: boolean
   context: Context
 }
 ```
@@ -2372,7 +2355,6 @@ _Response (success branch):_
 {
   deleted: boolean  // required
   list_id: string  // required
-  replayed: boolean
   context: Context
 }
 ```
@@ -2400,7 +2382,6 @@ _Response (success branch):_
 {
   list: Collection List  // required
   auth_token: string  // required
-  replayed: boolean
   context: Context
 }
 ```
@@ -2429,7 +2410,6 @@ _Response (success branch):_
 ```
 {
   list: Collection List  // required
-  replayed: boolean
   context: Context
 }
 ```
@@ -2504,7 +2484,6 @@ _Response (success branch):_
 {
   deleted: boolean  // required
   list_id: string  // required
-  replayed: boolean
   context: Context
 }
 ```
@@ -2727,7 +2706,6 @@ _Response (success branch):_
 ```
 {
   plans: object[]  // required
-  replayed: boolean
   context: Context
 }
 ```
@@ -2762,7 +2740,6 @@ _Response (success branch):_
   delivery_period_state: 'open' | 'closed'
   findings: object[]
   plan_summary: object
-  replayed: boolean
   context: Context
 }
 ```
@@ -2800,7 +2777,6 @@ _Response (success branch):_
   amount: object  // required
   headroom_restored: number  // required
   plan_summary: object  // required
-  replayed: boolean
   context: Context
 }
 ```
@@ -2878,7 +2854,6 @@ _Response (success branch):_
   mode: Governance Mode
   runtime_attestation_evaluations: Attestation Evaluation[]
   runtime_attestation_binding_digest: string
-  governance_context: string
   context: Context
 }
 ```

docs/development/WIRE-VERSION-COMPAT.md

@@ -79,7 +79,7 @@ from `@adcp/sdk/v2/projection`. These advisories remain outside the wire JSON.
 
 ```text
 schemas/cache/
-├── 3.3.0-beta.2/ # primary SDK pin
+├── 3.3.0-beta.3/ # primary SDK pin
 ├── 3.2.7/        # maintained stable release
 ├── 3.1.31/      # maintained stable release
 ├── 3.0.25/      # maintained stable release
@@ -88,11 +88,11 @@ schemas/cache/
 
 Run `npm run sync-schemas:all` to refresh the primary and maintained bundles. Run `npm run generate-types:all` to regenerate public types, then `npm run build:lib` to build and copy supported schemas into the package. `copy-schemas-to-dist.ts` excludes retired AdCP 2 caches even when present locally. `check-publish-protocol-artifacts.mjs` checks the published schema inventory and rejects retired type exports.
 
-The v17 beta primary pin is the signed AdCP 3.3.0-beta.2 bundle; it replaces 3.3.0-beta.1, which is no longer packaged or advertised. Stable SDK 16 remains on AdCP 3.2.7. The beta retains stable AdCP 3.2.7, 3.1.31 and 3.0.25 bundles for negotiation, schema projection and compliance runs.
+The v17 beta primary pin is the signed AdCP 3.3.0-beta.3 bundle; it replaces 3.3.0-beta.2, which is no longer packaged or advertised. Stable SDK 16 remains on AdCP 3.2.7. The beta retains stable AdCP 3.2.7, 3.1.31 and 3.0.25 bundles for negotiation, schema projection and compliance runs.
 
 Compliance pins select exact fixture bytes, unlike same-minor wire schema aliases. SDK 16.5.0 packages the 3.2.7 corpus; when upgrading from SDK 16.4.0, update explicit `--compliance-version 3.2.5` flags to `3.2.7`. A development pin of `3.2.6` must likewise advance. Retain the matching historical SDK if a run requires that older corpus. The maintained 3.1.31 and 3.0.25 corpora remain packaged.
 
-Build tooling also understands exact AdCP 3.3.0 `beta.N` and `rc.N` pins. Such a build retains maintained AdCP 3.0, 3.1, and 3.2 GA aliases through 3.2.7 while advertising only the selected prerelease, without a moving beta/RC-family alias. SDK 17 selects the exact 3.3.0-beta.2 preview. The stable v16 compatibility list continues to advertise only AdCP 3.2 and earlier.
+Build tooling also understands exact AdCP 3.3.0 `beta.N` and `rc.N` pins. Such a build retains maintained AdCP 3.0, 3.1, and 3.2 GA aliases through 3.2.7 while advertising only the selected prerelease, without a moving beta/RC-family alias. SDK 17 selects the exact 3.3.0-beta.3 preview. The stable v16 compatibility list continues to advertise only AdCP 3.2 and earlier.
 
 Conformance validates current and unversioned response payloads without synthesizing task status. The existing status-optional compatibility shim applies only to explicitly declared AdCP 3.0 payloads, and never to status-free compact tools. Closed response schemas admit only the canonical version-envelope fields alongside their declared task fields; other root restrictions and nested-body constraints remain enforced.
 

docs/development/v17-beta-plan.md

@@ -1,17 +1,17 @@
 # SDK 17 beta adoption
 
-SDK 17 beta adopts the published AdCP `3.3.0-beta.2` protocol bundle and publishes under `beta`. SDK 16 remains the stable AdCP 3.2 line on npm `latest`.
+SDK 17 beta adopts the published AdCP `3.3.0-beta.3` protocol bundle and publishes under `beta`. SDK 16 remains the stable AdCP 3.2 line on npm `latest`.
 
 ## Selected protocol bundle
 
-- Release: [AdCP v3.3.0-beta.2](https://github.com/adcontextprotocol/adcp/releases/tag/v3.3.0-beta.2), published October 30, 2026. It replaces [v3.3.0-beta.1](https://github.com/adcontextprotocol/adcp/releases/tag/v3.3.0-beta.1) (commit `c0dfa90c28bcb768f70b4da1dfc3ca057050fa0a`), which SDK 17 no longer packages or advertises.
-- Protocol commit: `fa39ca874b10ab7cf17d5cfa52abdce58b2dd274`.
-- Bundle SHA-256: `d75dc90192a2d13ffae2103f30bd505040a7ff0a40f8a7946d82730428dd6e8a`.
+- Release: [AdCP v3.3.0-beta.3](https://github.com/adcontextprotocol/adcp/releases/tag/v3.3.0-beta.3), published October 31, 2026. It replaces [v3.3.0-beta.2](https://github.com/adcontextprotocol/adcp/releases/tag/v3.3.0-beta.2) (commit `fa39ca874b10ab7cf17d5cfa52abdce58b2dd274`), which SDK 17 no longer packages or advertises.
+- Protocol commit: `a6106149a2b5c929eec0caa0042adbae4ccf3a9c`.
+- Bundle SHA-256: `ba61919ca0c9d67874604fbbca8945c133eaceed65da1ac962f78d94d7879f00`.
 - Source: the versioned protocol release tarball, verified by SHA-256 and the AdCP release workflow's cosign certificate. No moving branch or PR snapshot is used.
 
 ## SDK changes
 
-The primary pin is `3.3.0-beta.2`, with generated public types, runtime validators, tool metadata and documentation from that bundle. The package retains stable 3.2.7, 3.1.31 and 3.0.25 schemas and compliance corpora. Preview compatibility is exact: `3.3.0-beta.2` and `3.3-beta.2`, without a moving family alias. Moving from beta.1 to beta.2 is a beta-channel break: a beta.1 peer no longer negotiates the preview with this SDK and falls back to a shared stable release. Buyer negotiation requires an exact advertised preview and otherwise uses an available stable release.
+The primary pin is `3.3.0-beta.3`, with generated public types, runtime validators, tool metadata and documentation from that bundle. The package retains stable 3.2.7, 3.1.31 and 3.0.25 schemas and compliance corpora. Preview compatibility is exact: `3.3.0-beta.3` and `3.3-beta.3`, without a moving family alias. Moving from beta.2 to beta.3 is a beta-channel break: a beta.2 peer no longer negotiates the preview with this SDK and falls back to a shared stable release. Buyer negotiation requires an exact advertised preview and otherwise uses an available stable release.
 
 The HTML-markup `display_tag` mapping from [#3361](https://github.com/adcontextprotocol/adcp-client/pull/3361) is included as a major changeset. `display_html` and `display_WxH_html` project to inline-markup `display_tag`; actual `html5` zip creatives no longer match HTML-markup-only products. Delivery retains seller format identity, filters by delivery type and emits markup through the legacy HTML asset contract. SDK 16 keeps its previous mapping. See the [16 → 17 migration guide](../migration-16-to-17.md).
 

docs/guides/DELIVERY-WEBHOOK-PARSING.md

@@ -120,7 +120,7 @@ is not a delivery-data webhook.
 `notification_type: 'final'` concerns report scheduling; envelope `completed`
 does not mean the media buy has finished. Per-buy state remains in
 `media_buy_deliveries[].status`. This follows the protocol's
-[envelope/result distinction](https://github.com/adcontextprotocol/adcp/blob/v3.3.0-beta.2/docs/building/by-layer/L3/webhooks.mdx#payload-anatomy-envelope-vs-result).
+[envelope/result distinction](https://github.com/adcontextprotocol/adcp/blob/v3.3.0-beta.3/docs/building/by-layer/L3/webhooks.mdx#payload-anatomy-envelope-vs-result).
 
 The protocol also requires receivers to ignore `aggregated_totals` in pushed
 reports as an authority source. The parser preserves that field for auditing