Render configuration explanations from acquired reports
This commit is contained in:
@@ -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.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user