The most-specific test compares an argument expression to boxed and unboxed target types, and prefers the closest match. For top-level arguments, this serves as a means of disambiguation, but is also mostly redundant, given that the strict/loose applicability phases already disambiguate based on boxing.

In the future it may be useful to eliminate the strict/loose phases. But for now, we should roll back the most-specific behavior to more closely match 7. The only time boxing/unboxing should be taken into account is when comparing return types of functional interfaces.