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