ci(openspec): gate archived changes on having no unticked tasks - #113
Merged
Merged
Conversation
Completes the ADR-0023 §7 rollout. The other four repos wired this step after clearing real debt — 18 archived changes across them carried tasks that were never ticked, invisible to every gate because `validate --all --strict` does not read `changes/archive/`. This repo has no archived change yet, so the step passes vacuously today. That is the reason to add it now rather than later: it guards the FIRST archived change instead of the eighteenth. Verified the empty case is safe before wiring it — `validate --archived` exits 0 with "No items found to validate", so this cannot break CI on the next push. And verified the step is a gate rather than decoration, on a scratch copy of a repo that does have archived changes: exit 0 clean, exit 1 with a single box unticked. Verified on this branch: openspec validate --all --strict, npm run check, lint, test:i18n (parity OK across 3 locales) and validate:digests all rc=0.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
verbara-website | 28aa55c | Commit Preview URL Branch Preview URL |
Sep 21 2026, 12:57 PM |
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
1 participant
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.
Completes the ADR-0023 §7 rollout — the fifth and last repo.
Why here, where there is nothing to validate yet
The other four wired this after clearing real debt: 18 archived changes between them carried tasks that were never ticked, invisible to every gate because
validate --all --strictdoes not readchanges/archive/.This repo has no archived change yet, so the step passes vacuously today.
That is the argument for adding it now rather than later. It guards the first archived change instead of the eighteenth. The cost of the other four was a full session of disposing 35 boxes one by one against the tree; the cost here is one line.
Two things checked before wiring
The empty case is safe — otherwise this would break CI on the next push:
It is a gate, not decoration — proved on a scratch copy of a repo that does have archived changes:
What this costs from here
Archiving a change with an unticked box will fail CI. 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