Fix CI Doctor workflow monitoring non-existent workflows

[Copilot]

CI Doctor workflow had 0% success rate (20/20 failures) because it was configured to monitor "Daily Perf Improver" and "Daily Test Coverage Improver" workflows that don't exist in the repository. GitHub Actions immediately failed runs without executing jobs.

Changes

• Updated .github/workflows/ci-doctor.md to monitor the actual CI workflow
• Recompiled workflow lock file to reflect trigger change

# Before
workflows: ["Daily Perf Improver", "Daily Test Coverage Improver"]

# After
workflows: ["CI"]

The workflow will now trigger on actual CI failures and execute its diagnostic analysis jobs.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[P0] CI Doctor Workflow Completely Broken - 0% Success Rate</issue_title>
<issue_description># 🚨 Critical: CI Doctor Workflow Completely Broken

Summary

The CI Doctor workflow has a 0% success rate over the last 20 runs. This workflow is critical for diagnosing CI failures and has been non-functional since at least December 21, 2025.

Error Details

• Error Pattern: Exit code 7 (timeout after 120 seconds)
• Last Success: Before 2025-12-21
• Total Failures: 20/20 recent runs
• Impact: Unable to diagnose CI failures across the repository

Sample Failed Run

• Run: https://github.com/githubnext/gh-aw/actions/runs/20685353923
• Date: 2026-01-04
• Error: Process completed with exit code 7
• Timeout: "Retrying up to 120 times with 1s delay (120s total timeout)"

Suspected Root Causes

1. Timeout Configuration: 120s timeout may be insufficient
2. Network/API Latency: Possible increase in API response times
3. Resource Contention: Runner may be under heavy load
4. Code Regression: Recent changes may have introduced performance issues

Recommended Actions

Immediate (P0)

1. Review Workflow Configuration

   • Check timeout settings
   • Review recent changes to workflow
   • Examine job dependencies

2. Investigate Performance

   • Analyze what operations are taking >120s
   • Check for network/API latency issues
   • Review GitHub Actions runner logs

3. Temporary Mitigation

   • Consider disabling workflow until fixed
   • Document workaround for manual CI diagnosis

Follow-up

1. Increase timeout limit if operations legitimately take longer
2. Optimize slow operations
3. Add better error reporting/logging
4. Implement circuit breaker to prevent repeated failures

Related Issues

• Part of systemic timeout pattern affecting multiple workflows
• See: Daily News workflow (50% failure rate with same error)
• Related to meta-orchestrator cascade failure

Detection

Identified by Workflow Health Manager on 2026-01-14
Health Score Impact: Critical (P0) - workflow non-functional

---

Labels: workflow-health, priority-p0, type-failure, timeout
Assignee: @pelikhan (workflow owner)

AI generated by Workflow Health Manager - Meta-Orchestrator

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

• Fixes [P0] CI Doctor Workflow Completely Broken - 0% Success Rate #9897

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.