Add source publication command and runbook

docs/roadmap/implementation.md

@@ -649,7 +649,7 @@ local tag before push prevent publication.
 
 ## Stage 9: Expose publication and document ReleaseKit bootstrap
 
-Status: Pending. Depends on Stage 8.
+Status: Complete. Depends on Stage 8.
 
 1. Wire the complete public publisher into `releasekit publish`, with selected
    progress output, final result, exit classification, and signal cancellation.
@@ -672,6 +672,15 @@ committed profile and returns the expected exit/output behavior. Runbook command
 are exercised using a temporary repository configured like ReleaseKit. This
 stage prepares self-publication and does not publish a real ReleaseKit release.
 
+Evidence: `publish` runs the public publisher with the CLI signal context,
+selected progress output, final commit and tag-object output, and separate exit
+status for unresolved outcomes. A temporary committed profile runs the offline
+test command and publishes to a local bare remote. ReleaseKit's root profile,
+entry script, CLI and configuration guides, development guide, and maintainer
+runbook describe source-only publication and exact-object recovery. The
+runbook's dependency preparation is separate from offline validation. No real
+ReleaseKit release was published.
+
 ## Stage 10: Build selected targets with shared version injection
 
 Status: Pending. Depends on Stage 9.