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

Align ckconfig dependency attribution

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-04 15:07:05 +00:00
parent 5ccdcb91c9
commit 5a79b56e3c
2 changed files with 8 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# ConfigKit v1.1.0 adoption implementation plan
Status: Stages 1–4 complete; Stages 5–6 are not started.
Status: Stages 1–5 complete; Stage 6 is not started.
This plan is for a Luna coding agent implementing the selected
[ConfigKit adoption target](configkit-v1.1.0.md). Follow Stage 1 through Stage 6
@@ -240,6 +240,10 @@ feature, release publication, or external application migration is claimed.
## Stage 5: Align module attribution with the actual selected graph
**Completed.** The workspace-off module graph selects ConfigKit v1.1.0 and
vanity ReleaseKit v0.9.0; old-path ReleaseKit is no longer selected. Attribution
now reflects that graph and the pinned ConfigKit copyright and license source.
1. From ckconfig, inspect `GOWORK=off GOTOOLCHAIN=local go list -m -json all`
after tidy. Compare it with the existing module attribution. ConfigKit's
own tool requirement does not select CommandKit's release tool: retain the