Document the source release workflow

docs/roadmap/initial.md

@@ -9,7 +9,7 @@ Date: 2026-10-07.
 This document defines the selected initial target for the library: packages,
 features, integration contracts, dependencies, and completion evidence. It was
 prepared using [the agreed checklist](initial-plan.md). Implementation steps and
-stage evidence belong in [the completed implementation plan](implementation.md).
+stage evidence belong in the [completed initial implementation record](https://gitea.maximumdirect.net/eric/CommandKit/src/commit/3871d837489b9955998b362587a52b47282dc021/docs/roadmap/implementation.md).
 Detailed specifications below preserve the selected design baseline; they are
 planning history, not a parallel current API or operator reference. The included
 target is implemented; the table below records feature status.
@@ -592,11 +592,11 @@ framework, general dependency injection, concurrent-dispatch guarantees, and
 implementation of additional library families. None is needed to prove the
 initial selected feature target. Application-owned commands remain extensible.
 
-Consumer migrations, release publication, and ReleaseKit integration are separate
-work. Initial implementation should be a usable module with maintained examples;
-source-release tooling is planned under the release policy when preparing a
-releasable candidate. Do not create placeholder publisher commands or a binary
-build matrix.
+Consumer migrations and source publication were kept outside the initial
+library target. Current ReleaseKit adoption is tracked in the
+[adoption roadmap](releasekit.md) and its [implementation plan](implementation.md).
+The initial implementation targeted a usable module with maintained examples;
+it did not create placeholder publisher commands or a binary build matrix.
 
 ## Completion criteria