@txnlab/use-wallet-passkey derives a post-quantum (Falcon-1024) Algorand
account from a passkey's WebAuthn PRF output, so users need no extension,
app or seed phrase.

- connect() signs in with an existing passkey; connect({ create: true })
  creates one, then evaluates the PRF scoped to it
- Derivation: entropy = PRF output for a frozen per-context label; the
  keygen seed is SHA-512/256("PQK" || "f1" || entropy), as in algokey pq,
  algosdk, Lute and Pera, so the exported 25-word phrase restores the
  same account (pinned by the ARC-76 vectors)
- Every PRF ceremony uses userVerification: 'required'; a credential or
  derived key that doesn't match the stored account fails closed
- The private key lives in a dedicated worker started from a Blob URL
  (inlined at build time, so bundlers need no config); without session it
  is dropped after every request, with session it stays until an idle
  timeout and confirm chooses silent, presence or verify per request
- signTransactions signs with a pqsig; signData supports ARC-60 with
  scheme falcon-1024-det; exportRecoveryPhrase returns the phrase after a
  fresh verified ceremony; only public data is persisted
- Examples: register passkey({ session: true }) and a "Create passkey"
  button in all seven; the React example adds a recovery phrase panel
- e2e: create, sign, authenticate, sign in again and resume, against a
  Chromium virtual authenticator with PRF
- Docs: README, supported wallets, installation and the useWalletManager
  examples

Framework hooks return plain wallet objects, so reaching an adapter's own
methods (manager.getWallet(walletKey), cast to the adapter's type) needs
the WalletManager. Solid and Svelte already export useWalletManager.

- React: useWalletManager() returns the manager from WalletProvider and
  throws "useWalletManager must be used within the WalletProvider"
  outside it
- Vue: useWalletManager() injects the manager installed by
  WalletManagerPlugin and throws "WalletManager plugin is not properly
  installed" without it; useWallet and useNetwork now use it, with the
  same error
- Test both: same instance as the provider/plugin, and the error
- Docs: add a useWalletManager API reference page and a short section
  in each framework guide