Before concluding any task that modifies code, run a full build:
./mvnw -B clean verifyThis runs all tests across all modules and generates the JaCoCo aggregate coverage report.
Always check the aggregate report, never per-module reports in isolation:
report/target/site/jacoco-aggregate/jacoco.csv
Parse it to get per-module and per-class coverage. The aggregate reflects cross-module test coverage (e.g., pcsc Cucumber tests exercising core classes).
A per-module report like core/target/site/jacoco/jacoco.csv is misleading -it only shows coverage from that module's
own tests.
After modifying code, run the OpenRewrite check profile to detect style drift:
./mvnw -B verify -PcheckIf it fails (dry-run finds changes), apply fixes automatically with:
./mvnw -B process-sources -PfixupThen re-run ./mvnw clean verify to confirm the fixup didn't break anything.