base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Migrate ckprompt to the vanity module path

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-04 03:55:17 +00:00
parent 4a8f73f289
commit 3f1ed2f107
35 changed files with 137 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/consumers/guide.md
View File

@@ -13,14 +13,14 @@ installed at the application root, not as group children.
| --- | --- |
| `go.maximumdirect.net/commandkit` | The application needs typed command declarations and common CLI behavior. |
| `go.maximumdirect.net/ckconfig` | The application wants ConfigKit-backed configuration scopes and reports. |
| `gitea.maximumdirect.net/eric/CommandKit/integrations/ckprompt` | The application wants PromptKit engine configuration/comparison, five catalogs, named inspection, requirements discovery, request validation, or native smoke testing. |
| `go.maximumdirect.net/ckprompt` | The application wants PromptKit engine configuration/comparison, five catalogs, named inspection, requirements discovery, request validation, or native smoke testing. |
The ckconfig v0.2.0 candidate uses core v0.3.0. The ckprompt source still uses
the old core and ckconfig identities; its planned matched v0.2.0 release will
use the new paths. Update application imports and dependency versions together.
Old and new core paths have distinct Go type identities. Install core with
`go get go.maximumdirect.net/commandkit@v0.3.0` and the matching integration
with `go get go.maximumdirect.net/ckconfig@v0.2.0` once it is published.
The matched releases are core v0.3.0, ckconfig v0.2.0, and ckprompt v0.2.0.
Update application imports and dependency versions together; old and new core
paths have distinct Go type identities. Install core with
`go get go.maximumdirect.net/commandkit@v0.3.0` and either integration with
`go get go.maximumdirect.net/ckconfig@v0.2.0` or
`go get go.maximumdirect.net/ckprompt@v0.2.0`.
The two integrations are independent optional imports. `ckprompt` uses the
public scope and error contracts from `ckconfig`; importing it does not add the

5
docs/development.md
View File

@@ -99,10 +99,7 @@ Sibling-checkout references in retired planning records are historical review
evidence, not build dependencies. Implemented contracts belong in CommandKit
under their canonical owners.
The root module does not traverse nested modules. During the vanity-path
migration, ckprompt still imports the old core and ckconfig identities and
cannot compose with the migrated modules until its own migration is complete. After
the matched migrations, during development use a
The root module does not traverse nested modules. During development, use a
local workspace for all three modules; it is ignored and must not be committed.
If a local `go.work` already exists, preserve it and add these module directories:

7
docs/internal/overview.md
View File

@@ -6,10 +6,9 @@ own the optional ConfigKit and PromptKit integrations. The
[architecture policy](../policy/architecture.md) owns normative boundaries;
this page inventories the implemented owners.
The core and ckconfig modules declare `go.maximumdirect.net/commandkit` and
`go.maximumdirect.net/ckconfig`. Ckprompt retains the old module and import
identities until its planned matched release; Go treats those identities as
distinct.
The core, ckconfig, and ckprompt modules declare
`go.maximumdirect.net/commandkit`, `go.maximumdirect.net/ckconfig`, and
`go.maximumdirect.net/ckprompt`, respectively.
## Root `commandkit`

9
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# CommandKit vanity migration and dependency alignment plan
Status: Stages 1–4 complete; Stages 5–7 are not started.
Status: Stages 1–5 complete; Stages 6–7 are not started.
This plan is for the Luna coding agent implementing the
[feature roadmap](integration-dependency-alignment.md). Follow the stages in
@@ -253,7 +253,12 @@ identity. Downloading it for ckprompt is the next module's preparation.
## Stage 5: Migrate ckprompt and prepare its independent candidate
**Status:** not started.
**Completed.** Ckprompt declares `go.maximumdirect.net/ckprompt`, uses the
new core and ckconfig imports, and downloaded their v0.3.0 and v0.2.0 releases
with authentic sums. ConfigKit v0.8.0 and PromptKit v0.16.0 remain selected;
attribution records both distinct ReleaseKit tool modules in the resolved
graph. The v0.2.0 note and current consumer guidance are prepared; independent
suite validation follows.
1. Migrate `integrations/ckprompt` to `go.maximumdirect.net/ckprompt`. Update its
owned source/tests and composed example to import the new core, ckconfig,