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

Complete vanity migration roadmap

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-04 03:56:33 +00:00
parent 3699c6c5e6
commit 60841227b7
2 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# CommandKit vanity migration and dependency alignment plan
Status: Stages 1–6 complete; Stage 7 is not started.
Status: Stages 1–7 complete.
This plan is for the Luna coding agent implementing the
[feature roadmap](integration-dependency-alignment.md). Follow the stages in
@@ -323,7 +323,17 @@ module declarations and verified independent dependency graphs.
## Stage 7: Audit the completed migration and record evidence
**Status:** not started.
**Completed.** The cumulative migration was reviewed: all three module
declarations, owned Go imports, examples, direct dependencies, and the core
build identity use the selected vanity paths. Physical module directories, tag
prefixes, Go minimums, ReleaseKit selection, scripts, profiles, and production
API shapes remain unchanged. Current guidance and module attribution reflect
the matched dependency graph; historical records remain intact.
The source releases and their independent Go 1.26.8 publication suites are
recorded in Stages 2, 4, and 6. Earlier local-source diagnostics in the feature
roadmap were preparation evidence, not release validation. Hosted delivery is
separate and was not performed as part of this source migration.
1. Review the cumulative diff against the feature roadmap. Confirm all three
module declarations, owned imports, examples, direct dependency keys, and

7
docs/roadmap/integration-dependency-alignment.md
View File

@@ -1,9 +1,8 @@
# Integration dependency alignment and vanity-path migration
Status: proposed release-preparation roadmap. This pass adds documentation only;
dependency changes and publication remain future work. The
[implementation plan](implementation.md) owns execution stages, concrete tasks,
and validation tracking; this roadmap owns the target and selected scope.
Status: the vanity migration and matched source releases are complete. The
[implementation plan](implementation.md) records candidate commits, validation,
and publication outcomes; this roadmap retains the target and review history.
## Purpose and authority