Function interpret_for_ui_baseline 

pub async fn interpret_for_ui_baseline(input: &str) -> InterpreterResult

Baseline-tier interpret for the interactive UI (the Studio) — the cold-start engine. Runs on the bytecode VM with NO run-path optimizer (with_parsed_program, not with_optimized_program) and NO oracle (compile_with_types, not compile_with_oracle), so there is no optimize/analysis latency before execution. largo run and the benchmarks keep interpret_for_ui, which optimizes ahead of execution for peak throughput. Output is identical — the VM is differentially gated against the tree-walker on the SAME parsed statements (see the debug shadow-oracle assert in interpret_for_ui_baseline_sync_with_args); only the startup latency differs. This is the baseline half of the EXODIA tier split; promoting hot code to the optimized path is a later step.