Unit tests leave their temporary project directories behind in the system temp directory #529

Describe the bug

Several unit tests create a temporary project directory with mkdtempSync(join(tmpdir(), ...)) and never remove it, so every unit-test run leaves directories behind in the system temp directory:

• packages/ui/tests/cli.test.ts:17: the project() helper, prefix ca-cli-, one directory per call
• packages/ui/tests/workarounds.test.ts:8: the project() helper, prefix ca-wk-, one directory per call
• packages/ui/tests/brand.test.ts:66, :98 and :213 (prefix brand-) and :202 (prefix brand-proj-)

None of the three files removes these directories afterwards: there is no rmSync and no afterEach/afterAll teardown. On one machine that ran the suite repeatedly, 158 of these directories had accumulated. Noticed while working on #412.

Steps to reproduce

1. Count the leftovers: ls -d "${TMPDIR:-/tmp}"/ca-cli-* "${TMPDIR:-/tmp}"/ca-wk-* "${TMPDIR:-/tmp}"/brand-* 2>/dev/null | wc -l
2. Run bun run test:unit in packages/ui
3. Count again: the number has grown, and it grows again on every run

Expected behavior

Each test removes the temporary directories it created when it finishes, whether it passes or fails, so a test run leaves the temp directory as it found it.

Actual behavior

Directories prefixed ca-cli-, ca-wk-, brand- and brand-proj- stay in the temp directory after the run and pile up across runs.

@codeatlasdev/ui version

4.5.0 (main at 85086c5)

Svelte version

other

Framework

other

Minimal reproduction

No response

Before submitting

• I searched existing issues and this hasn't been reported yet
• I read the docs and confirmed this is unexpected behavior

Happy to send a PR for this.