This change is being adopted unanimously among bird taxonomies as far as I know, and similar frustrations are occurring in other places like eBird, although the way eBird’s taxonomy is programmed doesn’t involve a taxonomic tree in the same way so they have a bit more flexibility:
Not having to strictly follow a tree is nice in this case since it allows for taxonomically arbitrary slash options, but it is frustrating in a lot of other situations. For example you can’t search eBird for a higher level like “hawks and eagles” and have the search filter include all photos identified to species level below that level. It doesn’t recognize that “hawks and eagles” is a bucket that includes Cooper’s Hawk and Bald Eagle.
(For context for others reading:)