Skip to content

Commit c452427

Browse files
theCodeDriftclaude
andcommitted
docs(openspec): record add-vale-rule-engine as a minor release
Every one of these PRs carried skip-changeset while it was spec-only, which becomes wrong the moment implementation lands. Stating the impact in the proposal means the tip PR needs a changeset written, not a label kept. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CDv57zHq7abms3RReSQw6q
1 parent 8b2de91 commit c452427

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

‎openspec/changes/add-vale-rule-engine/proposal.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,8 @@ Taskless rules are ast-grep only — structural AST matching that fits code but
3434

3535
## Delivery shape
3636

37+
**Release impact: minor.** Adds a second rule engine and a new knowledge topic. Nothing existing breaks; ast-grep rules behave exactly as before. A whole new capability is a feature.
38+
3739
**Stacked, merging down.** The Vale engine is only correct once `check` can dispatch to it: the runner without the multi-engine orchestration ships an engine that never executes, and the orchestration without the runner dispatches to nothing.
3840

3941
| Unit | Scope |

0 commit comments

Comments
 (0)