fix(session): recover native bindings and diagnose missing FSM state - #81
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
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.
A missing or inherited SessionStart binding leaves a Codex session unable to enter its FSM, while status can report a nonexistent session as IDLE or select a newer parent's file.
Add
cxc session currentand explicitcxc session bindto corroborate the native root-thread ID and cwd against Codex's read-only database, then exclusively create missing state. Existing state is preserved; subagent IDs, incompatible native metadata and redirected state paths are refused. Status reports missing state and labels its selection source. Binding explicitly does not certify hook execution or Stop continuation.Emitted supported commands use their own payload CLI even when PATH contains an older development install; repo-only map/gui retain PATH routing. Both dispatchers, guidance and installed smoke contracts are updated. Includes 0.2.21 release metadata.
Validation at
884c81de4c4a1b8eb23c2af0ccbb61fd64d71306: all 11 checks passed, including four-platform CI (2646 tests), WSL drvfs/ext4, and packed installation. Three status regressions fail against the prior implementation. Independent review closed all findings; live recovery preserved other session files. No repository-wide local suite was run.