feat(presence)!: talk to service-player over HTTP

README.md

@@ -8,12 +8,20 @@
 
 ## Configuration
 
-The plugin requires the gRPC target to be provided via environment variable:
+The plugin requires the address of service-player. A proxy that cannot reach presence
+cannot decide whether a player may join, so this is required rather than defaulted:
 
 ```bash
-export PLAYER_PRESENCE_GRPC_TARGET="dns:///service-player.api.svc.cluster.local:9000"
+export PLAYER_SERVICE_URL="http://service-player.api.svc.cluster.local:9000"
 ```
 
+The scheme may be omitted (`service-player.api.svc.cluster.local:9000`), matching how
+the deploy sets the other service URLs; `http://` is assumed.
+
+Calls carry the projected workload token from `GROUNDS_TOKEN_FILE`
+(default `/var/run/secrets/grounds/token`). With no token file present — local dev
+against a service running `grounds.auth.enabled=false` — requests go out unauthenticated.
+
 Optional heartbeat configuration:
 
 ```bash

common/build.gradle.kts

@@ -1,17 +1,9 @@
-plugins { id("gg.grounds.grpc-conventions") }
-
-repositories {
-    maven {
-        url = uri("https://maven.pkg.github.com/groundsgg/*")
-        credentials {
-            username = providers.gradleProperty("github.user").get()
-            password = providers.gradleProperty("github.token").get()
-        }
-    }
-}
+plugins { id("gg.grounds.kotlin-conventions") }
 
 dependencies {
-    protobuf("gg.grounds:library-grpc-contracts-player:0.7.0")
+    // service-player is reached over HTTP now: the JDK's own client, and Jackson for the bodies —
+    // the same pair ForgeLinkClient already uses, so nothing new lands in the shaded jar.
+    implementation("tools.jackson.core:jackson-databind:3.0.4")
 
     testImplementation("org.junit.jupiter:junit-jupiter-api:5.13.4")
     testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine:5.13.4")