79856ba49b
The update entry points chose their target from the connection mode, so every surface in remote mode acted on the backend — including the ones showing the client's own status. The macOS "Check for Updates…" app-menu item is the clearest case: it sits next to "About Hermes" and is the OS-standard way to update THIS app, but on a Mac connected to a remote Linux backend it checked the Linux box. The backend was already current, so the action reported nothing and did nothing, and the desktop app drifted months behind with no error and no updater log to explain it. The update-available toast had the same split: a client check raised it, clicking it opened the backend's overlay, which has no target switcher and no way back. Surfaces bound to one target now name it; only genuinely generic commands still take the connection-mode default, so the command palette's remote-mode backend target and the everything-flow are unchanged. Co-authored-by: BerneYue <14088768+yuexiongHNU@users.noreply.github.com> Co-authored-by: David Metcalfe <80915+DavidMetcalfe@users.noreply.github.com> Co-authored-by: clayduncan <234173110+clayduncan@users.noreply.github.com> Co-authored-by: Dhana <227747512+whoisdhana@users.noreply.github.com>