pequenas correções + doc update

apps/operator-pwa/lib/auth.ts

@@ -2,33 +2,30 @@ import NextAuth from 'next-auth';
 import Credentials from 'next-auth/providers/credentials';
 import { prisma } from '@repo/db';
 import { authenticateCredential } from '@repo/api';
-import type { SessionUser } from '@repo/api';  // eslint-disable-line @typescript-eslint/no-unused-vars
+import type { SessionUser } from '@repo/api';
 import { env } from '../env';
 import { authConfig } from './auth.config';
 
 /**
  * ============================================================================
- *  Auth.js v5 — PLACEHOLDER configuration for the scaffold phase.
+ *  Auth.js v5 — operator authentication (v0.2).
  * ============================================================================
  *
- *  The Credentials provider below accepts ANY email that exists in the User
- *  table (seeded by `pnpm db:seed`). NO PASSWORD CHECK is performed. This is
- *  deliberately minimal — just enough to populate the tRPC context with a real
- *  Auth.js session — and MUST be replaced with real authentication before any
- *  non-dev deployment.
+ *  The Credentials provider below verifies an operator's PIN against the
+ *  scrypt hash in User.passwordHash (via authenticateCredential, which also
+ *  enforces role and account lockout). Only OPERATOR users may sign in here.
  *
  *  Auto sign-in
  *  ------------
  *  See `resolveUser()` below. When AUTH_DEV_AUTOLOGIN=true, server-side code
- *  that has no session falls back to the seeded admin user. This is a back
- *  door and is gated by an explicit env flag whose default in .env.example is
- *  FALSE.
+ *  that has no session falls back to the seeded admin user. This is a dev/CI
+ *  back door, gated TWICE: by an explicit env flag (default FALSE in
+ *  .env.example) AND by NODE_ENV — it is IGNORED when NODE_ENV=production.
  *
  *      !!! NEVER set AUTH_DEV_AUTOLOGIN=true in production. !!!
  *
- *  In production with AUTH_DEV_AUTOLOGIN unset/false, requests without a
- *  signed Auth.js session resolve to user=null, and protectedProcedure throws
- *  401.
+ *  In production (or with the flag off), requests without a signed Auth.js
+ *  session resolve to user=null, and protectedProcedure throws 401.
  * ============================================================================
  */