Fix Codex CMUX stale status cleanup#33
Merged
Merged
Conversation
Stabilize CMUX status ownership and clear observed stale understatus keys before applying new pills. Bump release metadata to 0.7.3 for deployment. Constraint: keep CMUX integration fail-soft and avoid set-progress Confidence: high Scope-risk: narrow Directive: Preserve status-key cleanup semantics and path-scoped staging for future fixes Tested: node npm/verify-release.js 0.7.3 --verify-packlist; cargo fmt --all -- --check; cargo test --all-targets --locked; cargo clippy --all-targets --locked -- -D warnings; npm test --prefix npm; git diff --check Not-tested: GitHub Actions release workflows not run until tag deployment
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.
Summary
understatus.codex.*keys fromcmux sidebar-statebefore applying new pillsclear-codexclear all observed understatus keys when no session key is supplied0.7.3Verification
node npm/verify-release.js 0.7.3 --verify-packlistcargo fmt --all -- --checkcargo test --all-targets --lockedcargo clippy --all-targets --locked -- -D warningsnpm test --prefix npmgit diff --checkclear-codexproducedstatus_count=0, then restore produced one active set