[Bug]: SSH environment added by ssh config alias breaks when the alias' port changes

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

The alias here is the only stable way to reach the machine: its port is reassigned on every VM start, and the ssh config entry is kept current automatically.

1. Create a VM reachable over SSH that gets assigned a high port on 127.0.0.1, with an entry added to ~/.ssh/config under an alias. The port changes on every VM start, the alias does not.
2. Confirm the alias works from a terminal: ssh <alias> connects.
3. In the desktop app, open Settings > Connections > Add environment > SSH.
4. Fill in two fields only: the host alias, so no address has to be typed, and the username. Leave the port empty, since the alias already carries it.
5. Connect. The environment is created and works normally.
6. Note that the saved connection is now labelled SSH <user>@127.0.0.1:<port>, so the resolved address and port were captured instead of the alias.
7. Restart the VM so it is assigned a different port. The ~/.ssh/config entry is updated accordingly. Change nothing in T3 Code.
8. Confirm the alias still works from a terminal: ssh <alias> connects.
9. Reconnect the saved environment in T3 Code.

Expected behavior

An environment added by alias keeps the alias as its address. Every connection attempt resolves the alias through the ssh config as it is at that moment, so a changed HostName or Port is picked up without touching T3 Code. A username typed by hand stays an override, because it was chosen deliberately.

Actual behavior

The alias is resolved once, when the environment is added, and the resolved host and port are persisted and reused. Step 9 fails: the connection is still aimed at the old port, even though ssh <alias> works from a terminal and the ssh config is correct. Nothing in the UI offers to go back to using the alias.

Impact

Major degradation or frequent failure

Version or commit

0.0.33

Environment

macOS, desktop app 0.0.33

Screenshots, recordings, or supporting files

Screenshot of the saved connection showing the captured address and port added in a comment below.

Workaround

Delete the saved connection and add it again with the same alias, on every port change.

Start in the apps/desktop SSH environment add-and-reconnect flow and reproduce the alias with a changing port described in the issue. Trace what is saved after the alias is resolved; done means the saved address remains the alias, while a manually entered username remains an override and reconnecting follows the current ~/.ssh/config.