test: port Android journeys to iOS

[jvsena42]

This PR:

1. Ports 28 of the 30 journeys from bitkit-android/journeys to journeys/.
2. Adds the accessibility identifiers they assert on, matching the Android testTag names.
3. Documents the XcodeBuildMCP and android CLIs for agents, and makes porting journeys part of porting an Android feature.

Description

File names, journey names and action prose are kept identical to the Android originals so the two platforms stay diffable. Only mechanics change: adb becomes xcodebuildmcp, testTags become accessibility identifiers.

Adapted where iOS genuinely differs, each noted in its own description and suite README:

• notification-permission — toggling off does not deep link into system settings on iOS, so that journey asserts what the toggle actually does and covers the real route in through Settings → Notifications.
• cjit-notifications — the notification extension maps a push type to fixed copy and never formats an amount, so the thousands-separator assertions are dropped. The duplicate and wrong-type ones port directly.
• hardware-wallet — USB reconnect becomes a Bridge reconnect, since iOS cannot do WebUSB.
• deeplinks — not ported. There is no screen or sheet router on iOS, only web URLs, Pubky callbacks and payment URIs, so these would assert a feature that does not exist. Recorded under "Not ported".

Most identifiers already matched, including the whole number pad. The gaps were screen containers, a few fields, the three background-setup switches which shared one binding and had none, and the over-max toasts on the transfer screens.

One behavioural change: widget list tiles are tap-gesture views, so the runtime snapshot never listed them as tappable. They now combine their children and carry the button trait, which also makes a tile read as one item under VoiceOver instead of separate fragments. No changelog fragment, since nothing else here is user-facing — but that part is worth a second opinion.

Trying it out

brew tap getsentry/xcodebuildmcp && brew install xcodebuildmcp
xcodebuildmcp setup          # Bitkit.xcodeproj, scheme Bitkit, Debug, iPhone 17
xcodebuildmcp simulator build-and-run

Because a journey is a shared spec, the same file can be run on Android too — AGENTS.md has the android CLI equivalents, and says to record a disagreement between the platforms rather than rewrite the journey to match.

The widgets journeys need no backend and are the quickest way to see the loop work. The rest need regtest from a sibling bitkit-docker checkout; the hardware wallet ones also need the Trezor emulator and the Bridge build, since the simulator has no Bluetooth LE. Preconditions are in each suite README.

Linked Issues/Tasks

• https://github.com/synonymdev/bitkit-android/tree/main/journeys — the source corpus
• fix: settle spending transfer maximums #686 — moves the receiving-capacity screen from rejecting an over-max keypress to snapping to the settled maximum. Whichever lands second updates the other; noted in the amount-limits README and on that PR.

Screenshot / Video

No visual changes. The only UI-affecting edit is accessibility metadata on the widget list tiles.

QA Notes

Manual Tests

You should not have to name a file. Ask for the flow and let the agent pick the journey:

• test the widgets flow
• test the send flow
• test the changes from this branch
• open a channel
• do a cross-platform payment
• check whether any journey has drifted from the code

The last one is the interesting one: a journey that no longer matches the app should come back as a failure, not be worked around.

Automated Checks

• No test targets changed, and nothing here is wired into CI: journeys are agent-evaluated and belong on the manual ai-device-tests workflow rather than a blocking gate.
• Verified on an iPhone 17 simulator while authoring: both widgets journeys plus send-amount-over-balance and transfer-spending-over-max walked end to end, and every added identifier asserted present with a deliberately bogus identifier as a control.
• swiftformat --lint reports only two pre-existing failures, in files this branch does not touch.

[greptile-apps]

Greptile Summary

The PR ports Android journey specifications to iOS and adds the accessibility identifiers needed to execute them manually.

• Adds 28 journey specifications covering amount limits, CJIT notifications, hardware wallets, notification permissions, and widgets.
• Adds shared accessibility identifiers to the corresponding SwiftUI screens and controls.
• Updates agent documentation with journey conventions and simulator tooling.
• Corrects the widget-tile accessibility state and clarifies that CJIT notification journeys require a physical device.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
Bitkit/Views/Widgets/WidgetsListSheetView.swift	Groups widget-tile accessibility content and applies the button trait only while tiles are enabled, resolving the prior accessibility finding.
journeys/cjit-notifications/README.md	Documents the physical-device and APNs requirements while explicitly distinguishing the simulator-only UI-test workflow from manual journeys.
AGENTS.md	Adds XcodeBuildMCP usage and cross-platform journey authoring and execution guidance.
Bitkit/Views/Transfer/FundManualAmountView.swift	Adds journey-facing accessibility identifiers to the amount screen, controls, and over-limit toast.
Bitkit/Views/Transfer/SpendingAdvancedView.swift	Adds accessibility identifiers for journey automation while preserving the transfer amount flow.

_{Reviews (3): Last reviewed commit: "docs: note that lsp mine is silent on su..." | Re-trigger Greptile}

[jvsena42]

This will help us review and test PRs faster and also reproduce bugs more reliably

[ovitrif]

The hardware-wallet activity-tags journey binds ActivityTag and ActivityTags to the wrong controls, so an identifier-first run can treat the Add Tag button as the chip and then miss the All Activity filter. This is iOS-only: Android's original journey does not attach those ids to those steps, and the shared app vocabulary already matches on both platforms.

[ben-kaufman]

The Swift changes build cleanly, but several journey definitions cannot run or validate the intended behavior as written. These harness issues should be corrected before merge so agents do not get deterministic false failures or false passes.

[ovitrif]

@jvsena42, I rechecked the follow-up to my identifier comment. ActivityTag, ActivityTags, and TagsPrompt now point to the intended controls and preserve Android parity, so that issue is resolved and I’m approving.

I think two pieces of guidance added here should be reconsidered before they turn every journey detail into a merge requirement. Android does not have the new iOS journeys/README.md rule that a journey is the source of truth and any disagreement means the app failed. The referenced ai-device-tests workflow is also something I added earlier; it only runs TrezorBridgeDashboardUITests and is not a journey runner. Rather than expanding that workflow, I think this PR should remove or reword the claim that journeys run there and describe journeys more modestly as agent-driven developer-assistance specs, not QA gates.

@ben-kaufman surfaced useful details, and I appreciate the care behind them, but I would triage them against Android before making them blockers: fix iOS-specific mistakes introduced by the port, preserve or document inherited Android limitations, and leave broader runner or hardening work for separate follow-ups. That keeps this PR focused on Android parity without dismissing the review.

[jvsena42]

Draft for check all comments

[jvsena42]

Reframed the journeys as developer-assistance specs instead of source of true

[jvsena42]

• Reframed the journeys as developer-assistance specs instead of source of true
• Asked the agent to re-run all journeys searching and fixing issues like Ben found
• Added the instruction for using Bitkit-android LSP skill and tested it