fix(agents): prevent backlog groomer from closing PRs as duplicates of their tracking issues #1325

Merged
freemo merged 1 commits from improvement/backlog-groomer-pr-vs-issue-distinction into master 2026-04-03 07:09:24 +00:00

1 Commits

Author SHA1 Message Date
freemo b485965e40 fix(agents): prevent backlog groomer from closing PRs as duplicates of their tracking issues
CI / lint (pull_request) Successful in 36s
CI / quality (pull_request) Successful in 41s
CI / typecheck (pull_request) Successful in 55s
CI / security (pull_request) Successful in 56s
CI / build (pull_request) Successful in 23s
CI / helm (pull_request) Successful in 31s
CI / benchmark-publish (pull_request) Has been skipped
CI / unit_tests (pull_request) Failing after 6m51s
CI / docker (pull_request) Has been skipped
CI / coverage (pull_request) Successful in 11m3s
CI / e2e_tests (pull_request) Failing after 15m0s
CI / integration_tests (pull_request) Failing after 22m8s
CI / status-check (pull_request) Failing after 1s
CI / benchmark-regression (pull_request) Successful in 55m15s
Agent evolver identified a critical systematic pattern:
- Pattern: The backlog groomer was closing PRs as 'duplicates' of their
  linked tracking issues. A PR containing 'Closes #N' was being treated
  as a duplicate of issue #N, when it is actually the implementation
  delivery vehicle for that issue.
- Evidence: At least 12 PRs were incorrectly closed (#1219, #1236, #1247,
  #1269, #1267, #953, #1198, #1220, #1237, #1238, #1246, #1248) — all
  with the same 'Duplicate Detected' comment pattern from groomer-1.
- Fix: Added explicit instructions to skip PRs during duplicate detection,
  added a guard in the analysis loop pseudocode, and added a rule in the
  Important Rules section.

This change requires human approval before taking effect.

ISSUES CLOSED: #2180
2026-04-03 06:37:08 +00:00