I agree that the method name does not fit, and would prefer "moveToPriorEntry" or even "moveToBeforePriorEntry".

I would want to see a concrete proposal about a more caller-driven approach. If it means something like replacing this 1 obscure new API call with 2 clearer ones, that would be good. But I'm not seeing that.
If it meant replacing this new call with more than 2 other new calls that were always called in the same pattern, I'd probably argue against it as exposing too much detail.