Expose safe inheritance origins in explanations

docs/cli.md

@@ -74,9 +74,14 @@ YAML summary of selected ID, backend, model, sampling controls, per-attempt
 timeout, service tier, and reasoning effort for each role. It omits credentials,
 endpoints, and arbitrary extra provider parameters. Explain writes a YAML
 sequence of field paths, source origins, and recorded derivations without
-resolved setting values. These views share the same settings and profile
-validation path as `process`. Unknown views are usage errors. The effective
-settings YAML is for inspection and is not guaranteed reloadable.
+resolved setting values. An inherited field may also include an `inheritance`
+sequence; each step identifies `from`, `to`, and `reference` paths as JSON
+pointers. These fields describe the effective inheritance chain without
+including configuration values. A direct child override reports its own source
+instead. Debug configuration origins use the same explanation shape. These views
+share the same settings and profile validation path as `process`. Unknown views
+are usage errors. The effective settings YAML is for inspection and is not
+guaranteed reloadable.
 
 For `process`, `--output` writes the corrected transcript to a file and leaves
 stdout empty on success. Without it, stdout carries transcript JSON only on

docs/internal/llm-runtime.md

@@ -24,6 +24,10 @@ Counts distinguish provider attempts, transient retries, and structural
 repairs, including on errors. Secrets from all configured backends, including unselected
 ones, are available to the diagnostics redaction boundary.
 
+CLI explain output and debug configuration origins share a value-free projection
+of effective field origins. The [CLI contract](../cli.md) defines its optional
+inheritance evidence fields.
+
 ## Orchestration
 
 CLI processing supplies two role clients from the same engine to the runner.

docs/roadmap/implementation.md

@@ -123,6 +123,8 @@ library tests, then commit the focused configuration unit.
 
 ## Stage 3 — Expose Compact Inheritance Evidence in Safe Inspection
 
+**Completion:** Complete.
+
 **Primary files:** `internal/framework/llm/safe_view.go`,
 `internal/framework/llm/runtime_inspection_test.go`, `docs/cli.md`, and the
 relevant explanation description in `docs/internal/llm-runtime.md` if needed.