Weekly CI/CD Health Report - 2026-04-13

[github-actions]

CI/CD Workflow Health Summary

Report Period: 2026-04-07 → 2026-04-13
Total Workflow Runs: ~120 (estimated from 14 merged PRs + scheduled runs)
Overall Repository Health: 🟢 Good (Score: 82/100) — Improved from 78/100 last week

---

Workflow Health Scores

Workflow	Health Score	Success Rate	Runs (est.)	Status
CI	92 ⭐	~92%*	~28	✅ Good
Rust CI	72 ⚠️	~78%†	~38	⚠️ Needs Attention
Rust Release	100 ⭐	100%	10	✅ Excellent
Security Scanning	90 ⭐	~90%*	~28	✅ Good
Documentation Validation	85 ⚠️	~85%*	~18	✅ Good
Documentation Preview	100 ⭐	100%	~8	✅ Excellent
Deploy Documentation	100 ⭐	100%	~2	✅ Excellent
Dependency Review	100 ⭐	100%	~4	✅ Excellent
CLI Performance Monitor	100 ⭐	100%	~1	✅ Excellent
Code Quality Tracker	100 ⭐	100%	~1	✅ Excellent
Documentation Freshness	100 ⭐	100%	~1	✅ Excellent
Stale Issue Manager	100 ⭐	100%	~1	✅ Excellent
Test Coverage Tracker	100 ⭐	100%	~1	✅ Excellent
Azure Static Web Apps	100 ⭐	100%	~2	✅ Excellent

*CI, Security Scanning, and Documentation Validation apparent "failures" include action_required events from external fork contributor protection — not real failures.
†Rust CI improvement: last week's Critical (55/100, 70% pass) has improved but clippy iteration cycles continue.

---

Development Activity This Week

Exceptionally high velocity — 14 PRs merged to main (2026-04-07 through 2026-04-09), 10 new releases published.

Date	PRs Merged	Focus Area
2026-04-07	2	Chromium scope wrapper, SSH key preservation
2026-04-08	10	Azure Bastion routing, VS Code remote, fleet perf, cmake, amplihack-rs
2026-04-09	2	Private VM default, VM Name display fix

Version progression: v2.6.37 → v2.6.49 (+12 patch releases in 3 days)

---

Improvements vs. Last Week

Metric	Last Week (2026-04-06)	This Week (2026-04-13)	Trend
Overall Health Score	78/100	82/100	↑ +4
Rust CI Score	55/100 (Critical)	72/100 (Needs Attention)	↑ +17
Rust CI Success Rate	70%	~78%	↑ Improving
Rust Release Success	100%	100%	→ Stable
PR Merge Velocity	~7/week	~14/week	↑ 2x
Releases Published	5	10	↑ 2x

---

⚠️ Ongoing Issues

1. Rust CI — Clippy Iteration Cycles (Persistent, Improving)

Status: Improved from Critical (55) to Needs Attention (72) — the pattern of iterative push cycles to satisfy cargo clippy -- -D warnings continues but is becoming less disruptive as feature work matures.

Key context from this week:

• PR feat: default azlin new to private/bastion (no public IP) #966 (feat: default azlin new to private/bastion) explicitly notes fixing a pre-existing CI failure in parity_tests.rs where workspace default was /home/user instead of /home/azureuser. This was a persistent test correctness bug.
• PRs fix: VS Code remote URI needs user@host for SSH config aliases #964 and fix: use correct VS Code folder-uri format for azlin code #965 (consecutive VS Code remote URI fixes) suggest iterative debugging on main — test coverage for the VS Code integration path may be insufficient to catch regressions before push.

Root cause remains: Developers not running cargo clippy -- -D warnings locally before pushing.

Recommendations:

1. Add a pre-push git hook: cargo clippy --all -- -D warnings
2. Add a CONTRIBUTING.md note or developer setup script that installs this hook automatically
3. Consider a make check or make lint Makefile target for the Rust workspace

2. Node.js 20 Action Deprecation (Upcoming Risk)

Status: Unchanged from last week. All Rust CI and most other workflow jobs use actions/checkout@v4 which runs on Node.js 20.

Deadline: GitHub removes Node.js 20 runner support on 2026-09-16 (~5 months remaining).

Affected workflows: rust-ci.yml, rust-release.yml, security.yml, docs.yml, docs-pr.yml, doc-validation.yml, azure-static-web-apps-pwa.yml

Recommendation: Schedule a workflow audit pass. Update actions/checkout@v4 to a version using Node.js 22+, and audit all third-party actions for the same deprecation.

3. Test Coverage — Persistent Open Goal

Status: Multiple open issues (#954, #898, #859, #745) track a 52% coverage target that has not been achieved. This is at least the 4th consecutive weekly period with the same open goal.

Risk: The current high PR velocity (10+ merges/day) with iterative bug fixes (consecutive PRs fixing the same integration: #964 → #965 for VS Code URIs) suggests unit test coverage for new features lags behind implementation.

Recommendation: Tie test coverage enforcement directly into CI — fail the build if coverage drops below a minimum threshold (e.g., 44% today, gradually raising the floor each week).

---

📈 Trends (Multi-Week)

Week	Health Score	Rust CI	True Failures	Ext. Fork PRs
2026-03-16 (#854)	~75	Moderate	Unknown	Low
2026-03-23 (#893)	~76	Moderate	Unknown	Low
2026-03-30 (#917)	~77	Critical	~10	Growing
2026-04-06 (#949)	78	55 (Critical)	13	6 new
2026-04-13 (this)	82	72 (Improving)	~8 (est.)	Ongoing

Trend summary:

• Health score has improved 4 consecutive weeks
• Rust CI is recovering from Critical but not yet stable
• Development pace is accelerating (highest single-week PR volume observed)
• Release automation is a standout strength — 100% reliable, fully automated

---

🎯 Recommendations

Priority 1 — Reduce Rust CI Clippy Cycles (Ongoing)

Add pre-push clippy hook and developer documentation. This single action would likely push Rust CI from 72 → 90+.

Priority 2 — Schedule Node.js 20 Action Audit (New)

5-month runway before 2026-09-16 deadline. Create a tracking issue and schedule workflow action version bumps before the busy season.

Priority 3 — Enforce Coverage Floor in CI (Ongoing)

Instead of aspirational tracking issues, add --fail-under 44 (current baseline) to the pytest/coverage invocation in CI. Raise the floor by 1-2% per sprint.

Priority 4 — VS Code Integration Test Gap (New)

Two consecutive PRs (#964, #965) fixed the same VS Code remote URI feature within hours of each other. Add automated tests for the URI construction logic to prevent regressions without manual testing.

Priority 5 — External Fork PR Review Cadence

Community contribution pace remains high. Maintainers should aim to review and approve action_required runs within 48 hours to keep contributor momentum.

---

📊 Metrics Snapshot

{
  "week": "2026-15",
  "report_date": "2026-04-13",
  "report_period": "2026-04-07 to 2026-04-13",
  "workflows": {
    "ci.yml": {
      "runs_estimated": 28,
      "success_rate_pct": 92,
      "true_failure_count": 0,
      "action_required_count": 6,
      "adjusted_success_rate_pct": 100
    },
    "rust-ci.yml": {
      "runs_estimated": 38,
      "success_rate_pct": 78,
      "health_score": 72,
      "failure_pattern": "Clippy -D warnings (iterative push cycles)",
      "notable": "Pre-existing parity_tests.rs bug fixed in #966"
    },
    "rust-release.yml": {
      "runs": 10,
      "success_rate_pct": 100,
      "releases_published": 10,
      "version_range": "v2.6.40 to v2.6.49"
    },
    "security.yml": {
      "runs_estimated": 28,
      "success_rate_pct": 90,
      "true_failure_count": 0,
      "action_required_count": 6
    }
  },
  "overall_health_score": 82,
  "total_runs_estimated": 120,
  "prs_merged": 14,
  "week_over_week_health_change": "+4",
  "open_coverage_target_issues": 4
}

---

Previous Reports

• 2026-04-06 Report (#949) — Score: 78/100
• 2026-03-30 Report (#917)
• 2026-03-23 Report (#893)
• 2026-03-16 Report (#854)

---

Generated automatically by CI/CD Workflow Health Monitor • workflow-health-monitor.lock.yml

Generated by CI/CD Workflow Health Monitor