[saioai]

The WSL job can stop on a download startup timeout before any test runs. It also covers only pager ownership.
This retries startup once and adds existing stdin, file, and output checks to the same disposable Ubuntu WSL 1 session.

What changes

• Run 17 existing public-entrypoint tests with 104 named subtests for Keep output deterministic and add quiet and verbose controls #392, Fix shell input, event streaming, and download completion #395, and Make file uploads and downloads easier to discover #397.
• Check stdin precedence, incremental streams, download completion, literal filenames, machine output, and quiet/verbose behavior.
• Retry one typed timeout before the image response opens. Certificate, HTTP, integrity, body-transfer, and file failures never retry.
• Require exact test execution, successful exits, complete streams, and verified payload hashes.
• Preserve the existing pager check, distro ownership, and work/cleanup deadlines.

Commands

Public CLI commands remain unchanged. Contributor controls run without WSL or network access:

python -I -B scripts/test_wsl_pager.py

The existing CI job builds both Linux test binaries and imports one pinned Ubuntu distro.
The runner accepts --process-binary for the fixed process suite.

Code

The workflow adds one test-binary build. The existing Python runner verifies and runs it inside the same owned distro.
Product code, Go tests, dependencies, and other CI jobs remain unchanged.

Tested

All 42 offline controls passed locally and on native Windows AMD64.
The native WSL job passed all 17 process tests and 104 subtests.
The existing pager test and its two subtests also passed. Payload hashes and named distro cleanup were verified.
The tested tree matches refreshed head 5a53de0. Head checks completed without failures. Conditional jobs were skipped.
The download opened on its first attempt. Retry recovery still has synthetic coverage only.
This does not establish WSL 2, ARM64 WSL, DrvFS, or Windows Terminal coverage.

Demo

There is no visible product change. CI retains separate process output, exit statuses, binary hashes, and distro cleanup results.

[github-actions]

Castiron custom code

Evaluated main: 97b43f2cacc586ab352de1d544bd0b3c89936364.

✅ No new custom-code files detected.

5 mixed files remain; 0 existing customizations changed.

Compared 97b43f2cacc5 → 5a53de09078d. Generated baselines verified.

5 existing customizations unchanged

• pkg/cmd/adminorganizationcertificate.go
• pkg/cmd/audiovoice.go
• scripts/castiron/custom_code_budget.py
• scripts/castiron/custom_code_report.py
• scripts/castiron/test_custom_code_budget.py

A changed generated baseline means this report cannot reliably identify which handwritten lines changed.

Inspect the custom-code diff

Download the exact patch produced by this run (requires repository access):

gh run download 38514975040 --repo openai/openai-cli \
  --name castiron-custom-code-38514975040-1 --dir /tmp/castiron-custom-code-38514975040-1
git apply --stat /tmp/castiron-custom-code-38514975040-1/custom-code.patch
cat /tmp/castiron-custom-code-38514975040-1/custom-code.patch

Or reproduce it from an SDK checkout containing the vendored reporter:

git fetch --no-tags origin 97b43f2cacc586ab352de1d544bd0b3c89936364 5a53de09078d429782bcbc04f491ddf89876cbef
python3 scripts/castiron/custom_code_report.py report \
  --base 97b43f2cacc586ab352de1d544bd0b3c89936364 \
  --head 5a53de09078d429782bcbc04f491ddf89876cbef --fetch --require-head-hash --public \
  --out /tmp/castiron-custom-code-5a53de09078d
cat /tmp/castiron-custom-code-5a53de09078d/custom-code.patch

This is the current full custom patch for mixed files, not an attribution of only the handwritten lines changed by this PR.

Full report and patch

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-14T04:56:38.139787Z	5a53de0	New commits
🔒 Security Review	✅ Completed 2026-10-14T04:57:27.276050Z	5a53de0	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.