Update documentation for web app, testing, and commit guidelines.

Update `README.md` to list `webApp` under top-level repository components with
a reference link to `webApp/README.md`, update tech stack description to
Kotlin/JS, React, and Tailwind CSS, and add dedicated sections for running the
Android app and running tests across all modules.

Update commit guidelines in `README.md` and `AGENTS.md` to specify line break
guidelines and the 80-character maximum line length requirement (with
exceptions to avoid breaking hyperlinks). Add references to `CODING-STYLE.md`
and `DEVELOPER-MODE.md`.

Test: Manually verified rendered Markdown in `README.md` and `AGENTS.md`.
Signed-off-by: David Zeuthen <zeuthen@gmail.com>

Author: davidz25

AGENTS.md

@@ -3,7 +3,7 @@
 ## 1. Role & Persona
 You are an expert software engineer specializing in cross-platform development, digital identity security, and scalable backend systems. You write concise, idiomatic, and production-ready code. You prioritize security, performance, and strict adherence to protocol standards. When you don't know something, you say so rather than hallucinating APIs.
 
-You should also be familiar with the project's [README.md](README.md) file.
+You should also be familiar with the project's [README.md](README.md), [CODING-STYLE.md](CODING-STYLE.md), and [DEVELOPER-MODE.md](DEVELOPER-MODE.md) files.
 
 ## 2. Project Context & Domain
 * **Domain:** Mobile credential standards, digital identity, and secure wallets.
@@ -56,6 +56,7 @@ The following rules apply when being asked to generate a commit.
 * The commit message should detail the changes being committed, not all the prompts that led to here. This includes changes to the source that was done by others, for example the human driving the AI.
 * Commit messages must be detailed and to the point. If referring to classes or types in the project enclose it in backticks, if referring to function or method names use trailing open and close parenthesis.
 * First line of the commit message must end in a period and be no longer than 72 characters and should avoid using type or function names.
+* Commit messages should use line breaks and lines should not be larger than 80 characters, with exceptions to avoid breaking hyperlinks.
 * Commit messages must have a "Test:" stanza detailing how the change was tested.
 * Commit messages have a Signed-off-by line.
 

README.md

@@ -7,6 +7,7 @@ This repository contains code for the Multipaz Wallet application
   frontend apps.
 - `androidApp` is the Android wallet client, using Jetpack Compose.
 - `iosApp` is the iOS wallet client, using SwiftUI.
+- `webApp` is the Web wallet client, using Kotlin/JS, React, and Tailwind CSS (see [webApp/README.md](webApp/README.md)).
 - `backend` is the wallet backend.
 
 ## What is Multipaz?
@@ -78,6 +79,14 @@ Set wallet backend.
 Multipaz Wallet includes a built-in Developer Mode for testing, debugging, and advanced configuration.
 For full details on enabling Developer Mode and all available options, see [DEVELOPER-MODE.md](DEVELOPER-MODE.md).
 
+## Running the Android app
+
+To build the Android app debug APK:
+```bash
+./gradlew :androidApp:assembleDebug
+```
+You can also open the repository root in Android Studio, select the `androidApp` run configuration, and run it on an emulator or physical device.
+
 ## Running the iOS app
 
 To run the iOS app, first you need to build the XCFramework, like this
@@ -93,15 +102,30 @@ You need to do these steps every time code in `shared/` is changed or when updat
 Multipaz version. Since building the framework is a time-consuming step (~10 minutes) changes
 to `shared/` are normally tested with the Android app, Web App, or unit tests first.
 
+## Running Tests
+
+To run unit and integration tests across the project modules:
+
+- **Shared Core:** `./gradlew :shared:allTests`
+- **Backend:** `./gradlew :backend:test`
+- **Android App:** `./gradlew :androidApp:testDebugUnitTest`
+- **Web App:** `./gradlew :webApp:jsBrowserTest`
+- **iOS App:** `xcodebuild -project iosApp/iosApp.xcodeproj -scheme iosApp -sdk iphonesimulator test`
+
 ## Contributions
 
+Please follow the coding style guidelines in [CODING-STYLE.md](CODING-STYLE.md).
+
 Commit messages must be detailed and to the point. If referring to classes or types in the
 project enclose it in backticks, if referring to function or method names use trailing
 open and close parenthesis.
 
 First line of the commit message must end in a period and be no longer than 72 characters
 and should avoid using type or function names.
 
+Commit messages should use line breaks and lines should not be larger than 80 characters,
+with exceptions to avoid breaking hyperlinks.
+
 Commit messages must have a "Test:" stanza detailing how the change was tested.
 
 Commit messages have a Signed-off-by line.