Complete implementation handoff documentation

docs/roadmap/releasekit.md

@@ -1,14 +1,16 @@
 # ReleaseKit: shared release process
 
-This is a proposal based on a review of PromptKit, ConfigKit, Audita, Notarius,
-Narratio, and Scriptorium on 2026-09-29. The implementation plan records the
-current implemented boundary; the internal Gitea page and asset-delivery
-client is implemented, while facade/CLI integration and broader integrations
-remain planned. The public facade architecture is
-accepted in [ADR 0001](../adr/0001-public-facade.md) and is implemented for
-runtime version, candidate validation, and source publication.
+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 progress toward this target state.
+instructions, acceptance checks, and implementation status. Consumer migration
+and measurement of local infrastructure reduction remain future adoption work.
 
 ## Opportunity
 
@@ -29,7 +31,7 @@ of publication scripts, 150–250 lines of checks and builders, and 400–500 li
 of repeated publication tests. ReleaseKit would gain its own implementation and
 tests, so this is a reduction in local code, not a net line-count saving.
 
-## Proposed publication standard
+## Selected publication standard
 
 1. Prepare and commit a version-matched note at `docs/releases/<version>.md`.
 2. Publish the candidate commit to authoritative `main` before invoking the