When hermes update triggers a venv rebuild on Windows, the running python.exe inside the venv is locked by the OS, so shutil.rmtree() silently fails to fully remove the directory. The subsequent uv venv command then fails with A directory already exists, leaving the venv in a half-deleted state (pyvenv.cfg gone, python.exe still present) which bricks the CLI with ModuleNotFoundError.

Fix: Adding --clear to the uv venv command makes it handle any leftover directory gracefully, regardless of what rmtree managed to remove. This is a one-line change in hermes_cli/managed_uv.py.

Before:

result = subprocess.run(
    [uv_bin, "venv", str(venv_dir), "--python", python_version],
    ...
)

After:

# Use --clear so uv handles any leftover directory that rmtree couldn't
# fully remove (e.g. on Windows where the running python.exe inside the
# venv is locked).  Without --clear, a partially-deleted venv causes
# "A directory already exists" and bricks the install.  See #37881.
result = subprocess.run(
    [uv_bin, "venv", str(venv_dir), "--clear", "--python", python_version],
    ...
)

Fixes #37881