A team may want to run moduleCheck with auto-correct enabled locally, but only run it as a "check" in CI. It's awkward to do that with the current api surface.

Instead of the property, the plugin could just define different tasks for auto-correct vs check behavior. Possibly something like:

# checks for correctness
./gradlew moduleCheck

# checks and applies changes
./gradlew moduleCheckApply

Other auto-fix plugins like Spotless, Kotlinter, and ktlint-gradle have similar patterns, so it should feel familiar to end-users.