Skip to content

fix(qualification): refuse nonzero outer stdio helper exit - #854

Merged
antropos17 merged 2 commits into
masterfrom
codex/stdio-exit-20261011
Oct 11, 2026
Merged

antropos17 merged 2 commits into
masterfrom
codex/stdio-exit-20261011

Conversation

@antropos17

Copy link
Copy Markdown
Owner

The native stdio transport could report Outcome.Complete when a helper exited through the outer signaled wait after stdin/output EOF with a nonzero exit code. Route that wait through the existing ExchangeExit identity and exit-code guard so exit 7 is refused during Exchange; keep the positive exit-0 path.

A focused Windows same-principal Job-owned fixture forces the outer wait with a real Node helper. The exit-7 case is refused during Exchange, and removing the guard demonstrably lets it reach Verify as Complete. The test-cloud-guest-stdio.ps1 -MutationControls run passed; two independent GPT-6.1 Sol reviews passed. This is transport regression coverage, not cross-account, protected-installation, guest-runtime, or E2 qualification.

@antropos17
antropos17 merged commit 328fc7f into master Oct 11, 2026
5 checks passed
@antropos17
antropos17 deleted the codex/stdio-exit-20261011 branch October 11, 2026 01:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant