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

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: