feat: support Paper 26.2 (Minecraft 26.2)

Paper 26.2 bundles Adventure 5.2.0, a major bump from the 4.26.1 shipped by 26.1.
Adventure 5 makes ClickEvent generic, so the raw type in
CommandContext.replyWithEvent no longer compiled. Auditing the rest of the
Adventure 5 removals found no other affected usage.

api-version is raised to 26.2, dropping 26.1 support: the two Adventure majors
are not binary compatible, so claiming 26.1 compatibility would be a lie.

Also fixes two problems found while verifying on a real server: the Velocity
healthcheck invoked mc-health, which does not exist in the mc-proxy image, so the
container had never once passed its check; and the debug environments pinned no
build at all, which meant the proxy came up as 4.1.0-SNAPSHOT while the plugin is
compiled against velocity-api 3.5.1. Server versions are now derived by x from
the Gradle coordinates so they cannot drift from what the plugin targets.

1 files changed, 5 insertions, 2 deletions

diff --git a/engine/build.gradle.kts b/engine/build.gradle.kts
index cef169a..854d965 100644
--- a/engine/build.gradle.kts
+++ b/engine/build.gradle.kts
@@ -11,7 +11,10 @@ dependencies {
     api("io.ktor:ktor-client-cio:3.5.2")
 
     // Adventure API (provided by platform implementations)
-    compileOnly("net.kyori:adventure-api:4.26.1")
+    // Pinned to the Paper-bundled version. Velocity (velocity-api 3.5.1) still ships Adventure 4.26.1,
+    // so engine must stay within the API surface both versions share -- currently just the Component type.
+    // Once platform-velocity moves to velocity-api 4.x (Adventure 5.2.0), this constraint goes away.
+    compileOnly("net.kyori:adventure-api:5.2.0")
 
-    testImplementation("net.kyori:adventure-api:4.26.1")
+    testImplementation("net.kyori:adventure-api:5.2.0")
 }