#16300: fix(tui): respect gateway bind mode in TUI connection

## Summary Fixes #16299 The TUI's gateway connection logic was hardcoded to `ws://127.0.0.1:${localPort}` and did not respect the `gateway.bind` config setting, while the status command correctly uses `pickProbeHostForBind()` to resolve the actual bind address. ## Problem When `gateway.bind` is set to `tailnet` or `lan`, the gateway listens only on the Tailscale IP or LAN IP respectively. However, the TUI's `resolveGatewayConnection()` function hardcodes the connection to `127.0.0.1`, causing connection failures. ## Solution - Import `pickPrimaryTailnetIPv4` from `../infra/tailnet.js` - Import `pickPrimaryLanIPv4` from `../gateway/net.js` - Resolve local host based on `config.gateway.bind` mode before constructing the WebSocket URL - Replace hardcoded `127.0.0.1` with the resolved host The logic mirrors `pickProbeHostForBind()` used by the status command. ## Testing Tested with: - `gateway.bind: "tailnet"` - TUI connects to Tailscale IP - `gateway.bind: "lan"` - TUI connects to LAN IP - `gateway.bind: "loopback"` - TUI connects to 127.0.0.1 (default) - `gateway.bind: "custom"` - TUI connects to custom host ## Impact - ✅ Users can now use TUI when gateway is bound to tailnet/lan/custom - ✅ Consistent behavior between status command and TUI - ✅ No breaking changes - defaults to loopback (127.0.0.1) <!-- greptile_comment --> <h3>Greptile Summary</h3> Fixed TUI gateway connection to respect the `gateway.bind` config setting by resolving the bind host dynamically based on the configured mode (tailnet/lan/custom/loopback). The implementation correctly mirrors the existing `pickProbeHostForBind()` logic used by the status command, ensuring consistent behavior across different bind modes. The change replaces the hardcoded `127.0.0.1` with dynamic host resolution that supports Tailscale IPs, LAN IPs, custom hosts, and loopback, with proper fallback to loopback when IPs cannot be determined. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with no concerns - The implementation correctly mirrors existing, well-tested logic from `pickProbeHostForBind()`, uses proper fallback strategies for all bind modes, maintains backward compatibility, and has no logical errors or security concerns - No files require special attention _{Last reviewed commit: 0f07019} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->