Validate PromptKit comparison and catalogs

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Implement PromptKit comparison and catalogs
 
-Status: Stages 1–10 complete; remaining stages are planned.
+Status: Stages 1–12 complete.
 
 ## Scope and authority
 
@@ -638,7 +638,7 @@ exercise or new release gate is needed for this adoption sprint.
 
 **Completion evidence (2026-10-12)**
 
-- The ckprompt module graph selects PromptKit v0.14.0, ConfigKit v0.7.1,
+- The workspace graph selected PromptKit v0.14.0, ConfigKit v0.7.1,
   ReleaseKit v0.4.1, and `golang.org/x/tools` v0.49.0. PromptKit's Go module
   origin confirms tag v0.14.0 resolves to the roadmap-pinned commit
   `143c6e9b3a675872117b0471e2ff8bcb25055a54`. The graph's Go tools module
@@ -657,8 +657,12 @@ exercise or new release gate is needed for this adoption sprint.
 - `GOTOOLCHAIN=local go list -m all` reported the graph above. `go mod download
   -json` confirmed both pinned origins. Local Markdown link targets in the two
   changed files exist, and `git diff --check -- '*.md' COPYRIGHT` passed.
-- Complete repository, consumer, and isolated graph/import validation remains
-  assigned to Stage 12.
+- Stage 12's isolated graph audit found that the distributed ckprompt graph
+  selects `golang.org/x/tools` v0.6.0 through `golang.org/x/text` v0.14.0;
+  v0.49.0 was only selected in the broader workspace graph. The attribution
+  now follows the isolated graph and its v0.6.0 source.
+- Complete repository, consumer, and isolated graph/import validation is
+  recorded in Stage 12 below.
 
 ## Stage 12: Validate the complete end state and finish
 
@@ -715,3 +719,37 @@ completion evidence matches checks actually performed.
 
 All product/API decisions needed for this plan are settled; no open questions
 remain.
+
+**Completion evidence (2026-10-12)**
+
+- `GOTOOLCHAIN=local go test ./...` passed for core, ckconfig, and ckprompt with
+  the local workspace. The root module includes its core example, backend, and
+  release-tool packages; each integration suite includes its maintained
+  consumer example.
+- Workspace-off suites passed for all three modules with `GOWORK=off
+  GOTOOLCHAIN=local` and `-mod=readonly`. Integration checks used disposable
+  `go.mod`/`go.sum` pairs outside the repository, temporary local replacements
+  only for unpublished core/ckconfig prerequisites, and no distributed manifest
+  changes. Their isolated `go list -m all` and `go list -deps -test ./...`
+  checks passed.
+- The isolated ckprompt graph selects PromptKit v0.14.0 and ConfigKit v0.7.1;
+  ckconfig selects ConfigKit v0.7.1 without ckprompt or PromptKit. Core imports
+  neither optional integration nor ConfigKit/PromptKit through production,
+  tests, examples, or tools. Core declares ReleaseKit v0.4.0, while both
+  integration graphs select v0.4.1. The isolated ckprompt graph selects
+  `golang.org/x/tools` v0.6.0 through `golang.org/x/text` v0.14.0; its notice
+  now follows that graph rather than the broader workspace selection.
+- All seven composed example commands passed: PromptKit comparison, app
+  comparison, prompt and profile catalogs, named prompt inspection, session
+  restore, and ordinary multi-scope validation. The YAML output showed the
+  fixture's native PromptKit additions/change/deletion, exact catalog values,
+  and named prompt fields; the session command returned its synthetic session.
+  No external service was used.
+- Audited the completed target against implementation, focused tests, canonical
+  docs, examples, and module-local notices. Requirement inspection remains
+  deferred. The Stage 2 limitation remains recorded: PromptKit v0.14.0 exposes
+  no public path to produce successful engine inspection warnings, so native
+  warning retention could not be exercised.
+- `git diff --check -- '*.md' COPYRIGHT` and the local Markdown link check for
+  changed documentation passed. No workspace files, replacements, or module
+  graph artifacts are tracked; no release was published or tagged.