@naculus/connect-appkit-vue 0.2.3 → 0.2.5

package/README.md

@@ -1,13 +1,19 @@
 # @naculus/connect-appkit-vue
 
-**Vue component wrappers for Naculus Connect Web Components** — auto-generated Vue proxies for all 24 Stencil components. Use `<connect-button>`, `<wallet-modal>`, etc. directly in Vue templates.
+**Vue component wrappers for Naculus Connect Web Components** — auto-generated Vue proxies for all 28 Stencil components. Use `<connect-button>`, `<wallet-modal>`, etc. directly in Vue templates.
 
-> **Components have parity with React. Composables do not.** All 24 components
+> **Components have parity with React. Composables do not.** All 28 components
 > are generated from the same Stencil source, so anything visual works the same
-> in both. The logic layer does not: this package exports four composables —
-> `useAccounts`, `useChain`, `usePassphraseGate`, `useSolanaBalance` — against
-> React's 54, so capability negotiation, session keys, simulation and the
-> transaction lifecycle are React-only today.
+> in both. The logic layer does not: this package exports six composables —
+> `useAccounts`, `useCapabilities`, `useChain`, `usePassphraseGate`,
+> `useSolanaBalance`, `useSolanaRoles` — against React's 55, so session keys,
+> simulation and the transaction lifecycle are React-only today.
+>
+> `useCapabilities` (the EIP-5792 query) and `useSolanaRoles` (which of
+> `identity` / `signer` / `payer` the connected Solana wallet can fill) are not
+> reimplementations: both bindings call the same functions in
+> `@naculus/connect-appkit-core`, so "absence is not a denial" cannot mean one
+> thing in React and another here.
 >
 > This is said here rather than discovered later. The table below lists both
 > packages at the same version, which is true of the release and not of the