feat(cli): tell the user to run `shirabe`, not `composer`

Messages that instruct the user to run a command named the Composer
binary. Shirabe ships as its own binary, so the hints now name it.

File names (composer.json, composer.lock), the "composer" repository
type and prose about Composer itself are untouched. The installer and
functional integration fixtures live in the Composer submodule and
cannot be edited, so their expected output is normalized on load.

1 files changed, 1 insertions, 1 deletions

diff --git a/crates/shirabe/src/command/create_project_command.rs b/crates/shirabe/src/command/create_project_command.rs
index e2161aa3..a2b44713 100644
--- a/crates/shirabe/src/command/create_project_command.rs
+++ b/crates/shirabe/src/command/create_project_command.rs
@@ -315,7 +315,7 @@ impl CreateProjectCommand {
                     if e.is_instanceof::<PluginBlockedException>() {
                         io.write_error("<error>Hint: To allow running the config command recommended below before dependencies are installed, run create-project with --no-install.</error>");
                         io.write_error(&format!(
-                            "<error>You can then cd into {}, configure allow-plugins, and finally run a composer install to complete the process.</error>",
+                            "<error>You can then cd into {}, configure allow-plugins, and finally run a shirabe install to complete the process.</error>",
                             getcwd().unwrap_or_default()
                         ));
                     }