Run check in CI's build job

The build job ran ./gradlew test, and forbidden-apis hangs off check,
so the previous commit's ban would never have failed a pull request.
check also runs Checkstyle and the Gradle plugin's validatePlugins,
which pass. The jdk jobs, which run the same code on other JDKs, keep
running only the tests. The README and CLAUDE.md say what CI runs.

Author: abashev

.github/workflows/ci.yml

@@ -51,7 +51,7 @@ jobs:
             caches/*/transforms
 
       - name: Build
-        run: ./gradlew test
+        run: ./gradlew check
 
       - name: Publish Test Report
         uses: mikepenz/action-junit-report@4a26df3e2ae132254ba12a53f65a388d0961e786 # v6.7.0

CLAUDE.md

@@ -1,7 +1,7 @@
 # Working in this repository
 
 Building and testing: the README's "Building and testing locally" section. Gradle runs on the Temurin 21 that
-`mise install` provides, `./gradlew test` is what CI runs, and `./gradlew formatDiff` formats the files you changed.
+`mise install` provides, `./gradlew check` is what CI runs, and `./gradlew formatDiff` formats the files you changed.
 
 ## Conventions for new code
 

README.md

@@ -134,7 +134,7 @@ fixes made the output differ from upstream, that numbering lost its meaning.
 
 ```bash
 mise trust && mise install
-./gradlew test      # what the CI build job runs
+./gradlew check     # what the CI build job runs: the tests, Checkstyle and forbidden-apis
 ```
 
 `-PjavaRuntime=25` runs the same tests on JDK 25, as CI's `jdk` jobs do for 25, 26 and 27, and for