Fix Issue Monster add_comment target for scheduled runs

[Copilot]

Issue Monster scheduled runs fail validation when attempting add_comment with default target=triggering in cron context where no triggering issue/PR exists.

Changes

• Configuration: Set target: "*" in add-comment safe-output config to allow explicit issue targeting
• Instructions: Updated Step 6 to require item_number parameter when calling add_comment

safeoutputs/add_comment(
  item_number=<issue_number>, 
  body="🍪 **Issue Monster has assigned this to Copilot!**..."
)

The target: "*" configuration requires the AI to specify which issue to comment on via item_number, instead of inferring from workflow context that doesn't exist in scheduled runs.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[deep-report] Fix Issue Monster scheduled runs to avoid add_comment target=triggering failures</issue_title>
<issue_description>Description
Safe output health reports show Issue Monster scheduled runs repeatedly attempting add_comment with target=triggering, which is invalid in cron context. Update the workflow prompt/config to generate explicit issue targets or switch to create_issue for scheduled runs.

Expected Impact
Eliminates recurring safe-output validation failures and improves Issue Monster success rate.

Suggested Agent
Issue Monster or Safe Output Health Monitor

Estimated Effort
Quick (< 1 hour)

Data Source
DeepReport Intelligence Briefing 2026-01-16 (run 21071073449); discussion #10145

AI generated by DeepReport - Intelligence Gathering Agent

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

• Fixes [deep-report] Fix Issue Monster scheduled runs to avoid add_comment target=triggering failures #10324

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.