Separate no-op run comments from failed runs issue

[Copilot]

No-op workflow run comments were being posted to the "[agentic-workflows] Failed runs" issue. They need a separate tracking issue to distinguish successful no-action runs from actual failures.

Changes

• Updated issue title: "[agentic-workflows] Agent runs" → "[agentic-workflows] No-Op Runs"
• Updated terminology: Renamed variables and log messages from "agent runs issue" to "no-op runs issue" throughout handle_noop_message.cjs
• Updated tests: All test expectations now validate the new "[agentic-workflows] No-Op Runs" title

Result

Two distinct tracking issues:

• "[agentic-workflows] Failed runs" - workflow failures (via handle_agent_failure.cjs)
• "[agentic-workflows] No-Op Runs" - successful no-action runs (via handle_noop_message.cjs)

// Before
const parentTitle = "[agentic-workflows] Agent runs";

// After
const parentTitle = "[agentic-workflows] No-Op Runs";

Original prompt

The no op comments should be on a different issue than the failed runs. Update the javascript code that creates the issue for noop messages.

See #14163 for a comment on tbe wrong issue.

---

💡 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.

[Copilot]

Pull request overview

This PR updates the no-op workflow run reporting so that no-op comments are posted to a dedicated tracking issue ([agentic-workflows] No-Op Runs) instead of being mixed into the failures tracking issue, improving operational triage and separation of signal.

Changes:

• Updated the parent tracking issue title used by handle_noop_message.cjs to "[agentic-workflows] No-Op Runs".
• Updated log/variable/test expectations to align with the new “No-Op Runs” parent issue naming.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
actions/setup/js/handle_noop_message.cjs	Switches the parent issue title and related messaging to target the dedicated no-op runs issue.
actions/setup/js/handle_noop_message.test.cjs	Updates test expectations to assert the new issue title and updated warning text.

Comments suppressed due to low confidence (1)

actions/setup/js/handle_noop_message.cjs:148

• The PR description says terminology was renamed throughout handle_noop_message.cjs, but there are still references to an "agent runs issue" in comments (e.g., the function header comment around main() and the inline comment above the agentConclusion check). Please update those remaining references for consistency with the new "No-Op Runs" issue.

    core.info("Agent succeeded with only noop outputs - posting to no-op runs issue");

    const { owner, repo } = context.repo;

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The helper name ensureAgentRunsIssue no longer matches its behavior (it now searches/creates the "[agentic-workflows] No-Op Runs" issue). Please rename the function/export (and any callers) to reflect no-op runs, and update any remaining in-file comments/log text that still refer to an "agent runs" issue to avoid confusion during debugging.

This issue also appears on line 146 of the same file.

Suggested change

	async function ensureAgentRunsIssue() {
	async function ensureNoOpRunsIssue() {