mirror of
https://github.com/aaddrick/claude-desktop-debian.git
synced 2026-05-17 00:26:21 +03:00
f1eed0e16f
Post-Phase 4 verification showed two issues (#311, #448) where the pipeline successfully produced valuable findings against current code, but the top-of-gate drift veto routed them to 8b drift-only and the findings were discarded. The reporter cited an older version (1.1.7464 on #311), the investigation ran cleanly on current (1.3.5610), and the reviewer approved the findings — yet the comment still read "couldn't reach a confident read." This change keeps drift detection and keeps the drift-bridge sweep. What changes is Stage 7: drift is no longer at the top of the gate. When drift is detected and 8a or 8c would render cleanly, the renderer prepends a drift banner (⚠ You reported this on X; bot investigated on Y. Citations may still apply.) and appends the drift-bridge-candidates block at the bottom. The finding citations stand — they describe current code in hypothesis voice, which is what the reader can verify against their own checkout. When drift is detected and the pipeline would otherwise route to 8b for any other reason (fetch-failure, invest-failure, review-failure, no-findings, low-confidence), the reason is overridden to `version-drift`. Drift-bridge candidates give the maintainer a more actionable signal than "no findings" on its own. Reviewer prompt gains one rubric addition: downgrade-confidence when the cited surface clearly post-dates the reporter's version. Catches the case where a finding is valid on current but wouldn't reproduce on what the reporter saw. Doesn't degrade findings indiscriminately — only when the reviewer can see version-specific evidence. Confirmed-duplicate routing wins over the drift-reason override (explicit exclusion in the override clause) because `triage: duplicate` is still the more specific read. Co-authored-by: Claude <claude@anthropic.com>