refactor(#2442): split harness-state persistence out of events.rs
This commit is contained in:
parent
bf657177d3
commit
91607f3896
7 changed files with 349 additions and 328 deletions
|
|
@ -62,7 +62,7 @@ pub(super) async fn api_state(State(state): State<AppState>) -> axum::Json<State
|
|||
swarm_name: crate::identity::swarm_name(),
|
||||
available_models: available_models(),
|
||||
effort,
|
||||
available_efforts: crate::events::EFFORT_LEVELS
|
||||
available_efforts: crate::harness_state::EFFORT_LEVELS
|
||||
.iter()
|
||||
.map(ToString::to_string)
|
||||
.collect(),
|
||||
|
|
@ -181,7 +181,7 @@ pub(super) struct StateSnapshot {
|
|||
effort: String,
|
||||
/// Selectable effort levels for the picker, ascending. Fixed set
|
||||
/// (`low`, `medium`, `high`, `xhigh`, `max`) — sourced from
|
||||
/// [`crate::events::EFFORT_LEVELS`], not operator-configurable like
|
||||
/// [`crate::harness_state::EFFORT_LEVELS`], not operator-configurable like
|
||||
/// `available_models`. The frontend renders one button per entry.
|
||||
available_efforts: Vec<String>,
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue