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

Complete the performance audit and update documentation

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-09 01:54:31 +00:00
parent 62b4a48e4f
commit 18ff0d6639
8 changed files with 157 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
docs/roadmap/releasekit.md
View File

@@ -8,11 +8,10 @@ Date: 2026-10-08.
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. The completed implementation and its evidence are
recorded in the
[final adoption audit](implementation.md#stage-6-audit-and-record-adoption-completion).
[maintainer release procedure](../release.md) owns current operations. This
document does not authorize publication. The completed implementation and its
evidence are recorded in the
[historical adoption record](https://gitea.maximumdirect.net/eric/CommandKit/src/commit/c0c03285f7beac3e96f1708b655c1eb2add35e79/docs/roadmap/implementation.md).
The [release policy](../policy/release.md),
[architecture policy](../policy/architecture.md), and
@@ -157,8 +156,9 @@ manual approval gate, or custom note checker.
The implemented release policy identifies the selected integration while
preserving substantive rules and provenance. README and developer navigation
point to the implemented runbook and describe release-tooling status accurately.
Current procedures belong in the runbook; this roadmap owns the target, and the
implementation plan owns execution and evidence.
Current procedures belong in the runbook; this roadmap owns the target and
adoption status. The completed execution evidence remains in the historical
adoption record.
### Licensing and incorporated material
@@ -176,7 +176,8 @@ integration, with links to upstream guidance where practical.
## Adoption coverage
These IDs identify the target capabilities and remaining baseline gaps.
Ordered assignments and checks belong in the implementation plan.
The completed assignments and checks are preserved in the historical adoption
record linked above.
| ID | Capability gap | Target result |
| --- | --- | --- |
@@ -185,7 +186,7 @@ Ordered assignments and checks belong in the implementation plan.
| RK-03 | Publication launcher | One repository publication command builds the module-selected CLI without changing candidate metadata and preserves its outcomes; bootstrap output is ignored. |
| RK-04 | Runbook and navigation | Maintainers have one canonical procedure for preparation, publication, and recovery; current documents describe available tooling accurately. |
| RK-05 | Licensing treatment | Incorporated material receives policy-conforming attribution and texts without blanket tooling requirements. |
| RK-06 | Integration confidence | The launcher/profile work together and adoption respects existing library boundaries; completion evidence and remaining release preparation are recorded in the implementation plan. |
| RK-06 | Integration confidence | The launcher/profile work together and adoption respects existing library boundaries; completion evidence and remaining release preparation are recorded in the completed adoption record. |
## Acceptance criteria
@@ -206,8 +207,8 @@ Successful adoption has focused evidence for these integration results:
affected documentation, notices, paths, and intended release links agree with
the implemented integration.
The implementation plan selects proportionate checks and reuses existing
evidence where sufficient. Adoption checks are not automatically permanent
The completed adoption record documents proportionate checks and reused
evidence. Adoption checks are not automatically permanent
release gates. Diagnostic `check` remains optional; the actual release publisher
validates its final candidate once.
@@ -221,7 +222,7 @@ 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)
[historical adoption record](https://gitea.maximumdirect.net/eric/CommandKit/src/commit/c0c03285f7beac3e96f1708b655c1eb2add35e79/docs/roadmap/implementation.md)
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.