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/src/command/remove_command.rs b/crates/shirabe/src/command/remove_command.rs
index e50999bb..1f6f25d0 100644
--- a/crates/shirabe/src/command/remove_command.rs
+++ b/crates/shirabe/src/command/remove_command.rs
@@ -637,7 +637,7 @@ impl Command for RemoveCommand {
         }
 
         io.write_error(&format!(
-            "<info>Running composer update {}{}</info>",
+            "<info>Running shirabe update {}{}</info>",
             packages.join(" "),
             flags
         ));
@@ -695,7 +695,7 @@ impl Command for RemoveCommand {
                     .is_empty()
                 {
                     io.write_error(&format!(
-                        "<error>Removal failed, {} is still present, it may be required by another package. See `composer why {}`.</error>",
+                        "<error>Removal failed, {} is still present, it may be required by another package. See `shirabe why {}`.</error>",
                         package, package
                     ));
                     return Ok(2);