Fix: scheduler: constrain clone-node-max to non-negative values

I'm not sure what effect negative values had, but it's logically impossible,
so this maps negative or invalid values to 0.