-
Notifications
You must be signed in to change notification settings - Fork 3k
fix(core): halt repeated shell inspection variants #5944
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+461
−16
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
91ec374
fix(core): halt repeated shell inspection variants
yiliang114 5aaec99
test(core): cover shell-stagnation streak reset, fix guard-count doc
yiliang114 2fd9ad0
fix(core): exclude write-bearing git chains from stagnation bucket
yiliang114 08bd62d
fix(core): halt repeated shell inspection variants
yiliang114 380782e
Merge remote review refinements
yiliang114 c2c73a7
fix(core): treat path-specific git diffs as progress
yiliang114 d8ab43f
test(core): cover shell stagnation guard boundaries
yiliang114 9f50530
test(core): address shell stagnation review feedback
yiliang114 f86b74e
docs(core): sync loop guard comments
yiliang114 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Critical]
SHELL_COMMAND_STAGNATIONis correctly added toisAlwaysOnhere, butnonInteractiveCli.test.tshas no test verifying the user-facing message for this new type. Existing always-on types (CONSECUTIVE_IDENTICAL_TOOL_CALLS,TURN_TOOL_CALL_CAP) have analogous tests asserting that the "always-on guard" hint appears and theskipLoopDetectionescape hatch does NOT. Without a parallel test, a future refactor could accidentally remove the new type fromisAlwaysOnand no test would catch the regression.Consider adding a test analogous to the existing always-on assertions:
— qwen3.7-max via Qwen Code /review
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think this is a critical correctness issue for the current PR. The runtime behavior is already wired correctly:
SHELL_COMMAND_STAGNATIONis included in the always-on branch, so the headless message does not suggestmodel.skipLoopDetectionas an escape hatch for this loop type.This is a reasonable regression-test hardening suggestion, but it is not blocking for the fix. We can follow up with a small dedicated
nonInteractiveCli.test.tsassertion that locks the user-facing message forSHELL_COMMAND_STAGNATION.