Record completed integration releases

docs/consumers/guide.md

@@ -14,14 +14,14 @@ applications.
 | `go.maximumdirect.net/ckconfig` | You want operators to view, validate, explain, and compare ConfigKit configuration. |
 | `go.maximumdirect.net/ckprompt` | You want operators to inspect PromptKit resources, check and preview requests, or run smoke tests. |
 
-Current integration source selects ConfigKit v1.2.0 and PromptKit v0.21.0.
+The v0.7.0 integrations select ConfigKit v1.2.0, and ckprompt selects PromptKit
+v0.21.0.
 
 | Selection | Core | ckconfig | ckprompt | Upstream libraries and status |
 | --- | --- | --- | --- | --- |
 | Published core | v0.6.0 | — | — | Usable independently. |
-| ConfigKit integration | v0.6.0 | v0.6.0 | — | ConfigKit v1.1.0. |
-| PromptKit integration | v0.6.0 | v0.6.0 | v0.6.0 | ConfigKit v1.1.0 and PromptKit v0.20.0. |
-| Current integration source | v0.6.0 | Local | Local | ConfigKit v1.2.0 and PromptKit v0.21.0. Coordinated releases are pending. |
+| ConfigKit integration | v0.6.0 | v0.7.0 | — | ConfigKit v1.2.0. |
+| PromptKit integration | v0.6.0 | v0.7.0 | v0.7.0 | ConfigKit v1.2.0 and PromptKit v0.21.0. |
 | Earlier matched integration set | v0.3.0 | v0.2.0 | v0.2.0 | ConfigKit v0.8.0 and PromptKit v0.16.0, using their earlier import paths. |
 
 Install the published core with:
@@ -30,9 +30,9 @@ Install the published core with:
 go get go.maximumdirect.net/commandkit@v0.6.0
 ```
 
-Select either integration with `go get go.maximumdirect.net/ckconfig@v0.6.0`
-or `go get go.maximumdirect.net/ckprompt@v0.6.0`. The published integrations
-select core v0.6.0, and ckprompt selects ckconfig v0.6.0, which includes
+Select either integration with `go get go.maximumdirect.net/ckconfig@v0.7.0`
+or `go get go.maximumdirect.net/ckprompt@v0.7.0`. The published integrations
+select core v0.6.0. ckprompt v0.7.0 selects ckconfig v0.7.0, which includes
 `AdaptDiagnostics`.
 They build independently against these released dependencies; a local workspace
 is optional for development. Published ckconfig v0.3.0 also uses ConfigKit v1.1.0
@@ -47,8 +47,6 @@ PromptKit v0.21.0 exposes main-relative companion imports through its existing
 configuration-source API. Applications select those inputs when constructing
 the engine supplied to ckprompt's loader callback. [PromptKit companion import guidance](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/171fb11f4e967a1da3af57843c6467954b14ba09/docs/consumers/pkg-promptkit.md#load-companion-prompts-relative-to-the-main-configuration).
 
-Coordinated integration releases are tracked in the future work record. [Pending integration work](../roadmap/future.md#pending-integration-work).
-
 Importing a module does not install its commands. Pass commands to
 `commandkit.New` or `App.Register` explicitly. ckprompt depends on ckconfig's
 public APIs, but you can install its `promptkit` commands without installing

docs/development.md

@@ -119,7 +119,7 @@ If a workspace already exists, ensure it includes these three modules. Preserve
 the ignored `go.work` and `go.work.sum`; do not commit them. Use
 `GOWORK=off GOTOOLCHAIN=local` for dependency preparation
 and independent module suites. Both integrations select released core v0.6.0;
-ckprompt also selects released ckconfig v0.6.0. Their declared dependencies
+ckprompt also selects released ckconfig v0.7.0. Their declared dependencies
 support independent builds. The aligned workspace exercises the local sources
 together.
 Run `GOWORK=off GOTOOLCHAIN=local go test ./...` separately from each module

docs/roadmap/future.md

@@ -1,7 +1,6 @@
 # Future work
 
-Status: pending integration releases, optional shell
-validation, and future capability proposals.
+Status: optional shell validation and future capability proposals.
 No delivery dates are selected here.
 
 ## Purpose and authority
@@ -31,19 +30,6 @@ 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 work
-
-ConfigKit v1.2.0 is adopted in both integration source modules, and ckprompt
-selects PromptKit v0.21.0. Release notes for ckconfig v0.7.0 and ckprompt v0.7.0
-are prepared in their respective release directories.
-
-Publish ckconfig v0.7.0 first. Then update ckprompt's declared ckconfig dependency
-from v0.6.0 to the published v0.7.0, refresh its checksums, and validate its
-independent candidate before publishing ckprompt v0.7.0. Update the consumer
-guide's published-version table as each release becomes available. The release
-procedure owns version availability checks, final validation, and publication.
-[Release procedure](../release.md#scope-and-release-order).
-
 ## Optional verification
 
 ### Optional shell completion validation

integrations/ckprompt/go.mod

@@ -3,7 +3,7 @@ module go.maximumdirect.net/ckprompt
 go 1.27.0
 
 require (
-	go.maximumdirect.net/ckconfig v0.6.0
+	go.maximumdirect.net/ckconfig v0.7.0
 	go.maximumdirect.net/commandkit v0.6.0
 	go.maximumdirect.net/configkit v1.2.0
 	go.maximumdirect.net/promptkit v0.21.0

integrations/ckprompt/go.sum

@@ -16,6 +16,8 @@ go.maximumdirect.net/ckconfig v0.5.0 h1:5YCPFySTFIFR+gzd0FjqkTPEVB7zkGa8kOEYh4aB
 go.maximumdirect.net/ckconfig v0.5.0/go.mod h1:BONXRSQlHdJvYVw9mN6lMV4G4ldlV/5fRO9EEApA99s=
 go.maximumdirect.net/ckconfig v0.6.0 h1:N7MJKJiXhv+tT4HA7dnINUxC0Uq8hzYmBTFjrpvkbvQ=
 go.maximumdirect.net/ckconfig v0.6.0/go.mod h1:69HOkR2Jbq7rJz3jlFAL6Oo5qorEiVrxQVLXoqav98s=
+go.maximumdirect.net/ckconfig v0.7.0 h1:jRmKqgReLYIRHJl7Pr4+TlucifFirGANcsoC+5WrW7A=
+go.maximumdirect.net/ckconfig v0.7.0/go.mod h1:ZBKCi0Z72+C6kQV+1HJHXFGcZTc11FYyaH1pQDSZFl8=
 go.maximumdirect.net/commandkit v0.4.0 h1:bWqflDWDn98FUCgh+0e+w6LGmvWIkaeJK519H7PjD2Y=
 go.maximumdirect.net/commandkit v0.4.0/go.mod h1:ZS98DewKNVBygKVDoh5MFD09CnPlP37dS9pVsID5Eoc=
 go.maximumdirect.net/commandkit v0.5.0 h1:Ln+bCp+FwCg4tZD3NaMKQXUDB3mPusgwsnRZmb0+3cM=