By: Lucien Huber <im@lcnbr.ch>
let run-card set commands reach the integration-test session build_cli_for_run_history ran a run card's commands on throwaway copies of the card's global and default-runtime settings, then gave the test fresh copies of the card's tables. A `set global` or `set default-runtime` command in the card therefore never reached the test's own commands: sm_load.toml asks for n_cores.feyngen=1, yet its tests generated on 10 threads. Run the commands on the settings the returned CLIState keeps, as the CLI does when it boots a card. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>