Group settings with explicit modes and one save action

docs/guides/provisioning.md

@@ -248,9 +248,9 @@ See [native host management](native-hosts.md) for command delivery and recovery.
 
 ## Concurrency limits
 
-Admin → Settings separates Concurrency and Retention, with independent
-save actions. Existing fleet restart, startup and destruction limits continue to
-apply. Additional per-host restart, startup and destruction limits, a combined
+Admin → Settings groups Concurrency separately from history and storage settings,
+with one Save changes action for all pending edits. Existing fleet restart, startup
+and removal limits continue to apply. Additional per-host restart, startup and destruction limits, a combined
 lifecycle limit, a rebuild limit, and a limit on hosts preparing game files default
 to 0 (no additional cap), preserving existing throughput on upgrade.
 

docs/guides/settings.md

@@ -1,18 +1,30 @@
 # Fleet settings
 
-Admin → Settings has independent **Concurrency** and **Retention**
-sections. Settings persist in SQLite, apply without restarting the controller,
-and are writable only by administrators. Saving one section preserves the other
-section's saved values. Upgrades preserve existing values and add new defaults.
+Admin → Settings groups fleet limits and retention by the work they affect.
+Search by name or description, or choose a category in the section list. Each row
+shows its default, effect, and whether it has changed. Switching categories or
+searching keeps your pending edits.
+
+The sticky **Save changes** bar saves all pending changes together. **Discard**
+restores the last saved values. Settings persist in SQLite, apply without restarting
+the controller, and are writable only by administrators. Upgrades preserve existing
+values and add new defaults.
+
+Use **Forever** for history with no age expiry and **No limit** for optional
+concurrency or telemetry count caps. **No age expiry** on artifact versions still
+allows the version-count policy to remove old unused versions. **No delay** applies
+to the game-file grace period; **No minimum** applies to minimum retained counts.
+Turning these modes off restores the last finite value. Numeric fields show the
+unit beside the value.
 
 ## Concurrency
 
-The existing fleet restart, startup and destruction limits default to 1. Additional
+The existing fleet restart, startup and removal limits default to 1. Additional
 limits default to 0 (no additional cap):
 
 - Restarts per host, including starts and rebuild recovery.
 - Startups per host, including creation and rebuilds.
-- Destructions per host, including migration source removal.
+- Removals per host, including migration source removal.
 - Combined lifecycle work across create/start/stop/restart/rebuild/destroy.
 - Rebuilds across the fleet, including host drain migrations.
 - Hosts downloading or verifying game files simultaneously, including manual imports.