[deep-report] Add repeat-offender detection to the automated [aw] workflow-failure issue filer #48672

Description

Across this week's data, the same workflow failing repeatedly gets a brand-new siloed [aw] <workflow> failed/produced no safe outputs issue every time instead of being linked/consolidated: Matt Pocock Skills Reviewer (9+ issues since 07-25), Design Decision Gate (3+ issues), and Daily Container Image Security Scan (4 issues: #47939, #48152, #48311, #48549) all show this pattern. This mirrors the same anti-pattern DeepReport's own prior run (#47811) had to manually clean up for goroutine/timeout fixes.

Expected Impact

When the automated failure detector is about to file an issue for a workflow that already has an open failure issue from the last N days, it should comment/re-open the existing issue instead of creating a new one. This directly reduces backlog noise and makes chronic failures visible as a single trend line instead of N disconnected data points.

Suggested Agent

New Agent (or extend the existing [aw] failure-detection automation).

Estimated Effort

Medium (1-4 hours)

Data Source

DeepReport Intelligence Briefing analysis, 2026-07-28. Cross-referenced patterns: Matt Pocock Skills Reviewer, Design Decision Gate, Daily Container Image Security Scan issue histories.

Generated by 🔬 Deep Report · age00 · 176.7 AIC · ⌖ 13.2 AIC · ⊞ 10.5K · ◷

• expires on Jul 30, 2026, 7:41 AM UTC-08:00