Identify configuration source files in load errors

docs/cli.md

@@ -223,6 +223,10 @@ go run ./cmd/notarius pipelines list \
 Successful commands write their primary result to standard output. Warnings and
 errors are written to standard error.
 
+Configuration load errors include ConfigKit's field diagnostics and source
+coordinates, followed by a source-ID legend identifying the acquired files or
+source labels. This includes imported files and the selected configuration profile.
+
 For **run --json**, actionable process warnings remain on standard error and standard output is a
 machine-readable success result only. Syntax and runtime diagnostics remain on
 standard error. Parse the result only after the process exits with status 0.

docs/roadmap/remediation.md

@@ -137,6 +137,9 @@ normalization instead of reporting a synthetic default for the explicit value.
 
 ## Finding 4 — Include Source Filenames In Load Diagnostics
 
+Status: Addressed. CLI load errors include a quoted source legend; command tests
+cover imported/profile failures, source coordinates, and terminal-control escaping.
+
 Priority: P2. Import/profile failures lack actionable file attribution.
 
 `internal/cli/configkit_load.go:29` calls `WriteDiagnostics` with diagnostics