You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Strong recovery this run — both P0/P1 workflows that were failing are now healthy. Overall health score reached 74/100 (↑8 from 66 last run). All 176 workflows have corresponding lock files.
Summary
Metric
Value
Total workflows
176
Healthy
163+ (~93%)
Warning (stale locks)
13
Critical (P0)
0 ✅
Missing lock files
0 ✅
Recoveries This Run 🎉
Issue Triage Agent → RECOVERED ✅
Previous status: P0 Critical — 15+ consecutive day failure (since March 6)
Action: Monitoring for consistency — no new issue needed
Warnings ⚠️
13 Stale Lock Files (P2)
Lock files are older than their source .md files — needs make recompile:
View 13 stale workflows
Workflow
Status
agent-performance-analyzer
stale lock
bot-detection
stale lock
ci-doctor
stale lock
daily-doc-updater
stale lock
daily-security-red-team
stale lock
daily-testify-uber-super-expert
stale lock
delight
stale lock
duplicate-code-detector
stale lock
mcp-inspector
stale lock
python-data-charts
stale lock
smoke-copilot
stale lock
ubuntu-image-analyzer
stale lock
workflow-normalizer
stale lock
Fix: Run make recompile to regenerate all lock files from source markdown.
Known Pre-existing Issues (P2)
Contribution Check: safe_outputs failure on schedule runs — pr-filter-results.json missing in schedule context. Agent logic is healthy; issue is infrastructure-level.
AI Moderator: ~17% failure rate due to race condition on closed PRs during branch checkout.
Healthy Workflows ✅
All critical operational workflows are running normally:
Integrity filtering activated and filtered the following item during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.
issue:#unknown (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
Overview
Strong recovery this run — both P0/P1 workflows that were failing are now healthy. Overall health score reached 74/100 (↑8 from 66 last run). All 176 workflows have corresponding lock files.
Summary
Recoveries This Run 🎉
Issue Triage Agent → RECOVERED ✅
Smoke Gemini → RECOVERED ✅
Warnings⚠️
13 Stale Lock Files (P2)
Lock files are older than their source
.mdfiles — needsmake recompile:View 13 stale workflows
agent-performance-analyzerbot-detectionci-doctordaily-doc-updaterdaily-security-red-teamdaily-testify-uber-super-expertdelightduplicate-code-detectormcp-inspectorpython-data-chartssmoke-copilotubuntu-image-analyzerworkflow-normalizerFix: Run
make recompileto regenerate all lock files from source markdown.Known Pre-existing Issues (P2)
safe_outputsfailure on schedule runs —pr-filter-results.jsonmissing in schedule context. Agent logic is healthy; issue is infrastructure-level.Healthy Workflows ✅
All critical operational workflows are running normally:
Trends
Actions Taken This Run
References: §23374688097
Note
🔒 Integrity filtering filtered 1 item
Integrity filtering activated and filtered the following item during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)