authjs-knowledge-patch

# Auth.js Knowledge Patch Use this patch to choose the maintained authentication path, avoid security-sensitive provider mistakes, and apply current Auth.js integration patterns. Read the topic reference before changing an affected flow; the quick reference below prioritizes breaking behavior, security updates, and common implementation work. ## Reference index | Reference | Topics | | --- | --- | | [Better Auth transition](references/better-auth-transition.md) | Project status, choosing Auth.js or Better Auth, migration direction | | [Providers and authentication](references/providers-and-authentication.md) | Account linking, credentials errors, email providers, passkeys, OAuth customization, redirect proxies | | [Sessions and frameworks](references/sessions-and-frameworks.md) | Session lifecycle, Qwik, SvelteKit, Express | | [v5 migration](references/v5-migration.md) | Next.js Pages Router limitations, Next.js 16 proxy protection | | [Adapters, operations, and security](references/adapters-operations-and-security.md) | Adapter contracts, value normalization, logging, security upgrade floors | ## Decide between Auth.js and Better Auth - Prefer Better Auth for a new project. - Keep Auth.js for an existing application that needs continued security and urgent fixes, or when Better Auth still lacks a required capability such as stateless sessions without a database. - Use the NextAuth migration guide when moving an existing application to Better Auth. - Read [Better Auth tr...