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

7
README.md
View File

@@ -20,11 +20,10 @@ defines the shared visibility policy.
| --- | --- | --- |
| `go.maximumdirect.net/commandkit` | `commandkit` | Typed commands, bindings, execution reporting and outcomes, help, and version. |
| `go.maximumdirect.net/ckconfig` | `ckconfig` | ConfigKit-backed `config` scopes, including configuration source evidence. |
| `gitea.maximumdirect.net/eric/CommandKit/integrations/ckprompt` | `ckprompt` | PromptKit engine configuration/comparison, five catalogs, named inspection, requirements discovery, concrete request validation, and native smoke tests. |
| `go.maximumdirect.net/ckprompt` | `ckprompt` | PromptKit engine configuration/comparison, five catalogs, named inspection, requirements discovery, concrete request validation, and native smoke tests. |
Importing an integration does not install commands. The ckconfig v0.2.0
candidate uses core v0.3.0; ckprompt still uses the old core identity and cannot
be composed with the new core path until its planned v0.2.0 release. See the
Importing an integration does not install commands. The matched ckconfig and
ckprompt v0.2.0 modules use core v0.3.0. See the
[consumer guide](docs/consumers/guide.md#module-selection) for migration details.
## Examples