fix(examples): keep wallet connect retryable after rejection

[omerbek]

Summary

• keep EVM and Solana provider candidates local until wallet permission and account discovery succeed
• restore disconnected provider and action-button state when a connection attempt fails, allowing users to retry without reloading
• add focused connection helpers and regression tests across the send, swap, EVM bridge, and Solana bridge examples

Fixes #6.

Testing

• cd app-kit-send && npm test && npm run build
• cd app-kit-swap && npm test && npm run build
• cd app-kit-bridge-evm && npm test && npm run build
• cd app-kit-bridge-solana && npm test && npm run build

All 10 tests pass and all four Vite production builds complete successfully on Node.js v24.20.0.

[kutluhaneth46]

Thanks for the retryability fix — the catch path restoring provider = null / disabling the action button is the right shape.

One gap across the shared connectEvmProvider helpers (send / swap / bridge-evm / bridge-solana):

const accounts = (await provider.request({ method: "eth_accounts", ... })) as string[];
return { provider, account: accounts[0] };

If eth_accounts returns [] (or accounts[0] is otherwise missing), the helper still resolves successfully. Callers then do:

walletInfo.textContent = connection.account ?? "Connected";
sendButton.disabled = false; // or bridgeButton.disabled = false on EVM-only examples

So the UI can show a fake "Connected" state and re-enable the action with no usable account. Pre-PR code had the same accounts[0] hole, but the new helper + disabled = false makes the success path more assertive.

Suggested harden (same for Solana when address is missing):

1. Prefer the accounts array returned by eth_requestAccounts (avoid a second eth_accounts round-trip that can race empty).
2. if (!account) throw new Error("No account returned after wallet permission"); so the existing catch path keeps the button disabled.

Happy to re-review once that lands.

[omerbek]

Good point. I pushed cc3debd to cover that path as part of this PR.

The EVM helpers now use the account list returned by eth_requestAccounts and throw if it is empty, so the existing catch path keeps the UI disabled instead of reporting a usable connection. I also added the same missing-address guard for the Solana helper.

Verified locally with Node 22.12.0:

• app-kit-send: vitest run, tsc, vite build
• app-kit-swap: vitest run, tsc, vite build
• app-kit-bridge-evm: vitest run, tsc, vite build
• app-kit-bridge-solana: vitest run, tsc, vite build

[hjchen-circle]

We acknowledge the issue raised in #6, but the scope of the proposed fix goes far beyond the original issue. Closing the PR. The issue is resolved in #9