From b1ecd9a0780066d1cce162e43775114dbf0c33d5 Mon Sep 17 00:00:00 2001
From: Eric Rakestraw <eric@rakestraw.us>
Date: Thu, 8 Oct 2026 17:08:35 +0000
Subject: [PATCH] Clarify release command exit statuses

---
 docs/release.md             | 10 +++++-----
 docs/roadmap/remediation.md |  4 ++++
 2 files changed, 9 insertions(+), 5 deletions(-)

diff --git a/docs/release.md b/docs/release.md
index 4fe11e9..ec24646 100644
--- a/docs/release.md
+++ b/docs/release.md
@@ -81,11 +81,11 @@ go list -m gitea.maximumdirect.net/eric/ReleaseKit
 "$releasekit_bin" version
 ```
 
-The module-selected executable is ReleaseKit v0.2.0. Do not use `go run` or
-`go tool` for publication: the native executable preserves its exit status and
-the publication-state diagnostics. ReleaseKit's child Go commands use the
-`go` found on `PATH` with `GOTOOLCHAIN=local`; keep the selected executable
-first on `PATH` through the publication command.
+The module-selected executable is ReleaseKit v0.2.0. Use the built executable
+for publication to preserve its exit status and publication-state diagnostics.
+`go run` maps a nonzero child exit status to 1. ReleaseKit's child Go commands
+use the `go` found on `PATH` with `GOTOOLCHAIN=local`; keep the selected
+executable first on `PATH` through the publication command.
 
 Verify access to the authoritative remote without displaying credentials:
 
diff --git a/docs/roadmap/remediation.md b/docs/roadmap/remediation.md
index 748e659..812e7d8 100644
--- a/docs/roadmap/remediation.md
+++ b/docs/roadmap/remediation.md
@@ -43,6 +43,10 @@ gate or ConfigKit-owned recovery implementation.
 
 ## 2. Remove the unsupported prohibition on `go tool` (P3)
 
+Status: Complete. The runbook retains the built-executable workflow and limits
+its exit-status explanation to `go run`. A fresh `go tool` check preserved
+ReleaseKit's status 2 and publication diagnostics.
+
 Affected: [release procedure](../release.md#1-select-go-and-prepare-the-tool),
 lines 84–86.