Format files according to Biome standards

README.md

@@ -9,7 +9,7 @@ Features a premium animated homepage (typewriter hero, floating orbs, scroll cou
 ## System Requirements
 
 | Component                    | Version            | Notes                                   |
-| --------------- | ------------ | --------------------------------------- |
+| ---------------------------- | ------------------ | --------------------------------------- |
 | Node.js                      | 26.12.1            | Pinned in `.nvmrc` (`>=26.12.1 <27`)    |
 | pnpm                         | 12.11.2            | Pinned via `packageManager`             |
 | npm                          | >= 11.x            | Supported alternative                   |
@@ -58,12 +58,14 @@ yarn install
 The CMS supports both **MySQL / MariaDB** and **PostgreSQL**. The database type is automatically detected from your `DATABASE_URL` protocol (`mysql://` or `postgres://`).
 
 #### Option A: MySQL / MariaDB
+
 Create your database:
 ```sql
 CREATE DATABASE IF NOT EXISTS epicnext_cms CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
 ```
 
 #### Option B: PostgreSQL
+
 Create your database:
 ```sql
 CREATE DATABASE epicnext_cms;
@@ -1396,7 +1398,6 @@ suite at any running CMS with `PLAYWRIGHT_BASE_URL`.
 ### Testing & Quality Assurance
 
 EpicNext-CMS maintains strict engineering standards enforced through automated testing pipelines:
-
 1. **Unit & Integration Testing (Vitest)**:
    - Run tests: `pnpm test`
    - Run integration tests: `pnpm test:integration`
@@ -1423,7 +1424,6 @@ EpicNext-CMS maintains strict engineering standards enforced through automated t
 ## Production Deployment & Zero-Downtime Releases
 
 EpicNext-CMS is engineered for enterprise-grade production environments with zero-downtime deployment capabilities:
-
 1. **Blue/Green Slot Deployments**:
    - Updates run through containerized slot orchestration (`scripts/docker-update.sh`), ensuring seamless transitions between release versions without dropping requests.
    - Automatic health check verification (`/api/health`) validates database connectivity, Redis/Valkey status, and RCON liveness before routing production traffic.

drizzle.config.ts

@@ -7,7 +7,8 @@ import { defineConfig } from "drizzle-kit";
 // or `push` against it. CMS DDL stays in drizzle/migrations/*.sql applied by
 // `pnpm db:migrate`. Use `pnpm db:generate` only for draft SQL under drizzle/drafts/.
 const dbUrl = process.env.DATABASE_URL ?? "";
-const isPostgres = dbUrl.startsWith("postgres://") || dbUrl.startsWith("postgresql://");
+const isPostgres =
+	dbUrl.startsWith("postgres://") || dbUrl.startsWith("postgresql://");
 
 export default defineConfig({
 	dialect: isPostgres ? "postgresql" : "mysql",