diff --git a/docs/consumers/guide.md b/docs/consumers/guide.md
index e237e22..9d5fc76 100644
--- a/docs/consumers/guide.md
+++ b/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.7.0 | — | ConfigKit v1.2.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. The ckprompt v0.7.0 release is pending. |
+| 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:
@@ -31,10 +31,9 @@ go get go.maximumdirect.net/commandkit@v0.6.0
 ```
 
 Select either integration with `go get go.maximumdirect.net/ckconfig@v0.7.0`
-or `go get go.maximumdirect.net/ckprompt@v0.6.0`. The published integrations
-select core v0.6.0. Published ckprompt v0.6.0 selects ckconfig v0.6.0.
-Current ckprompt source selects published ckconfig v0.7.0. Both ckconfig versions
-include `AdaptDiagnostics`.
+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
 and does not compose with ckprompt v0.2.0's earlier ConfigKit dependency.
@@ -48,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
diff --git a/docs/roadmap/future.md b/docs/roadmap/future.md
index ec3d88b..548a604 100644
--- a/docs/roadmap/future.md
+++ b/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,18 +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
-
-ckconfig v0.7.0 is published with its hosted release page. ckprompt now selects
-published ckconfig v0.7.0, ConfigKit v1.2.0, and PromptKit v0.21.0. Its v0.7.0
-release note and dependency checksums are prepared.
-
-Publish ckprompt v0.7.0 with the release procedure's independent candidate
-validation, then update the consumer guide's published-version table and retire
-this completed coordination item. 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