d5edb66199
Field incident (2026-08-20): a Windows Desktop update hand-off (update --yes --gateway --force) left a swarm of per-profile serve backends (mr-tester, probe-inherit, turqoise, clippy, maroon, …) holding cryptography/_rust.pyd. Some still had a live parent (the tearing-down Electron process, or the venv launcher->worker two-hop chain mid-exit), so the strict orphan-only reap (_orphaned_desktop_backend_pids, which bails the instant ANY holder has a live parent) disqualified the whole set and the venv-holder guard dead-ended. The user saw a ~12-minute hang, force-closed, and the half-done state stranded bot sessions. New rung: _handoff_reapable_backend_pids reaps surviving Hermes serve/dashboard backends from this venv — live parent or not — but ONLY in the hand-off context the caller gates on: args.gateway AND the update-incomplete marker present AND no live hermes.exe shim. In that window nothing legitimate supervises or respawns a serve backend (the Desktop tree-kills its backends and parks any relaunch behind the marker, #50238), so a surviving backend is a leak, not a race. A non-backend holder (operator REPL, stray script) still disqualifies the whole set; psutil-unavailable returns None (keep refusing). Wired as the final rung before the existing dead-end, after the orphan-only reap.