I believe we need to carefully separate framework core functionality (transactional item processing with restart support) from other provided features - examples being start limit support and isAllowStartIfComplete property. I see these as nice-to-have features not essential to a batch framework and our architecture should clearly reflect that - currently they are penetrated in the very heart of the domain model and execution logic, which I see as a design flaw. They should instead be layered on top of the core (e.g. subclasses providing extra properties).

I remember Lucas arguing in the past that start limit support is a scheduling concern, strictly speaking out of framework's focus that would better be removed. I largely agree with that - however including few useful addons can indeed have a positive overall effect as it can serve as excellent example how to extend framework core capabilities cleanly - assuming we manage to achieve clear core/add-on separation in the first place.