Ah, I see in the code this is because I never finished implementing checking of item status at the same position because it's a
lot of work for very little benefit... There's just a //TODO there
It's not as easy as simply having it update the window on waiting, because if something changes, the scan window should emit a sound and redraw/reanimate its contents, but that shouldn't be done unless it can be confirmed 100% that something
did change.
So technically this isn't the only change which might not trigger a scan update. Even the item integrity change update was "faked" into the system with a hack (apparently if the item is replaced with another of identical integrity at that same position, the window actually won't update!). Probably the best I could do here without spending ages on it would be to add an explicit check for container contents, akin to how integrity checking is handled...