Verify the integrated application and complete the migration

docs/roadmap/configkit.md

@@ -2,9 +2,9 @@
 
 **Last updated:** 2026-09-24
 
-**Status:** Final target selected; production implementation pending. The boundary
-and selected overlays are verified. The [implementation plan](implementation.md)
-owns execution stages; no production migration or release has begun.
+**Status:** Production implementation complete. The selected configuration and
+overlay model is implemented; [implementation evidence](implementation.md)
+records verification. No release has been published.
 
 ## Purpose and Direction
 
@@ -20,15 +20,14 @@ guide instead of legacy loaders, aliases, dual operating modes, or an ongoing
 compatibility layer. Retain existing syntax only when it independently suits the
 new model, not because compatibility requires it.
 
-The initial review and prototype used ConfigKit v0.3.1. The prototype now pins
-v0.4.0 and verifies its selected-overlay path; original v0.3.1 findings remain
-historical. The installed
-application must depend on a versioned module, not a sibling checkout or local
-module replacement.
+The initial review and prototype used ConfigKit v0.3.1, then verified v0.4.0
+selected overlays. Those findings remain historical; the prototype was removed
+after production integration. The application depends on a versioned module,
+without a sibling checkout or local module replacement.
 
 The shared boundary/prototype unit is complete. Its [selected contract, inventory,
 and evidence](library-boundary-findings.md) define the detailed target alongside
-this roadmap. Production configuration migration has not begun.
+this roadmap. Production configuration migration is complete.
 
 ## Target End State