feat(SorobanScreen): last-used contract not pre-filled, no saved contracts dropdown, no Open in Stellar Expert link for contract

[k-deejah]

Problem

1. SorobanScreen has no persistent contract ID between sessions — closing the browser clears the last-used contract ID. With the localStorage history from issue b38 (contracts list), the most recently used contract ID should be pre-filled on mount.

2. SorobanScreen has no way to switch between multiple saved contracts — the localStorage history stores up to 5 contract IDs but the only way to use them is via the datalist suggestion in the input. A "Saved Contracts" sidebar panel or dropdown that directly sets the active contract ID would be more convenient.

3. SorobanScreen has no "Open in Stellar Expert" link for the current contract — after entering a contract ID, users have no one-click path to view the contract on the block explorer.

Solution

1. On mount, pre-fill contractId from localStorage["sorokit-recent-contracts"][0] if available.
2. Add a "Saved Contracts" dropdown below the Contract ID input listing the 5 recent IDs; clicking one sets it as the current contract.
3. Add an "Open in Stellar Expert" icon link next to the Contract ID input when contractId.trim() is non-empty.

Acceptance Criteria

• Last-used contract ID is pre-filled on mount
• "Saved Contracts" dropdown lists and applies saved contract IDs
• "Open in Stellar Expert" link appears for non-empty contract IDs
• npm run build passes

---

Note for Contributors: Write a clear PR description. Include a screenshot of the saved contracts dropdown and the Stellar Expert link.

[oscar24357]

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

hello boss, good morning, can you please assign me this issue

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

[khaleedadedotun-collab]

@khaleedadedotun-collab has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

i would like to work on this issue immediately.

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

[BernardOnuh]

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

Hello, I am interested in resolving this task. I have analyzed the requirements and mapped out an efficient path forward for execution. Please assign the issue to me if it is still open, and I will get started right away.

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

[Caneryy]

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

Hello, please can I work on this issue?

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

[drips-wave]

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

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