Add PromptKit engine adapters

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Implement the optional integration modules and captured registration API
 
-Status: implementation in progress. Stages 1 through 10 are complete; subsequent work follows the ordered roadmap.
+Status: implementation in progress. Stages 1 through 11 are complete; subsequent work follows the ordered roadmap.
 Execute the stages in order. Each stage is sized as a separate Luna coding-agent
 assignment. This document authorizes no publication or changes to sibling
 repositories.
@@ -543,6 +543,18 @@ inspection through PromptKit's released public APIs.
 facets, both adapters' nil wiring and retained errors, callback narrowing,
 diagnostics on lookup failure, and no construction-time acquisition.
 
+**Completion evidence — complete:** `ConfigScope` exposes PromptKit's native
+effective/source/explanation facets and validation capability through the public
+ckconfig scope contract. `FromEngine` returns the selected typed suite and named
+callbacks, passing selection, input, state and context to the loader; request
+identity is preserved and an empty prompt version keeps PromptKit's default
+selection semantics. Both adapters use one private acquisition/diagnostic path.
+Nil loaders are retained through `ckconfig.WithScopeError` or the suite's private
+issues, including after scope capability narrowing or callback removal. Focused
+adapter tests pass with a temporary workspace and a clean copy of ckconfig's
+production files; the full ckprompt module suite remains deferred until Stage 13
+replaces the mixed-package prototype tests.
+
 ## Stage 12: Assemble named PromptKit inspection and reports
 
 **Outcome:** independent optional prompt/profile commands use the core pipeline.