Automated Duplicate Issue Detection & Cleanup (Core + CLI)

[Kavirubc]

Idea Description

In large repos (2,000+ issues), duplicates aren't always "open-to-open." Often, a user opens an issue that was fixed a year ago, or they report a bug that is currently being addressed in an active PR. The tool should be able to tell, "This looks like Issue #123 (Closed) and PR #456 (Merged); it might be a regression or a duplicate of a past fix."

Potential Benefits

Prevents "Duplicate Bloat": Stops the issue tracker from filling up with problems that have already been solved.

Identifies Regressions: Quickly flags if a previous fix has been undone by recent changes, allowing for faster rollbacks or patches.

Smarter Triaging: Saves maintainers from manual "archaeology"—searching through hundreds of closed items to see if they've seen a bug before.

Data Accuracy: Provides a clearer picture of project health by distinguishing between truly new bugs and recurring ones.