In the next version, #731, a few changes have been made to input and navigator to try and address this.
The precision of the movement should be more precise to hopefully avoid the case where it flat out misses the stairs. When the bot tries to prune nodes that are too close to each other, it'll now do a LoS check to make sure it doesn't skip an important node, like it could do near stairs, which causes it to miss them altogether.
It still might be possible for the bot to get stuck, and I'm noticing some really heavy desync in this area (Act 3 always seemed to have more of it for me), so some more fixes might need to be put in place to avoid the issue further.
