Workflow Health Dashboard

[aspire-repo-bot]

— 2026-05-22

Overview

Total: 10 | Healthy: 10 (100%) | Warning: 0 (0%) | Critical: 0 (0%) | Inactive: 10 (100%)

Summary

All workflows are in excellent compilation health:

• ✅ All 4 agentic workflows have valid, up-to-date lock files
• ✅ Zero frontmatter-hash mismatches
• ✅ Zero schema validation errors
• ✅ Zero deprecation warnings

Run-time health: No execution data available yet. This appears to be the initial health check before any workflows have been executed.

Configuration Quality Assessment

All workflows demonstrate strong configuration practices:

Agentic Workflows (4)

• ✅ ci-coach.md — concurrency configured, timeouts set (15-30m), scoped permissions
• ✅ issue-arborist.md — concurrency configured, timeouts set (15-20m), scoped permissions
• ✅ update-integration-data.md — concurrency configured, timeouts set (20m), scoped permissions
• ✅ workflow-health-manager.md — concurrency configured, timeout configured, scoped permissions

Plain GitHub Actions Workflows (6)

• ✅ apphost-build.yml — permissions: contents:read only
• ✅ ci.yml — permissions: contents:read, security-events:write (appropriate)
• ✅ copilot-setup-steps.yml — [not analyzed for runtime yet]
• ✅ frontend-build.yml — permissions: contents:read only
• ✅ tools-tests.yml — permissions: contents:read only
• ✅ update-release-branch.yml — permissions: {}, concurrency configured

Systemic patterns

• No patterns detected (no run history available)

Trends (this run vs previous)

• First health check run — no baseline for comparison
• All workflows ready for execution
• Compilation infrastructure validated and healthy

Next Steps

1. Monitor first runs — When workflows begin executing, the next health check will establish baseline success rates
2. Watch for:
   • Timeout issues (particularly for 15-20m agent timeouts)
   • Permission errors (though all are conservatively scoped)
   • Concurrency thrashing (all have appropriate groups configured)

Last updated: 2026-05-22T05:01:47Z
Status: Initial health check — no run history available
Next check: Will assess actual execution health once workflows begin running

Generated by Workflow Health Manager — Meta-Orchestrator · ● 1.7M · ◷