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

Migrate ckconfig to the vanity module path

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-04 03:52:46 +00:00
parent f0121ad466
commit 92a327db97
36 changed files with 113 additions and 58 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/consumers/guide.md
View File

@@ -12,16 +12,15 @@ installed at the application root, not as group children.
| Import | Use when |
| --- | --- |
| `go.maximumdirect.net/commandkit` | The application needs typed command declarations and common CLI behavior. |
| `gitea.maximumdirect.net/eric/CommandKit/integrations/ckconfig` | The application wants ConfigKit-backed configuration scopes and reports. |
| `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. |
The integration paths in the table are their current source identities; they
use the old core path and do not compose with `go.maximumdirect.net/commandkit`.
For the new core v0.3.0 identity, the planned matched releases are
`go.maximumdirect.net/ckconfig v0.2.0` and `go.maximumdirect.net/ckprompt v0.2.0`.
Update application imports and dependency versions together when those releases
are available. Old and new core paths have distinct Go type identities.
Install the new core with `go get go.maximumdirect.net/commandkit@v0.3.0`.
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 two integrations are independent optional imports. `ckprompt` uses the
public scope and error contracts from `ckconfig`; importing it does not add the

4
docs/development.md
View File

@@ -100,8 +100,8 @@ 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, integrations still import the old core identity and cannot compose
with the migrated root until their own module migrations are complete. After
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
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,9 +6,10 @@ own the optional ConfigKit and PromptKit integrations. The
[architecture policy](../policy/architecture.md) owns normative boundaries;
this page inventories the implemented owners.
The core module now declares `go.maximumdirect.net/commandkit`. The integration
modules retain their old module and core import identities until their planned
matched releases; Go treats those identities as distinct.
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.
## Root `commandkit`

9
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# CommandKit vanity migration and dependency alignment plan
Status: Stages 1–2 complete; Stages 3–7 are not started.
Status: Stages 1–3 complete; Stages 4–7 are not started.
This plan is for the Luna coding agent implementing the
[feature roadmap](integration-dependency-alignment.md). Follow the stages in
@@ -176,7 +176,12 @@ sums is part of Stage 3, not a new completion gate for core publication.
## Stage 3: Migrate ckconfig and prepare its independent candidate
**Status:** not started.
**Completed.** Ckconfig declares `go.maximumdirect.net/ckconfig`, imports the
new core identity, and downloaded `go.maximumdirect.net/commandkit v0.3.0`
with authentic sums. The resolved graph retains ConfigKit v0.8.0 and selects
both the older ReleaseKit v0.4.1 and vanity ReleaseKit v0.9.0 tool modules;
module-local attribution and current guidance reflect those selections. The
v0.2.0 release note is prepared; independent suite validation follows.
1. In `integrations/ckconfig`, migrate the module declaration to
`go.maximumdirect.net/ckconfig`. Update all owned imports, tests, and the