Add source publication command and runbook

docs/policy/release.md

@@ -18,10 +18,8 @@ policy and link to it rather than introduce additional release requirements.
 
 This policy governs releases of ReleaseKit itself. Consumer release capabilities
 are designed in the [product roadmap](../roadmap/releasekit.md) and acquire exact
-public contracts when implemented. ReleaseKit currently has no publication
-command. Create the maintainer runbook alongside the first working command;
-the [policy adoption roadmap](../roadmap/policy.md#4-define-releasekits-own-release-path)
-owns that pending work.
+public contracts when implemented. ReleaseKit's source publication command and
+maintainer runbook are implemented; no ReleaseKit release has been published.
 
 ## Release Model And Completion
 
@@ -33,8 +31,8 @@ The procedure must name the authoritative publication remote.
 A successful push of the intended annotated tag, with its source commit already
 published on authoritative `main`, completes the release. The remote branch must
 identify the validated candidate before the command publishes only the exact
-intended tag object. The runbook will identify the authoritative endpoint and
-command when publication is implemented.
+intended tag object. The [maintainer runbook](../release.md) identifies the
+authoritative endpoint and command.
 
 Release commands must finish at successful publication. They must not wait for
 or poll CI, require successful CI status, inspect downloadable artifacts, or