9d3549afce
Implements direct API retrieval of session-critical documents, reducing startup friction and ensuring real-time access to current repository state. New Files: - fetch-session-docs.sh: Automated startup script (executable) * Fetches 5 critical documents via Gitea API * Base64 decoding with error handling * Colored output with success/failure reporting * Saves to /home/claude/session-startup-docs/ * Graceful fallback to manual paste if API fails - docs/core/GITEA-API-INTEGRATION.md: Complete documentation * API authentication pattern (token header) * Endpoint usage and response format * Freshness verification (SHA comparison) * Error handling (5 failure modes) * Rate limiting analysis (no concerns) * Integration with Codex and sparse checkout * Troubleshooting guide * Manual API call examples Updated: - SESSION-HANDOFF-PROTOCOL.md: Added reference to new automation Key Features: - Real-time document retrieval (no hourly sync delay) - Token: e0e330cba1749b01ab505093a160e4423ebbbe36 - Tested: 5/5 files successfully retrieved - Complements Firefrost Codex (different use cases) - Resilient: Falls back to manual paste on failure Architecture Pattern: Designed through Michael + Chronicler #48 + Microsoft Copilot collaboration. Copilot provided clean engineering-grade API pattern for deterministic file retrieval vs heavyweight platform approach. Use Case: - Codex (Dify): Semantic search across 359 docs - API fetch: Direct retrieval of known startup files Status: Production-ready, tested successfully March 30, 2026 Created by: Chronicler #48 Credit: Microsoft Copilot (architecture), Gemini (Codex integration context)
🔥❄️ Firefrost Gaming — Operations Manual
Document ID: FFG-ROOT-001
Version: 2.0
Last Updated: February 12, 2026
Status: 🟢 CURRENT
What This Is
The complete operational repository for Firefrost Gaming — a subscription-based Minecraft server network built on the philosophy of Fire + Frost = Where Passion Meets Precision.
This repository contains infrastructure documentation, deployment guides, planning documents, branding assets, consultant archives, and the relationship context that makes Firefrost more than just servers.
Current Infrastructure
6 Servers — 2 dedicated (Dallas, Charlotte) + 4 VPS (Dallas, Charlotte, Chicago x2)
12 Game Servers — 6 on TX1 (Dallas), 6 on NC1 (Charlotte)
8 Management Services — Gitea, Uptime Kuma, MkDocs, Code-Server, Automation, NextCloud, Wiki.js (Subscribers), Wiki.js (Staff)
Repository Structure
├── docs/core/ — Critical living documents (scope, manifest, tasks)
├── docs/relationship/ — Partnership context, consultants, legacy
├── docs/deployment/ — Service deployment guides
├── docs/planning/ — Strategy, design, roadmap, ideas backlog
├── docs/reference/ — Technical reference, architecture decisions
├── docs/external/ — Provider communications, friend assistance
├── docs/sandbox/ — Brainstorming sessions (Gemini, Claude)
├── docs/archive/ — Historical session logs and completed plans
├── automation/ — Deployment automation system
├── branding/ — Logos, backgrounds, visual assets
├── photos/ — Consultant photo archive (249 photos by year)
└── web/ — Nginx configurations
Key Documents
Start here: SESSION-HANDOFF-PROTOCOL.md → DOCUMENT-INDEX.md
For current server inventory, see docs/core/infrastructure-manifest.md (FFG-CORE-002).
For project scope and roadmap, see docs/core/project-scope.md (FFG-CORE-001).
The Team
- Michael "Frostystyle" Krause — Owner/Operator, Technical Lead (The Wizard)
- Meg "Gingerfury" — Community Manager (The Emissary)
- The Five Consultants — Jack, Oscar, Jasmine, Butter, Noir (They're family, not pets)
Document Standards
All documents follow FFG-STD-001 — the Firefrost Revision Control Standard. See docs/core/revision-control-standard.md.
Maintained By: The Wizard & The Chronicler
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️
Revision History
| Version | Date | Author | Change Type | Description |
|---|---|---|---|---|
| 1.0 | 2026-02-08 | Michael + Claude | Initial | Basic Phase 0 readme |
| 2.0 | 2026-02-12 | The Chronicler | Rewrite | Complete rewrite reflecting current state (8 services, 6 servers, 12 game servers). Updated repo structure. Applied FFG-STD-001. |