From 72d3ebb501da5c239d9ca89d11dcaac8aff94645 Mon Sep 17 00:00:00 2001
From: rcourtman <8825017+rcourtman@users.noreply.github.com>
Date: Mon, 31 Aug 2026 22:11:38 +0100
Subject: [PATCH] Keep hot-dev build temp on the configured Go temp volume

The Go linker's dsymutil step writes DWARF output under TMPDIR rather
than GOTMPDIR, so backend builds failed with ENOSPC on the
space-constrained boot volume even with GOCACHE and GOTMPDIR already on
the Development SSD. hot-dev now exports TMPDIR from the machine's
configured GOTMPDIR when one exists, keeping every build temp file on
the same volume as the rest of the build state.
---
 scripts/hot-dev.sh | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/scripts/hot-dev.sh b/scripts/hot-dev.sh
index c5d571a98..06d72bc58 100755
--- a/scripts/hot-dev.sh
+++ b/scripts/hot-dev.sh
@@ -59,6 +59,17 @@ source "${SCRIPT_DIR}/lib/hot-dev-runtime.sh"
 
 HOT_DEV_LAB_MODE_FILE="${HOT_DEV_LAB_MODE_FILE:-${ROOT_DIR}/tmp/hot-dev.lab-agents-mode}"
 
+# Keep build temp files off the boot volume. The Go linker's dsymutil step
+# writes its DWARF output under TMPDIR (not GOTMPDIR), so on a machine with a
+# space-constrained system disk the backend build fails with ENOSPC even
+# though GOCACHE/GOTMPDIR already live on the big volume. Follow the
+# machine's configured GOTMPDIR when one exists.
+HOT_DEV_GO_TMPDIR="$(go env GOTMPDIR 2>/dev/null || true)"
+if [[ -n "${HOT_DEV_GO_TMPDIR}" ]]; then
+    mkdir -p "${HOT_DEV_GO_TMPDIR}" 2>/dev/null || true
+    export TMPDIR="${HOT_DEV_GO_TMPDIR}"
+fi
+
 # --- Helper Functions ---
 
 log_info() { printf "\033[0;34m[hot-dev]\033[0m %s\n" "$1"; }