Migrate ckprompt to the vanity module path
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# CommandKit vanity migration and dependency alignment plan
|
||||
|
||||
Status: Stages 1–4 complete; Stages 5–7 are not started.
|
||||
Status: Stages 1–5 complete; Stages 6–7 are not started.
|
||||
|
||||
This plan is for the Luna coding agent implementing the
|
||||
[feature roadmap](integration-dependency-alignment.md). Follow the stages in
|
||||
@@ -253,7 +253,12 @@ identity. Downloading it for ckprompt is the next module's preparation.
|
||||
|
||||
## Stage 5: Migrate ckprompt and prepare its independent candidate
|
||||
|
||||
**Status:** not started.
|
||||
**Completed.** Ckprompt declares `go.maximumdirect.net/ckprompt`, uses the
|
||||
new core and ckconfig imports, and downloaded their v0.3.0 and v0.2.0 releases
|
||||
with authentic sums. ConfigKit v0.8.0 and PromptKit v0.16.0 remain selected;
|
||||
attribution records both distinct ReleaseKit tool modules in the resolved
|
||||
graph. The v0.2.0 note and current consumer guidance are prepared; independent
|
||||
suite validation follows.
|
||||
|
||||
1. Migrate `integrations/ckprompt` to `go.maximumdirect.net/ckprompt`. Update its
|
||||
owned source/tests and composed example to import the new core, ckconfig,
|
||||
|
||||
Reference in New Issue
Block a user