chore(cli): address PR feedback — test imports, nerdctl in runtime hint

- Move Message import to mod tests scope (CodeRabbit)
- Mention nerdctl in install-options bullet (514Ben)

Made-with: Cursor

Author: okane16

apps/framework-cli/src/cli.rs

@@ -2388,7 +2388,10 @@ async fn confirm_and_save_migration_legacy(
 
 #[cfg(test)]
 mod tests {
-    use crate::{cli::settings::read_settings, utilities::machine_id::get_or_create_machine_id};
+    use crate::{
+        cli::display::Message, cli::settings::read_settings,
+        utilities::machine_id::get_or_create_machine_id,
+    };
 
     use super::*;
 
@@ -2492,7 +2495,6 @@ mod tests {
 
     #[test]
     fn format_infrastructure_routine_failure_preserves_details_and_error() {
-        use crate::cli::display::Message;
         let rf = RoutineFailure::new(
             Message::new(
                 "Failed".to_string(),
@@ -2512,7 +2514,6 @@ mod tests {
 
     #[test]
     fn format_infrastructure_routine_failure_without_source_error() {
-        use crate::cli::display::Message;
         let rf = RoutineFailure::error(Message::new(
             "Build".to_string(),
             "something went wrong".to_string(),

apps/framework-cli/src/cli/routines/util.rs

@@ -9,7 +9,7 @@ fn container_runtime_not_found_message(configured: &str) -> String {
          \n\
          Choose one of the following:\n\
          \n\
-         • Install a Docker-compatible CLI (Docker Desktop, Docker Engine, or Finch) and ensure the command is on your `PATH`.\n\
+         • Install a Docker-compatible CLI (Docker Desktop, Docker Engine, Finch, or nerdctl) and ensure the command is on your `PATH`.\n\
          \n\
          • Point Moose at a specific binary: set `container_cli_path` under `[dev]` in `~/.moose/config.toml`, or set the\n\
          environment variable `MOOSE_DEV__CONTAINER_CLI_PATH` to the full path of your `docker`, `finch`, or `nerdctl` executable.\n\