chore: release package (beta)

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@adcp/sdk@8.1.0-beta.14

Minor Changes

• 965fb43: Add shared mock-server scenario scaffolding for storyboard fixtures: token-protected /_scenario/* HTTP routes surfaced in mock-server summaries, programmatic handle.scenario, fixture reset/state snapshots, authenticated scripted fault responses, loopback-only webhook emit/capture stubs, and exact idempotency_key replay handling on state-creation mock routes.

• 8ec6cbd: Expose a public schema-root override for hosted compliance runs via schemaRoot options and registerExternalSchemaRoot from @adcp/sdk/testing.

• 35947d7: Harden RegistryClient transport defaults with timeout, max body size, redirect policy, and injectable fetch options. The default registry host now uses the canonical upstream registry, and callers pinned to the legacy host can either update baseUrl or opt into redirect: 'follow'.

  Regenerate registry OpenAPI types so CreateAdagentsRequest accepts catalog metadata fields for community mirror manifests, while preserving backward-compatible listAgents()/listPublishers() source summaries and the legacy type: 'si' list-agent filter. Add CI drift checks that regenerate registry types from the bundled upstream registry OpenAPI before validating generated files.

• 748e5c9: breaking: remove the preview RFC 9421 transport response-signing surface from the beta line

  AdCP 3.x does not authorize generic RFC 9421 §2.2.9 transport response signing. The SDK no longer exports signResponse, signResponseAsync, verifyResponseSignature, createResponseVerifier, ResponseSignatureError, RESPONSE_SIGNING_TAG, RESPONSE_MANDATORY_COMPONENTS, buildResponseSignatureBase, ResponseLike, prepareResponseSignature, finalizeResponseSignature, SignResponseOptions, PreparedResponseSignature, SignedResponse, the response-verifier option/result types, or the 'response-signing' JWK purpose.

  Runtime helpers also reject the retired purpose: pemToAdcpJwk({ adcp_use: 'response-signing' }) and mintEphemeralEd25519Key({ adcp_use: 'response-signing' }) now throw, and InMemorySigningProvider preserves retired or unknown raw purpose strings so signRequestAsync() and signWebhookAsync() still fail closed instead of silently treating the key as unscoped.

  Request signing and webhook signing are unchanged. There is no conformant AdCP 3.x replacement for generic transport response signing; future designated-task payload JWS support should land under a fresh spec-defined purpose and helper surface.

• 2764c56: Adopt several SDK-side follow-ups unblocked by the AdCP 3.1 schema cache.

  • Preserve explicit conversion_tracking.supported_targets declarations without inventing a default; omitted values mean only target-less event goals are guaranteed.
  • Allow supported_optimization_metrics to derive from a static productCatalog.
  • Treat sponsored-intelligence as a first-class specialism in compile-time and runtime platform validation, and update the SI example/skill docs.
  • Align upstream-recorder RecordedCall output with the cached 3.1 query_upstream_traffic schema, including raw/digest attestation metadata, payload length, and digest-mode identifier proofs.
  • Honor storyboard required_any_of_tools gates with requirement_unmet skips and skip-cause aggregation.

  BREAKING:

  • RecordedCall is now a raw/digest discriminated union for the 3.1 query_upstream_traffic response. Raw calls carry payload and payload_length; digest calls carry payload_digest_sha256, payload_length, and optional identifier_match_proofs. Consumers that assumed RecordedCall.payload was always present, or that construct RecordedCall literals, need to handle the branch-specific fields.
  • validatePlatform now rejects specialisms: ['sponsored-intelligence'] unless the platform provides the sponsoredIntelligence implementation required by that specialism. Adapters that previously advertised the specialism without dispatch support must either add the platform field or stop advertising the specialism.

• 363ddf5: Add seed_buyer_agent support for comply_test_controller and storyboard controller seeding.

Patch Changes

• 6e7dfa4: Dedupe core-authored shared schemas from generated tool types while preserving compatibility re-exports.
• 0938599: Add a proxy-seller Snap bridge example and let bridgeFromSessionStore loaders receive the resolved bridge context.
• b6a3d89: Fix compliance storyboard negotiation for strict legacy AdCP 3.0 sellers by using a major-only version envelope and validating responses against the negotiated server version.
• 8502e9f: Preserve ZodObject JavaScript ergonomics for additional record/object schema intersections.