From the review of #103 and #109 together.
The skill's "What actually gates a merge" section states the workflow "runs exactly three things" and lists them. Once #109 merges there is a fourth step, check_cards.py, gated to schedule and workflow_dispatch. The section already says to re-derive the list from the workflow file, but a hard-coded "exactly three" becomes false on the day it lands, and the distinction between a merge-blocking step and a nightly-only one is precisely the kind of thing the skill exists to record.
Fix belongs in #109, after #103 merges.
From the review of #103 and #109 together.
The skill's "What actually gates a merge" section states the workflow "runs exactly three things" and lists them. Once #109 merges there is a fourth step,
check_cards.py, gated toscheduleandworkflow_dispatch. The section already says to re-derive the list from the workflow file, but a hard-coded "exactly three" becomes false on the day it lands, and the distinction between a merge-blocking step and a nightly-only one is precisely the kind of thing the skill exists to record.Fix belongs in #109, after #103 merges.