The desktop approval-mode store keyed its per-profile cache by name but sent
`config.get` / `config.set` without a `profile` param. The gateway's config
RPCs are `@_profile_scoped`, so an unscoped call resolves to the backend's
*launch* profile: the menu showed one profile's mode for every profile, and a
write made while viewing another profile silently edited the launch profile.
Name the profile each read/write is for (a blank name is the launch profile, so
omit the param and keep the backend's os.environ/session precedence) — the same
rule `api/client.ts`'s `profileScoped()` already uses for REST settings.
ef6039cc77