ci(openspec): gate archived changes on having no unticked tasks - #342
Merged
Merged
Conversation
ADR-0023 §7 deferred this gate per repo until that repo reached rc=0, because wiring it earlier would have turned existing debt into a red main. This repo reached rc=0 on 2026-09-21; before that it carried closed changes with work still outstanding and nothing could see it. One step beside the existing strict validate, in the same job. Verified it is a gate and not decoration: on a scratch copy `validate --archived` exits 0 clean and exits 1 with a single box unticked in one archived change. What this costs from here: archiving a change with an unticked box fails CI. That is the intent — the alternative is what this repo just spent a session undoing — but the box must then be dispositioned honestly, either `- [x]` with evidence or harvested into an open change, never ticked to get green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
One step beside the existing strict validate, in the same
openspecjob:Why now, and not before
ADR-0023 §7 deferred this gate per repo until that repo reached rc=0 — wiring it earlier would have turned existing debt into a red
main. This repo reached rc=0 on 2026-09-21. Before that it carried closed changes with work still outstanding, and nothing could see it:validate --all --strictdoes not readchanges/archive/.It is a gate, not decoration
Proved on a scratch copy rather than assumed:
What this costs from here
Archiving a change with an unticked box now fails CI. That is the intent — the alternative is what this repo just spent a session undoing — but it adds real friction at close-out, and the box must then be dispositioned honestly:
- [x]with evidence, or harvested into an open change. Never ticked to get green.Verification on this branch
decision_ref: verbara-meta/ADR-0023 §7🤖 Generated with Claude Code