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

Complete ReleaseKit adoption roadmap

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-04 03:04:15 +00:00
parent 2cde616ce5
commit 289a171e97
2 changed files with 14 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# ReleaseKit v0.9.0 implementation plan # ReleaseKit v0.9.0 implementation plan
Status: Stages 1–5 complete; Stage 6 is not started. Status: Stages 1–6 complete.
Implement these stages in integer order during one end-to-end sprint. The target Implement these stages in integer order during one end-to-end sprint. The target
audience is the Luna coding agent. Intermediate stages may temporarily leave audience is the Luna coding agent. Intermediate stages may temporarily leave
@@ -98,7 +98,8 @@ under the local commit policy.
**Completed.** Go 1.26.8 selected and downloaded v0.9.0; tidy changed only **Completed.** Go 1.26.8 selected and downloaded v0.9.0; tidy changed only
the tool requirement and its two checksum entries. The helper reported the tool requirement and its two checksum entries. The helper reported
`releasekit v0.9.0` under foreign target and workspace settings without changing `releasekit v0.9.0` under foreign target and workspace settings without changing
module metadata. Documentation alignment and snapshot checks follow. module metadata. In accordance with the requested per-stage commits, metadata
was committed separately before documentation alignment and snapshot checks.
From the repository root, put Go 1.26.8 on `PATH` using the existing From the repository root, put Go 1.26.8 on `PATH` using the existing
[toolchain setup](../release.md#release-toolchain). Use normal dependency [toolchain setup](../release.md#release-toolchain). Use normal dependency
@@ -302,7 +303,11 @@ accurately. These results complement Stage 4; they do not authorize a release.
## Stage 6: Review completion evidence and finish the sprint ## Stage 6: Review completion evidence and finish the sprint
**Status:** not started. **Completed.** The complete diff was reviewed against the feature roadmap.
The only Go source change is the completion assertion; the scripts, profiles,
integration modules, production APIs, and R1/R2 fixes remain unchanged. The
root and workspace-backed integration checks cover the Stage 4 snapshot;
subsequent changes only record completion and update roadmap status.
1. Review the complete diff against the feature roadmap. Confirm the only code 1. Review the complete diff against the feature roadmap. Confirm the only code
change is the order-independent test assertion; metadata selects v0.9.0; change is the order-independent test assertion; metadata selects v0.9.0;

13
docs/roadmap/releasekit-v0.9.0.md
View File

@@ -1,10 +1,9 @@
# ReleaseKit v0.9.0 adoption # ReleaseKit v0.9.0 adoption
Status: R1 and R2 remediation is complete in separate commits. ReleaseKit v0.9.0 Status: R1 and R2 remediation, ReleaseKit v0.9.0 adoption, and the completion
adoption and the completion assertion repair remain planned; the root tool still assertion repair are complete. The [implementation plan](implementation.md)
selects v0.8.0. The [implementation plan](implementation.md) owns stage order, records stage order, tasks, and validation evidence. This document owns the
tasks, and validation tracking. This document owns the target and selected target and selected choices; it does not authorize source or hosted publication.
choices; it does not authorize source or hosted publication.
## Purpose and authority ## Purpose and authority
@@ -150,8 +149,8 @@ The completion assertion compares the expected alias source/target records
without depending on their iteration order, while detecting missing, unexpected, without depending on their iteration order, while detecting missing, unexpected,
or duplicate records. Its routing and visible-completion assertions remain. or duplicate records. Its routing and visible-completion assertions remain.
Production alias ordering and public contracts are unchanged. This correction Production alias ordering and public contracts are unchanged. This correction
remains part of the maintenance scope, separate from completed R1/R2 remediation; was completed as part of the maintenance scope, separate from R1/R2 remediation;
the implementation plan owns the test changes and focused verification. the implementation plan records the test changes and focused verification.
Ordinary releases retain their single selected-module publication suite and Ordinary releases retain their single selected-module publication suite and
separate hosted-delivery outcome. One-time upgrade diagnostics are maintenance separate hosted-delivery outcome. One-time upgrade diagnostics are maintenance