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/package/locker.rs b/crates/shirabe/src/package/locker.rs
index d6db1ab7..b98b8dae 100644
--- a/crates/shirabe/src/package/locker.rs
+++ b/crates/shirabe/src/package/locker.rs
@@ -194,7 +194,7 @@ impl Locker {
             if let Some(packages_dev) = lock_data.get("packages-dev").cloned() {
                 locked_packages = array_merge(locked_packages, packages_dev);
             } else {
-                return Err(RuntimeException::new("The lock file does not contain require-dev information, run install with the --no-dev option or delete it and run composer update to generate a new lock file.".to_string())
+                return Err(RuntimeException::new("The lock file does not contain require-dev information, run install with the --no-dev option or delete it and run shirabe update to generate a new lock file.".to_string())
                 .into());
             }
         }
@@ -268,7 +268,7 @@ impl Locker {
         }
 
         Err(RuntimeException::new(
-            "Your composer.lock is invalid. Run \"composer update\" to generate a new one."
+            "Your composer.lock is invalid. Run \"shirabe update\" to generate a new one."
                 .to_string(),
         )
         .into())