[codex] refresh plugin regression fixtures#79444
[codex] refresh plugin regression fixtures#79444JayZeeDesign wants to merge 3 commits intoopenclaw:mainfrom
Conversation
|
Codex review: needs maintainer review before merge. Summary Reproducibility: not applicable. this is a test fixture refresh PR, not a user bug report. The relevant behavior is reviewable from the current formatter/helper source, the PR diff, CI state, and supplied terminal proof. Real behavior proof Next step before merge Security Review detailsBest possible solution: Land the focused test-only fixture refresh after normal maintainer review, while leaving production SSRF and channel streaming behavior unchanged. Do we have a high-confidence way to reproduce the issue? Not applicable: this is a test fixture refresh PR, not a user bug report. The relevant behavior is reviewable from the current formatter/helper source, the PR diff, CI state, and supplied terminal proof. Is this the best way to solve the issue? Yes: deterministic guarded-network mocks and updated fixture expectations are the narrowest maintainable fix for this drift. Changing production SSRF, progress formatting, or channel behavior would be broader than this PR's scope. What I checked:
Likely related people:
Codex review notes: model gpt-5.5, reasoning high; reviewed against 8cd978c02a74. |
1abd17d to
42a0ebc
Compare
|
Ready for maintainer landing. Current head: I rebased onto current I attempted direct push, merge, and auto-merge, but GitHub rejected them because |
42a0ebc to
08cb36b
Compare
08cb36b to
4a1f5ed
Compare
4a1f5ed to
30f5891
Compare
30f5891 to
fe64d6a
Compare
fe64d6a to
f777268
Compare
f777268 to
11d879a
Compare
11d879a to
2254eb8
Compare
2254eb8 to
0ebf77c
Compare
fe31f70 to
e51ac85
Compare
e51ac85 to
eaacc6d
Compare
a8043ec to
2d6debd
Compare
2d6debd to
9f5e0cd
Compare
9f5e0cd to
b6a7da6
Compare
Summary
main.Real behavior proof
Behavior addressed: Bundled plugin surfaces should still load and expose their runtime command/tool/channel account contracts after the regression fixture updates. The failing areas covered by this patch were deterministic test regressions around guarded network fetch/navigation, staged media outputs, progress streaming line windows, current Codex media thread fixtures, and one current-main extension lint assertion.
Real environment tested: Local macOS checkout after this patch, using the built OpenClaw dist entrypoint at
dist/index.jsand the publishednpm:@openclaw/kitchen-sink@latestplugin fixture.Exact steps or command run after this patch:
pnpm test:plugins:kitchen-sink-rpcEvidence after fix: Terminal output from a real local OpenClaw kitchen-sink RPC walk:
Observed result after fix: OpenClaw loaded the kitchen-sink plugin through the dist entrypoint, discovered the expected command aliases, discovered all three kitchen-sink catalog tools, resolved the local channel account as ready/linked/running/connected, and completed the account probe successfully.
What was not tested: Live third-party provider/channel credentials were not exercised because this patch changes test fixtures and support mocks only; broad plugin contracts and extension shards were run as supplemental coverage.
Verification
pnpm test:plugins:kitchen-sink-rpcpnpm test:contracts:pluginspnpm plugins:inventory:checkpnpm plugins:boundary-report:cipnpm test:extensionspnpm test extensions/qa-lab/src/gateway-child.test.ts -- --reporter=verbosepnpm check:changedgit diff --check origin/main..HEADpnpm exec oxfmt --check --threads=1 <changed ts files>Direct push and merge/auto-merge to
openclaw/openclaw:mainwere attempted, but the authenticated account does not have the required upstream permissions. This PR publishes the validated commits from a fork for maintainer landing.