Document how a dApp detects a wallet's in-app browser and connects directly

[briwylde08]

A dApp opened inside a wallet's in-app browser can connect to that wallet directly and skip the wallet picker, but this is undocumented. Freighter mobile injects window.stellar.provider === 'freighter'; builders discover it by trial and error. freighter-mobile PRs #1000–#1002 (in-app WebView provider, silent SEP-10 login) would extend this.

Please add a short, wallet-neutral page in the wallet-integration docs:

• how to detect the in-wallet context;
• how to connect without a picker, with a copy-paste snippet;
• a note that a cross-network connection protocol has been proposed and may supersede this.

Surfaced by Frontier Lab's ecosystem crawl.

[legend4tech]

Hey @briwylde08 , I'd love to take this issue on

I have a solid background in frontend development and I can definitely see how the redundant wallet picker creates a frustrating UX when already inside an in-app browser.

I can put together a clean, wallet-neutral docs page that covers:

1. The logic for detecting the in-wallet context (e.g., checking window.stellar.provider).
2. A straightforward, copy-paste snippet for bypassing the picker and connecting silently.
3. A note regarding the proposed cross-network connection protocol so developers know the standard may evolve.

Let me know if I can get this assigned to me, and I'll get a PR up