dfcef70061
Fixes #88654. After an in-place update, the manual-gateway leg of the restart phase did this for every profile-mapped gateway: restart_mode = _prepare_profile_gateway_update_restart(proc.profile, pid) if restart_mode is None: continue A None means no relaunch could be armed. The bare continue skipped the drain and the stop, and the unmapped sweep immediately below skips any pid already in profile_processes, so the process was never killed and never counted into the "Stopped N manual gateway process(es)" summary. The gateway kept running with its pre-update modules resident while the new code sat on disk, and every lazy import from that point mixed versions: cannot import name '_MAX_TOOL_ERROR_CHARS' from 'tools.registry' with no operator signal of any kind. Two changes. _prepare_profile_gateway_update_restart now falls back to replaying the process's own captured command line when the profile-derived relaunch cannot be armed. launch_detached_gateway_restart_by_cmdline already exists for exactly this case and documents itself as the companion for gateways with no profile mapping; the Windows post-update path already uses it the same way. The argv is captured a few lines earlier for the external-supervisor check, so the fallback costs nothing extra. The external-supervisor branch still short-circuits first, because replaying argv there would escape the manager and race its replacement process. When neither mechanism can arm a relaunch, the update path no longer falls through silently. It says so, naming the profile and pid, and hands the process to the existing unmapped sweep so it is stopped and reported through the established "Restart manually: hermes gateway run" contract. Leaving it running was the actual harm: a gateway on stale modules fails every lazy import for as long as it lives.