Use the declared YAML dependency in comparison tests

docs/roadmap/implementation.md

@@ -726,12 +726,20 @@ remain.
   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.
+- Workspace-off results for core and ckconfig used `GOWORK=off
+  GOTOOLCHAIN=local` and `-mod=readonly`; isolated module and package/import
+  enumeration also passed. The original ckprompt result did not establish
+  compatibility with its committed manifest: review finding
+  [R-5](remediation.md#r-5-validate-the-committed-ckprompt-manifest-without-an-extra-test-only-yaml-api)
+  found a test-only YAML v3 import requiring additional manifest tidying.
+- After the R-5 import repair, fresh copied ckprompt manifests passed
+  `go test -count=1 ./...`, `go list -m all`, and `go list -deps -test ./...`
+  with `GOWORK=off GOTOOLCHAIN=local` and `-mod=readonly` on Go 1.26.8. These
+  copies added only temporary replacements for unpublished core/ckconfig
+  prerequisites, were not tidied, and retained their exact manifest/sum bytes
+  throughout validation. Distributed metadata needed no changes. The results
+  prove compatibility with local prerequisite sources, not future tag
+  availability.
 - 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,