Retire completed roadmaps and preserve adoption work

docs/roadmap/releasekit.md

@@ -1,16 +1,16 @@
 # ReleaseKit: shared release process
 
-This proposal records a review of PromptKit, ConfigKit, Audita, Notarius,
-Narratio, and Scriptorium on 2026-09-29. The initial library, CLI, build and
-delivery paths, and prepared Woodpecker examples are implemented; the
-[implementation plan](implementation.md) records the completed boundary and
-evidence. The public facade architecture is accepted in
-[ADR 0001](../adr/0001-public-facade.md) and implemented for runtime version,
-candidate validation, source publication, selected-target builds, and tagged-
-source delivery.
-The [implementation plan](implementation.md) owns ordered stages, execution
-instructions, acceptance checks, and implementation status. Consumer migration
-and measurement of local infrastructure reduction remain future adoption work.
+Status: Initial implementation, policy adoption, and architecture remediation
+are complete. Consumer adoption, publication, and live integration work remain.
+
+This roadmap records the shared release-process opportunity identified in
+PromptKit, ConfigKit, Audita, Notarius, Narratio, and Scriptorium on 2026-09-29,
+and the remaining adoption goals. The [internal package inventory](../internal/overview.md)
+records implemented capability owners and behavioral evidence. The
+[architecture policy](../policy/architecture.md) and
+[ADR 0001](../adr/0001-public-facade.md) own the facade boundaries and rationale.
+The completed implementation, policy adoption, and remediation plans are
+preserved in Git history.
 
 ## Opportunity
 
@@ -96,8 +96,8 @@ and GoDoc own exact public API contracts; additional public packages and
 extension interfaces require a deliberate decision grounded in durable consumer
 needs.
 
-Compiled-export and dependency checks will protect facade ownership.
-External-package behavioral tests will protect error identity, value ownership,
+Compiled-export and dependency checks protect facade ownership.
+External-package behavioral tests protect error identity, value ownership,
 callback lifetime, and observable outcomes across forwarding and conversions.
 
 ## Shared tool boundary
@@ -202,10 +202,24 @@ Existing published tags, notes, pages, and assets retain their historical conten
 
 Consumer policy and procedure changes should describe the deliberately adopted
 standard and its compatibility impact. Adoption should demonstrate reduced local
-infrastructure and one coherent release model. The implementation plan owns the
-complete initial ReleaseKit implementation and its development evidence.
-Architecture review follows that implementation; broader testing and consumer
-migration steps will be chosen afterward.
+infrastructure and one coherent release model.
+
+## Remaining work
+
+- Prepare and publish the first ReleaseKit source release under the
+  [maintainer procedure](../release.md), then deliver its hosted note page.
+- Choose the broader consumer integration test plan and migration sequence.
+  Evaluate API clarity, product-specific checks, and the infrastructure removed
+  from each consuming repository.
+- Select immutable ReleaseKit deployment pins and Go image digests for consumer
+  workflows. Provision delivery credentials and activate the prepared Woodpecker
+  workflows as part of deployment.
+- Verify live Gitea delivery and Woodpecker execution. Existing verification uses
+  local Git and HTTP fixtures; no live deployment has been verified.
+- Keep ReleaseKit executable binary distribution deferred until deliverables
+  are deliberately selected. Selecting binaries would require delivery
+  declarations, target checks, automation responsibilities, and corresponding
+  release policy and procedure updates.
 
 ## Reviewed implementations