fix(hub): keep shim dir off the child cwd so Windows cleanup can rmdir

[antfubot]

Why

Follow-up to #408. The retry added there downgraded the Windows unit-test failure from EPERM to EBUSY but did not fix it:

Error: EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\devframe-terminals-shim-...'
 ❯ cleanup src/node/__tests__/host-terminals.test.ts

EBUSY on the rmdir syscall for the temp dir itself (not a file inside it) means a process in the tree still holds that directory as its current working directory. The shim session spawns the child with cwd: dir, so Windows keeps dir locked, and no amount of retrying clears a held cwd.

What

The .cmd shim resolves child.cjs through %~dp0 (an absolute path), so the child needs no cwd of its own. Spawn it from the parent temp dir (tmpdir()) instead of the shim's own dir, so nothing holds the dir open and the later rmdir succeeds. The existing retry still covers transient file-handle release for the files inside.

Test-only change; no runtime behaviour changes.

This PR was created with the help of an agent.

[coldtea-pr-lens]

◈ PR Lens

Note

Only tests changed, so PR Lens left this pull request undrawn. Comment @pr-lens draw to draw it

_{github.comment.notice: false in .github/pr-lens.yml turns this note off}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
devframe	Skipped		Sep 25, 2026 2:50am UTC