Add noop handling to CI Failure Doctor for successful CI runs

[Copilot]

CI Failure Doctor workflow produces "No Safe Outputs Generated" warnings when the monitored CI workflow succeeds. The workflow exits early without signaling completion via safe outputs.

Changes

• safe-outputs configuration: Added noop to enable explicit no-op signaling
• Investigation protocol: Updated Phase 1 instructions to call noop when workflow_run.conclusion is not failure or cancelled

Implementation

When CI passes, the agent now calls:

{
  "type": "noop",
  "message": "CI workflow completed successfully - no investigation needed"
}

This follows the pattern already used in security-guard.md, hourly-ci-cleaner.md, and breaking-change-checker.md.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[agentics] CI Failure Doctor failed</issue_title>
<issue_description>### Workflow Failure

Workflow: CI Failure Doctor
Branch: main
Run URL: https://github.com/githubnext/gh-aw/actions/runs/21546784074

⚠️ No Safe Outputs Generated: The agent job succeeded but did not produce any safe outputs. This typically indicates:

• The safe output server failed to run
• The prompt failed to generate any meaningful result
• The agent should have called noop to explicitly indicate no action was taken

Action Required

Debug this workflow failure using the agentic-workflows agent:

/agent agentic-workflows

When prompted, instruct the agent to debug this workflow failure.

Generated from CI Failure Doctor

• expires on Feb 7, 2026, 3:40 PM UTC

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

@pelikhan Make sure it calls noop is nothing to do.

• Fixes [agentics] CI Failure Doctor failed #12960

---

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