refactor(auth)!: split session state from client actions

[onmax]

This is a breaking cleanup for the Pinia issue found while testing #295.

useUserSession() now returns only session state and session lifecycle actions, so it can be returned directly from Pinia setup stores without forwarding Better Auth's dynamic client proxies through store state.

Auth calls move to explicit composables (which is much better dx overall!):

const signInEmail = useSignIn('email')
const signUpEmail = useSignUp('email')
const client = useAuthClient()
const sendVerificationEmail = useAuthClientAction(client => client.sendVerificationEmail)

Old patterns like these no longer work:

const { signIn, signUp, client } = useUserSession()
userStore.signIn.email(...)
userStore.authClient.sendVerificationEmail(...)

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/maximogarciamartinezs-projects?upgradeToPro=build-rate-limit

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@onmax/nuxt-better-auth@339

commit: bef644a

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	better-auth	bef644a	May 06 2026, 02:10 PM

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nuxt-better-auth-docs	Ready	Preview, Comment	May 6, 2026 1:51pm

[jd-solanki]

This new API seems a bit weird to me:

const signInEmail = useSignIn('email')
const signUpEmail = useSignUp('email')
const client = useAuthClient()
const sendVerificationEmail = useAuthClientAction(client => client.sendVerificationEmail)

Isn't possible to have guessable API like:

auth.signUp.email
auth.signOut