Consolidate LintMonster function-length issues into one tracking workflow

[Copilot]

LintMonster was treating closely related long-function findings in pkg/workflow and pkg/cli as separate issues, which led to duplicate trackers and conflicting counts for the same backlog. This change makes the workflow maintain one authoritative function-length tracking issue and explicitly fold duplicates into it.

• Workflow behavior

  • Treats all largefunc / long-function findings across pkg/workflow and pkg/cli as a single function-length refactoring backlog.
  • Instructs the agent to use the current lint run as the source of truth for the active count.
  • Replaces split tracking (pkg/workflow, pkg/cli, part-based follow-ups) with one consolidated tracking issue.

• Issue lifecycle

  • Reuses an existing open tracking issue when one already covers the same backlog.
  • Updates the authoritative issue with the current count, affected paths, and next refactoring slices.
  • Closes older duplicate lint-monster issues with a pointer comment to the authoritative tracker.

• Safe-output support

  • Adds update-issue so the workflow can refresh an existing tracker instead of opening a new one.
  • Adds close-issue with a [lint-monster] title guard and duplicate close reason to safely retire overlapping issues.

• Generated workflow

  • Regenerates lint-monster.lock.yml so the compiled workflow matches the new source behavior and safe-output contract.

Example of the new workflow contract:

safe-outputs:
  close-issue:
    max: 10
    required-title-prefix: "[lint-monster] "
    state-reason: duplicate
  update-issue:
    max: 10
    title-prefix: "[lint-monster] "

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.