Upgrade ckprompt to PromptKit v0.14.0

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Implement PromptKit comparison and catalogs
 
-Status: planned; no stages have been implemented under this plan.
+Status: Stage 1 complete; remaining stages are planned.
 
 ## Scope and authority
 
@@ -97,6 +97,25 @@ For isolated test/list checks after preparing the disposable files, use
 availability. The reviewed maintainer toolchain is Go 1.26.8; do not raise the
 consumer minimum to that patch version.
 
+**Completion evidence (2026-10-12)**
+
+- Updated ckprompt to PromptKit v0.14.0. `go mod download -json` confirmed the
+  release tag resolves to the roadmap's pinned source commit
+  `143c6e9b3a675872117b0471e2ff8bcb25055a54`; Go tooling supplied the module
+  checksums. Go 1.26.0, ConfigKit v0.7.1, and the existing CommandKit module
+  requirements remain unchanged. No additional indirect requirements were
+  needed, and the ignored workspace remains unchanged.
+- Workspace-off `go test ./...` passed for both ckprompt and ckconfig with
+  `GOWORK=off GOTOOLCHAIN=local`, `-mod=readonly`, temporary module/sum pairs,
+  and local replacements only for unpublished CommandKit prerequisites.
+- `GOTOOLCHAIN=local go test ./...` passed in `integrations/ckprompt` with the
+  workspace. The isolated ckprompt graph selected PromptKit v0.14.0 and ConfigKit
+  v0.7.1; the isolated ckconfig graph selected ConfigKit v0.7.1 and contained no
+  PromptKit module. The existing composed negative diff test passed; there were
+  no baseline failures.
+- Full repository and final assembled-state validation remain assigned to
+  Stage 12.
+
 ## Stage 2: Make engine diagnostics reusable for paired acquisition
 
 **Outcome:** private engine acquisition retains completed diagnostics and can