[sdk] Add Freighter wallet auto-reconnect on page reload

[Otaiki1]

Summary

sdk/src/wallet/freighter.adapter.ts connects to the Freighter extension. After a page reload, the SDK loses the wallet connection and the user must click "Connect" again. Freighter supports an isConnected check that can be used to auto-reconnect.

What to do

1. On FreighterAdapter construction (or in connect()), call Freighter's isConnected() API.
2. If already connected, retrieve the public key and set the internal state without showing a permission prompt.
3. Emit a reconnected event on the adapter so the client's WalletProvider can update state.
4. Store the last connected wallet type (e.g. 'freighter') in localStorage and attempt auto-reconnect on AppProviders mount.
5. Write a test that simulates a page reload scenario with a pre-connected Freighter.

Acceptance criteria

• After a page reload, a previously connected Freighter wallet reconnects without user interaction.
• Auto-reconnect does not show a Freighter permission prompt.

[jethrojohn739-max]

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

Hi maintenaner, I’m a full stack developer with experience in smart contract development and modern web technologies. I’m comfortable navigating existing codebases, understanding project requirements, and following contribution guidelines. I will be glad if this issue is assigned to me.

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

[Padom2020]

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

Hi! I'd like to apply to work on this issue.
I'm a fullstack developer with over 5 years of experience, including SDK/wallet integration work and Freighter-based Stellar dApp connections. I've built highly complex production software including my ecommerce platform digemart.com, eventcrib.com, and stannscollegeddl.org, with wallet persistence and reconnect flows being part of that work.
My plan:

In FreighterAdapter construction (or connect()), call Freighter's isConnected() API to check for an existing connection before prompting the user.
If already connected, retrieve the public key directly and set internal adapter state without triggering a permission prompt.
Emit a reconnected event from the adapter so WalletProvider can update its state accordingly without a fresh connect flow.
Store the last connected wallet type ('freighter') in localStorage, and on AppProviders mount, check for that stored value and attempt auto-reconnect using the isConnected check.
Handle the edge case where localStorage says the wallet was connected but Freighter itself reports disconnected (e.g. user revoked permission externally) fall back to the normal manual connect flow rather than erroring.
Write a test simulating a page reload with a pre-connected Freighter (mocking isConnected() and localStorage state) verifying reconnect happens silently with no permission prompt.

I'll open a draft PR within 6 hours of confirming scope so maintainers can confirm the exact reconnected event contract expected by WalletProvider.
Looking forward to contributing!

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

[mc-stephen]

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

Hi, I'm familiar with this, please assign, will fix ASAP, thanks.

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

[charityzarmai]

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

Hi maintainer I can handle this issue please assign it to me thank you

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

[amankoli09]

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

Can I work on this PR merge within 1hr

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

[drips-wave]

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

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

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @charityzarmai as part of the Stellar Wave Program's 6th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor successfully implemented the auto-reconnect feature for the Freighter wallet, addressing all requirements including localStorage persistence, the isConnected check, and the necessary hook updates. The PR has been merged, and it includes comprehensive documentation and unit tests to verify the implementation.

😎 @charityzarmai: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.