Restrict Issue Monster to cookie-labeled issues from automated workflows

[Copilot]

Issue Monster was processing all open issues including human-contributed ones. Now requires the cookie label to identify approved work queue items from automated workflows.

Changes

Issue Monster search query

• Added label:cookie requirement to issue search
• Human-contributed issues without this label are ignored

Updated 27 agentic workflows with cookie label

• /plan workflow: [plan, ai-generated, cookie]
• Code quality workflows (11): breaking-change-checker, cli-consistency-checker, daily-file-diet, daily-safe-output-optimizer, daily-testify-uber-super-expert, duplicate-code-detector, go-pattern-detector, semantic-function-refactor, super-linter, stale-repo-identifier, video-analyzer
• Dependencies workflows (2): cli-version-checker, dependabot-go-checker
• Performance workflows (3): daily-cli-performance, deep-report, discussion-task-miner
• Maintenance workflows (3): step-name-alignment, workflow-normalizer, workflow-skill-extractor
• Security workflows (1): security-compliance
• Analysis & monitoring workflows (6): repo-audit-analyzer, ci-doctor, daily-multi-device-docs-tester, delight, agent-performance-analyzer, workflow-health-manager

All these workflows now create issues eligible for Issue Monster processing.

Intentionally excluded workflows

• Smoke test workflows (temporary issues)
• Special purpose workflows (poem-bot, issue-arborist)
• craft workflow (does not have create-issue in safe-outputs)

Label adoption

Additional issue-generating workflows can opt into Issue Monster processing by adding cookie to their safe-outputs.create-issue.labels configuration:

safe-outputs:
  create-issue:
    labels: [category, ai-generated, cookie]

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Turn off Issue Monster except for issues generated by, say, "/plan"</issue_title>
<issue_description>Can we just turn off Issue Monster except for issues generated by, say, "/plan" please, via a label issue-monster-cookie or something?
It just doesn't look right that it triggers on human-contributed issues #11079
</issue_description>

Comments on the Issue (you are @copilot in this section)

@pelikhan Another strategy: ignore issues with assignees https://github.com//pull/11090 @dsyme Yeah that doesn't work because * 1P issue contributors forget to assign someone * 3P issue contributors would never assign someone (not even sure if they're allowed to)

Just turn off issue monster except for issues that are known to be approved work queue work in some way </comment_new>
<comment_new>@dsyme
Decision:

1. All issue generating agentic wotkflows creating issues should label the issue with "cookie" label
2. Issue Monster wotkflow should only work on issues with that label

• Fixes Turn off Issue Monster except for issues generated by, say, "/plan" #11086

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[dsyme]

@copilot lots of other agentic workflows have create-issue: - update all those too using your best judgment - nearly all of them should have cookie

[Copilot]

Updated 20 additional agentic workflows with the cookie label in commit 78acb32.

Added cookie to:
Code quality (11): breaking-change-checker, cli-consistency-checker, daily-file-diet, daily-safe-output-optimizer, daily-testify-uber-super-expert, duplicate-code-detector, go-pattern-detector, semantic-function-refactor, super-linter, stale-repo-identifier, video-analyzer

Dependencies (2): cli-version-checker, dependabot-go-checker

Performance (3): daily-cli-performance, deep-report, discussion-task-miner

Maintenance (3): step-name-alignment, workflow-normalizer, workflow-skill-extractor

Security (1): security-compliance

Intentionally excluded:

• Smoke test workflows (temporary test issues that expire quickly)
• Reporting workflows (status reports, not actionable work)
• Special purpose workflows (poem-bot, delight, issue-arborist, ci-doctor, etc.)

[dsyme]

@copilot Enable these too for cookie please:

craft (template/example)
repo-audit-analyzer (analysis/reporting)
ci-doctor (diagnostic, not assignable work)
daily-multi-device-docs-tester (testing infrastructure)
delight (user experience analysis)
agent-performance-analyzer (analysis/reporting)
workflow-health-manager (monitoring/reporting

[Copilot]

Added cookie label to 6 workflows in commit bb85b90:

✅ repo-audit-analyzer
✅ ci-doctor
✅ daily-multi-device-docs-tester
✅ delight
✅ agent-performance-analyzer
✅ workflow-health-manager

Note: The craft workflow does not have create-issue in its safe-outputs (only add-comment and push-to-pull-request-branch), so no changes were needed for it.