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

Preserve ConfigKit result evidence alongside loader errors

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-07 12:04:46 +00:00
parent 07e1634e79
commit d7a85f5f35
3 changed files with 76 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/roadmap/remediation.md
View File

@@ -1,6 +1,6 @@
# Shared reporting and PromptKit adoption remediation
Status: five open findings; R1–R2 complete. R1–R3 are from the architectural review of
Status: four open findings; R1–R3 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.
@@ -114,6 +114,13 @@ should continue to stop domain work.
## R3 — P2: A native ConfigKit result accompanying an error loses evidence
**Complete.** Result-plus-error acquisition now retains sources, findings, and
ordinary messages without exposing effective, explanation, or metadata facets.
A matched LoadError still supplies the sole authoritative snapshot. Regression
checks cover application/cancellation causes, absent versus empty findings,
source and validation reports, warning delivery, and presentation failures.
The independent ckconfig suite passes with Go 1.27.0.
**Location:** [configkit_adapter.go](../../integrations/ckconfig/configkit_adapter.go),
FromConfigKit.Acquire lines 35–47.