Render configuration explanations from acquired reports

docs/cli.md

@@ -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:
 

docs/roadmap/remediation.md

@@ -1,6 +1,6 @@
 # Shared reporting and PromptKit adoption remediation
 
-Status: seven open findings. R1–R3 are from the architectural review of
+Status: six open findings; R1 complete. R1–R3 are from the architectural review of
 `f83866e44a8a9066db52cbd2aa5cccde0d69a839`. R4–R7 are from the algorithmic
 audit of `f5b2d1f80c4720b762f3301c29d5050710c210d0`; R4 is a correctness
 issue and R5–R7 are efficiency opportunities for consideration.
@@ -33,6 +33,11 @@ These findings do not request stronger domain validation or new guarantees.
 
 ## R1 — P2: Explain still uses a separate provider text renderer
 
+**Complete.** A reusable template now renders the acquired projection, including
+scope, metadata history, origins, and a shared source legend. No provider text
+writer is called by the handler. Cross-format evidence and delivery-failure
+regressions and the independent ckconfig suite pass with Go 1.27.0.
+
 **Location:** [explain.go](../../integrations/ckconfig/explain.go),
 `runConfigExplanation`, particularly lines 160–169.