//! Standalone managed `tm` driver — alias registry, global config, load, and run.
//!
//! Why: trusty-mpm's existing session launch path mutates the global `~/.claude`
//! on every invocation, making it unsafe to run alongside the user's own
//! claude-mpm setup. This module adds a `register/load/run` lifecycle that
//! operates entirely under `~/.trusty-mpm/` — never touching `~/.claude/` or
//! `~/.claude.json` — so the driver can replace claude-mpm for daily work
//! without collision (DOC-24).
//! What: seven submodules — `registry` (alias→URL persistence), `global_config`
//! (ensure the one tm-global config dir exists), `hooks` (managed hook triad
//! definitions and idempotent merge), `settings_defaults` (seed
//! `outputStyle`/`statusLine` defense-in-depth, issue #2214), `load` (clone +
//! prepare a managed workspace), `run` (launch claude with CLAUDE_CONFIG_DIR
//! isolation), and `trust_seed` (project trust + MCP-server pre-seeding into
//! managed config dir).
//! Test: unit tests in each submodule's `#[cfg(test)]` block.
// #7789: proves both managed-tier settings.json writers are wired to the #7780
// preserve-then-rewrite loader.
pub use preseed_managed_trust;