Expose configuration metadata and findings
This commit is contained in:
@@ -297,8 +297,9 @@ example config scopes
|
||||
example config scopes --format yaml
|
||||
```
|
||||
|
||||
Text output uses one `scope: operation, operation` line per scope. YAML uses a
|
||||
`scopes` sequence with explicit `name` and `operations` fields. Scope order is
|
||||
Text output uses one `scope: operation, operation` line per scope and lists any
|
||||
declared optional features. Structured output uses a `scopes` sequence with
|
||||
`name`, `operations`, and any supported `features`. Scope order is
|
||||
`app`, then `promptkit`, then other names alphabetically. A metadata-only scope
|
||||
can be listed without an acquisition callback. Discovery does not construct a
|
||||
runtime context or acquire configuration. It reports the intersection between
|
||||
|
||||
Reference in New Issue
Block a user