Module resolved_defaults 

Single, shared implementation of “resolve the server’s current effective run configuration purely from live Config” — no per-request overrides.

This is the one place that combines crate::model_areas’s auxiliary-area resolution, crate::model_config_helper’s provider-type/gold-config resolution, crate::prompt_defaults’s template read, and crate::context::assemble_system_prompt into a single resolved snapshot. Two callers need EXACTLY this: bamboo-server’s connect bridge (resolve_connect_run_config, called once per inbound chat message) and the public GET /api/v1/execute/defaults HTTP handler (an external connector’s “what would the server currently run with” probe, issue #480). Both call resolve_default_run_config rather than each reimplementing the cascade — that reimplementation is exactly the drift #480 set out to prevent.

Deliberately mirrors schedule_app::manager::resolve_run_config_from_config minus the per-job overrides a scheduled run supports (a chat message or a defaults probe has none).

Structs

ResolvedDefaultRunConfig

Resolved model/prompt/workspace configuration for a run that carries no per-request overrides, derived purely from the live global config.

Functions

resolve_default_run_config

Resolve the server’s current effective run configuration purely from live Config — no per-request overrides. See the module docs for why this is the sole implementation of this cascade.