Hey! Your PR title Fix/desktop server switch doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

@Brendonovich I just tried to merge with dev, this issue still happens when using the <Show> Component, when I try to switch from local (sidecar-cli) to a remote majority of the times it gets stuck, with only the titl bar actually showing we are in another server, but the rest of the app remains the same.

In the video the whole page doesnt reload to switch to a new server. That was the reason I opted to use the <For> component with just that current server in the array, I am not sure why that ensures better remounting than using . I could try do some more looking today since the solution that worked is not really the best, and there must be a nicer way to go about it

I have singled out the issue to be related to running PTY instances, when you have none running, server switches happen as it should, but once you open one it breaks, so trying to get some fixes for that, went with adding server scoped terminal caches, even if its a good addition it doesnt solve the issue, so I made it into another PR, while I work on this one to solve the main issue.

Made a new commit that fixes the issue, makes switching of servers even with the terminal open simple.
The changes are here;

1. When we switch servers the change allows for navigating home before the server is changed, this removes any issue of using the directory or state of the old server that still remains to make fetches to the new server which will most of the time break if the new server doesnt have the same dir or terminal pty id

2. In the codebase currently mounted terminal instances outlive the currently active workspace/server. So this is why when you have a teminal open and switch servers everything breaks, so my solution was to bind mounted terminal callbacks to their owning workspace session so reconnect, cleanup, and clone flows update the original terminal store (from previous server) instead of whatever workspace becomes active after a server switch.

Result

This PR goes well with this one allowing for proper revival of pty with stale ID