A writer of the stopped app can still be finishing in the data directory
when the smoke test removes its temp root, so rmdir failed with
ENOTEMPTY after the test had passed. The temp root is disposable: a
failed cleanup now logs a warning.
scripts/release-smoke.mjs runs on every release target:
- installer: installs the server archive with packages/launcher into a
temporary directory, requires a clean doctor report (only the PATH
warning is allowed), starts run on a free port with a temporary data
directory, waits for /health, stops it and uninstalls;
- desktop: starts the packaged app (an executable or a macOS .app) with
a temporary data directory, waits until its sidecar answers /health on
127.0.0.1:3333, then stops the app and the sidecar and checks that the
port is released.
The process tree is stopped through the process group on macOS and
Linux and with taskkill /T on Windows. The tests run both modes against
stand-in payloads.