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, 2 insertions, 2 deletions

diff --git a/crates/shirabe/tests/command/install_command_test.rs b/crates/shirabe/tests/command/install_command_test.rs
index 11afd464..abf489ab 100644
--- a/crates/shirabe/tests/command/install_command_test.rs
+++ b/crates/shirabe/tests/command/install_command_test.rs
@@ -50,13 +50,13 @@ Generating autoload files"#,
                 "packages",
                 InputValue::Array(vec!["vendor/package".to_string()]),
             )],
-            r#"Invalid argument vendor/package. Use "composer require vendor/package" instead to add packages to your composer.json."#,
+            r#"Invalid argument vendor/package. Use "shirabe require vendor/package" instead to add packages to your composer.json."#,
         ),
         (
             "it writes an error when no-install flag is passed",
             serde_json::json!({ "repositories": [] }),
             vec![("--no-install", InputValue::from(true))],
-            r#"Invalid option "--no-install". Use "composer update --no-install" instead if you are trying to update the composer.lock file."#,
+            r#"Invalid option "--no-install". Use "shirabe update --no-install" instead if you are trying to update the composer.lock file."#,
         ),
     ]
 }