Description
I'll be the first to admit this is a bit nit picky any property marked with Importance.HIGH should be guarded against nonsensical values.
With that said I would like to suggest that TASKS_MAX_CONFIG be validating against a lower bound limit of 1.
I do understand this is unlikely to happen and the configuration is nonsensical but there is no penalty for stopping someone from trying it out.