ci: fail the build when the generated workflow catalog drifts from its source
WHY THIS MATTERS With 13k generated lines, no reviewer can eyeball whether a regeneration of systemWorkflows.ts is faithful. This was flagged in PR #256 and deferred; PR #309 tripling the file's size makes it overdue. HOW IT WORKS The new workflows-drift job checks out this repo and mike-workflows as siblings (the layout the generator expects), pins mike-workflows to the commit stamped inside the generated file (grepped from SYSTEM_WORKFLOWS_SOURCE_COMMIT), reruns the zero-dependency generator, and fails on `git diff --exit-code` over the generated outputs. Any hand-edit, stale regeneration, or locale-dependent ordering difference turns the PR red instead of shipping silently. Found by review of PR #309. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E4PXCdenNH5Mqhm5Sre9Zs
| Repository | open-legal-products/mike |
|---|---|
| Author | Amal <mamalanand3@gmail.com> |
| Authored | |
| Committed | |
| Parents | 946e4978 |
| Stats | 1 file changed , +46 |
| Part of | Refactor workflows into defaults, add-ons, and quick actions |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-0ca6c460.md
from inside the repo you want the change in.