Repository navigation
Preserve Settings refresh ownership and clean the VS Code image - #5
Merged
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.
The VS Code landing image now shows the app without the capture frame, control badge or extra pointer. The expanded findings tree, code hover and Problems remain visible. Original application pixels are preserved outside the small blank-background repair; README links target the metadata-checked PNG. Git history remains intact.
Settings now preserves the current dashboard read when a provider job reaches terminal state. Previously, post-command and terminal callbacks both used manual refresh, so terminal polling could cancel an unfinished post-command read. A stable callback uses the existing mutation queue and preserves the discovery-retry budget reset.
A held-response regression reproduces the old cancellation and requires the retained read to finish before a fresh terminal read starts and completes. The complete Advisor journey and strengthened regression pass locally (2/2); Web build and typecheck pass. Fresh full CI is required on this head. Error guards, deadlines, authorization, consent and push-protection semantics are unchanged. Prior native/platform evidence keeps its original identities.