mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-05-05 23:42:03 +00:00
fix(review): preserve highest severity during dedup merge
When deduplication merges findings with different severities (e.g., a Critical typecheck error with a Suggestion from LLM review), the merged finding now uses the highest severity. Deterministic severity is treated as authoritative and cannot be downgraded. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
ab0259c1a1
commit
48340c3acf
1 changed files with 1 additions and 1 deletions
|
|
@ -204,7 +204,7 @@ In addition to their primary focus, each review agent (1-4) MUST perform cross-f
|
|||
|
||||
### Deduplication
|
||||
|
||||
Before verification, merge findings that refer to the same issue (same file, same line range, same root cause) even if reported by different agents. Keep the most detailed description and note which agents flagged it. **If a merged finding includes any deterministic source** (`[linter]`, `[typecheck]`, `[build]`, `[test]`), treat the entire merged finding as pre-confirmed — retain all source tags for reporting but skip verification.
|
||||
Before verification, merge findings that refer to the same issue (same file, same line range, same root cause) even if reported by different agents. Keep the most detailed description and note which agents flagged it. When severities differ across merged items, use the **highest severity** — never let deduplication downgrade severity. **If a merged finding includes any deterministic source** (`[linter]`, `[typecheck]`, `[build]`, `[test]`), treat the entire merged finding as pre-confirmed — retain all source tags for reporting, preserve deterministic severity as authoritative, and skip verification.
|
||||
|
||||
### Independent verification
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue