@beignet/provider-auth-better-auth 0.0.20 → 0.0.22

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @beignet/provider-auth-better-auth
 
+## 0.0.22
+
+### Patch Changes
+
+- Normalize provider README setup guidance across first-party provider packages.
+
+## 0.0.21
+
 ## 0.0.20
 
 ## 0.0.19

package/README.md

@@ -249,6 +249,18 @@ request once with
 then call an app-owned helper such as `requireUser(ctx)` instead of depending
 on the raw request.
 
+`beignet doctor --strict` checks that installed Better Auth providers are
+registered in `server/providers.ts`. The provider does not declare Beignet-owned
+env vars because Better Auth configuration, secrets, database adapter options,
+and social provider credentials stay in your app's Better Auth setup.
+
+## Installed ports
+
+The provider contributes `ctx.ports.auth`, the standard Beignet `AuthPort`.
+It does not expose a Better Auth escape hatch; route handlers that need
+provider-native auth flows should mount Better Auth's own routes separately,
+usually under `app/api/auth/[...all]/route.ts`.
+
 ## Devtools
 
 When `@beignet/devtools` is installed before this provider, auth checks
@@ -259,6 +271,25 @@ The provider records `auth.getSession`, `auth.getUser`, and
 duration. User and session objects are not recorded. Provider failures are
 recorded with `.failed` event names and the original error is rethrown.
 
+## Failure behavior
+
+Unauthenticated `requireUser(...)` calls throw `AuthUnauthorizedError`, which
+the Beignet server maps to a framework-owned `401` response. Better Auth
+session lookup or route errors are rethrown so hooks and server error handling
+can report them consistently.
+
+## Local and tests
+
+Use an app-owned fake `AuthPort` in use-case tests and route tests that only
+need authenticated/anonymous branches. Keep Better Auth itself covered through
+the app's auth route tests and provider integration tests.
+
+## Deployment notes
+
+Deploy the Better Auth database schema and secret configuration before enabling
+authenticated routes. Keep business authorization in feature policies and use
+Beignet auth hooks only for HTTP-boundary authentication.
+
 ## API reference
 
 ### `AuthPort<User, Session>`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@beignet/provider-auth-better-auth",
-  "version": "0.0.20",
+  "version": "0.0.22",
   "type": "module",
   "description": "Better Auth provider for Beignet - adds auth port for authentication and session management",
   "main": "./dist/index.js",