Render configuration explanations from acquired reports

This commit is contained in:
2026-11-07 12:01:53 +00:00
parent 3a7e2d4ce7
commit c61e125649
4 changed files with 92 additions and 30 deletions

View File

@@ -462,9 +462,9 @@ when present, its explicitness. Path discovery does not include values or histor
Pointer tokens use JSON Pointer escaping: `~1` represents `/` and `~0`
represents `~`. A malformed pointer is a usage error with status `2` and is
rejected before acquisition. A well-formed path that is unknown in the selected
configuration is an operational error with status `1`. Text output includes
the scope's native explanation and available field metadata. Structured output
includes metadata when supplied by the scope.
configuration is an operational error with status `1`. Text, YAML, and JSON
render the same acquired explanation, available field metadata and metadata history, and source labels. Text uses CommandKit's
explanation template; the handler does not call the provider's text writer.
Structured output uses these root fields: