From e70a0ef301a3d34f64a6cba86dd68b728436534d Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Sat, 21 Nov 2026 19:50:40 +0000 Subject: [PATCH] Record adoption validation and release follow-up --- .../configkit-v1.4.0-promptkit-v0.24.0.md | 8 ++++---- docs/roadmap/future.md | 20 ++++++++++++++++++- docs/roadmap/implementation.md | 20 +++++++++++++++++-- 3 files changed, 41 insertions(+), 7 deletions(-) diff --git a/docs/roadmap/configkit-v1.4.0-promptkit-v0.24.0.md b/docs/roadmap/configkit-v1.4.0-promptkit-v0.24.0.md index 3c4842d..0fea04b 100644 --- a/docs/roadmap/configkit-v1.4.0-promptkit-v0.24.0.md +++ b/docs/roadmap/configkit-v1.4.0-promptkit-v0.24.0.md @@ -1,6 +1,6 @@ # ConfigKit v1.4.0 and PromptKit v0.24.0 adoption -Status: agreed adoption direction; implementation pending. Prepared 2026-11-21. +Status: implementation complete; coordinated releases pending. Prepared 2026-11-21. This document defines the desired target and accepted scope, not implemented behavior or authorization to publish releases. The [implementation plan](implementation.md) owns execution stages and completion @@ -275,6 +275,6 @@ needed for the selected application workflow. ## Execution status -The [staged implementation plan](implementation.md) is ready. No significant -product decisions remain open. Implementation and release work remain pending; -the plan records their separate completion evidence within this accepted scope. +The [staged implementation plan](implementation.md) records the completed local +work and validation evidence. The coordinated integration releases remain pending +as recorded in [future work](future.md#pending-integration-release-coordination). diff --git a/docs/roadmap/future.md b/docs/roadmap/future.md index be40f24..758a5b4 100644 --- a/docs/roadmap/future.md +++ b/docs/roadmap/future.md @@ -1,6 +1,7 @@ # Future work -Status — optional shell validation and future capability proposals. +Status — integration release coordination, optional shell validation, and future +capability proposals. No delivery dates are selected here. ## Purpose and authority @@ -37,6 +38,23 @@ govern any future implementation. The [CLI reference](../cli.md), public GoDoc, and [consumer guide](../consumers/guide.md) own implemented behavior. Retaining an idea here does not select its syntax, API, priority, or delivery date. +## Pending integration release coordination + +The ConfigKit v1.4.0 and PromptKit v0.24.0 adoption is implemented locally; +publication remains separate. Follow the [release procedure](../release.md) +and obtain the required publication authorization. Prepare and release ckconfig +v0.10.0 first. Then select that actual release in ckprompt, tidy with real +checksums, update matching-version attribution, and run ckprompt's independent +default suite before preparing its v0.11.0 release. Core remains v0.7.0 for this +adoption. Candidate notes and planned versions must be checked again at release +time. Hosted delivery is separately authorized. + +The current ckprompt checkout still requires published ckconfig v0.9.0, which +lacks the new path-reader API. Its aligned workspace and isolated local-replace +tests passed; those checks do not establish an independent build against the +published requirement. See the [implementation record](implementation.md) for +the validation evidence and upstream missing-file error-identity limitation. + ## Optional verification ### Optional shell completion validation diff --git a/docs/roadmap/implementation.md b/docs/roadmap/implementation.md index de6d7bb..8b9f590 100644 --- a/docs/roadmap/implementation.md +++ b/docs/roadmap/implementation.md @@ -1,6 +1,6 @@ # ConfigKit and PromptKit adoption implementation plan -Status: ready for implementation; no stages completed. Prepared 2026-11-21. +Status: implementation complete; coordinated releases pending. Prepared 2026-11-21. Implementation baseline: `320526d3fc92fac7795b4b5e65c623181680452d`. ## Authority and execution @@ -368,7 +368,23 @@ remaining dependency release coordination without claiming publication. ## Stage 7: Validate the result and record release coordination -Status: pending. +Status: complete. + +Evidence: With Go 1.27.4, `GOWORK=off GOTOOLCHAIN=local go test ./...` +passed separately in core and ckconfig; ckconfig `go mod tidy` and `go mod +download` completed without further changes. From the root, the aligned +workspace commands `GOTOOLCHAIN=local go test ./...`, `go test +./integrations/ckconfig/...`, and `go test ./integrations/ckprompt/...` all +passed. For isolated ckprompt validation, copied its module files to a temporary +directory, replaced ckconfig with the local module only in that temporary +modfile, ran tidy and `GOWORK=off GOTOOLCHAIN=local go test -modfile=... ./...`, +and removed the temporary files; both package and example passed. This is not +independent validation against the published ckconfig v0.9.0 requirement. +Reviewed the module and attribution diffs, focused evidence, prose whitespace, +and local links and fragments. No core optional dependencies were introduced. +The remaining release order and dependency validation are recorded in +[future work](future.md#pending-integration-release-coordination). The Stage 4 +record explains the upstream missing-file error-identity limitation. 1. Format changed Go files, finish tidy/download with the workspace disabled where the module can resolve its selected APIs, and inspect all module and