From a22aaa5dfa8e8158a9614f3456b2d734952b6993 Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Thu, 8 Oct 2026 17:08:53 +0000 Subject: [PATCH] Mark ReleaseKit adoption complete --- docs/roadmap/implementation.md | 7 ++++--- docs/roadmap/releasekit.md | 15 ++++++++------- docs/roadmap/remediation.md | 4 ++++ 3 files changed, 16 insertions(+), 10 deletions(-) diff --git a/docs/roadmap/implementation.md b/docs/roadmap/implementation.md index 2f0857d..4a5b3a1 100644 --- a/docs/roadmap/implementation.md +++ b/docs/roadmap/implementation.md @@ -1,8 +1,9 @@ # Implement ReleaseKit adoption -Status: Planned. Implement the stages below in order. The target state and -policy choices are in the [ReleaseKit adoption roadmap](releasekit.md); this -plan is the execution checklist. Use ReleaseKit v0.2.0 at tagged commit +Status: Complete. All seven stages below have been implemented and verified. +The [ReleaseKit adoption roadmap](releasekit.md) owns the target state and +policy choices; this plan records the execution checklist. Use ReleaseKit v0.2.0 +at tagged commit `e030794969fb7787e647a90bbc4eb81bd0610f07` for the initial migration. Do not publish a real ConfigKit version as part of implementation. Keep the current release procedure authoritative until the replacement is working. diff --git a/docs/roadmap/releasekit.md b/docs/roadmap/releasekit.md index c8e4edf..5162fa5 100644 --- a/docs/roadmap/releasekit.md +++ b/docs/roadmap/releasekit.md @@ -1,7 +1,7 @@ # Adopt ReleaseKit for source releases -Status: In progress. The ReleaseKit profile and workflow are in place; isolated -fixture verification remains in the implementation plan. This roadmap uses +Status: Complete. The ReleaseKit profile, workflow, and isolated fixture +verification are in place. This roadmap uses ReleaseKit v0.2.0 (tagged commit `e030794969fb7787e647a90bbc4eb81bd0610f07`) as the initial adoption baseline. The [ReleaseKit release note](https://gitea.maximumdirect.net/eric/ReleaseKit/src/tag/v0.2.0/docs/releases/v0.2.0.md) @@ -104,11 +104,12 @@ release process adds no ConfigKit public API or runtime use of ReleaseKit. - Retired the local release scripts and duplicated publication/gate tests. The development-check test and small profile-wiring test remain; generic ReleaseKit publication behavior is not duplicated in ConfigKit's tests. -- The remaining migration verification exercises the selected profile and - release command against isolated candidates and a temporary Git remote, - including validation failure and successful tag publication. It confirms - the selected Go minimum and one invocation of each selected gate, without - publishing a real ConfigKit version or requiring a separate CI run. +- Completed migration verification exercised the selected profile and release + command against isolated candidates and a temporary Git remote, including + validation failure, successful tag publication, and wrong-endpoint rejection + before validation. It confirmed the selected Go minimum and one invocation + of each selected gate, without publishing a real ConfigKit version or + requiring a separate CI run. Historical tags and release notes remain unchanged. This adoption work does not itself authorize publication of a ConfigKit version. diff --git a/docs/roadmap/remediation.md b/docs/roadmap/remediation.md index 812e7d8..095ecc5 100644 --- a/docs/roadmap/remediation.md +++ b/docs/roadmap/remediation.md @@ -63,6 +63,10 @@ specifically for `go run`. No additional execution mode or test matrix is needed ## 3. Reconcile completed implementation status (P3) +Status: Complete. The roadmap and implementation plan now identify the migration +as complete, and the roadmap describes fixture verification as completed. +Completed documents remain available for retirement during release preparation. + Affected: the adoption roadmap's opening status and final migration-verification bullet, and the implementation plan's opening status.