Record ckconfig release completion

docs/consumers/guide.md

@@ -16,7 +16,7 @@ installed at the application root, not as group children.
 | `go.maximumdirect.net/ckprompt` | The application wants PromptKit engine configuration/comparison, five catalogs, named inspection, requirements discovery, request validation, or native smoke testing. |
 
 The published matched releases are core v0.3.0, ckconfig v0.2.0, and ckprompt v0.2.0.
-The local ckconfig v0.3.0 candidate uses ConfigKit v1.1.0 and does not compose
+The published ckconfig v0.3.0 uses ConfigKit v1.1.0 and does not compose
 with ckprompt v0.2.0, which retains ckconfig v0.2.0 and ConfigKit v0.8.0.
 Update application imports and dependency versions together; old and new core
 paths have distinct Go type identities. Install core with
@@ -32,8 +32,8 @@ core-only, ConfigKit-only, and composed applications.
 
 ## Go compatibility
 
-Core and ckprompt declare a consumer minimum of Go 1.26.0; the ckconfig
-v0.3.0 candidate requires Go 1.27.0. The root module also
+Core and ckprompt declare a consumer minimum of Go 1.26.0; ckconfig
+v0.3.0 requires Go 1.27.0. The root module also
 selects ReleaseKit v0.9.0 (`go.maximumdirect.net/releasekit`) as a Go tool, which
 makes that tool's module graph part of the root consumer module requirements
 even though production packages do not import ReleaseKit. The
@@ -358,7 +358,7 @@ and [PromptKit v0.16.0 consumer guidance](https://gitea.maximumdirect.net/eric/p
 
 ## ConfigKit v1.1 migration
 
-The ckconfig v0.3.0 candidate uses `go.maximumdirect.net/configkit v1.1.0`
+Ckconfig v0.3.0 uses `go.maximumdirect.net/configkit v1.1.0`
 and Go 1.27.0. Consumers must migrate ConfigKit imports and values passed to
 ckconfig: the old and new package paths have distinct type identities. Source
 reports rename `destination_unresolved` to `destination_is_fallback` and