ai-dev-tools-composition-root

name	ai-dev-tools-composition-root
description	Guidance for this project's composition root pattern — how SharedCompositionRoot centralises shared service wiring, how the Mac app and CLI targets each have their own root that wraps it, and how platform-specific additions (models, git client, credentials) are layered on top. Use this when adding new shared services, creating a new CLI command that needs services, modifying how providers or credentials are wired, reviewing code that constructs services outside a composition root, or any time someone asks how dependency wiring works in this project.
user-invocable	true

Composition Root Pattern

Why composition roots exist

Every service in this app must be constructed somewhere. The wrong answer is constructing them in the command or model that happens to need them — that scatters wiring logic, makes it easy for two callers to wire the same service differently, and hides what the app actually depends on.

The composition root is the single place where services are assembled. Callers receive what they need from the root; they never build services themselves.

This is not a singleton. The root is created once at startup (or once per command invocation in the CLI), held by the entry point, and injected downward. There is no static shared.

---

SharedCompositionRoot (Services layer)

Sources/Services/ProviderRegistryService/SharedCompositionRoot.swift

Builds everything both platforms share:

Property	Type
credentialResolver	CredentialResolver