Upgrade prototype to ConfigKit 0.4.0

docs/roadmap/implementation.md

@@ -46,7 +46,8 @@ prefix below. Root `go test ./...` does not cover this nested module.
 
 ## Stage 1: Upgrade the Prototype Dependency
 
-**Status:** Pending. **Depends on:** nothing.
+**Status:** Complete (2026-09-24). **Depends on:** nothing. ConfigKit v0.4.0 pinned;
+the nested offline tests and demonstration passed with the expected 1/4/0/2 result.
 
 Read the prototype README, `go.mod`, `go.sum`, and the current ConfigKit roadmap.
 Confirm the working tree and run the existing nested-module tests once as a

docs/roadmap/library-boundary-findings.md

@@ -13,12 +13,19 @@ evidence; they do not establish overlay integration.
 ## Selected Boundary
 
 The prototype lives in [examples/library-adoption](../../examples/library-adoption/README.md),
-a separate Go module using published ConfigKit v0.3.1, PromptKit v0.11.0, and
+a separate Go module now using published ConfigKit v0.4.0, PromptKit v0.11.0, and
 Audita v1.1.0. The Audita dependency lets this consumer reuse actual internal domain
 helpers through its Audita module namespace without a local replacement. It does
 not make those internal packages a new public API. Remove this dependency along
 with the prototype when equivalent production integration tests exist.
 
+The initial prototype results below were recorded with ConfigKit v0.3.1. On
+2026-09-24, upgrading only its ConfigKit pin and sums to v0.4.0 required no source
+changes. With Go 1.26.8 on linux/amd64, the nested offline `go test ./...` passed
+and `go run .` still reported one accepted correction, four attempts, zero
+transient retries, and two structural repairs. This verifies the dependency
+upgrade, not selected-overlay behavior.
+
 ConfigKit owns loading, presence, explicit overrides, secret resolution, and
 redacted effective settings. PromptKit owns profile parsing, rendering, provider
 execution, transient retries, structural repair, and backend admission. Audita