docs(consultations): Close Forge architecture consult — Option A selected

Phase 1 deployment decided: Arbiter static file serving.
The Forge is now officially post-launch. Focus returns to Task #126.

docs/consultations/gemini-the-forge-architecture-2026-04-11.md

@@ -135,3 +135,19 @@ Every architectural decision validated. Gemini pushed back exactly where we need
 3. Begin Phase 1 ONLY after April 15 launch — or as a genuine spare-time diversion if Michael wants (no pressure)
 4. Revisit for Phase 2 architecture consultation when ready to add real-time events + illustrated assets
 
+
+---
+
+## Deployment Decision (April 11, 2026)
+
+**Decision:** Option A — Static files served directly through Arbiter route
+
+**Rationale:**
+- Zero new deployment surface; drop files in Arbiter's public folder
+- No CORS configuration needed (same origin as data endpoints)
+- The Forge depends on Arbiter data anyway — shared uptime fate is logical for a local wall display
+- Minimizes friction so Phase 1 can happen when Michael has spare time without becoming its own project
+- Migration to Cloudflare Pages remains trivial later (Phase 4+) if The Forge grows into a public-facing showcase
+
+**Consultation Status:** CLOSED. Vault locked. Post-launch pickup.
+