MovementAscend jump cost needs tuning

I just guessed you'd jump after 0.5 blocks of walking but that isn't accurate. What should the cost really be for movementascend?

The issue names MovementAscend but provides no file or test path. Locate the MovementAscend movement-cost logic, then investigate how the 0.5-block estimate affects pathfinding and determine the intended cost from the surrounding implementation or project discussion. Done means the cost is justified and the resulting behavior is validated.

Written by the indexing model from the issue text.