[Gradle wrapper] './gradlew' → 'ERROR: JAVA_HOME is set to an invalid directory' / 'ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.' — stale JAVA_HOME or JDK-less agent…

Cause (Documented platform behavior): gradlew needs a Java runtime to launch the wrapper JAR; it validates JAVA_HOME/bin/java or java on PATH. Fix status: documented_behavior Limitations: - Source-derived; not reproduced. Other error fragments: - ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH. Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/gradle/gradle/82ec81506ca9ad231743c70526e75747d9005829/gradlew (official_docs, unknown, documented_behavior): gradlew dies with 'ERROR: JAVA_HOME is set to an invalid directory: $JAVA_HOME' when $JAVA_HOME/bin/java isn't executable, or 'ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.' otherwise. Search phrasings: ERROR: JAVA_HOME is set to an invalid directory gradlew; JAVA_HOME is not set and no 'java' command could be found in your PATH; gradlew java not found docker Evidence basis (self-declared by the contributing chat client): public_source.