test: stop a background writer failing teardown's rm

tests/add-app-errors.bats

@@ -12,7 +12,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 @test "add refuses to run outside a git repository" {

tests/add-app.bats

@@ -6,7 +6,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 @test "add installs an adapter at an arbitrary path" {

tests/compose.bats

@@ -6,7 +6,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 @test "the compose files are valid" {

tests/docs.bats

@@ -6,7 +6,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 @test "docs is a config root with the full contract" {

tests/helpers/setup.bash

@@ -21,6 +21,11 @@ if [ -z "${GIT_CONFIG_GLOBAL:-}" ]; then
   export GIT_CONFIG_GLOBAL
   git config --global user.name "scaffold tests"
   git config --global user.email "tests@scaffold.invalid"
+  # `scaffold new` commits, and a commit can hand the repository to a detached
+  # `git gc`. That process outlives the command and keeps writing into .git,
+  # which is the likeliest thing remove_workdir below is racing. A throwaway
+  # repository has nothing worth maintaining.
+  git config --global gc.auto 0
 fi
 
 # mise records every config it trusts under its state directory, so a suite
@@ -62,3 +67,27 @@ copy_toolbox() {
   cp "${SCAFFOLD_ROOT}/docs/PROVENANCE.md" "$dest/docs/" 2>/dev/null || true
   printf '%s' "$dest"
 }
+
+# remove_workdir — teardown's `rm -rf`, retried.
+#
+# `rm -rf` reports "Directory not empty" when an entry appears after it walked
+# the directory, so a background process still writing into a generated project
+# fails a teardown that has nothing to do with what the test asserted. Seen on
+# CI against `tests/compose.bats`, which generates a project per test under
+# --jobs, and on a different test each run; never reproduced locally, and the
+# writer was never caught in the act, so this waits the race out rather than
+# naming a cause. A tree that is genuinely stuck still fails, and says what is
+# left in it.
+remove_workdir() {
+  local -r dir="$1"
+
+  for _ in 1 2 3 4 5; do
+    rm -rf "$dir" 2>/dev/null && return 0
+    sleep 1
+  done
+
+  rm -rf "$dir" && return 0
+  echo "could not remove ${dir}, left behind:" >&2
+  find "$dir" >&2
+  return 1
+}

tests/new-flask.bats

@@ -5,7 +5,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 @test "flask generates an app at apps/api" {

tests/new-laravel-api.bats

@@ -5,7 +5,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 @test "laravel-api generates an app at apps/api" {

tests/new-laravel-inertia.bats

@@ -5,7 +5,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 @test "laravel-inertia generates a single app at apps/app" {

tests/new-nestjs.bats

@@ -5,7 +5,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 @test "nestjs generates an app at apps/api" {

tests/new-nextjs.bats

@@ -5,7 +5,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 @test "nextjs generates an app at apps/web" {

tests/new-project.bats

@@ -5,7 +5,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 @test "new creates a git repository on main" {

tests/publish.bats

@@ -9,7 +9,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 # _stub_gh — a `gh` that records what it was asked to do and answers from

tests/update.bats

@@ -14,7 +14,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 _commit() {

tests/workflows.bats

@@ -28,7 +28,7 @@ setup() {
 }
 
 teardown() {
-  rm -rf "$WORKDIR"
+  remove_workdir "$WORKDIR"
 }
 
 @test "the project ships five workflows" {