Upgrade ReleaseKit and simplify release tooling

docs/roadmap/releasekit.md

@@ -1,7 +1,8 @@
 # ReleaseKit v0.3.0 Upgrade Roadmap
 
 **Last updated:** 2026-10-08
-**Status:** Release policy adopted; library and toolchain upgrade pending.
+**Status:** Implementation complete; first upgraded release and live delivery
+observation pending.
 
 ## Purpose
 
@@ -11,9 +12,9 @@ ReleaseKit; Audita supplies product facts, compatibility decisions, release
 notes, and thin integration wiring. Standardization and less locally owned
 release code remain the reasons for adoption.
 
-This roadmap replaces the completed initial-adoption roadmap. It defines the
-upgrade's target state and required work; a later implementation plan can own
-ordered execution steps.
+This roadmap replaces the completed initial-adoption roadmap. It records the
+upgrade's target state and completed scope. The upgrade was implemented in one
+pass without a separate staged plan.
 
 ## Current Baseline
 
@@ -41,10 +42,11 @@ At Audita commit `17421bc5f352f3fdeb67561b2b60b49979822228`:
 The initial adoption's [review findings](remediation.md) are resolved. They are
 historical context, not additional work for this upgrade.
 
-Since that baseline, Audita has adopted release policy 1.6 and updated its
-provenance, policy attribution, and release runbook. The current Go minimum and
-selected release toolchain remain 1.25.5. The dependency, tool registration,
-bootstrap simplification, and Go 1.26 upgrade described below remain pending.
+Since that baseline, Audita has adopted release policy 1.6, registered and
+upgraded the ReleaseKit tool to v0.3.0, simplified the local wrapper, and
+updated CI and notices. The current Go minimum is 1.26.0; the selected release
+toolchain is 1.26.8. The scope below records the requirements fulfilled by this
+implementation.
 
 ## Selected Upstream Revisions
 
@@ -94,7 +96,7 @@ increases in minor releases, with the increase and required source-consumer
 action explained in the release note. Patch releases preserve the consumer
 minimum. Other compatibility changes remain governed by the adopted policy.
 
-## Work Required
+## Implemented Scope
 
 ### Module Selection and Local Tooling
 
@@ -208,3 +210,22 @@ asynchronously when the first upgraded release is published and address any
 deployment failures through the shared recovery procedure. No significant
 feature decisions remain open; implementation details and final release
 preparation can be resolved within the agreed scope.
+
+## Implementation Completion
+
+Completed with Go 1.26.8. The readonly offline full suite passed. The real local
+wrapper selected ReleaseKit v0.3.0; disposable Go-tool fixtures verified native
+argument boundaries, statuses 0/2/3, and unchanged module files. The CI workflow
+matches the v0.3.0 maintained template with Audita's existing secret mapping.
+The real ReleaseKit builder produced both required Linux artifacts using the
+test identifier v0.0.0, passed its native version smoke check, and emitted
+matching artifact digests in its build receipt. Temporary output was removed.
+The new release-tool dependencies are absent from Audita's runtime dependency
+list. ReleaseKit and Go runtime/vendor attribution identify their selected
+source revisions, with existing applicable license texts reused.
+
+This verification built modified local source and did not claim a clean,
+published release candidate. Release preparation will validate its final
+committed candidate through the ordinary publication command. No tags, source
+pushes, hosted uploads, or LLM calls were made during implementation; live
+artifact delivery remains a separate observation for the next release.