Best possible solution:

Keep the PR open for maintainer review and CI. The desired end state is a focused OpenAI provider test that verifies the Codex native transport handoff while preserving confidence that the provider still uses the canonical SDK stream-family behavior.

Acceptance criteria:

• pnpm test extensions/openai/openai-provider.test.ts -- --reporter=verbose
• pnpm test:changed
• pnpm exec oxfmt --check --threads=1 extensions/openai/openai-provider.test.ts
• pnpm check:changed
• git diff --check

What I checked:

• Protected label: The provided GitHub context lists the maintainer label on this open PR, so the cleanup policy requires explicit maintainer handling rather than auto-close or repair automation.
• PR diff scope: The public PR diff modifies only extensions/openai/openai-provider.test.ts, adding a hoisted mock object, mocking openclaw/plugin-sdk/provider-stream-family, resetting the native transport mock before each test, and asserting the Codex native transport call. (extensions/openai/openai-provider.test.ts:1, 79dac5e4b309)
• Production native Codex route: Current main's attribution wrapper routes openai-codex traffic through codexNativeTransportStreamFn when injected, otherwise through createOpenAIResponsesTransportStreamFn(), matching the PR's stated native transport concern. (src/agents/pi-embedded-runner/openai-stream-wrappers.ts:491, 7c51cd2baf1c)
• SDK hook composition: Current main's OpenAI Responses stream-family hook composes attribution, fast mode, service tier, text verbosity, Codex native web search, string content, thinking-level, reasoning compatibility, and context management wrappers. (src/plugin-sdk/provider-stream.ts:103, 7c51cd2baf1c)
• OpenAI plugin SDK boundary: The OpenAI plugin builds provider hooks from OPENAI_RESPONSES_STREAM_HOOKS via the plugin SDK subpath and wraps it with provider-local native web search behavior, so the PR is changing a test around the same boundary production uses. (extensions/openai/shared.ts:86, 7c51cd2baf1c)
• Current main test path: Current main's Codex wrapper composition test still calls runWrappedPayloadCase, whose fake upstream stream invokes options.onPayload; that is the path the PR replaces with a native transport mock for Codex. (extensions/openai/openai-provider.test.ts:679, 7c51cd2baf1c)

Likely related people:

• steipete: Recent public history shows OpenAI provider, native web search, native transport, and OpenAI provider test maintenance, including the native attribution transport change this PR adapts to. (role: recent maintainer; confidence: high; commits: d1b2d81752b8, 713807b55d0b, a81c4757311a; files: src/agents/pi-embedded-runner/openai-stream-wrappers.ts, extensions/openai/openai-provider.test.ts, extensions/openai/shared.ts)
• vincentkoc: Public history links this maintainer to shared provider stream hook families and provider stream wrapper composition, which is the SDK boundary mocked by the PR. (role: SDK stream-family owner; confidence: medium; commits: eea7ba53455a, 30479b4ee049, 7ad72281f73d; files: src/plugin-sdk/provider-stream.ts, src/plugin-sdk/provider-stream-family.ts)
• jalehman: Although this person authored the PR, they also appear in merged history for moving provider replay/runtime ownership into plugins, which is adjacent to the OpenAI provider test and plugin boundary touched here. (role: prior provider runtime contributor; confidence: medium; commits: 799c6f40aa69; files: extensions/openai/openai-provider.test.ts, extensions/openai/shared.ts, src/plugin-sdk/provider-stream.ts)
• a-tokyo: Public history links this contributor to OpenAI Responses thinking-level mapping in the current stream-family chain, which maintainers may want to keep aligned when reviewing the mocked chain. (role: adjacent wrapper contributor; confidence: low; commits: c92490881b71; files: src/plugin-sdk/provider-stream.ts, src/agents/pi-embedded-runner/openai-stream-wrappers.ts)

Remaining risk / open question:

• I did not run tests because this review was explicitly read-only; the PR body reports targeted test, changed-test, formatter, changed-check, and diff-check runs.
• The PR mock reimplements the SDK stream-family chain to inject the native transport and does not include the non-exported string-content or thinking-level wrappers from current main's production hook; this was not a proven bug in the changed assertion, but it is the main point for maintainer review.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 7c51cd2baf1c.