Simplify the library migration to target the final integration

docs/roadmap/library-boundary.md

@@ -36,7 +36,7 @@ Required work:
   alone is insufficient evidence.
 - Record new results separately from the historical v0.3.1 findings. Expand the
   existing ConfigKit roadmap into a concrete production implementation handoff,
-  including the interim runtime boundary and removal of legacy configuration.
+  including final runtime integration and removal of legacy configuration.
 
 Target end state: reviewers can run the prototype with and without the testing
 selection and see both LLM roles switch models. The offline test suite establishes
@@ -254,8 +254,8 @@ This unit is complete only when:
   code is clearly isolated and has a removal/integration destination during the
   production migrations; no second supported runtime is introduced.
 - A component-level follow-up identifies code to replace, domain code to retain,
-  tests to update, documentation/migration-guide work, and any temporary bridge
-  needed while ConfigKit lands ahead of PromptKit.
+  tests to update, documentation/migration-guide work, and direct integration of
+  the final configuration and PromptKit runtime.
 - Licensing/distribution follow-up for the selected dependency graph is identified
   for the later release stage; this prototype does not claim release compliance.
 - Roadmap links and examples resolve, appropriate checks pass, and commits contain