docs(consultations): Gemini consultation for Task #92 Ubuntu setup

Ready to implement the Desktop MCP Server. HP laptop blue-screened,
wiping for Ubuntu Server. Questions on:
- Security packages and configs
- MCP in Docker vs host
- SSH key management
- Cloudflare Tunnel setup
- Discord approval integration
- Startup/recovery automation
- Monitoring

Chronicler #73

docs/consultations/gemini-task-92-ubuntu-setup-2026-04-09.md

@@ -0,0 +1,94 @@
+# Gemini Consultation: Task #92 Implementation — Ubuntu Server Setup
+
+**Date:** April 9, 2026  
+**From:** Michael (The Wizard) + Claude (Chronicler #73)  
+**To:** Gemini (Architectural Partner)  
+**Re:** Ready to implement the Desktop MCP Server — need your input on Ubuntu setup
+
+---
+
+## Hey Gemini! 👋
+
+Remember Task #92 — the Desktop MCP Server you helped us design back on April 8th? We discussed evolving it from a Raspberry Pi to Michael's HP laptop, potentially as an SSH MCP Connector that would let Claude.ai execute commands directly.
+
+Well, the laptop just blue-screened itself into oblivion (0x00000025 — bootloader corruption), and the recovery tools won't work. So we're taking it as a sign: **time to wipe it and set up Ubuntu Server.**
+
+Before we dive in, we want your architectural input on the setup.
+
+---
+
+## The Hardware
+
+- HP Laptop (exact specs TBD, but modern enough)
+- Will sit on a shelf, dedicated server duty
+- Always-on, minimal interaction needed
+
+---
+
+## Our Current Plan
+
+1. Install **Ubuntu Server 24.04 LTS**
+2. Install **Cockpit** for web-based management
+3. Install **Docker** for containerization
+4. Install **Node.js** for the MCP server
+5. Set up **Cloudflare Tunnel** (`cloudflared`) to expose MCP endpoint
+6. Deploy the **MCP server** (SSH connector)
+7. Configure **SSH keys** to Firefrost servers
+8. Put it on the shelf
+
+---
+
+## What We Remember From Your Architecture
+
+From our April 8th consultation, you recommended:
+
+- **SSH MCP Connector** approach — Claude.ai could execute commands without leaving chat
+- **`claude_executor` user** with restricted sudo, NOT root (zero-trust)
+- **Discord approval mechanism** — Interactive buttons in `#mcp-approvals` channel for sensitive commands
+- **Context handoffs** via file-based system
+- Potential merge of Task #92, #93, #94 into **"Trinity Core"**
+
+---
+
+## Specific Questions
+
+1. **Ubuntu Server Setup:** Any specific packages or configurations you'd recommend beyond the basics (Cockpit, Docker, Node, cloudflared)? Fail2ban? UFW firewall rules? Anything security-specific?
+
+2. **MCP Server Architecture:** Should the MCP server run directly on the host, or in a Docker container? What are the tradeoffs for our use case?
+
+3. **SSH Key Management:** The laptop needs to SSH into Command Center, Panel, TX1, NC1, and possibly others. Should each server have its own key pair, or one key for all? Where should private keys live?
+
+4. **Cloudflare Tunnel Configuration:** Any gotchas with `cloudflared` and MCP endpoints? Should we use Access policies to restrict who can hit the endpoint?
+
+5. **Discord Approval System:** For the approval mechanism you designed — should that be part of the MCP server itself, or a separate service? How should it integrate with Arbiter (our existing backend)?
+
+6. **Startup/Recovery:** If the laptop reboots (power outage, kernel update), what should auto-start? Systemd services for everything? Docker Compose?
+
+7. **Monitoring:** Should this laptop report into our existing Uptime Kuma on Command Center? What metrics matter for an MCP gateway?
+
+---
+
+## Context That Might Help
+
+- **Current infrastructure:** Command Center (63.143.34.217), Panel (45.94.168.138), TX1 (38.68.14.26), NC1 (216.239.104.130)
+- **Arbiter 3.5.0** runs on Command Center — handles Stripe webhooks, Trinity Console, Discord bot commands
+- **Michael's constraints:** Hand/arm limitations from surgery — minimize manual intervention
+- **Claude Connectors:** We already have Canva, Cloudflare, Stripe MCP connectors working in Claude.ai
+- **Goal:** Claude.ai can execute server commands with Michael's approval, without leaving chat
+
+---
+
+## What We're NOT Doing
+
+- NOT giving unsupervised root access to anything
+- NOT exposing SSH directly to the internet
+- NOT abandoning the approval mechanism for destructive commands
+- NOT overcomplicating it — this should be maintainable
+
+---
+
+Thanks Gemini! We're excited to finally build this thing. Your architecture guidance has been solid, and we want to make sure the implementation matches the vision.
+
+🔥❄️
+
+— Michael + Claude (Chronicler #73)