refactor: replace Prisma ORM runtime with Drizzle ORM facade

- Replace Prisma client runtime with Drizzle ORM (zero Prisma engine/query engine in production)
- Add Prisma-compatible facade (@/lib/prisma-facade.ts) backed by Drizzle for backwards compatibility
- Runtime queries route through Drizzle ORM; @prisma/client is now devDependency (types only)
- Remove @prisma/adapter-mariadb dependency; delete prisma-pool.ts and types/prisma.ts
- New Drizzle schema layer: src/db/schema.ts (176 tables) and src/lib/db.ts (connection)
- Update README documenting the dual-layer ORM architecture
- Restore src/generated/ gitignore (build artifact for local type generation)
- 0 TypeScript errors, 583 tests passing

The facade intentionally uses `any` types to match the Prisma Client API surface,
allowing existing code to run unmodified while routing queries through Drizzle at runtime.

README.md

@@ -1,6 +1,6 @@
 # EpicNext-CMS v1.0.1
 
-A modern, high-performance content management system for Habbo hotel emulators, built on **Next.js 16** (App Router) with **Prisma 7** and **React 19**. Designed to integrate seamlessly with Polaris / Arcturus Morningstar MySQL/MariaDB databases.
+A modern, high-performance content management system for Habbo hotel emulators, built on **Next.js 16** (App Router) with **Drizzle ORM** and **React 19**. Designed to integrate seamlessly with Polaris / Arcturus Morningstar MySQL/MariaDB databases.
 
 Features a premium animated homepage (typewriter hero, floating orbs, scroll counters), a full admin panel, NextAuth authentication (bcrypt with MD5-to-bcrypt upgrade), real-time RCON communication, Server-Sent Events for live radio data, smooth page transitions, and PM2 production deployment.
 
@@ -37,7 +37,9 @@ The CMS shares a database with the Polaris/Arcturus emulator. Use an existing da
 CREATE DATABASE IF NOT EXISTS epicnext_cms CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
 ```
 
-The CMS reads emulator-owned tables (`users`, `items`, `rooms`, `bans`, etc.) directly. It never creates, alters, or drops them.
+The CMS reads emulator-owned tables (`users`, `items`, `rooms`, `bans`, etc.) directly. It never creates, alters, or drops them. The Drizzle schema in `src/db/schema.ts` is generated from the existing database structure and does not modify it.
+
+> **Note:** The CMS does **not** own the database schema — it maps to tables that are managed by the emulator. All Drizzle schema definitions use `drizzle-orm`'s runtime mapping (no `drizzle-kit push/migrate` is ever run against the emulator schema). CMS-owned tables (`website_*`, `radio_*`, etc.) are created via idempotent SQL files in `prisma/migrations/`.
 
 ### 3. Configure Environment
 
@@ -56,13 +58,21 @@ APP_URL=http://localhost:3000
 
 See `.env.example` for all optional variables (RCON, email, Redis, OAuth, PayPal, etc.).
 
-### 4. Generate Prisma Client
+### 4. Type Generation (Optional for Development)
 
 ```bash
 pnpm prisma:generate
 ```
 
-Generates TypeScript types in `src/generated/prisma/`.
+Generates TypeScript types in `src/generated/prisma/`. This is only needed for developer type-checking of the `prisma` facade — it does not add any Prisma runtime overhead in production. The facade (`src/lib/prisma-facade.ts`) routes all queries through Drizzle ORM at runtime.
+
+Alternatively, you can work with Drizzle directly via the typed schema in `src/db/schema.ts`:
+
+```ts
+import { db } from "@/lib/db";
+import { users } from "@/db/schema";
+const result = await db.select().from(users).where(eq(users.username, "hello"));
+```
 
 ### 5. Run CMS Migrations
 
@@ -161,20 +171,21 @@ The CMS runs behind an nginx reverse proxy on the default port 3000. Static asse
 
 ```
 ├── prisma/
-│   ├── schema.prisma          # ~190 models (emulator + CMS)
+│   ├── schema.prisma          # ~190 models (emulator + CMS) — used for type generation only
 │   └── migrations/            # 16 SQL migrations for CMS tables
-├── scripts/
-│   ├── apply-migrations.ts    # Custom migration runner
-│   ├── jobs-worker.ts         # Background task scheduler
-│   └── sql-statements.ts      # SQL parsing utilities
 ├── src/
+│   ├── db/
+│   │   ├── schema.ts          # Drizzle ORM schema (176 tables — runtime data layer)
+│   │   └── migrations/        # Drizzle migration files (if used)
 │   ├── app/                   # Next.js App Router (pages & API routes)
 │   ├── actions/               # Server Actions
 │   ├── components/            # UI components
 │   ├── lib/
 │   │   ├── auth/              # NextAuth, password hashing, 2FA, SSO tickets
 │   │   ├── services/          # RCON, email, currency, PayPal, alerts
-│   │   ├── prisma.ts          # Database connection singleton
+│   │   ├── prisma.ts          # Prisma-compatible facade (routes to Drizzle at runtime)
+│   │   ├── prisma-facade.ts   # Drizzle-backed implementation of Prisma API surface
+│   │   ├── db.ts              # Drizzle connection singleton (runtime)
 │   │   ├── redis.ts           # Redis client (ioredis)
 │   │   ├── redis-cache.ts     # Redis caching utility for API routes
 │   │   ├── cache.ts           # In-memory cache fallback
@@ -198,6 +209,16 @@ The CMS runs behind an nginx reverse proxy on the default port 3000. Static asse
 | CMS tables (`website_*`, `radio_*`, etc.)         | CMS-owned               | `prisma/migrations/*.sql` (16 files) |
 | Migration tracking                                | `cms_migrations` table  | Auto-created by migration runner     |
 
+### ORM Architecture
+
+The CMS uses a dual-layer approach:
+
+- **Runtime (Drizzle ORM)**: `@/lib/db` exposes a Drizzle singleton connected to the MySQL/MariaDB database. All new code should use this directly. The schema is defined in `src/db/schema.ts` with 176 tables typed against the existing database columns.
+- **Legacy Compatibility (Prisma Facade)**: `@/lib/prisma` provides a Prisma-compatible API surface backed by Drizzle. This allows existing code to continue working without refactoring. The facade (`@/lib/prisma-facade.ts`) implements the Prisma client API (`findMany`, `findUnique`, `create`, `$transaction`, `$queryRaw`, etc.) but routes all queries through Drizzle at runtime — **no Prisma client engine or query engine is loaded in production**.
+- **Type Generation**: `src/generated/prisma/` (regenerated via `pnpm prisma:generate`) exists solely for TypeScript type-checking. It is `gitignore`d and is never bundled in the production build.
+
+Migration path: new database access should use `import { db } from "@/lib/db"` with queries built via `src/db/schema.ts`. The facade is maintained for backwards compatibility but is not recommended for new code.
+
 ---
 
 ## Optional Integrations