Verify ConfigKit integration and record release handoff

docs/internal/adapters.md

@@ -53,6 +53,11 @@ preparation or generation.
 formats a safe application-owned effective profile view. It intentionally does
 not require prompt, schema, or artifact sources.
 
+The `config` family loads the same application ConfigKit result once and uses
+its validation, effective-output, source, and explanation views directly. It
+does not construct a Promptkit engine. The CLI maps source records into a small
+JSON DTO for `sources`; `show` and `explain` use ConfigKit's own writers.
+
 `serve` constructs Scriptorium's restricted HTTP artifact reader, injects it
 with `promptkit.WithArtifactReader`, passes the engine through the HTTP
 adapter's consumer-owned `Runner` interface, and starts the server.

docs/internal/sources.md

@@ -49,6 +49,10 @@ Every configuration-loading command uses this boundary. The CLI maps only
 explicitly visited application flags to ConfigKit overrides and prints
 structured load diagnostics before engine construction. The old application
 YAML decoder and merge path have been removed.
+Application `config` inspection reuses the result's frozen effective,
+provenance, and history views without constructing an engine or reloading
+sources. It does not resolve API-key environment values; ordinary backend
+parameters remain visible by the selected inspection policy.
 
 ## Restricted HTTP Artifact Reader