docs: make readme trezor testing entrypoint

List Android and iOS Trezor emulator checks directly in README so Bitkit app PR testing starts there.

Add root AGENTS.md guidance to keep actionable test workflows in README.

Author: ovitrif

AGENTS.md

@@ -0,0 +1,7 @@
+# Agent Notes
+
+## Bitkit App Testing Docs
+
+- Treat `README.md` as the entry point for testing Bitkit app PRs and merged features.
+- When adding or changing test workflows, keep the actionable setup and check steps in `README.md`, not only in supporting docs.
+- Supporting docs such as `docs/trezor-emulator.md` may contain deeper internals and troubleshooting, but README must remain enough to run the test flow.

CHANGELOG.md

@@ -8,6 +8,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
 
 ### Changed
+- Expand README Trezor testing guidance with separate Bitkit Android and Bitkit iOS checklists
 - Show ready-to-copy settle and cancel commands in `holdinvoice` output
 - Simplify LND funding step in README to a single command instead of clipboard-based two-step flow
 
@@ -16,6 +17,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Preserve LNURL-pay invoice millisatoshi precision by creating invoices with LND `value_msat` instead of truncating callback amounts to sats
 
 ### Added
+- Root `AGENTS.md` reminder to keep README as the Bitkit app testing entry point
 - Trezor User Env Docker service and `scripts/trezor-emulator` helper for quickly smoke-testing Bitkit app Trezor PRs
 - Trezor emulator PR-check documentation in `docs/trezor-emulator.md`
 - Support `amount_msat` query param in `/generate/bolt11` endpoint for sub-sat precision invoices

README.md

@@ -167,30 +167,59 @@ docker compose logs -f bitcoind
 
 #### Trezor Hardware PRs
 
-Use the bundled Trezor User Env helper when checking Bitkit app PRs that need the official Trezor emulator:
+Use this section as the entry point when checking Bitkit app PRs or merged features that need the official Trezor emulator. Start by preparing the deterministic Trezor User Env:
 
 ```bash
 ./scripts/trezor-emulator start
 ```
 
 The macOS Trezor User Env service is included in the default `docker compose up -d` stack. The helper starts or reuses that service, then resets Bridge and the emulator into the deterministic review state. Linux users can start the host-network service with `docker compose --profile trezor-linux up -d trezor-user-env-linux`.
 
-For Bitkit Android on a physical phone:
+The helper starts the official Trezor User Env without its regtest stack, launches Bridge, wipes a deterministic T2T1 emulator, and sets it up with the `all all ...` seed and `Bitkit Test Trezor` label. It uses `scripts/trezor-controller.py` inside the container to talk to the User Env websocket controller.
+
+##### Bitkit Android
+
+For a physical phone, reverse the Bridge port and install the dev build with Bridge enabled:
 
 ```bash
 ./scripts/trezor-emulator adb
 TREZOR_BRIDGE=true TREZOR_BRIDGE_URL=http://127.0.0.1:21325 ./gradlew installDevDebug
 ```
 
-For Bitkit Android on an emulator:
+For an Android emulator, install with the emulator host Bridge URL:
 
 ```bash
 TREZOR_BRIDGE=true TREZOR_BRIDGE_URL=http://10.0.2.2:21325 ./gradlew installDevDebug
 ```
 
-For Bitkit iOS, run the relevant Trezor branch from Xcode and open `Settings -> Advanced -> Trezor Hardware Wallet`.
+Open the dashboard at `Settings -> Advanced -> Dev Settings -> Trezor`, then check:
+
+- Scan shows the Bridge emulator device
+- Connect succeeds and device features are shown
+- Get address succeeds
+- Get public key succeeds
+- Sign and verify message succeed
+- Send or compose reaches the expected funded or no-funds state
+- Disconnect, reconnect, and forget-device cleanup behave correctly
+
+##### Bitkit iOS
+
+Run the relevant Trezor branch from Xcode. The User Env dashboard and Bridge are available on the host at:
+
+- User Env dashboard: `http://localhost:9002`
+- Trezor Bridge: `http://localhost:21325`
+
+Open the dashboard at `Settings -> Advanced -> Trezor Hardware Wallet`, then check:
+
+- Scan shows the Bridge emulator device
+- Connect succeeds and device features are shown
+- Get address succeeds
+- Get public key succeeds
+- Sign and verify message succeed
+- Send or compose reaches the expected funded or no-funds state
+- Disconnect, reconnect, and forget-device cleanup behave correctly
 
-The helper starts the official Trezor User Env without its regtest stack, launches Bridge, wipes a deterministic T2T1 emulator, and sets it up with the `all all ...` seed and `Bitkit Test Trezor` label. It uses `scripts/trezor-controller.py` inside the container to talk to the User Env websocket controller. See [docs/trezor-emulator.md](docs/trezor-emulator.md) for the smoke checklist, helper internals, and troubleshooting commands.
+See [docs/trezor-emulator.md](docs/trezor-emulator.md) for helper internals, environment overrides, and troubleshooting commands.
 
 #### Bech32 LNURL Pay