Merged Gateway HTTPRoute path matching doesn't respect priority as defined in API docs

I'm using a merged gateway with cert-manager http01 solver. My main HTTPRoute has a PathPrefix match on `/`. When cert-manager create a HTTPRoute it creates an Exact match for `/.well-known[...]`. According the the API docs, when two HTTPRoutes provide a match the following should happen:
>Across all rules specified on applicable Routes, precedence must be
given to the match having:
"Exact" path match.
"Prefix" path match with largest number of characters.
Method match.

Unless I'm reading that wrong, the Exact match should take priority. However, the gateway is matching on the PathPrefix and sending the requests to my service pods rather than the cert-manager pod.