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

Record release code retention decisions

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-04 02:44:34 +00:00
parent 0fc00039bd
commit 87eb84ccb4
1 changed files with 28 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -97,6 +97,28 @@ The new generated Go recovery commands complement the helper's existing host
handling. Recovery continues to use saved publication evidence and the upstream handling. Recovery continues to use saved publication evidence and the upstream
record formats; CommandKit does not acquire a parallel recovery implementation. record formats; CommandKit does not acquire a parallel recovery implementation.
### Release-code simplification review
The v0.9.0 review identified no additional local release implementation to remove.
The earlier simplification already delegated generic validation, publication,
delivery, and recovery to ReleaseKit. This release improves launcher examples
and generated recovery commands without adding validation options that replace
the remaining CommandKit code.
Retain the shared helper's module/profile selection and execution environment.
Host normalization must happen before Go compiles and runs ReleaseKit. Retain
the legacy publication wrapper to preserve the established maintainer interface.
The upstream multi-module launcher example adds a module map and temporary
metadata preparation for a different tool-selection model; replacing our
root-owned registered-tool helper with it would add machinery.
Retain the focused [wiring tests](../../scripts/release_test.go) for profile
selections, argument forwarding, environment, streams, status, and optional-shell
handling. ReleaseKit owns validation and recovery semantics; CommandKit's tests
continue to cover its own adapter. The adoption work therefore preserves the
release-code structure while updating the dependency and documentation, alongside
the separately planned completion assertion repair.
### Current documentation and history ### Current documentation and history
Current release procedure, project-specific release policy, consumer Go-tool Current release procedure, project-specific release policy, consumer Go-tool
@@ -105,6 +127,10 @@ notice links use the corresponding immutable source revision. Record that the
host-safe launcher request has shipped upstream instead of describing it as host-safe launcher request has shipped upstream instead of describing it as
pending in the earlier feature roadmap. pending in the earlier feature roadmap.
Continue linking to upstream recovery and delivery contracts from the maintainer
procedure. Use ReleaseKit's generated recovery commands and keep local guidance
focused on CommandKit's entry points and selections.
Preserve the baseline and validation history in completed implementation and Preserve the baseline and validation history in completed implementation and
review records. Do not mechanically replace every historical v0.8.0 reference. review records. Do not mechanically replace every historical v0.8.0 reference.
Integration attribution describes its own selected published dependency graph; Integration attribution describes its own selected published dependency graph;
@@ -134,6 +160,8 @@ a new internal alias order merely to make this assertion pass.
- [x] Complete R2 in its own commit (`4d92ee4`), recording verification in - [x] Complete R2 in its own commit (`4d92ee4`), recording verification in
[remediation.md](remediation.md). R1/R2 scheduling is resolved by their delivery [remediation.md](remediation.md). R1/R2 scheduling is resolved by their delivery
before adoption. before adoption.
- [x] Review remaining release code against v0.9.0. Retain the helper, legacy
wrapper, profiles, and focused wiring tests for the reasons above.
- [ ] Repair the completion assertion's ordering assumption and verify the - [ ] Repair the completion assertion's ordering assumption and verify the
correction with focused repetitions. Preserve production ordering behavior correction with focused repetitions. Preserve production ordering behavior
and the remaining routing assertions. and the remaining routing assertions.