fix: preserve dict copy provenance and triage scope#648
Draft
ApexWorm wants to merge 3 commits into
Draft
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.
Dict-copy provenance
The Python dict-key detector no longer treats copied mappings as fresh empty dictionaries, preventing false phantom-read findings from dict(source) and dict(**source).
Triage scope
A refreshed triage cycle could be blocked by historical clusters and stale frozen issue IDs. This update scopes organize, enrich, sense-check, runner validation, and confirmations to the live frozen review set. An empty live scope is now distinct from legacy unscoped validation, and strategist output preserves deliberate skipped IDs.
Verification