[Wave 6 6/10] Frontend order recovery from coordinator API after reload

[karagozemin]

Summary

Add frontend order recovery from the coordinator API so pending/refundable swaps survive page reloads instead of relying only on local UI state.

Context

• The frontend has refund UI and transaction history components, but recovery across reloads depends on what the browser still knows.
• The coordinator persists order state and is the right source for reconstructing pending/refundable swaps.
• This improves the core safety promise: users can return later and still see how to claim or refund.

Scope

• Add a small frontend service/hook to fetch orders for the connected Ethereum/Stellar addresses from the coordinator.
• Merge recovered orders into TransactionHistory without duplicating locally created orders.
• Surface refundable status into RefundDialog when the recovered order has enough on-chain metadata.
• Add tests for reload/recovery and duplicate suppression.

Acceptance criteria

• After reconnecting a wallet, the frontend requests relevant coordinator orders and renders them in transaction history.
• Recovered orders with expired timelocks expose the refund action when the contract/order id is known.
• Local pending orders and recovered orders are de-duplicated by hashlock/order id/tx hash.
• Frontend tests cover successful recovery and coordinator failure fallback.

Pointers

• frontend/src/components/TransactionHistory.tsx
• frontend/src/features/refund/RefundDialog.tsx
• frontend/src/lib/sdk-context.ts
• frontend/src/lib/useNetworkMode.ts
• coordinator/src/server/routes/orders.ts
• packages/sdk/src/types/index.ts

Complexity

Medium (frontend state + API integration)

[BuddiBisong]

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

i can work on this front end issue and deliver a good result

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

[drips-wave]

Congratulations, @BuddiBisong! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @BuddiBisong: 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 🌊