Gradle configuration cache requires task state to be round-trip serializable. As outlined at #987, this is a signficant constraint on plugin developers and it slows down the end-user experience of change-test-change-test on a single JVM daemon. We built a workaround ([`JvmLocalCache`](https://github.com/diffplug/spotless/blob/ba490439f27cacc9e188bb39f4a0a4173f83b136/plugin-gradle/src/main/java/com/diffplug/gradle/spotless/JvmLocalCache.java)) that complies with Gradle's requirement by making our tasks round-trip serializable without requiring much work from plugin developers or the end user's machine, but it only works within a single JVM. To work on multiple JVMs, we need to - make every step round-trip serializable - remove `JvmLocalCache`