"The data is wrong" bug that was two UI ambiguities: list index vs item name, and adjacent items on a map
A user reported that the number in a detail panel did not match what they saw in an embedded 3D viewer, twice, even after "selecting the same door". The data was correct both times. Worth recording because the fix was not in the data path at all.
What was actually happening: 1. Index vs identity. A stepper chip read "Clear door 6 of 31" (position in the findings list), while the item itself was named "Scan doorway 3". The first three list positions were non-door checks, so index and name were offset. The user reasonably read both as "door 6". 2. Adjacent items. A minimap ringed the selected doorway correctly, the user walked there in the viewer, and looked at the most prominent door in view: a 5 ft 9 in double door. The selected item was a 2 ft 6 in door 1.4 m to its left, visible in the same frame. 3. Unit mismatch made it harder to notice. The viewer labels dimensions in feet and inches (2 ft 6 in); the panel showed decimal inches (29.6 in). Same value, not obviously the same.
How I confirmed it instead of guessing: dumped every item with its stored width and position, found the selected one, and searched for neighbours within a few metres. One neighbour had exactly the width shown on screen. That turned "mismatch" into "wrong neighbour" in one query.
Fix that helped immediately (cheap): show a distinguishing attribute everywhere the item is named, in the same format the other view uses. Here: "Scan doorway 3 - 2 ft 6 in opening" in the list row, the minimap caption and the action panel, plus one sentence telling the user to match that width on screen because doorways often sit side by side.
Fix that removes the cause (not done yet): link the two views so selecting an item steers the viewer to it.
General takeaways: - When two panes are not synchronised, every label of a selected item should carry something the user can cross-check against the other pane. - Never show a bare list position next to items that have their own numbers. - Match the unit format of whatever the user is comparing against. - Before debugging a suspected data mismatch, look for a neighbour that has the value the user saw.