docs: refresh hw journeys

Author: ovitrif

journeys/hardware-wallet/README.md

@@ -14,14 +14,19 @@ The Bridge transport is HTTP (`TrezorBridgeTransport` → `http://127.0.0.1:2132
 - **Reliably simulated**: the device itself (deterministic seed and label), the full
   wallet protocol (scan, connect, features, xpubs, watchers, signing), and therefore all
   home-screen UI behavior: tiles, balances, activity, indicators, sheets. This includes the
-  Connect Hardware flow's Searching → Found → Paired steps (the device pairs without a code).
+  Connect Hardware flow's Intro → Searching → Found → Paired steps (the Bridge device pairs
+  without the inline pair-code step).
 - **Partially simulated**: the USB attach → auto-reconnect chain. The OS-level attach
   intent can be injected with `am start -a android.hardware.usb.action.USB_DEVICE_ATTACHED`,
-  which drives the full in-app path (MainActivity → AppViewModel → reconnect loop), with
-  the Bridge standing in for the transport.
+  which drives the in-app reconnect path (MainActivity → AppViewModel → reconnect loop), with
+  the Bridge standing in for the transport. A real OS chooser event with a `UsbDevice` extra
+  is still needed to verify the "Open with Bitkit" path that opens the Found Device sheet for
+  an unpaired Trezor.
 - **Not simulated**: kernel/libusbhost behavior, USB enumeration timing, permission
-  grants, the OS app picker, and the THP one-time pairing code (the inline Pair Device step
-  of the connect flow). Those need a physical device.
+  grants, the OS app picker, BLE runtime/settings recovery, THP one-time pairing code
+  (the inline Pair Device step), and passphrase/hidden-wallet selection. Those need a physical
+  device or a dedicated emulator scenario; passphrase coverage is tracked in
+  synonymdev/bitkit-android#1030.
 
 Journey steps that start with `adb:` are device commands the runner executes verbatim
 instead of UI interactions.
@@ -55,16 +60,31 @@ Remove step forgets the device.
 | Journey | Covers |
 | - | - |
 | `connect-home-tile.xml` | Dev-screen connect, home tile, indicator, balance, detail screen opens |
-| `activity-blue-icons.xml` | Hardware activity merge, blue icons, All Activity filters, detail fallback |
-| `usb-reconnect.xml` | Disconnect indicator, injected USB attach intent → silent auto-reconnect |
-| `suggestion-intro-sheet.xml` | Forget device, Hardware suggestion card, full connect flow (Searching → Found → Paired → Finish) re-pairs |
+| `activity-blue-icons.xml` | Hardware activity merge, blue icons, All Activity filters, current watch-only detail fallback |
+| `usb-reconnect.xml` | Disconnect indicator, injected USB attach intent → silent auto-reconnect; physical-device chooser path noted separately |
+| `suggestion-intro-sheet.xml` | Forget device, Hardware suggestion card, full connect flow (Intro → Searching → Found → Paired → Finish) re-pairs |
 | `connect-flow.xml` | Settings Add button → connect flow with an edited Label Funds → paired device count + name |
-| `settings-hardware-wallets.xml` | Payments count row, Hardware Wallets screen list, Add button sheet, per-row delete confirm + re-pair |
-| `detail-overview.xml` | Detail screen overview, Transfer placeholder, activity, Remove confirm + forget |
+| `settings-hardware-wallets.xml` | Payments count row, Hardware Wallets screen list, Add button sheet/back dismiss, per-row delete confirm + re-pair |
+| `detail-overview.xml` | Detail screen overview, Transfer placeholder when funded, activity, Remove confirm + forget |
 
 Connect-flow testTags: `HardwareSheet`, `HwIntroScreen`, `HwSearchingScreen`,
 `HwFoundScreen`, `HwPairedScreen`, `HwPairedLabelField`, `HwPairedFinish`,
-`HwPairScreen` (inline pair code, physical device only).
+`HwPairScreen` (inline pair code, physical device only), `HwSearchingError`, and
+`HwFoundError`.
+
+The current Connect Hardware sheet starts USB discovery immediately after Continue. BLE is
+included only once Android nearby-devices permission is granted and Bluetooth is enabled.
+The sheet has no internal back navigation; Android back dismisses the sheet.
+
+If Android shows the Nearby devices/Bluetooth runtime permission prompt after tapping
+Continue, allow it and keep waiting on the Searching step. If permission is denied, Bitkit
+should show its Bluetooth access recovery dialog with an Open Settings action; that recovery
+path is better validated on a physical device because the Bridge path can still find devices
+without BLE.
+
+Current journeys pair the standard wallet. Hidden/passphrase wallet behavior is intentionally
+not asserted here yet; it needs explicit UX and identity-scoping coverage as described in
+synonymdev/bitkit-android#1030.
 
 To exercise the received-money sheet (not covered by a journey because it needs an
 out-of-band transfer), fund the emulator wallet on regtest from `bitkit-docker`, e.g.

journeys/hardware-wallet/activity-blue-icons.xml

@@ -1,9 +1,10 @@
 <journey name="Hardware Wallet Activity Blue Icons">
   <description>
     Verifies hardware wallet on-chain activity merged into the home list and the All
-    Activity screen with blue icon variants, filter behavior, and the activity detail
-    fallback. Requires a paired Bridge emulator whose wallet has at least one on-chain
-    transaction (run connect-home-tile.xml first; fund per README.md if the
+    Activity screen with blue icon variants, filter behavior, and the current watch-only
+    activity detail fallback until Core-backed hardware activity support lands. Requires a
+    paired Bridge emulator whose wallet has at least one on-chain transaction (run
+    connect-home-tile.xml first; fund per README.md if the
     deterministic wallet has no history).
   </description>
   <actions>

journeys/hardware-wallet/connect-flow.xml

@@ -29,6 +29,9 @@
     <action>
       Verify the sheet advances to the "Connect Device" step (testTag "HwSearchingScreen") headed "Searching for devices"
     </action>
+    <action>
+      If Android shows a Nearby devices/Bluetooth permission prompt or Bluetooth enable prompt, allow it and continue waiting on the Searching step
+    </action>
     <action>
       Verify the sheet advances to the "Found Device" step (testTag "HwFoundScreen") headed "Found Trezor" within 15 seconds, then tap "Connect"
     </action>

journeys/hardware-wallet/connect-home-tile.xml

@@ -2,8 +2,8 @@
   <description>
     Pairs the Bridge Trezor emulator through the dev Trezor screen, then verifies the
     home-screen hardware wallet tile: name, connection indicator, balance, and the
-    not-yet-implemented overview notice. Requires the bitkit-docker Trezor User Env
-    running and a Bridge-enabled build (see README.md).
+    hardware wallet detail screen. Requires the bitkit-docker Trezor User Env running
+    and a Bridge-enabled build (see README.md).
   </description>
   <actions>
     <action>
@@ -40,7 +40,7 @@
       Tap the hardware wallet tile
     </action>
     <action>
-      Verify the hardware wallet detail screen opens, showing the device name with a blue bitcoin icon in the top bar and a balance header
+      Verify the hardware wallet detail screen opens (testTag "HardwareWalletScreen"), showing the device name with a blue bitcoin icon in the top bar and a balance header
     </action>
     <action>
       Navigate back to the wallet home screen

journeys/hardware-wallet/detail-overview.xml

@@ -1,10 +1,10 @@
 <journey name="Hardware Wallet Detail Overview">
   <description>
     Opens the hardware wallet detail screen from the home tile and verifies its overview:
-    the top bar, balance header, the not-yet-implemented Transfer To Spending action, the
-    grouped activity list, and the Remove device confirm dialog. The final Remove step
-    forgets the device, so run this last (re-run connect-home-tile.xml to pair again).
-    Requires a paired Bridge emulator (run connect-home-tile.xml first).
+    the top bar, balance header, the current Transfer To Spending placeholder when funds
+    are present, the grouped activity list, and the Remove device confirm dialog. The final
+    Remove step forgets the device, so run this last (re-run connect-home-tile.xml to pair
+    again). Requires a paired Bridge emulator (run connect-home-tile.xml first).
   </description>
   <actions>
     <action>
@@ -14,16 +14,16 @@
       Tap the hardware wallet tile beneath the SAVINGS and SPENDING tiles
     </action>
     <action>
-      Verify the hardware wallet detail screen opens, showing the device name with a blue bitcoin icon in the top bar and a balance header
+      Verify the hardware wallet detail screen opens (testTag "HardwareWalletScreen"), showing the device name with a blue bitcoin icon in the top bar and a balance header
     </action>
     <action>
-      If a "Transfer To Spending" button is shown, tap it and verify a notice appears saying "Transfer to spending not yet implemented.", otherwise skip this step
+      If a "Transfer To Spending" button is shown (testTag "HwTransferToSpending"), tap it and verify a notice appears saying "Transfer to spending not yet implemented.", otherwise skip this step
     </action>
     <action>
       If the activity list shows transactions, verify their circular icons are blue, then tap the first one, verify an activity detail screen opens, and navigate back
     </action>
     <action>
-      Tap the "Remove" button labelled with the device name near the bottom of the screen
+      Tap the "Remove" button labelled with the device name near the bottom of the screen (testTag "RemoveHardwareWallet")
     </action>
     <action>
       Verify a confirm dialog appears explaining that your funds are safe and your coins won't be deleted

journeys/hardware-wallet/settings-hardware-wallets.xml

@@ -21,16 +21,16 @@
       Tap the "Hardware Wallets" row
     </action>
     <action>
-      Verify the Hardware Wallets screen opens with the top bar titled "Hardware Wallets"
+      Verify the Hardware Wallets screen opens (testTag "HardwareWalletsScreen") with the top bar titled "Hardware Wallets"
     </action>
     <action>
       Verify the paired device is listed with its name, a bitcoin balance prefixed with the ₿ symbol, and a green connection indicator on the left
     </action>
     <action>
-      Tap the "Add Hardware Wallet" button near the bottom
+      Tap the "Add Hardware Wallet" button near the bottom (testTag "AddHardwareWallet")
     </action>
     <action>
-      Verify a bottom sheet opens titled "Hardware Wallet" showing Trezor and Ledger device images, then tap "Cancel" to close it
+      Verify a bottom sheet opens titled "Hardware Wallet" (testTag "HwIntroScreen") showing hardware device illustrations, then press Android back and verify the sheet closes back to the Hardware Wallets screen
     </action>
     <action>
       Tap the trash (delete) icon on the device row

journeys/hardware-wallet/suggestion-intro-sheet.xml

@@ -26,14 +26,17 @@
       Tap the "Hardware" suggestion card
     </action>
     <action>
-      Verify a bottom sheet opens titled "Hardware Wallet" showing Trezor and Ledger device images
+      Verify a bottom sheet opens titled "Hardware Wallet" (testTag "HwIntroScreen") showing hardware device illustrations
     </action>
     <action>
       Verify the headline reads "Add your hardware wallet" with the words "hardware wallet" in blue
     </action>
     <action>
       Tap the "Continue" button and verify the sheet advances to the "Connect Device" step headed "Searching for devices", showing a loading animation and a "Cancel" button
     </action>
+    <action>
+      If Android shows a Nearby devices/Bluetooth permission prompt or Bluetooth enable prompt, allow it and continue waiting on the Searching step
+    </action>
     <action>
       Verify the sheet advances to the "Found Device" step within 15 seconds, headed "Found Trezor" with a "Connect" button
     </action>

journeys/hardware-wallet/usb-reconnect.xml

@@ -3,8 +3,10 @@
     Verifies the disconnect indicator and the USB-attach auto-reconnect chain by
     injecting the OS attach intent, with the Bridge emulator standing in for the
     transport. Covers MainActivity intent handling, the serialized reconnect retry
-    loop, and the prompt-free reconnect. Requires a paired Bridge emulator (run
-    connect-home-tile.xml first).
+    loop, and the prompt-free reconnect for an already paired wallet. The unpaired
+    physical-device OS chooser path ("Open with Bitkit" → Found Device sheet) cannot
+    be fully simulated by this injected intent because it lacks a real UsbDevice extra.
+    Requires a paired Bridge emulator (run connect-home-tile.xml first).
   </description>
   <actions>
     <action>