Repository navigation
Worker C R1/R2: prioritize conflicting reconstruction review evidence - #814
Open
KAVentures wants to merge 2 commits into
Open
KAVentures wants to merge 2 commits into
KAVentures wants to merge 2 commits into
Conversation
KAVentures
marked this pull request as ready for review
November 12, 2026 10:11
This branch has not been deployed
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.
Fixes a production review-queue ordering inversion: candidates with cross-case, scope, taint or competing-component risk were sorted after low-risk inspection suggestions. Rank conflicted candidates first, then risk count and existing relation priority; disclose total conflicted candidates and ordering metadata. Keeps canonical membership unchanged, no auto-approval, no privacy/auth changes. Adds deterministic regression coverage. Existing authenticated review-queue consumers use the production function. This is an incremental operator-review correctness improvement, not held-out F1 or contamination acceptance. Hold merge until all six mandatory exact-head workflows, native/browser/packaging jobs and reviews pass. Refs #326 #370.