Verify ConfigKit integration and record release handoff

docs/roadmap/configkit.md

@@ -2,11 +2,10 @@
 
 ## Status And Intent
 
-Accepted feature direction, drafted on 2026-09-26; not implemented. This
-roadmap defines the target behavior and changes from the reviewed baseline.
-The [implementation plan](implementation.md) owns sequencing, concrete interfaces,
-verification steps, and implementation status. This document owns the desired
-end state and the policy choices behind it.
+Implemented feature direction, drafted on 2026-09-26 and delivered through the
+[implementation plan](implementation.md). This roadmap records the target
+behavior and changes from the reviewed baseline; the implementation plan owns
+sequencing, concrete interfaces, and verification evidence.
 
 The user is adopting ConfigKit across an application suite to standardize
 configuration semantics. Scriptorium will make a clean cutover to ConfigKit's
@@ -20,7 +19,7 @@ application-specific reason or a genuine ownership boundary, not backward
 compatibility alone. The [architecture policy](../policy/architecture.md) and
 [ADR 0004](../adr/0004-definition-boundary.md) remain the scope boundaries.
 
-## Reviewed Baseline
+## Reviewed Baseline (Historical)
 
 Scriptorium consumes Promptkit v0.11.0. Its `internal/config` package uses
 yaml.v3 directly and manually applies defaults, file settings, and CLI overrides.
@@ -225,3 +224,8 @@ the relevant secret to the API key. Inspection therefore preserves parameter
 values and environment-reference names, while actual API-key values remain
 outside the application configuration pipeline. Visibility is intentional;
 this is not a promise to detect secrets placed inside arbitrary parameter values.
+
+The delivered `config show` and `config explain` commands use ConfigKit's
+inspection writers without secret tags or a second redaction path. Both
+effective and historical parameter values remain visible; `api_key_env` names
+remain visible while Promptkit alone resolves selected credential values.