fix(codex): preserve truthful tool outcomes - #104
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codex tool output containing words such as
error:could be counted as failure even after an explicit successful exit. Both output adapters now share status parsing: explicit failure wins, trustworthy zero exits succeed, and missing or running outcomes remain unknown. Runtime trace storage and failure follow-ups preserve that uncertainty.Closes #36. Bumps the source package to 0.13.1.
Validation: source check, typecheck, all 776 tests, build, and packed CLI check passed on Node 24 with one worker and a 2 GiB aggregate memory limit. Independent review found and then verified fixes for embedded receipt headers and malformed numeric exits. The original July session was not replayed; retained regressions cover its reported output shape.
Publication is separate: the existing npm publisher has an unresolved authorization failure. This PR does not repair its credential or claim that 0.13.1 is available from npm.