Settings: Consolidate to a single Save button instead of multiple #88
Description
Problem
The settings page currently has multiple save buttons (one per section or setting group). This is confusing UX - users expect to make all their changes and hit one Save.
Current behavior
Multiple save buttons scattered across the settings page, each saving a different section independently.
Expected behavior
- Single "Save" button (likely at the bottom or in a sticky footer/header)
- All settings changes are collected and saved together on one action
- Optionally: dirty state indicator showing unsaved changes
- Optionally: discard/reset option to revert unsaved changes
Why this matters
Multiple save buttons create cognitive overhead - users have to think about which section they changed and which button to press. A single save is the standard pattern users expect.