[aw-failures] Issue Monster: `assign_to_agent` uses `issue-number` field (should be `issue_number`)

[github-actions]

Problem Statement

The issue-monster workflow emits assign_to_agent safe-output items using issue-number (hyphen) instead of the required issue_number (underscore). This causes all assign_to_agent calls to fail validation, meaning issues are never actually assigned to Copilot even though the agent thinks they are.

Evidence

Run: §24623096622 — 2026-04-19 06:45 UTC

Errors from agent_output.json:

Line 1: assign_to_agent requires at least one of: 'issue_number', 'pull_number' fields
Line 2: assign_to_agent requires at least one of: 'issue_number', 'pull_number' fields
Line 3: assign_to_agent requires at least one of: 'issue_number', 'pull_number' fields

Raw safeoutputs.jsonl shows:

{"agent":"copilot","issue-number":"27152","type":"assign_to_agent"}
{"agent":"copilot","issue-number":"27151","type":"assign_to_agent"}
{"agent":"copilot","issue-number":"27150","type":"assign_to_agent"}

The field is issue-number (hyphen) but must be issue_number (underscore).

The add_comment output referencing issue 27152 succeeded — the comment says "assigned to Copilot" but the actual assignment failed silently to the agent.

Root Cause

The issue-monster prompt uses a tool or template that emits issue-number instead of issue_number in the assign_to_agent safe-output schema. The schema requires issue_number or pull_number.

Proposed Remediation

Update the issue-monster workflow prompt or its safe-outputs tool definition to use issue_number (underscore) in all assign_to_agent items. Also update the add_comment body to avoid misleading "assigned to Copilot" messages when assignment may fail.

Success Criteria

Next Issue Monster run completes with 0 assign_to_agent validation errors, and assigned issues actually have Copilot assigned.

Parent: #27128
References: §24623096622

Generated by [aw] Failure Investigator (6h) · ● 719.8K · ◷

• expires on Apr 26, 2026, 7:20 AM UTC