## Java and Spring Boot - Treat the configured JDK, Spring Boot, Gradle, plugin, dependency, and package versions as authoritative. - Use the repository's Gradle Wrapper. Do not substitute a machine-global Gradle installation. - Preserve the established package layout and controller, application/service, domain, and persistence boundaries. - Keep controllers thin, place business rules in the established service/domain layer, and prefer constructor injection. - Apply request and configuration validation at boundaries and preserve the project's exception and response conventions. - Make transaction boundaries explicit and narrow; do not add broad transactions to hide lifecycle or query problems. - Preserve authentication, authorization, auditing, logging, and secret-management conventions. - Do not edit generated QueryDSL or other generated sources. Change their source definitions and regenerate only when the repository workflow requires it. - Use the approved KriCommon contract when the project profile includes it; do not duplicate shared backend behavior locally. - Run the narrowest relevant Gradle compile, test, static-analysis, and build tasks.