Centralize Go validation and build environments

docs/consumers/build.md

@@ -50,13 +50,18 @@ resolved from the repository. Selected artifact filenames are regenerated. Other
 directory are left in place. A failed later build or native version check returns the binaries already
 generated in `BuildResult.Artifacts`.
 
-Builds use the prepared local Go toolchain, readonly module mode, disabled
-module network access, `CGO_ENABLED=0`, `-trimpath`, and `-buildvcs=false`. Each
-selected target is compiled explicitly. ReleaseKit then runs the `version`
-command on a native binary and requires `<binary> <version>` followed by a
-newline. If no selected target matches the Go host, it builds a temporary
-native binary for this check and removes it afterward. Cross-compilation does
-not promise that a binary runs on another platform.
+Builds use the available compatible Go toolchain selected locally; ReleaseKit
+does not download a different toolchain automatically. It disables workspace
+discovery and module network access, uses readonly module mode, sets
+`CGO_ENABLED=0`, and passes `-trimpath` and `-buildvcs=false`. Effective cache,
+module-cache, temporary-directory, and tool settings are retained, including
+values from Go's persistent environment file. Ambient experiment and CPU
+feature settings are cleared so the selected toolchain uses its baseline for
+each target. Each selected target is compiled explicitly. ReleaseKit then runs
+the `version` command on a native binary and requires `<binary> <version>`
+followed by a newline. If no selected target matches the Go host, it builds a
+temporary native binary for this check and removes it afterward.
+Cross-compilation does not promise that a binary runs on another platform.
 
 An empty target list records the source commit and returns without invoking Go,
 creating the output directory, or running a version check. It does not require a