# unknown > LutherHeggs Android Client (Agent Ready Specification) 1. Purpose This document defines the required skills, constraints, architectural rules, and operational boundaries for any coding agent contributing to the LutherHeggs Android frontend. The agent must follow this specification exactly. No deviations, reinterpretations, or architectural drift are permitted. The Android client integrates with two backend microservices: • Security Service — identity, authentication, token issuance, token rot... - Author: metadzin - Repository: metadzin/lutherheggs_frontend - Version: 20260208092754 - Stars: 0 - Forks: 0 - Last Updated: 2026-02-08 - Source: https://github.com/metadzin/lutherheggs_frontend - Web: https://mule.run/skillshub/@@metadzin/lutherheggs_frontend~unknown:20260208092754 --- # LutherHeggs Android This repository contains the LutherHeggs Android app. CI — Unit Tests The project includes a GitHub Actions workflow that runs JVM unit tests on push and pull requests to main/master/develop. The workflow is located at `.github/workflows/android-unit-tests.yml`. Workflow status badge:

[![Android Unit Tests](https://github.com/metadzin/lutherheggs_frontend/actions/workflows/android-unit-tests.yml/badge.svg)](https://github.com/metadzin/lutherheggs_frontend/actions/workflows/android-unit-tests.yml) This badge shows the status of the `android-unit-tests.yml` workflow (JVM unit tests). Click the badge to view recent workflow runs and test results. How to run tests locally - Run unit tests: ``` ./gradlew :app:testDebugUnitTest ``` Notes - The tests currently use an in-memory stack (InMemoryTokenStore, InMemoryAuthRepository, etc.) so unit tests are fast and do not require network. - When you have a working Gradle environment (your earlier TLS/network issue resolved), the CI workflow and local tests will retrieve dependencies automatically. If you want, I can update the badge URL to a different repo path or add a README section with the CI status badge and build matrix.