Add missing cdpHeaders field to v3 server openapi spec
Merged
PI
8mo ago+12+12+01234567890123456789-0-0-0123456789
why
cdpHeaders is already plumbed through packages/server correctly, it was just missing from the spec.
- packages/core/lib/v3/types/public/api.ts:15 defines cdpHeaders on LocalBrowserLaunchOptionsSchema.
- packages/server/src/routes/v1/sessions/start.ts:192 forwards browser.launchOptions with a spread into localBrowserLaunchOptions, so cdpHeaders is preserved.
- packages/server/src/lib/InMemorySessionStore.ts:240 passes localBrowserLaunchOptions straight into new V3(...).
- packages/core/lib/v3/v3.ts:750 passes lbo.cdpHeaders into V3Context.create(...).
- packages/core/lib/v3/understudy/context.ts:167 finally uses it in CdpConnection.connect(wsUrl, { headers: opts?.cdpHeaders }).
what changed
test plan
Summary by cubic
Added the missing cdpHeaders field to the v3 server OpenAPI spec so clients can send custom Chrome DevTools Protocol headers. This aligns the spec with server launch options and prevents client codegen/validation errors.