v7.6.1

• Settings are no longer lost on every launch. The Chromium flags are assembled before main() sets the application and organization names, and assembling them now reads a setting — the custom-frame check added in 7.6.0 for the frameless-window scroll fix (#104). That first read is what constructs SettingsManager, a function-local static that takes both names once, when it is built, so the whole run pointed at an unnamed store: every read returned its default (light window theme, "follow system theme" off, so the system was never consulted either, and no saved accounts) and every write was discarded. The names are now set before anything reads a setting. Nothing was ever written to the wrong place, so an existing configuration comes back untouched.
• The same fix is expected to resolve the 100% CPU hang on restart (#98), whose perf profile pointed at the settings and single-instance startup path (QSettings, QSharedMemory::attach) rather than the process spawn: the single-instance shared memory is keyed on the application name, which is now set before it is created.