From c69a75d1c924cc93db5567b5a8258ad4d8d9dc15 Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Sun, 11 Oct 2026 22:06:08 +0000 Subject: [PATCH] Validate configuration comparison sprint --- docs/roadmap/implementation.md | 28 ++++++++++++++++++++++++---- 1 file changed, 24 insertions(+), 4 deletions(-) diff --git a/docs/roadmap/implementation.md b/docs/roadmap/implementation.md index 743531c..571832b 100644 --- a/docs/roadmap/implementation.md +++ b/docs/roadmap/implementation.md @@ -673,7 +673,27 @@ module boundaries, without implying publication or new guarantees. report remaining unrelated work. Follow existing release preparation later; this sprint does not publish or wait for module proxy availability. -**Completion evidence:** all three default suites, independent module graph -reviews (with local-source limits identified when applicable), maintained consumer -results, feature-to-evidence audit, and reviewed final documentation/distribution -changes. No significant product/API decisions remain open in this plan. +**Completion evidence — complete:** the workspace `go test ./...` commands pass +at the root and in both integration modules. Core also passes +`GOWORK=off GOTOOLCHAIN=local go test -mod=readonly ./...`; its workspace-off +module and package graphs retain ReleaseKit v0.4.0 and exclude ConfigKit, +PromptKit, and the integration packages. Both integrations pass their +workspace-off tests and read-only module/package graph checks with disposable +modfiles containing only the planned local replacements for unpublished +CommandKit modules. Those graphs select ConfigKit v0.7.1 and ReleaseKit v0.4.1; +ckprompt retains PromptKit v0.12.0. Direct package imports stay within the +integration boundaries. The alternate-file checks establish compatibility with +the local CommandKit sources and released external dependencies, not availability +of the future CommandKit module tags. + +The maintained simple and composed diff commands emit their expected YAML +changes (`greeting: Goodbye` and `default_campaign: autumn`) with no stderr. +Default show/greet, composed validation, named prompt inspection, and session +restore commands also succeed. Code graph and focused test review covers paired +input timing, callback-free discovery, equal-selection loads, diagnostic +retention, native safe values and concealed changes, all report categories, +null/deletion distinctions, delivery failures, fresh invocation state, and +ordinary inspection regressions. `ConfigScope` still declares only validate, +show, sources, and explain. Stage 12's notice, release-note, metadata, link, and +whitespace evidence is recorded above. No release was published or release +launcher run, and no significant product/API decisions remain open.