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, 6 insertions, 6 deletions

diff --git a/crates/mozart-core/src/config.rs b/crates/mozart-core/src/config.rs
index cbb3ba6..1220dee 100644
--- a/crates/mozart-core/src/config.rs
+++ b/crates/mozart-core/src/config.rs
@@ -328,12 +328,6 @@ impl Config {
     }
 }
 
-fn substitute(s: &str, vendor_dir: &str, home: &str, cache_dir: &str) -> String {
-    s.replace("{$vendor-dir}", vendor_dir)
-        .replace("{$home}", home)
-        .replace("{$cache-dir}", cache_dir)
-}
-
 /// Resolve `{$vendor-dir}`, `{$home}`, and `{$cache-dir}` placeholders in
 /// string-valued fields.  Only one pass is performed (no recursive expansion).
 pub fn resolve_references(config: &mut Config) {
@@ -368,3 +362,9 @@ pub fn resolve_references(config: &mut Config) {
         }
     }
 }
+
+fn substitute(s: &str, vendor_dir: &str, home: &str, cache_dir: &str) -> String {
+    s.replace("{$vendor-dir}", vendor_dir)
+        .replace("{$home}", home)
+        .replace("{$cache-dir}", cache_dir)
+}