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

Record ReleaseKit adoption completion

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-08 16:52:04 +00:00
parent 8c5fea0aae
commit c0c03285f7
2 changed files with 48 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# ReleaseKit adoption implementation plan
Status: ready for implementation; Stages 1–6 pending.
Status: complete; Stages 1–6 complete.
Date: 2026-10-08.
@@ -462,7 +462,7 @@ work. Commit the stage.
## Stage 6: audit and record adoption completion
**Status:** pending. **Prerequisite:** Stages 1–5.
**Status:** complete. **Prerequisite:** Stages 1–5.
**Files:** this plan and `releasekit.md` for completion evidence; focused fixes
only if the audit discovers a real incomplete deliverable.
@@ -494,5 +494,39 @@ only if the audit discovers a real incomplete deliverable.
result, the reviewed deliverable and boundary checks, and the final clean Git
status. Correct any missing result before declaring adoption complete.
Observed 2026-10-08: the final offline suite passed:
```sh
GOWORK=off GOTOOLCHAIN=local GOPROXY=off GONOPROXY=none GOSUMDB=off go test -mod=readonly -count=1 ./...
```
It passed for the root library, internal Cobra adapter, scripts, and both
examples; the opt-in publication test remained skipped in the default suite.
The opt-in disposable-repository exercise passed earlier and is unchanged by
subsequent edits. These module and package checks passed:
```sh
GOWORK=off GOTOOLCHAIN=local go list -m gitea.maximumdirect.net/eric/ReleaseKit
GOWORK=off GOTOOLCHAIN=local go mod tidy -diff
GOWORK=off GOTOOLCHAIN=local go mod verify
GOWORK=off GOTOOLCHAIN=local go list -deps -test ./...
GOWORK=off GOTOOLCHAIN=local go list -f '{{.ImportPath}} GoFiles={{.GoFiles}} TestGoFiles={{.TestGoFiles}} XTestGoFiles={{.XTestGoFiles}}' ./scripts
```
The module selection is v0.2.0; tidy reports no changes and all modules verify.
The readonly CLI build and version check passed without changing module
metadata. The profile has exactly the selected three fields;
`git ls-tree HEAD scripts/release` reports mode 100755, and
`git check-ignore -v .releasekit/bin/releasekit` matches the root ignore rule.
No ReleaseKit Go package appears in the dependency listing; `scripts` reports
`GoFiles=[]` and only the two external test files. Those are the only Go files
added since the completed initial implementation. No source was copied, no
runtime dependency attribution changed, and no exported production API changed.
The runbook, navigation, historical references, release policy provenance, and
README licensing footer were reviewed. All 243 local links across 13 documents
passed; staged Markdown whitespace checks passed. No platform skips occurred.
Stage commits: `ada2021`, `012af5e`, `f9ec143`, `d3f0891`, and `8c5fea0`. The final
workspace was clean after the completion commit.
**Completion:** all six stages and all roadmap coverage IDs have authoritative
implementation evidence. Source publication itself remains unperformed.

14
docs/roadmap/releasekit.md
View File

@@ -1,6 +1,6 @@
# ReleaseKit adoption roadmap
Status: adoption selected; implementation not started.
Status: adoption complete; RK-01–RK-06 implemented and reviewed.
Date: 2026-10-08.
@@ -10,7 +10,9 @@ This roadmap defines the target state for adopting ReleaseKit as CommandKit's
maintainer release tooling and the gaps from its reviewed baseline. The
[implementation plan](implementation.md) owns ordered execution steps,
stage-specific checks, and implementation evidence. This document does not
authorize publication or claim that release tooling already exists.
authorize publication. The completed implementation and its evidence are
recorded in the
[final adoption audit](implementation.md#stage-6-audit-and-record-adoption-completion).
The [release policy](../policy/release.md),
[architecture policy](../policy/architecture.md), and
@@ -216,6 +218,14 @@ select a fresh version, prepare its note and final candidate, and follow the
runbook with publication authorization. Do not create a placeholder release
note or publish a tag merely to complete tooling adoption.
## Adoption completion
RK-01 through RK-06 were implemented and reviewed on 2026-10-08. The
[implementation plan's final audit](implementation.md#stage-6-audit-and-record-adoption-completion)
records validation results and the local commit for each completed stage. No
CommandKit release note or tag was created; preparing and publishing the first
real release remains separate authorized work under the runbook.
## Deferred capabilities
Hosted Gitea release-page delivery is deferred. If selected later, reuse the