[aw] Workflow Health Dashboard — 2026-04-30

[github-actions]

Overview

77% success rate today (23/30 scheduled runs) — slight recovery from 73% on Apr 29. 7 failures recorded. All 205 workflows compile with lock files present. The safe_outputs failure pattern continues, with a new workflow (Daily Community Attribution Updater) joining the affected set.

Summary

Metric	Value
Total workflows	205
Missing lock files	0 ✅
Scheduled runs today	30
Successes	23 (77%)
Failures	7 (23%)
Health Score	77/100 ↑+4

Critical Issues 🚨

Daily Fact About gh-aw (P0 — ongoing)

• Error: codex: command not found — codex binary unavailable on runner
• Tracking issue: [aw] Daily Fact About gh-aw failed #29088
• Pattern: Recurring daily failure; codex engine not installed in runner environment
• Run: §25163325014

Warnings ⚠️

Safe Outputs Failures (6 workflows — recurring pattern)

The following workflows had safe_outputs job failures. This is a recurring pattern from Apr 29 with one new addition today:

Workflow	Run	Status
Daily Rendering Scripts Verifier	§25162697356	Recurring
Developer Documentation Consolidator	§25162557165	Recurring
Daily AstroStyleLite Markdown Spellcheck	§25162377257	Recurring
Instructions Janitor	§25162158074	Recurring
Daily AW Cross-Repo Compile Check	§25162144631	Recurring
Daily Community Attribution Updater	§25161944698	New today

Pattern: safe_outputs job fails in cleanup/post-job phase. No OTEL on several. Possible shared infrastructure issue.

Carry-Forward Issues

Issue	Status
CI integration tests failing (#29108 context)	Needs monitoring
Documentation Unbloat claude auth (#28659)	OPEN
GitHub Remote MCP Auth Test (#27965)	OPEN day 9+
MCP gateway session timeout (#23153)	OPEN
awf-api-proxy sidecar unhealthy (#27888)	OPEN
GitHub App rate limit (#27251)	OPEN
CODEX_HOME collision (#27512)	OPEN
Safe Outputs SEC-004 (#27235)	OPEN
Node.js 20 deprecation in CI	Sep 2026 deadline

Systemic Issues

• P0: Codex binary missing — 1 workflow fails daily. Tracked in [aw] Daily Fact About gh-aw failed #29088.
• P2: Safe_outputs recurring failures — 6 workflows failing in safe_outputs job daily. Pattern stable (no escalation today). May indicate shared infra or Docker environment issue for these specific workflows.

Trends

• Apr 27: 93% → Apr 28: 57% (THREAT_DETECTION_RESULT) → Apr 29: 73% → Apr 30: 77% ↑
• THREAT_DETECTION_RESULT failure: NOT recurring for 2nd consecutive day — likely resolved
• Safe_outputs failures: stable at 6 workflows (one new addition today — Community Attribution Updater)
• No new P0/P1 regressions detected

Actions Taken

• Updated repo memory (workflow-health-latest.md)
• No new P0/P1 issues created (existing tracking issues cover all identified failures)
• Created this dashboard issue

References:

• §25164831125 — This workflow health run
• §25163325014 — Daily Fact About gh-aw (codex failure)
• §25161944698 — Daily Community Attribution Updater (new safe_outputs failure)

Note

🔒 Integrity filter blocked 1 item

The following item was blocked because it doesn't meet the GitHub integrity level.

• #19099 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

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

• expires on May 1, 2026, 12:22 PM UTC