base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Add detailed validation evidence

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-07 04:52:58 +00:00
parent 1986c44f49
commit 0b70f37267
5 changed files with 286 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/cli.md
View File

@@ -335,12 +335,20 @@ with each reached scope and its outcome (`valid`, `failed`, or `canceled`).
example config validate
example config validate --scope promptkit --format yaml
example config validate --scope all
example config validate --scope all --details --severity warning --code schema.version
```
Each successful scope is reported as `SCOPE: valid`. Aggregate validation stops
at the first load failure or cancellation, then submits one report containing
the reached scopes. Output errors occur after acquisition has stopped. Provider
warnings go to the diagnostic stream and do not alone make validation fail.
`--details` includes native findings and the source references needed to
interpret them. Each scope's detail state is `unavailable`, `empty`, `filtered`,
or `present`. Repeat `--severity error|warning` or `--code CODE` to filter
findings: values within a filter match any, and the two filters narrow together.
Filters require `--details` and never change the validation outcome. Detailed
output suppresses ordinary warnings associated with its native findings; other
messages and terminal failure explanations remain visible.
`--config` and `--overlay` preserve whether an
empty value was explicitly supplied, so a scope callback can map those inputs to
its own ConfigKit load policy. Help and invalid syntax do not call scope