bridge: Request — Deploy Phase 11A to Command Center

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

docs/code-bridge/requests/REQ-2026-04-12-phase11a-deploy.md

@@ -0,0 +1,39 @@
+# Architectural Request
+
+**Date:** 2026-04-12
+**Topic:** Deploy Phase 11A — MVC licensing migration + Arbiter routes
+
+## 1. Current State
+Phase 11A code is committed and pushed to `main` (fd50009). Migration SQL and API routes are ready.
+
+## 2. The Blocker
+Code cannot deploy to Command Center — Chronicler handles Arbiter deployments via Trinity Core.
+
+## 3. Deployment Steps for Chronicler
+
+1. Run migration on Command Center:
+   ```
+   psql -U arbiter -d arbiter_db -f services/arbiter-3.0/migrations/138_mvc_licensing.sql
+   ```
+
+2. Deploy Arbiter code (standard pattern):
+   - Clone to /tmp
+   - Copy to /opt/arbiter-3.0
+   - Restart Arbiter service
+   - Verify health endpoint
+
+3. Add these env vars to Arbiter .env (placeholders until BBB listings go live):
+   ```
+   BBB_STANDARD_RESOURCE_ID=PLACEHOLDER_STANDARD
+   BBB_PRO_RESOURCE_ID=PLACEHOLDER_PRO
+   BBB_WEBHOOK_SECRET=PLACEHOLDER_SECRET
+   ```
+
+4. Verify new endpoints respond:
+   ```
+   curl https://discord-bot.firefrostgaming.com/api/mvc/latest-version
+   ```
+   Expected: `{"version":"1.0.0","download_url":"..."}`
+
+## 4. After Deployment
+Once confirmed, Code will proceed to Phase 11B/C (Discord /verify-mvc command + customer role).