Plan PromptKit 0.18 adoption

docs/roadmap/future.md

@@ -23,22 +23,12 @@ an idea here does not select its syntax, API, priority, or delivery date.
 
 ### ckprompt dependency migration and workspace alignment
 
-Review the upstream PromptKit vanity release and select compatible ConfigKit
-and PromptKit dependencies before migrating ckprompt's adapters and maintained
-composed consumer. The new ckconfig uses vanity ConfigKit types; ckprompt v0.2.0
-still uses published ckconfig v0.2.0 and old-path ConfigKit v0.8.0. Their local
-sources do not currently compose in the three-module workspace. See the
-[consumer guide](../consumers/guide.md#module-selection) for the current module
-relationship.
-
-The follow-up includes migrating affected imports and public type boundaries,
-selecting real released dependency versions and the required Go minimum,
-updating notices and migration guidance, and validating both ckprompt's
-independent graph and the aligned composed consumer. Restore three-module
-workspace guidance when those dependencies align, updating the ignored workspace
-Go version as needed. Until then, preserve local workspace files and validate
-with workspace discovery off as described in the [development guide](../development.md).
-No unreviewed PromptKit version or new compatibility bridge is selected here.
+The [PromptKit v0.18.0 adoption roadmap](promptkit-v0.18.0.md) owns the proposed
+dependency set, API/report and fixture migration, workspace alignment, and open
+release/example choices. The current ckprompt v0.2.0 still uses published
+ckconfig v0.2.0 and old-path ConfigKit v0.8.0; it does not compose with local
+ckconfig v0.3.0. See the [consumer guide](../consumers/guide.md#module-selection)
+and [development guide](../development.md) for current module and workspace use.
 
 ## Future capability targets