tooling-compatibility-matrixlisted

# Tooling Compatibility Matrix Offline baseline for hardening and high or critical refactor tooling recommendations. This skill never fetches versions. Every emitted version must include `verify-latest-at-execution: true` and an executor task to verify that the chosen version is current and CVE-free before installation. ## Standing rules - Prefer existing project conventions when present. - Use this matrix for deterministic first-pass versions and compatibility notes. - Pair every install task with a build verification command. - If a version or plugin compatibility is uncertain, mark it as `hypothesis` and require verification before install. - Web fetch remains denied for harness workers. ## Java matrix | Detected stack | Baseline tooling | Compatibility notes | | --- | --- | --- | | Java 8 + Maven/Gradle | JUnit 5.x via `junit-bom`, AssertJ 3.x, Mockito, JaCoCo 0.8.x, PIT Java-8-compatible line + `pitest-junit5-plugin` | Choose a PIT line compatible with Java 8; verify plugin/JUnit 5 compatibility before install. | | Java 11+ + Maven/Gradle | JUnit 5.x via `junit-bom`, AssertJ 3.x, Mockito, ApprovalTests when snapshots help, JaCoCo 0.8.x, current PIT + `pitest-junit5-plugin` | PIT >=1.15 requires Java 11+; plugin must match JUnit 5.x. | | Existing JUnit 4 | Keep JUnit 4 characterization if cheapest; add JUnit Vintage only when running JUnit 4 tests under JUnit Platform is required | Do not migrate tests as part of refactor safety unless required for execution. | ### M