feat(client/linux): bind a host to a profile, or connect with one just this once

The other half of P1 on GTK (design/client-settings-profiles.md §5.2): until now a profile could be created and edited but only *used* through `--profile` or a URL. Host cards get two menus, and they are separate on purpose — the predictability rule is that connecting with a profile must never change what the card does next time. - **Connect with ▸** is a one-off. It rides `ConnectRequest.profile` into the session's `--profile` flag and touches no stored state. "Default settings" in that menu is `Some("")`, not `None`: on a bound host, asking for the defaults is a real choice and has to survive as a value rather than degrade into "use the binding". - **Default profile ▸** is the explicit rebinding act. It writes straight onto the host record — the binding IS a field there, so there is no map to keep in step — matched by fingerprint, else by address, like every other per-host lookup in this client. - The card carries a **chip** naming its bound profile, so what a plain click will do is visible without opening a menu. A binding whose profile was deleted shows nothing and connects with the defaults, which is exactly what the resolver does. A URL's `profile=` now takes the same one-off route, since it is the same kind of thing. Verified on .21: `punktfunk://connect/Bound%20Box?profile=Work` against a host bound to "Game" spawned a session that logged `profile=Work id=bbbbbbbbbbbb` — the one-off won, and the binding on disk was untouched. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-07-28 22:24:56 +02:00
parent 37a42078a0
commit 808eba7292
5 changed files with 151 additions and 27 deletions
@@ -736,24 +736,6 @@ fn group(title: &str, description: &str) -> adw::PreferencesGroup {
 /// there so the library toggle takes effect without a nav round-trip). `probes` is the
 /// shell's startup device probe (`AppModel::probes`) — may still be empty. Returns the
 /// presented dialog so the screenshot harness can select a page; callers ignore it.
-pub fn show(
-    parent: &impl IsA<gtk::Widget>,
-    settings: Rc<RefCell<Settings>>,
-    gamepads: &crate::gamepad::GamepadService,
-    probes: &DeviceProbes,
-    on_closed: impl Fn() + 'static,
-) -> adw::PreferencesDialog {
-    show_scoped(
-        parent,
-        settings,
-        gamepads,
-        probes,
-        Scope::Defaults,
-        |_| {},
-        on_closed,
-    )
-}
-
 /// The dialog in a given [`Scope`]. `on_scope` asks the app to re-open it in another one:
 /// switching scope closes this dialog first, so the layer being edited is committed before
 /// the next one is loaded, and there is exactly one place that builds the rows.