[deep-report] [quick-win] Consolidate the overlapping lint-monster function-length issues into one tracking epic

[github-actions]

Problem

There are currently 10 open lint-monster issues, several of which report the same underlying problem (long functions in pkg/workflow / pkg/cli) with wildly inconsistent counts, creating signal pollution in the tracker:

• #36050 — pkg/workflow function length violations ("286 issues")
• #35368 — Break up long functions in pkg/workflow/ ("2417 issues")
• #35846 — Refactor long functions in pkg/workflow exceeding 60-line limit
• #35847 — Refactor long functions in pkg/cli exceeding 60-line limit
• #35367 — Break up long functions in pkg/cli/
• #36175 — Refactor long functions Part 2 of 2

The Agent Performance Report names LintMonster as an ongoing P1. The duplication makes it hard to know which issue is authoritative.

Suggested fix

1. Pick (or open) one authoritative epic for "function-length refactoring".
2. Close the duplicates with a pointer to the epic, or convert them to checklist items under it.
3. Reconcile the conflicting counts to a single source-of-truth number from the current linter run.

Success criteria

• One authoritative function-length tracking issue; duplicates closed/linked.

Effort

~1 h triage. Suggested agent: issue-triage / lint-monster.

Source: DeepReport 2026-06-01 (Agent Performance Report #36261, open-issue analysis).

Generated by 🔬 DeepReport - Intelligence Gathering Agent · opus48 1.6M · ◷

• expires on Jun 3, 2026, 4:41 PM UTC

[github-actions]

🍪 Issue Monster selected this for Copilot

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

If assignment succeeds, 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 · haiku45 27.3K · ◷