[deep-report] Make Contribution Check reports idempotent to prevent duplicate open/closed issues

[github-actions]

Description

Recent weekly-issues analysis shows same-day Contribution Check report duplication (#22694 open while #22628 is closed with effectively the same report title/date). Implement an idempotency key (for example date + workflow + target scope) and dedupe-before-create behavior so reruns update/close the existing issue instead of creating a near-duplicate.

Expected Impact

Reduces issue noise, improves trust in automated reporting, and avoids manual cleanup from duplicate report artifacts.

Suggested Agent

contribution-check workflow owner or issue-arborist automation maintainer.

Estimated Effort

Medium (1-4 hours).

Data Source

DeepReport analysis run §23497741571, weekly issues snapshot (updated 2026-03-24).

Generated by DeepReport - Intelligence Gathering Agent · ◷

• expires on Mar 26, 2026, 3:41 PM UTC

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

The Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · ◷