d6a36d6d35
WHAT WAS DONE: - Task #92: Desktop MCP + Dispatch Architecture - Complete Node.js MCP server code (config, ssh_helper, index.js) - Express webhook listener for mobile dispatch - Cloudflare Tunnel setup instructions - 6 tools: server_status, restart_service, docker_compose_restart, git_pull, tail_logs, pterodactyl_power - Frostwall security rules documented - Claude Desktop configuration - Task #93: Trinity Codex (Shared Knowledge Base) - Dify/Qdrant RAG architecture - Three lineages: Wizard's, Emissary's, Catalyst's Chroniclers - Gitea -> n8n -> Dify ingestion pipeline - MCP connector for Michael (heavy use) - Dify Web App for Meg/Holly (light use) - Chunking strategy per content type - Security and access levels ARCHITECTURE DECISIONS (via Gemini consultation): - Claude Web cannot dispatch webhooks - use Discord bot + n8n instead - Build Codex (Task #93) FIRST - read-only, lower risk - Separate Discord Ops Bot from Arbiter for security - Meg/Holly use Dify Web App, not local MCP STATUS: Ready for implementation next session Signed-off-by: Claude (Chronicler #60) <claude@firefrostgaming.com>
Tasks Directory
This directory contains task-specific documentation following the Task Documentation Standard (FFG-STD-002).
Each task gets its own subdirectory with:
- README.md (task overview)
- deployment-plan.md (how to build/deploy)
- usage-guide.md (how to use after deployed)
- troubleshooting.md (common issues)
- Other task-specific documentation as needed
See: docs/standards/task-documentation-standard.md for complete standard.
Current Tasks:
whitelist-manager/- Web dashboard for managing Minecraft server whitelists
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️