Why
CLI behavior contracts need to describe review-oriented expectations as the clean-code proof path expands.
What Changes
- Keep the YAML schema and validation tool for CLI behavior scenarios.
- Add optional clean-code category metadata so review scenarios can assert expected code-quality categories.
- Preserve backward compatibility by keeping the new metadata optional.
OpenSpec Change Proposal: cli-val-01-behavior-contract-standard
Why
CLI behavior contracts need to describe review-oriented expectations as the clean-code proof path expands.
What Changes
OpenSpec Change Proposal: cli-val-01-behavior-contract-standard