Persist server-advertised experimental features from the TUI (#42674)

## What changed

- Save writable `/experimental` selections through `config/batchWrite`, including features that are not known to the local client.
- Refresh configured values after writes and surface timeouts, failures, and higher-priority overrides without changing the active task's settings.
- Serialize saves and discovery, let accepted writes finish after the popup closes, and retain uncertain selections for explicit retry.

## Testing

- Cover new server feature keys, server defaults, overrides, write and readback failures, timeouts, selected config profiles, and popup retry behavior.

GitOrigin-RevId: acee4e10cbb8c2fce9211e8fadd3cd67fa0eb1a5
This commit is contained in:
Eric Traut authored and copyberry committed 2026-09-04 04:55:40 +00:00
1 parent b995d06050
commit 048a936a23
18 files changed
+647 -81

No files matched your search

+2
View File
@@ -219,6 +219,7 @@ mod config_persistence;
mod connector_mentions;
mod event_dispatch;
mod exit_summary;
mod experimental_features;
mod file_change_approvals;
mod history_pagination;
mod history_ui;
@@ -537,6 +538,7 @@ struct InitialHistoryReplayBuffer {
}
pub(crate) struct App {
feature_write_lock: Arc<tokio::sync::Mutex<()>>,
model_catalog: Arc<ModelCatalog>,
pub(crate) session_telemetry: SessionTelemetry,
pub(crate) app_event_tx: AppEventSender,