I am somehow concerned about coding an interlock to set movement always to positive as default, on API design point of view.
I agree it is better for user to have intensive APIs such as returning error on negative value passed for movements, but we'd better to have low(est) level APIs at least, and also system level functional checks to be taken care (or even "also" taken care?) by upper sequencer.

I should not have said "always". I think the request was for move requests to make the hysteresis correction by default. We would certainly add an argument to disable/skip the correction.