refactor(composer): move Composer and Factory from mozart-core to mozart

Composer needs DownloadManager (from mozart-registry), but mozart-core
sits below mozart-registry in the dependency graph — adding the field
would create a dependency cycle. Moving Composer and create_composer to
the mozart CLI crate breaks the cycle and lets the root state container
hold a DownloadManager.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

1 files changed, 4 insertions, 4 deletions

diff --git a/crates/mozart/src/commands/config.rs b/crates/mozart/src/commands/config.rs
index 7227556..5012163 100644
--- a/crates/mozart/src/commands/config.rs
+++ b/crates/mozart/src/commands/config.rs
@@ -1,15 +1,15 @@
+use super::config_helpers::{
+    add_repository, read_json_file, remove_repository, render_value, write_json_file,
+};
 use anyhow::anyhow;
 use clap::Args;
+use mozart_core::composer::composer_home;
 use mozart_core::config::resolve_references;
 use mozart_core::console_writeln;
 use mozart_core::factory::create_config;
 use std::collections::BTreeMap;
 use std::path::{Path, PathBuf};
 
-use super::config_helpers::{
-    add_repository, composer_home, read_json_file, remove_repository, render_value, write_json_file,
-};
-
 #[derive(Args)]
 pub struct ConfigArgs {
     /// Setting key