Reported by clutchmuffin: TUI saved e.g. CUSTOM_REFRESH_RATES=165 but
Gaming Mode always launched at 60 Hz. Two stacked bugs:
1. Settings TUI wrote ~/.config/environment.d/gamescope-session-plus.conf
but never reloaded systemd's user env, so the running user manager
(and therefore gamescope-session-plus@.service) still had the old
values until next login. Now flush_pending calls
`systemctl --user import-environment` / `unset-environment` for the
keys it just touched.
2. CUSTOM_REFRESH_RATES was written as a single scalar. Gamescope's
--custom-refresh-rates is a list of *switchable* rates, not a
launch-rate selector — and with no safe 60 Hz fallback in the list,
some DRM/NVIDIA paths drop to the EDID-preferred 60 Hz on first
launch. TUI now writes a comma list (e.g. 60,165). show_state and
confirm_risky_save de-list to the highest member for display /
validation.
Adds a troubleshooting README entry documenting the Steam BPM
client-side rate persistence as the canonical first-launch workaround.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>