docs(openspec): record add-vale-binary-packages 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

Author: theCodeDrift

openspec/changes/add-vale-binary-packages/proposal.md

@@ -35,6 +35,8 @@ This change produces the artifact the resolver needs: per-platform Vale binary p
 
 ## Delivery shape
 
+**Release impact: minor.** Adds per-platform binary packages and declares them as CLI `optionalDependencies`. Install gains a bundled binary — additive, but a change to what shipping the CLI actually delivers.
+
 **Stacked, merging forward.** Publishing is inert until something pins it, which is what makes these units independently safe.
 
 | Unit | Scope                                                         | Safe alone because                                    |