fix: update issue-monster assign-to-agent safe-outputs configuration

[Copilot]

Updates the issue-monster workflow's assign-to-agent safe-outputs to use the structured configuration format with explicit constraints.

Changes

• max: 3 — Matches workflow's design of assigning up to 3 issues per run
• name: "copilot" — Restricts to copilot agent only

safe-outputs:
  assign-to-agent:
    max: 3
    name: "copilot"

Note: The original request included target: "*" and allowed: [copilot], but these are not valid schema fields for assign-to-agent. The valid fields are github-token, max, name, and target-repo. The configuration was adjusted to use valid schema fields that achieve the same goal.

Files Updated

• .github/workflows/issue-monster.md — Updated configuration
• .github/workflows/issue-monster.lock.yml — Regenerated with gh aw compile
• Other lock files were also regenerated due to gh-aw compiler version update (v0.36.0)

Original prompt

change issue monster's assign to agent safeoutput to

assign-to-agent:
max: 3
target: "*" # Requires explicit issue_number in agent output
allowed: [copilot] # Only allow copilot agent

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Mossaka]

@copilot generate the yamls and push

[Copilot]

@copilot generate the yamls and push

Generated and pushed lock YAML files in 110002d. Note: I adjusted the configuration to use valid schema fields (max: 3, name: "copilot") since target: "*" and allowed: [copilot] are not supported by the agentic-workflow schema.

[github-actions]

✅ Coverage Check Passed

Overall Coverage

Metric	Base	PR	Delta
Lines	77.88%	77.88%	➡️ +0.00%
Statements	77.94%	77.94%	➡️ +0.00%
Functions	77.29%	77.29%	➡️ +0.00%
Branches	71.00%	71.00%	➡️ +0.00%

---

Coverage comparison generated by scripts/ci/compare-coverage.ts