The comment described the runner as preferring the selector over the element's
own coordinates unconditionally. resolveCoordinates has since made the
coordinates win when the selector is ambiguous, so the two files stated opposite
rules for the same conflict. The reason the helper exists survives: the recorded
selector is still the element's identity in the trace, and TapSelector still
resolves it on the device.