[plan] Workflow Lifecycle Management & Staleness Detection Improvements

[github-actions]

Overview

This tracking issue covers improvements to workflow compilation consistency, staleness detection, and lifecycle management in gh-aw. Currently, 28% of workflows (46/164) lack compiled .lock.yml files, and staleness detection relies solely on timestamps rather than content hashes.

Source: Discussion #6133

Current State

• 46 uncompiled workflows (28% of total)
• Timestamp-only staleness detection
• No CI enforcement of compilation consistency
• Limited user guidance for fixing stale workflows
• No bulk synchronization commands

Goals

1. Implement robust hash-based staleness detection with metadata versioning
2. Add CI enforcement to prevent uncompiled workflows from being merged
3. Provide actionable user guidance with clear next steps
4. Enable bulk operations for repository-wide workflow management
5. Add developer tooling (pre-commit hooks) to catch issues early

Planned Sub-Issues

This tracking issue has 5 sub-issues covering:

• Lock file metadata and hash-based staleness detection
• CI workflow for compilation consistency enforcement
• Proactive staleness warnings and actionable guidance
• Bulk synchronization commands (compile --all, sync, clean)
• Pre-commit hooks and developer documentation

Success Metrics

• Uncompiled workflow rate: 28% → <5%
• Staleness detection: Timestamp-only → Hash-based primary method
• CI enforcement: No → Yes (automated in PRs)
• Bulk operations: None → Multiple commands available
• Lock file metadata: 0% → 100% coverage

AI generated by Plan Command for discussion #6133