CI: Gradle 9.8.0 -> 9.8.1

[bernardladenthin]

Summary

• Gradle 9.8.0 → 9.8.1 (released 2026-10-07). It changes the literal in the verify-signing-key-gradle job, which is kept identical in all four sibling repos, and refreshes its hash in .github/shared-files.sha256. In java-llama.cpp it also changes GRADLE_VERSION for the Android jobs.
• This commit belonged to the previous PR, but that PR was merged before it was pushed. It is replayed here onto the new main.
• The dependency and plugin sweep behind it found nothing else to update:
  • versions-maven-plugin over every POM: all plugins are current, and the only newer dependency is jqwik 1.10.1, which stays at 1.9.3 by policy.
  • Versions inside plugin configuration are current: Error Prone, NullAway, Checker, Lombok, JMH, jcstress, palantir-java-format.
  • AGP, Kotlin, AndroidX and the Compose BOM are current.
  • check-versions.py reports 0 differences between the four repos.

Test plan

• check-shared-files.py reports 0 files changed here alone. The job hash is identical on all four branches, so the cross-repo warnings clear once all four are merged.
• check-run-scripts.py passes, and the buildcheck unit tests pass.
• CI is green on this branch. verify-signing-key-gradle runs with 9.8.1.

Related issues / PRs

The same change is made in java-llama.cpp, BitcoinAddressFinder, streambuffer and srcmorph.

Checklist

• I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md
• My commits follow Conventional Commits. They use the repository's usual CI: prefix instead.
• No security-sensitive changes

🤖 Generated with Claude Code

https://claude.ai/code/session_01AytmJF9faEiQEVt6eetQS2

---

Generated by Claude Code

[claude]

Review Summary

Status: ✅ Approved

Findings

This PR contains a straightforward Gradle version bump from 9.8.0 to 9.8.1 with proper hash synchronization.

Strengths:

• ✅ Patch version bump (expected to contain only bugfixes/security updates)
• ✅ Correctly maintains cross-repo shared-file consistency
• ✅ Hash in .github/shared-files.sha256 is properly updated
• ✅ Changes are minimal and focused
• ✅ Well-documented commit message explaining the scope of the change
• ✅ Follows project conventions for dependency version updates

Code Quality:

• No code changes, only configuration updates
• Version string is properly quoted
• Consistent with existing formatting

Security:

• Patch version bump is low-risk
• No new dependencies introduced
• Hash validation ensures integrity

Process Compliance:

• Correctly synchronized across all four sibling repositories (as noted in PR description)
• Followed the project's dependency review process (versions-maven-plugin sweep mentioned)
• No policy violations detected

No issues found. Ready to merge.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud