wtclaude
b0117acac1
The app has been reading exactly one field of the website's admin theming contract -- brand.accent. This lands the store the rest of M12 builds on: GET /public/settings' `theme` (the resolved token map) and `nav_public` (the raw nav override row) are now decoded, coerced and held beside the brand as one SiteAppearance, refreshed on resume alongside the session re-validation. Nothing reads the two new fields yet. Phase 0's hard rule is that it must change nothing on screen, so RunicApp still takes `brand: BrandDto?` and the theme is still seeded from the accent alone; AppState.Ready is the only place a type changed. Two judgement calls, both in service of THEMING_AND_NAV.md section 2's forgiving-on-read rule: - `theme` is modeled as a raw JsonElement rather than Map<String,String>?. kotlinx fails the decode of the whole object on a value of an unexpected kind, and `theme` shares its payload with `brand` and `push` -- one odd token would have blanked the branding and dropped the push relay URL. It is coerced field-by-field instead, so a bad token costs exactly itself. - A failed *refresh* keeps the last good appearance rather than falling back to NONE. Only the initial load can produce NONE, so a moment of no connectivity on resume cannot repaint a themed shard back to the defaults. The second-stage parse stops at "is this a plain object", mirroring the web client's lib/settingsJson.js exactly; reading items/sections/links out of it is phases 5 and 6's job, so no half-built nav model ships here. Tests: SettingsJsonTest (6) and SiteAppearanceTest (8) cover the two pure modules, plus three decode cases in PublicDtoTest for the wire shapes. 360 unit tests green; lintDebug and assembleDebug clean. Co-Authored-By: Claude <noreply@anthropic.com>
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 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.
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.