wtclaude
4878b74e09
R10's leg B: identity, and the half of R2 a player is allowed to see. Every route this calls existed and answered before a line of Kotlin was written, except the entitlement read, which is this phase's one website change. **One drawer row under the player group, shaped like `CharactersScreen` one game along**: the code card first, then what the code got them. A link is fleet-wide, so it is not a tab under one server — a Steam account is one person wherever they play, while stats are per server and per wipe. **Gated on `rust`, not on `identity`.** The module declares a surface word per feature, and D16's rule is that a capability answers one question — *is the module there*. `MenuAccess.PLAYER` is `isPlayer || isStaff`, which is right here: `/player/rust/*` is `requireAuth` with no role above it, and staff play the game too. **Two reads, neither blocking the other.** An entitlement is authored against the website account, so it exists before a Steam id does — the person who has just been given something and has not linked yet is exactly the one who needs both halves at once, and a failure on either leaves the other standing. **The four refusals stay four pieces of advice.** 400 is a spent code, 409 is a Steam account another account holds (`/unlink` in game releases it), 429 is the limiter, and 503 is a server that could not be reached — where the code is still good, so it may not say "get a new one". A player told otherwise goes back to the same unreachable server for another code. The app does no scope arithmetic: `*` never reaches a screen. Each entry arrives with its servers already resolved and each marked, because a second implementation of `inScope` is a second thing to keep true. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PMH6bw1jXMgbyF3ZWGEzSM
Runic Gateway — Android app
A native Android client for a Runic Gateway shard's public site + player self-service. It is
purely an API client of the website backend — it never talks to the link/ sidecar or the game
shard directly, and it ships none of the shard/sidecar wiring. It surfaces the same content and
player features as the website's browser client, minus every administrative/management console.
The authoritative design contract is docs/android/PLAN.md
in the RunicGateway/docs repo. The authoritative API reference is the committed OpenAPI spec at
website/server/swagger/swagger-output.json.
Status
M0 — repo scaffold. Gradle + Compose + Hilt skeleton with CI (lint + unit test + debug build). The functional Kotlin pass (M1–M4) and the design pass (M5) follow — see the plan's milestones (§9).
Stack
| Concern | Choice |
|---|---|
| Language / UI | Kotlin + Jetpack Compose (Material 3) |
| Navigation | Navigation-Compose, single-activity |
| HTTP | Retrofit + OkHttp, kotlinx.serialization |
| Async | Coroutines + Flow |
| DI | Hilt |
| Prefs / base URL | Jetpack DataStore |
| Tokens at rest | EncryptedSharedPreferences |
| Images | Coil |
| Min SDK | Android 10 (API 29) |
| Target / compile SDK | 35 |
Dependency and plugin versions are pinned in gradle/libs.versions.toml.
Build
Requires JDK 17 and the Android SDK (ANDROID_HOME / local.properties).
./gradlew assembleDebug # build a debug APK -> app/build/outputs/apk/debug/
./gradlew test # JVM unit tests
./gradlew lint # Android lint
./gradlew installDebug # install on a connected device/emulator
The app self-configures its server URL on first run (PLAN.md §3), so a single build works against any shard's website — there is no compiled-in API host.
CI
.gitea/workflows/pr-checks.yml gates PRs into main and edge with
./gradlew lint test assembleDebug on the org's self-hosted runner (JDK 17 + Android SDK). Debug
builds are auto-signed, so the gate needs no secrets. This pipeline is verified green end-to-end on
the runner (M0). A signed release APK attached to a Gitea release comes at M6.
edge is in the trigger deliberately: a workstream that lands its phases on a working branch
before one cutover PR into main otherwise gets no CI at all until the cutover — which is what
happened to all nine M12 phase PRs (docs/website/ENGAGEMENT.md §7.1 Q8). sonarqube.yml is
unaffected: it is a push-on-main analysis, not a PR gate.
The workflow carries a few runner-specific accommodations (each explained in comments in the file), because this self-hosted runner differs from a stock GitHub runner:
- JDK 17 is installed via
apt(notactions/setup-java) — the runner can't resolveapi.adoptium.net, while the Ubuntu mirrors are reachable. - SDK packages are installed explicitly via
sdkmanager, withset +o pipefailsoyesdying ofSIGPIPEdoesn't fail the step. gradlewischmod +x'd in the run step — the runner's checkout does not preserve the git executable bit, so./gradlewalone fails with "Permission denied".
Contributing
See CONTRIBUTING.md. AI-assisted contributions must be disclosed (org
policy): tick the PR box naming the tool and add a Co-Authored-By trailer to AI-authored commits.
Licensed GPL-3.0-or-later.