[2026 Wallet] Exercise hardware-wallet builds and mocks in CI

[Nanle-code]

Objective

Compile optional backends and test device approval, rejection, disconnect, and unsupported envelopes.

Target area

hardware-wallet feature and integration tests

Acceptance criteria

• The objective is implemented with clear handling for invalid input, unsupported environments, and failure paths.
• Automated tests cover the primary flow, at least one boundary case, and at least one failure case.
• User-facing documentation or developer guidance is updated, including compatibility, security, or migration notes where applicable.

Source: .github/roadmap-issues-2026-07-29.json.

[TheWeirdDee]

@TheWeirdDee has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on this issue. I’m interested in strengthening StarForge’s hardware-wallet support by exercising the optional backend in CI and making the device interaction paths deterministic and well-tested.

My approach would be to first inspect the existing hardware-wallet feature flags, abstractions, and integration-test patterns, then add mocks covering approval, rejection, disconnects, unsupported transaction envelopes, and invalid inputs. I’ll ensure unsupported environments fail gracefully rather than making CI dependent on physical hardware.

I’ll also add the necessary CI coverage for the optional backend, document the expected hardware-wallet capabilities and failure modes, and verify that existing default builds and tests remain unaffected. The implementation will include primary, boundary, and failure-path tests and preserve the repository’s existing lint and security checks.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @TheWeirdDee to this issue.

[drips-wave]

Congratulations, @TheWeirdDee! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @TheWeirdDee: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[TheWeirdDee]

Fixed in #759.

[TheWeirdDee]

Opened #759 to address this — adds a dedicated CI job that builds and tests the hardware-wallet feature (Ledger + Trezor), plus coverage for approval, rejection, disconnect, and unsupported-envelope handling. I don't have close permissions on this repo, so this will auto-close once the PR merges (it includes Closes #666).