87ae4ae94b
Five follow-ups to #57659 from post-merge review: 1. install.ps1: gateway scheduled-task re-enable now runs in a finally (a thrown Remove-Item/uv venv failure previously stranded the user's gateway autostart disabled), and tasks that were already disabled before the install are no longer blindly re-enabled. 2. The venv-python holder guard is no longer bypassed by plain --force (which the desktop bootstrap passes on every update while its lock probe only checks hermes.exe/app.asar). New explicit --force-venv is the escape hatch; --force keeps bypassing only the hermes.exe shim guard. 3. _detect_venv_python_processes now also catches uv/base-interpreter trampolines whose exe is outside the venv, via cmdline (venv path or '-m hermes_cli.main' tied to this install root) and cwd. 4. Missing venv python is now UNHEALTHY on managed installs (.hermes-bootstrap-complete / .update-incomplete markers) so the repair lane runs instead of 'Already up to date!'; the repair branch recreates the venv first when it's gone entirely. Dev checkouts keep reporting healthy. 5. install.ps1 comment no longer claims a Startup-folder disarm the code doesn't perform (logon-only, not a mid-install respawner). |
||
|---|---|---|
| .. | ||
| bootstrap.rs | ||
| events.rs | ||
| install_script.rs | ||
| lib.rs | ||
| main.rs | ||
| paths.rs | ||
| powershell.rs | ||
| update.rs | ||