docs: Add Arbiter database connection info to infrastructure manifest

Added complete Arbiter 3.0 / Trinity Console section to Command Center:
- Database connection details (host, port, db name, user)
- Migration command pattern (PGPASSWORD approach)
- Deploy pattern for Arbiter updates
- Password reference to Vaultwarden (not plaintext)

This was missing and caused confusion during Task #94 deployment.

Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>

docs/core/infrastructure-manifest.md

@@ -120,10 +120,41 @@
 ### Command Center Details
 
 - **Primary IP:** 63.143.34.217
-- **Services:** Gitea, Uptime Kuma, Code-Server, Automation daemon
+- **Services:** Gitea, Uptime Kuma, Code-Server, Automation daemon, Arbiter 3.0, Trinity Console
 - **Node.js:** 20.20.0
 - **Nginx:** Reverse proxy for all services
 
+#### Arbiter 3.0 / Trinity Console
+
+- **Path:** `/opt/arbiter-3.0`
+- **Service:** `arbiter-3` (systemctl)
+- **Domain:** discord-bot.firefrostgaming.com
+- **Admin Panel:** discord-bot.firefrostgaming.com/admin
+
+**Database Connection:**
+- **Host:** 127.0.0.1
+- **Port:** 5432
+- **Database:** arbiter_db
+- **User:** arbiter
+- **Password:** (in Vaultwarden under "Arbiter PostgreSQL")
+
+**Running Migrations:**
+```bash
+# From Command Center, run migration files directly:
+PGPASSWORD='[password]' psql -U arbiter -d arbiter_db -h 127.0.0.1 -f /path/to/migration.sql
+
+# Or connect interactively:
+PGPASSWORD='[password]' psql -U arbiter -d arbiter_db -h 127.0.0.1
+```
+
+**Deploy Pattern:**
+```bash
+cd /tmp
+git clone https://git.firefrostgaming.com/firefrost-gaming/firefrost-services.git
+# Copy specific files to /opt/arbiter-3.0
+systemctl restart arbiter-3
+```
+
 ### Panel Details
 
 - **Primary IP:** 45.94.168.138