fix(vscode): prevent drained questions from reappearing - #13547
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (3 files)
Reviewed by grok-4.6 · Input: 52.2K · Output: 7.1K · Cached: 317.2K Review guidance: REVIEW.md from base branch |
marius-kilocode
enabled auto-merge
August 28, 2026 12:31
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.
Settings saves reject pending questions and clear the UI, but a delayed recovery scan can replay an old question before the rejection SSE arrives.
Invalidate recovery immediately after a successful rejection or NotFound response, using the existing revision guard. Keep the fix to one production line; snapshot backend behavior is unchanged.
The focused regression covers both outcomes and verifies invalidation before the clear notification. It fails without the fix and passes with it. All 19 focused tests, extension/webview typechecks, lint, knip, and the change-marker guard pass. The live VS Code heavy-load scenario was not exercised.