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

Migrate core to the vanity module path

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-04 03:49:38 +00:00
parent 881dae27c4
commit e256eb1cc0
48 changed files with 120 additions and 87 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@@ -18,14 +18,15 @@ defines the shared visibility policy.
| Module | Package | Provides |
| --- | --- | --- |
| `gitea.maximumdirect.net/eric/CommandKit` | `commandkit` | Typed commands, bindings, execution reporting and outcomes, help, and version. |
| `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. |
| `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. Pass its declaration to
`commandkit.New` or `App.Register` to install it. The integrations depend on the
core and their selected upstream libraries; the core does not depend on either
integration.
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
[consumer guide](docs/consumers/guide.md#module-selection) for migration details.
## Examples