fix(ci): isolate cargo-rail bootstrap target dir on Windows

Author: loadingalias

justfile

@@ -7,18 +7,18 @@ test crate="":
 build:
     @echo "Change Detection Plan:"
     @echo ""
-    @cargo run --quiet -- rail plan --merge-base --explain
+    @cargo run --quiet --target-dir "${RAIL_BOOTSTRAP_TARGET_DIR:-target/cargo-rail-bootstrap}" -- rail plan --merge-base --explain
     @echo ""
     @echo "Building affected crates..."
-    @cargo run --quiet -- rail run --merge-base --profile local --surface build
+    @cargo run --quiet --target-dir "${RAIL_BOOTSTRAP_TARGET_DIR:-target/cargo-rail-bootstrap}" -- rail run --merge-base --profile local --surface build
 
 build-release:
     @echo "Change Detection Plan:"
     @echo ""
-    @cargo run --quiet -- rail plan --merge-base --explain
+    @cargo run --quiet --target-dir "${RAIL_BOOTSTRAP_TARGET_DIR:-target/cargo-rail-bootstrap}" -- rail plan --merge-base --explain
     @echo ""
     @echo "Building affected crates (release)..."
-    @cargo run --quiet -- rail run --merge-base --profile local --surface build -- --release
+    @cargo run --quiet --target-dir "${RAIL_BOOTSTRAP_TARGET_DIR:-target/cargo-rail-bootstrap}" -- rail run --merge-base --profile local --surface build -- --release
 
 # Full Workspace Commands (no change detection)
 
@@ -43,18 +43,18 @@ ci-test:
     @scripts/test/test.sh
 
 ci-build:
-    @cargo run --quiet -- rail run --since "${RAIL_SINCE:-HEAD~1}" --surface build
+    @cargo run --quiet --target-dir "${RAIL_BOOTSTRAP_TARGET_DIR:-target/cargo-rail-bootstrap}" -- rail run --since "${RAIL_SINCE:-HEAD~1}" --surface build
 
 # Explainability
 
 plan:
-    cargo run --quiet -- rail plan --merge-base -f json
+    cargo run --quiet --target-dir "${RAIL_BOOTSTRAP_TARGET_DIR:-target/cargo-rail-bootstrap}" -- rail plan --merge-base -f json
 
 why:
-    cargo run --quiet -- rail plan --merge-base --explain
+    cargo run --quiet --target-dir "${RAIL_BOOTSTRAP_TARGET_DIR:-target/cargo-rail-bootstrap}" -- rail plan --merge-base --explain
 
 dry-run surface="test":
-    cargo run --quiet -- rail run --merge-base --surface {{ surface }} --dry-run --print-cmd --explain
+    cargo run --quiet --target-dir "${RAIL_BOOTSTRAP_TARGET_DIR:-target/cargo-rail-bootstrap}" -- rail run --merge-base --surface {{ surface }} --dry-run --print-cmd --explain
 
 # Maintenance
 

scripts/check/check.sh

@@ -16,7 +16,11 @@ set -euo pipefail
 #   CARGO_RAIL_TEST_MODE    # "commit" forces CI mode
 #   RAIL_SINCE              # Git ref for comparison
 
-RAIL_CMD=(cargo run --quiet -- rail)
+# Run the control-plane cargo-rail binary from an isolated target dir.
+# This avoids Windows file-lock conflicts when cargo-rail later asks Cargo
+# to build or test the workspace's own `target` tree.
+RAIL_BOOTSTRAP_TARGET_DIR="${RAIL_BOOTSTRAP_TARGET_DIR:-target/cargo-rail-bootstrap}"
+RAIL_CMD=(cargo run --quiet --target-dir "$RAIL_BOOTSTRAP_TARGET_DIR" -- rail)
 
 # Parse arguments
 CI_MODE=false

scripts/test/test.sh

@@ -15,7 +15,11 @@ set -euo pipefail
 #   CARGO_RAIL_TEST_MODE   # "local" (default) or "commit" (CI)
 #   RAIL_SINCE             # Git ref for CI comparison
 
-RAIL_CMD=(cargo run --quiet -- rail)
+# Run the control-plane cargo-rail binary from an isolated target dir.
+# On Windows, `cargo nextest` cannot rebuild `target/debug/cargo-rail.exe`
+# while that exact binary is still running via `cargo run`.
+RAIL_BOOTSTRAP_TARGET_DIR="${RAIL_BOOTSTRAP_TARGET_DIR:-target/cargo-rail-bootstrap}"
+RAIL_CMD=(cargo run --quiet --target-dir "$RAIL_BOOTSTRAP_TARGET_DIR" -- rail)
 
 ARG="${1:-}"
 MODE="${CARGO_RAIL_TEST_MODE:-local}"