chore: localize bot workflows for the JVM family

.github/workflows/greetings.yml

@@ -15,31 +15,26 @@ jobs:
       with:
         repo_token: ${{ secrets.GITHUB_TOKEN }}
         issue_message: |
-            Thanks for opening your first issue on **guard-core-rs**!
+            Thanks for opening your first issue on **spring-boot-guard**!
 
             To help us triage quickly, please make sure your report includes:
-            - A clear reproduction (a short Rust snippet or failing test is ideal)
-            - Output of `rustc --version && cargo --version` (MSRV is 1.92)
-            - The crate you are using (`guard-core-rs` facade, `guard-core-engine`, or the PyO3 bindings) and the version you depend on
-            - A conformance data point if relevant: the corpus case id and whether it passes, xfails, or drifts (`cargo test -p guard-core-conformance`)
+            - A clear reproduction (a short Kotlin snippet or failing test is ideal)
+            - Output of `./gradlew --version` (JDK 17 is the floor)
+            - The framework version in use (Spring Boot 3.x is the target (a 4.x lane joins the test matrix in a later wave))
+            - The guard-core engine version you depend on
 
             A few pointers:
-            - Scan [README.md](../blob/master/README.md) and [AGENTS.md](../blob/master/AGENTS.md) for the engine layout and its honest status (the 4.x pattern-table scan stage is not ported yet; do not expect full parity with the Python engine).
+            - Scan [README.md](../blob/master/README.md) for the adapter layout and its honest status (W0 scaffold: the adapter implementation lands in a later wave).
             - **Security vulnerability?** Do **not** open a public issue - please use GitHub's private vulnerability reporting.
 
             Thanks again - a maintainer will be with you soon.
         pr_message: |
-            Thanks for opening your first pull request on **guard-core-rs**!
+            Thanks for opening your first pull request on **spring-boot-guard**!
 
             Quick checklist before review (most of these are enforced by CI, but worth a glance):
             - [ ] The PR body says `Closes #N` for an open issue (the `issue-link` check enforces it); chores take the `no-issue` label
-            - [ ] `cargo fmt --all -- --check` reports no files
-            - [ ] `cargo clippy --workspace --all-targets --exclude guard-core-python -- -D warnings` is clean
-            - [ ] `cargo test --workspace --exclude guard-core-python` passes
-            - [ ] The conformance gate is green: `cargo test -p guard-core-conformance` (a flipped corpus case needs a ledger or xfail update with a written reason)
-            - [ ] `RUSTDOCFLAGS="-D warnings" cargo doc --workspace --exclude guard-core-python --no-deps --all-features` is clean
-            - [ ] No outer `#[allow(...)]` in non-test, non-fuzz code; an entry under `## Unreleased` in [CHANGELOG.md](../blob/master/CHANGELOG.md)
+            - [ ] `./gradlew spotlessCheck detekt` is clean
+            - [ ] `./gradlew build` passes
+            - [ ] No blanket `@Suppress` in non-test code
 
-            See [AGENTS.md](../blob/master/AGENTS.md) for the boundary rules (the engine crate stays pure, synchronous, CPU-bound) and the conformance honesty policy.
-
-            Welcome aboard - a maintainer will review shortly.
+            See [README.md](../blob/master/README.md) for the adapter status. Welcome aboard - a maintainer will review shortly.

.github/workflows/stale.yml

@@ -38,8 +38,8 @@ jobs:
             If it's still relevant, please leave a comment - otherwise it will be closed in 14 days.
 
             Things that help keep an issue moving:
-            - A current reproduction (Rust snippet or failing test)
-            - Output of `rustc --version && cargo --version` and the feature flags in use
+            - A current reproduction (Kotlin snippet or failing test)
+            - Output of `./gradlew --version` (JDK, Gradle, Kotlin) and the modules in use
             - Any new findings since the last activity
 
             Maintainers can keep this open indefinitely by adding the `pinned` label.