[deep-report] Add rolling/update-existing-issue mode to reduce repeat auto-filed failure issues #60673

Description

Repository-wide issue volume is dominated by automated per-run failure reports: the 2026-09-13 Daily Issues Report (#60630) found 1000 issues sampled, 940 authored by app/github-actions, with clusters like "[WIP] Daily Go Test Parallelizer: work in progress" and "Issue Monster hit engine rate limit (HTTP 429)" recurring many times in a few days (e.g. 6 separate "Issue Monster hit engine rate limit" issues between 2026-09-10 and 2026-09-13, each auto-closed and re-opened fresh rather than reusing one tracker). This pattern was also flagged as a top finding in the prior DeepReport Intelligence Briefing (#60625).

Expected Impact

Cuts triage noise substantially and makes genuinely new regressions easier to spot against the baseline of expected recurring failures (e.g. rate limits, chronic WIP stubs).

Suggested Change

Add an optional "rolling"/"update-existing" mode to the safe-outputs create_issue configuration (pkg/workflow/safe_outputs_config_types.go and the corresponding compiler/handler code) so that a workflow can be configured to search for and update/reopen a single canonical issue for a given failure signature (e.g. by tracker-id + error class) instead of always creating a new one. This is additive — existing workflows keep today's create-per-run behavior unless they opt in.

Suggested Agent

Workflow-config / safe-outputs engineer familiar with pkg/workflow/compiler_safe_outputs_builder.go and the create_issue safe-output implementation.

Estimated Effort

Medium (3-4 hours).

Data Source

Daily Issues Report #60630 (2026-09-13) + DeepReport Intelligence Briefing #60625 (2026-09-13); confirmed no existing "rolling"/dedup mechanism for create_issue via grep of pkg/workflow/*.go this cycle.

network:
  allowed:
    - defaults
    - "api.anthropic.com"

Generated by 🔬 Deep Report · claude · agent · 366.1 AIC · ⌖ 13.2 AIC · ⊞ 12.8K · ◷

• expires on Sep 15, 2026, 10:41 AM UTC-08:00