mecha10-cli 0.6.5

//! Command handlers (orchestration layer)
//!
//! Handlers are responsible for orchestrating services to implement command logic.
//! They sit between the CLI interface (commands) and business logic (services).
//!
//! # Responsibilities
//!
//! - Orchestrate service calls in the correct order
//! - Handle user interaction (prompts, progress bars)
//! - Format and present output to the user
//! - Handle errors and provide user-friendly messages
//!
//! # Design Principles
//!
//! - **Thin layer**: Handlers should delegate to services, not contain business logic
//! - **UI concerns**: Handlers manage all user interaction
//! - **Error handling**: Convert service errors to user-friendly messages
//! - **No state**: Handlers receive CliContext and command args only
//! ```

/// Generates a command handler that dispatches to `$inner` for the single `Remote` variant of
/// `$cmd`. `ps` and `stop` are both pass-through dispatchers over a one-variant command enum
/// today; once a second variant lands here, hand-write the `match` instead of forcing it through
/// this macro.
macro_rules! remote_dispatch_handler {
    ($name:ident, $cmd:ty, $inner:ident) => {
        /// Handle the command
        pub async fn $name(ctx: &mut crate::context::CliContext, command: &$cmd) -> anyhow::Result<()> {
            match command {
                <$cmd>::Remote => $inner(ctx).await,
            }
        }
    };
}

pub mod add;
pub mod auth;
pub mod build;
pub mod cache;
pub mod config;
pub mod dev;
pub mod diagnostics;
pub mod format;
pub mod init;
pub mod lint;
pub mod logs;
pub mod model;
pub mod ps;
pub mod run;
pub mod schema;
pub mod setup;
pub mod sim;
pub mod stop;
pub mod topics;
pub mod topology;
pub mod train;
pub mod upload;