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
{{ message }}
Repository navigation
[deep-report] Batch recompile 18 stale lock files introduced by PR #26372 #26453
The Workflow Health Dashboard (Apr 15, #26421) reports 18 stale .lock.yml files whose source .md files are newer than their compiled outputs. The regression was introduced by PR #26372 (context propagation refactor, merged Apr 15 06:04Z), which touched workflow files without triggering recompilation. This is a repeat of the Apr 3 batch where 19 stale files were detected.
Expected Impact
Stale lock files mean deployed workflows may not reflect the latest source changes, leading to subtle behavioral divergence. Batch recompiling all 18 files will restore consistency between .md source files and their compiled .lock.yml counterparts and prevent silent behavior mismatches.
Suggested Agent
Agentic Maintenance — run gh aw compile for all affected workflows and commit the resulting .lock.yml files in a single PR.
Estimated Effort
Fast (< 30 min)
Data Source
DeepReport Intelligence Briefing — 2026-04-15 (run §24461694592). Source: [workflow-health] Dashboard #26421 and prior pattern from known_patterns.md (Apr 3 had 19 stale files).
Activity