Bryan Helmkamp 06d9ef6118 refactor(cli): inject user settings layer into build_run_manifest ... build_run_manifest was reading FABRO_CONFIG env and ~/.fabro/settings.toml internally, which forced its 3 unit tests to use unsafe std::env::set_var to isolate from the developer's real config. This violates the project rule against mutating shared mutable state in tests. Add user_layer: SettingsLayer and user_settings_path: Option<PathBuf> to ManifestBuildInput so callers pass the user layer explicitly. - Production callers (graph, preflight, validate, run/create) load via load_settings_user() + active_settings_path(None) at the command boundary. - Tests pass SettingsLayer::default() and None, needing no env access. - Delete all unsafe { set_var/remove_var } blocks and #[allow(unsafe_code)] attributes from the 3 manifest_builder tests. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-04-10 08:49:22 -04:00
..
crates	refactor(cli): inject user settings layer into build_run_manifest	2026-04-10 08:49:22 -04:00
packages/fabro-api-client	Merge origin/main into main	2026-04-09 21:11:55 -04:00