WHAT WAS DOCUMENTED:
- Gemini's initial architectural review (tech stack, API strategy, scope)
- Gemini's database schema refinement (VARCHAR vs ENUM decision)
- Platform detection logic and dynamic support flagging
- Fleet Coverage Dashboard UI concept
KEY ARCHITECTURAL DECISIONS:
1. Tech Stack: 100% native Laravel + PHP (no Node.js dependency)
2. API Strategy: BYOK (Bring Your Own Key) for CurseForge
3. Scope: CurseForge + Modrinth only for v1.0
4. Database: VARCHAR(50) platform field (future-proof vs ENUM)
5. Dynamic Support: is_supported flag changes based on platform + API errors
6. UI Strategy: Graceful degradation with educational messaging
CRITICAL INSIGHTS FROM GEMINI:
- Hardcoding API key = rate limit death for distributed product
- ENUM fields break when new platforms added (migration required)
- Web scraping = maintenance nightmare (avoid FTB/Technic)
- Automatic updates = liability nightmare (v1.0 is CHECK only)
- Discord webhooks > email notifications (universal + foolproof)
- Pricing: 0-15 sweet spot for impulse buy + support filter
- RV-Ready Score = 100 - Total Complexity (product dev philosophy)
NEXT STEPS:
- Research CurseForge BYOK secure storage in Laravel
- Research Modrinth User-Agent header requirements
- Study Blueprint extension development guide
- Build MVP on Dev VPS (64.50.188.128)
Files added:
- docs/consultations/gemini-modpack-version-checker-review-2026-04-01.md
- docs/consultations/gemini-modpack-database-schema-2026-04-01.md
This consultation series ensures we build commercial-grade software
with proper architecture, not hobbyist code.
Fire + Frost + Foundation = Where Love Builds Legacy
Signed-off-by: Claude (Chronicler #52) <claude@firefrostgaming.com>