[Docs] Update frontend architecture doc for wallet abstraction layer

[collinsezedike]

Summary

apps/docs/architecture/frontend.md still describes wallet connection as calling connectFreighter() directly. That function no longer exists in the codebase.

Motivation

The feat(web): extract wallet abstraction layer from Freighter flow commit replaced direct Freighter calls with a WalletAdapter interface (apps/web/src/lib/wallet.ts). useWalletConnect now calls wallet.connect() against a FreighterWallet implementation of that interface. No doc anywhere mentions this abstraction, so the architecture doc is both factually wrong (connectFreighter() doesn't exist) and missing the part of the design that matters most: this is exactly the seam the queued multi-wallet issues (xBull, LOBSTR) are meant to plug into.

Proposed Solution

Update the "Wallet store" section of frontend.md to describe the actual flow: useWalletConnect calls wallet.connect()/wallet.isInstalled()/wallet.isAuthorized() against the WalletAdapter interface, currently implemented only by FreighterWallet. Briefly note that adding a wallet means adding a new WalletAdapter implementation and selecting it, not touching callers.

Scope

Field	Value
Area	Docs
Protocol affected	None
Network	both
Breaking change?	No

Alternatives Considered

None, this is a factual correction plus a missing-content gap, not a design decision.

Acceptance Criteria

• frontend.md's wallet section reflects wallet.connect() via WalletAdapter, not connectFreighter()
• Briefly documents the WalletAdapter interface and how a new wallet gets added
• No remaining doc references to connectFreighter()

Additional Context

Found while auditing docs for staleness after recent PR/issue activity. connectFreighter() is confirmed absent from apps/web/src entirely, replaced by apps/web/src/lib/wallet.ts's WalletAdapter/FreighterWallet.

[GazzyLee]

I’d be happy to take this on. I’ll update the frontend architecture docs to reflect the current WalletAdapter flow, document how useWalletConnect interacts with the adapter, and explain how new wallet implementations can plug into the abstraction without changing callers. I’ll also remove any remaining stale connectFreighter() references.

[collinsezedike]

Go for it, @GazzyLee

[grantfox-oss]

🦊 GrantFox — @GazzyLee has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #521)
2. Your PR will be reviewed by the drydocs maintainers

Good luck! Track your progress on GrantFox.