fix: close stdio gateway and bound resource shutdown (0.13.2) - #33
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.
When a stdio client disconnects, WinCode 0.13.1 can stay alive because its production entry ignores EOF. This change routes closed pipes and transport termination through one bounded shutdown path, cancels startup and active operations, and prevents late initialization from recreating resources.
Cleanup shares the existing eight-second budget and still reaches independently owned processes if an adapter hangs. The release is 0.13.2; audited Skill guidance is synchronized.
Validation: reproduced the production-entry EOF failure before fixing it; 321 core tests pass with one optional skip, 35 desktop tests pass, and 27 focused lifecycle tests pass. Fixed a timing-sensitive TTL test using a controlled clock without weakening expiry assertions. Actual Codex reconnection and idle reclamation are not claimed by this PR.