feat(tui): add destructive command guard settings - #75
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
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
/codexplusplusValidation
just test -p codex-tui dcg_views_snapshotjust test -p codex-tui dcg_nux_persists_globally_and_prepares_oncejust test -p codex-tui welcome_help_first_and_later_startup_snapshotcargo insta pending-snapshots --manifest-path tui/Cargo.tomljust fix -p codex-tui(passes with the pre-existingaccounts_tests.rstoo-many-arguments warning)just fmtrvw_302da961)The full
codex-tuisuite was also exercised during implementation. All feature-specific tests passed; unrelated existing snapshot drift remains in mainline version/workstation-instruction snapshots.Scope
The final diff is exactly 600 changed lines and keeps fork-owned behavior isolated under
codex_plus_pluswith minimal upstream seams.