Complete vanity migration roadmap
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user