base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 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

9
README.md
View File

@@ -19,13 +19,12 @@ defines the shared visibility policy.
| Module | Package | Provides |
| --- | --- | --- |
| `go.maximumdirect.net/commandkit` | `commandkit` | Typed commands, bindings, execution reporting and outcomes, help, and version. |
| `gitea.maximumdirect.net/eric/CommandKit/integrations/ckconfig` | `ckconfig` | ConfigKit-backed `config` scopes, including configuration source evidence. |
| `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. |
Importing an integration does not install commands. The integrations currently
use the old core module identity and cannot be composed with the new core path.
The planned matched releases are `go.maximumdirect.net/ckconfig v0.2.0` and
`go.maximumdirect.net/ckprompt v0.2.0`, using core v0.3.0. See the
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
[consumer guide](docs/consumers/guide.md#module-selection) for migration details.
## Examples