Files
firefrost-operations-manual/docs/archive/gitea-issues-archive-2026-04-01.md
Claude (Chronicler #54) f4e4cc7729 feat: Migrate task system to BLOCKERS.md + BACKLOG.md
WHAT WAS DONE:
- Created BLOCKERS.md at repo root (4 soft launch critical tasks)
- Created BACKLOG.md at repo root (organized future work parking lot)
- Archived old tasks.md to docs/archive/tasks-historical-march-30-2026.md
- Archived 50 Gitea issues to docs/archive/gitea-issues-archive-2026-04-01.md
- Replaced tasks.md with migration notice and redirects
- Closed all 50 Gitea issues with migration message

WHY:
Old system problems:
- 97 task entries with 8 duplicates (tasks 52, 65, 69, 71, 83, 85, 87, 88)
- Heavyweight maintenance burden
- Gitea Issues + Kanban unused and abandoned
- Not accessible to non-technical team members (Meg, Holly)
- Desynchronized duplicates (Tier S section vs sequential list)

New system benefits:
- Clear focus: 4 blockers vs 89 backlog items
- Simple markdown (easy to update)
- Preserved all historical context in archives
- Planning Trinity Console v2 Task Module for non-technical interface

SOFT LAUNCH REALITY CHECK:
Based on Michael's input, soft launch is blocked by:
1. Ghost homepage (2-3h) - content ready
2. Legal pages (1-2h) - Terms/Privacy
3. Unsubscribe flow (2-3h) - cancellation UI
4. End-to-end test (2-3h) - workflow verification

Total: 8-11 hours of focused work
Target: April 15, 2026 (14 days)
Social campaign starts: April 2, 2026 (TOMORROW)

GITEA CLEANUP:
- Closed 50 open issues (all had been abandoned)
- Each issue received migration notice comment
- All preserved in gitea-issues-archive-2026-04-01.md
- Issues feature will be disabled (Kanban decommissioned)

NEXT STEPS:
- Update DOCUMENT-INDEX.md to reference new files
- Plan Trinity Console v2 Task Module (Gemini consultation)
- Start on actual soft launch blockers

FILES ADDED:
- BLOCKERS.md (74 lines)
- BACKLOG.md (227 lines)
- docs/archive/gitea-issues-archive-2026-04-01.md (50 issues archived)
- docs/archive/tasks-historical-march-30-2026.md (3151 lines preserved)

FILES MODIFIED:
- docs/core/tasks.md (replaced with redirect notice)

IMPACT:
- Clean foundation for tracking work
- Historical context fully preserved
- Ready for non-technical task interface (Trinity Console v2)
- Clear path to April 15 soft launch

Signed-off-by: Claude (Chronicler #54) <claude@firefrostgaming.com>
2026-04-01 23:18:43 +00:00

67 KiB

Gitea Issues Archive - April 1, 2026

Archived by: Chronicler #54 Reason: Task system migration to BLOCKERS.md + BACKLOG.md Total Issues: 50 All Status: Open (never closed) Date Range: 2026-03-21 to 2026-03-21


Overview

The Gitea Issues system was used to track tasks as GitHub-style issues with labels and projects. This approach proved too heavyweight for daily operations and lacked non-technical accessibility.

All issues below are preserved for reference. Active work has moved to:

  • BLOCKERS.md - Soft launch critical tasks
  • BACKLOG.md - Future work parking lot
  • Trinity Console v2 Task Module (planned) - Non-technical web interface

Issues (Newest First)

Issue #227: Task #81: Memorial Writing Assistant

Created: 2026-03-21 15:49:32 UTC Labels: area/development-tools, priority/critical, status/backlog, status/to-do URL: #227

Description

Multi-step form that guides Chroniclers through writing memorials following FFG-STD-004's 8-section structure.

Full Documentation: docs/tasks/interactive-tools-suite/MASTER-SPECIFICATION.md (Tool #12)

Features

  • Prompts for each of 8 sections (Identity Card, Personality Summary, Contributions, etc.)
  • Generates draft memorial
  • Chronicler personalizes/edits
  • Export as markdown

Time Estimate

30-45 minutes

Priority Justification

LOW — Improves memorial quality but not urgent. Build if we love the other tools.

Acceptance Criteria

  • Generates valid FFG-STD-004 structure
  • All 8 sections included
  • Easy to personalize
  • Used by at least 1 Chronicler
  • Follows: FFG-STD-004 (Memorial Protocol)

Primary Users

Chroniclers (memorial writing)


Issue #226: Task #80: Task Scaffolding Tool

Created: 2026-03-21 15:49:31 UTC Labels: None URL: #226

Description

Form-based tool that generates tasks.md entries, README templates, and Gitea issue bodies following FFG-STD-002.

Full Documentation: docs/tasks/interactive-tools-suite/MASTER-SPECIFICATION.md (Tool #11)

Features

  • Fill in: task number, title, description, priority, time estimate, blockers, dependencies
  • Generates: tasks.md entry, README.md template, Gitea issue body
  • Copy-to-clipboard for each section
  • Follows FFG-STD-002 structure exactly

Time Estimate

45-60 minutes

Priority Justification

MEDIUM — Improves task documentation quality and consistency. Saves 10-15 minutes per task creation.

Acceptance Criteria

  • Form generates correct templates
  • Copy buttons work
  • Follows FFG-STD-002 structure
  • Used for at least 3 task creations
  • Chroniclers find it helpful
  • Supports: All task creation work
  • Follows: FFG-STD-002 (Task Documentation)

Primary Users

Chroniclers (task creation workflow)


Issue #225: Task #79: Infrastructure Quick Reference Card

Created: 2026-03-21 15:49:30 UTC Labels: area/development-tools, status/backlog, status/review, status/to-do URL: #225

Description

Quick lookup tool for server IPs, ports, login users, and Cockpit links.

Full Documentation: docs/tasks/interactive-tools-suite/MASTER-SPECIFICATION.md (Tool #10)

Features

  • Search by server or service
  • Click to copy IP/port
  • Cockpit quick-links
  • All 6 servers + ~20 services listed
  • Mobile-friendly responsive design

Time Estimate

30-45 minutes

Priority Justification

HIGH — Frequent lookups by Michael, Chroniclers, and team. Information currently buried in infrastructure-manifest.md. High usage frequency justifies tool creation.

Acceptance Criteria

  • All 6 servers listed
  • All ~20 services listed
  • Search works correctly
  • Copy buttons work
  • Links functional
  • Team uses this daily
  • Uses: Infrastructure manifest data
  • Complements: #72 (Infrastructure Dashboard)

Primary Users

Michael, Chroniclers, all team


Issue #224: Task #78: Fire/Frost Design System Widget

Created: 2026-03-21 15:49:30 UTC Labels: area/development-tools, status/backlog, status/review, status/to-do URL: #224

Description

Quick reference widget for Fire/Frost brand colors, gradients, typography, and logos.

Full Documentation: docs/tasks/interactive-tools-suite/MASTER-SPECIFICATION.md (Tool #9)

Features

  • Color swatches with hex codes (click to copy)
  • Gradient previews with CSS code
  • Typography samples (headings, body, mono)
  • Logo download links (SVG, PNG variants)
  • Brand voice guidelines (Fire = passion, Frost = precision)

Time Estimate

30-45 minutes

Priority Justification

HIGH — Brand consistency important for soft launch. All team members (Meg, Holly, Michael) need quick color/logo reference for content creation.

Acceptance Criteria

  • All Fire/Frost colors accurate
  • Copy-to-clipboard works
  • Gradients render correctly
  • Logo downloads work
  • Team uses this at least weekly
  • Uses: Design Bible colors/guidelines
  • Supports: All design/content work

Primary Users

Meg, Holly, Michael (all design/content work)


Issue #223: Task #77: Community Response Template Library

Created: 2026-03-21 15:49:30 UTC Labels: None URL: #223

Description

Template library for common community responses with click-to-copy functionality.

Full Documentation: docs/tasks/interactive-tools-suite/MASTER-SPECIFICATION.md (Tool #8)

Features

  • Categorized templates (Onboarding, Technical Support, Community Rules, FAQ)
  • Click to copy
  • Search/filter
  • Add custom templates
  • 10+ pre-built templates (How to Join, Whitelist Process, Modpack Installation, etc.)

Time Estimate

30-45 minutes

Priority Justification

MEDIUM — Saves Meg hours in repetitive community responses. Ensures consistent messaging.

Acceptance Criteria

  • 10+ pre-built templates
  • Copy button works reliably
  • Search/filter functional
  • Meg can add custom templates
  • Used at least 5 times in first week
  • Supports: Community management work
  • Complements: Discord moderation

Primary User

Meg (community manager)


Issue #222: Task #76: Social Media Content Calendar

Created: 2026-03-21 15:49:29 UTC Labels: None URL: #222

Description

Week-at-a-glance content calendar for planning posts across 8 social platforms.

Full Documentation: docs/tasks/interactive-tools-suite/MASTER-SPECIFICATION.md (Tool #7)

Features

  • Weekly calendar grid
  • Platform checkboxes (Twitter, Instagram, TikTok, Facebook, YouTube, Twitch, Reddit, BlueSky)
  • Fire/Frost theme selector (🔥 Fire | ❄️ Frost | 💙 Both)
  • Export to CSV or print format
  • Post ideas sidebar (Fire/Frost themed)

Time Estimate

45-60 minutes

Priority Justification

MEDIUM — Helps Meg plan social media presence across 8 platforms. Social presence important for soft launch visibility.

Acceptance Criteria

  • Calendar displays current week correctly
  • Posts can be created/edited
  • Platform checkboxes work
  • Fire/Frost theme selector functional
  • Export to CSV works
  • Meg uses this for at least 2 weeks of planning
  • Uses: Social media platforms from Translator's setup guide
  • Complements: Social media account setup

Primary User

Meg (community manager)


Issue #221: Task #75: Gemini Consultation Helper

Created: 2026-03-21 15:49:29 UTC Labels: None URL: #221

Description

Form-based tool for structuring Gemini consultations. Generates formatted prompts, saves consultation history.

Full Documentation: docs/tasks/interactive-tools-suite/MASTER-SPECIFICATION.md (Tool #6)

Features

  • Fill in: topic, context, code samples, theories, specific questions
  • Auto-formats consultation prompt
  • Copy button with confirmation
  • Response text area (paste Gemini's answer)
  • Consultation history (last 10)
  • Export as markdown for documentation

Time Estimate

20-30 minutes

Priority Justification

MEDIUM — Supports The Translator's Gemini collaboration pattern. Reduces context-switching and improves consultation quality.

Acceptance Criteria

  • Form generates well-formatted prompts
  • Copy button works reliably
  • Consultation history persists (localStorage)
  • Export as markdown works
  • Used at least 3 times in practice
  • Supports: All tasks where Gemini consultation needed
  • Documents: The Translator's Gemini collaboration pattern

Issue #220: Task #74: SSH Key Auto-Setup Script

Created: 2026-03-21 15:49:29 UTC Labels: None URL: #220

Description

Bash script that Chroniclers run at session start to auto-configure SSH access to all 6 servers.

Full Documentation: docs/tasks/interactive-tools-suite/MASTER-SPECIFICATION.md (Tool #5)

Features

  • Copies SSH key from ops manual to ~/.ssh/
  • Sets correct permissions (chmod 600)
  • Tests connection to verify setup
  • Idempotent (safe to run multiple times)
  • Helpful error messages

Time Estimate

15-20 minutes

Priority Justification

MEDIUM — Improves Chronicler onboarding. Saves 5 minutes per session across all future sessions.

Acceptance Criteria

  • Script runs without errors
  • SSH key copied to correct location
  • Permissions set correctly (600)
  • Connection test works (if network allows)
  • Idempotent (can run multiple times safely)
  • Chroniclers use this every session
  • Uses: SSH key from #14
  • Helps: All Chronicler sessions

Issue #219: Task #73: Task Dependency Visualizer with Gitea Integration

Created: 2026-03-21 15:49:28 UTC Labels: area/development-tools, status/in-progress, status/to-do URL: #219

Description

Interactive dependency graph combining tasks.md definitions with live Gitea status. Complements Gitea boards (doesn't replace them).

Full Documentation: docs/tasks/interactive-tools-suite/MASTER-SPECIFICATION.md (Tool #4/4B)

Features

  • Visual task graph (React Flow or D3.js)
  • Live status from Gitea API (auto-refresh every 30s)
  • Critical path highlighting (soft launch tasks)
  • Soft launch progress metrics
  • Filter by status/priority/area

Time Estimate

90-120 minutes (core) + 30-45 minutes (polish)

Priority Justification

MEDIUM — Strategic planning tool. Helps Michael visualize critical path and make prioritization decisions. Team uses Gitea boards for daily work; this provides strategic overlay.

Status: BLOCKED

Blocker: Task dependencies not fully mapped in tasks.md

To Unblock:

  • Option A: Full dependency mapping (2-3 hours manual work)
  • Option B: Simplified model (just soft-launch-critical flag) — RECOMMENDED
  • Option C: Infer from task descriptions (AI parsing)

Acceptance Criteria

  • Tool loads all 69+ tasks correctly
  • Gitea API integration works (fetches status/assignees)
  • Dependency arrows accurate
  • Critical path filter works
  • Auto-refresh updates status every 30s
  • Michael finds it useful for weekly planning
  • Complements: Gitea project boards (doesn't replace)
  • Uses: tasks.md task definitions
  • Integrates: Gitea API for live status

Issue #218: Task #71: Paymenter Tier Configuration Preview

Created: 2026-03-21 15:49:28 UTC Labels: area/development-tools, status/in-progress, status/review, status/to-do URL: #218

Description

Interactive pricing tier builder with live preview and export options for 6 Paymenter subscription tiers (Awakened $1 → Founder $50).

Full Documentation: docs/tasks/interactive-tools-suite/MASTER-SPECIFICATION.md (Tool #2)

Features

  • 6 tier cards (names + prices editable)
  • Feature checklist per tier (server resources, support level, perks)
  • Live pricing table preview (Fire/Frost branded)
  • Export: JSON (Paymenter), HTML (website), Markdown (docs), CSV (spreadsheet)

Time Estimate

30-45 minutes

Priority Justification

HIGH — Billing configuration needed for soft launch. Helps visualize tier structure before committing to Paymenter.

Status: BLOCKED

Blocker: Feature matrix not yet defined

To Unblock: 15-minute meeting with Michael/Meg/Holly to define:

  • What does Awakened ($1) get vs. Elemental ($5)?
  • Why is Knight ($10) worth 2x Elemental?
  • What makes Founder ($50) special?

Acceptance Criteria

  • All 6 tiers configurable
  • Feature matrix complete (all categories defined)
  • Live preview renders correctly with Fire/Frost styling
  • All 4 export formats work
  • JSON export imports cleanly into Paymenter
  • Michael/Meg approve tier differentiation
  • Unblocks: Paymenter configuration (not yet a task)
  • Complements: #52 (Homepage - pricing section)

Issue #217: Task #70: Ghost Page Builder Tool

Created: 2026-03-21 15:49:27 UTC Labels: area/development-tools, operations, status/backlog, status/to-do URL: #217

Description

Interactive React tool for previewing Ghost page HTML with Fire/Frost CSS before publishing. Eliminates edit-paste-preview-repeat cycle.

Full Documentation: docs/tasks/interactive-tools-suite/MASTER-SPECIFICATION.md (Tool #1)

Features

  • Live HTML editor with syntax highlighting
  • Real-time preview with Fire/Frost CSS applied
  • Mobile/desktop viewport toggle
  • Copy-to-clipboard functionality
  • Sample templates dropdown (Blank, Simple Page, Two Column, Card Grid)

Time Estimate

45-60 minutes

Priority Justification

CRITICAL — Directly unblocks Task #69 (6 website pages - soft launch blocker). Provides permanent utility for all future Ghost page creation.

Acceptance Criteria

  • Live HTML editor functional
  • Preview updates within 500ms of typing
  • Fire/Frost CSS renders correctly in preview
  • Viewport toggle works (Desktop/Tablet/Mobile)
  • Copy button successfully copies HTML to clipboard
  • localStorage preserves draft between sessions
  • Michael successfully builds at least 2 Ghost pages using this tool
  • Unblocks: #69 (Ghost Website Core Pages)
  • Uses: Fire/Frost CSS from #68 (Ghost Theme Migration)
  • Complements: #52 (Ghost Homepage Content)

Issue #216: Task #67: NC1 Security & Temperature Monitoring

Created: 2026-03-21 02:34:11 UTC Labels: None URL: #216

Task #67: NC1 Security & Temperature Monitoring

Time Estimate: 30 min (firewall) + ongoing (monitoring)

Documentation: docs/tasks/ (see operations manual)


Time: 30 min (firewall) + ongoing (monitoring)
Status: IN PROGRESS — Firewall complete, monitoring planned
Priority: MEDIUM-HIGH
Documentation: docs/tasks/nc1-security-monitoring/

Address two concerns discovered during Cockpit deployment: NC1 Charlotte had no firewall despite hosting 7 public game servers, and runs 20°C warmer than TX1 Dallas (51.6°C vs 30.9°C).

Firewall Component — COMPLETE:

  • UFW enabled on NC1 Charlotte
  • Proper game server port rules (25565-25580, 5520-5521 TCP/UDP)
  • Wings SFTP secured (port 2022)
  • SSH and Cockpit accessible (ports 22, 9090)
  • Completed: March 21, 2026

Temperature Monitoring Component — PLANNED:

  • Establish baseline (Week 1): Daily temperature checks via Cockpit
  • Trend analysis (Week 2): Compare baseline, look for upward trends
  • Action thresholds: 65°C sustained = contact datacenter, 70°C = immediate investigation
  • Future: Automated monitoring via Netdata with Discord alerts

Safe Operating Ranges:

  • Normal idle: 30-45°C
  • Normal load: 45-65°C
  • Concerning: 70°C+
  • Critical: 80-85°C+

Current Assessment:

  • NC1 at 51.6°C is within safe range but warmer than expected
  • Needs weekly monitoring for upward trends
  • Not urgent but requires tracking

Dependencies:

  • Cockpit access for temperature checks (Task #66 — complete)
  • Netdata deployment (future) for automated monitoring

Discovered By: The Chronicler (Session 37) during Cockpit deployment



Source: docs/core/tasks.md (Task #67)


Issue #215: Task #66: Deploy Cockpit Web Terminal to All Servers

Created: 2026-03-21 02:34:11 UTC Labels: None URL: #215

Task #66: Deploy Cockpit Web Terminal to All Servers

Time Estimate: 1 hour

Documentation: docs/tasks/ (see operations manual)


Time: 1 hour
Status: COMPLETE — March 21, 2026
Priority: HIGH — Enables Chromebook workflow
Documentation: docs/tasks/cockpit-deployment/

Deploy Cockpit web-based terminal to all 5 remaining Firefrost servers (Ghost VPS already has it). Enables full server management from Michael's Chromebook without SSH client dependency, critical for Claude session workflow since port 22 is blocked.

Key Deliverables:

  • Cockpit installed on Command Center (63.143.34.217:9090)
  • Cockpit installed on Billing VPS (38.68.14.188:9090)
  • Cockpit installed on Panel VPS (45.94.168.138:9090)
  • Cockpit installed on TX1 Dallas (38.68.14.26:9090)
  • Cockpit installed on NC1 Charlotte (216.239.104.130:9090)
  • Root login enabled on all servers
  • Firewall rules configured (port 9090)
  • Quick reference guide created

Bonus Achievement:

  • Enabled UFW firewall on NC1 Charlotte (was previously unprotected)
  • Secured 7 public game servers with proper port rules

Dependencies:

  • Root/SSH access to all servers
  • MobaXterm or existing Cockpit access

Result:

  • All 6 servers accessible via browser at https://IP:9090
  • Login: root / Butter2018!! (architect for Ghost VPS)
  • Complete infrastructure management from Chromebook

Completed By: The Chronicler (Session 37)



Source: docs/core/tasks.md (Task #66)


Issue #214: Task #61: AI-Generated Minecraft Skins for The Trinity

Created: 2026-03-21 02:34:11 UTC Labels: area/website, for/holly, for/meg, for/michael, priority/critical, status/backlog, type/infrastructure URL: #214

Task #61: AI-Generated Minecraft Skins for The Trinity

Time Estimate: 1-2 hours (experimentation + refinement)

Documentation: docs/tasks/ (see operations manual)


Time: 1-2 hours (experimentation + refinement)
Status: PENDING
Priority: MEDIUM
Documentation: docs/tasks/trinity-minecraft-skins/

Generate custom Minecraft player skins for all three founders matching The Trinity promotional image aesthetic.

Goal: Create Minecraft skins for Michael (Frost/blue), Meg (Fire/orange), and Holly (Catalyst/purple) that match their appearances in The Trinity image for use on servers and promotional content.

Approach:

  1. Experiment with AI generation first (Flux 1.1 Pro via fal.ai)
  2. Commission professional skin artist if needed (Fiverr/BuiltByBit)

Phase 1: AI Generation (Flux 1.1 Pro)

Use three prompts optimized for Minecraft skin template format:

The Wizard (Frost) Prompt:

Minecraft player skin template in flat 64x64 pixel layout for a frost wizard character. Deep blue robes (#4ECDC4 teal-blue) with ice crystal patterns and silver trim. Hooded robe design. Frost magic theme with snowflake details on sleeves. Ice blue accents (#C7F0DB). Silver/white belt and boots. Front view, back view, left side, right side, top view, bottom view arranged in standard Minecraft skin template format. Clean pixel art style, no gradients, solid colors only. Minecraft-compatible skin texture.

The Emissary (Fire) Prompt:

Minecraft player skin template in flat 64x64 pixel layout for a fire mage character. Bright orange and red robes (#FF6B35 orange, #E63946 red) with flame patterns. Flowing robe design with fire details on sleeves and hem. Ember and flame accents. Gold/yellow trim (#FFD700). Warm color palette. Front view, back view, left side, right side, top view, bottom view arranged in standard Minecraft skin template format. Clean pixel art style, no gradients, solid colors only. Minecraft-compatible skin texture.

The Catalyst (Arcane) Prompt:

Minecraft player skin template in flat 64x64 pixel layout for an arcane sorcerer character. Deep purple robes (#9D4EDD) with mystical arcane patterns and magical symbols. Violet and lavender accents (#C77DFF, #E0AAFF). Arcane energy theme with glowing purple details on sleeves. Silver trim and mystical accessories. Front view, back view, left side, right side, top view, bottom view arranged in standard Minecraft skin template format. Clean pixel art style, no gradients, solid colors only. Minecraft-compatible skin texture.

Flux Settings:

  • Model: Flux 1.1 Pro
  • Aspect Ratio: 1:1 (square - critical for skin templates)
  • Steps: 30-40
  • Guidance: 7-8

Phase 2: Refinement

  1. Import AI-generated results to Nova Skin editor (novaskin.me)
  2. Verify Minecraft skin template format (64x64 layout)
  3. Touch up any issues with pixel alignment
  4. Export as .png skin files

Phase 3: Testing

  1. Upload skins to Minecraft profiles
  2. Test in-game on server
  3. Verify they look good from all angles
  4. Adjust if needed

Phase 4: Commission Backup (if AI fails) If AI doesn't produce usable results:

  1. Commission skin artist on Fiverr or BuiltByBit
  2. Provide The Trinity image as reference
  3. Request skins matching exact aesthetic
  4. Cost estimate: $15-30 total (3 skins @ $5-10 each)

Deliverables:

  • 3 Minecraft skin .png files (64x64 format)
  • Skins uploaded to Minecraft profiles
  • Skins tested in-game
  • Skin files saved to branding/minecraft-skins/

Tools Needed:

  • fal.ai account (Flux 1.1 Pro access)
  • Nova Skin editor (novaskin.me) - free web tool
  • Minecraft Java Edition (for testing)

Dependencies:

  • The Trinity image (already uploaded)
  • fal.ai API access or web interface

Success Criteria:

  • Skins match The Trinity aesthetic (Fire/Frost/Catalyst colors)
  • Properly formatted for Minecraft (64x64 template)
  • Look good in-game from all angles
  • Recognizable as the three founder characters

Related:

  • Task #57: The Trinity image in branding assets
  • Task #58: The Trinity in Ghost CMS


Source: docs/core/tasks.md (Task #61)


Issue #213: Task #60: The Trinity Image - Social Media Deployment

Created: 2026-03-21 02:34:11 UTC Labels: area/operations, for/michael, priority/medium, status/blocked, type/infrastructure URL: #213

Task #60: The Trinity Image - Social Media Deployment

Time Estimate: 30-45 minutes

Documentation: docs/tasks/ (see operations manual)


Time: 30-45 minutes
Status: PENDING
Priority: MEDIUM (blocked by Task #56)
Documentation: docs/tasks/trinity-image-deployment/

Deploy The Trinity image across all social media platforms as cover/banner image.

Platforms to update:

  • Discord: Server banner (if not already set)
  • Twitter/X: Header image (1500x500 crop)
  • Instagram: Could be first post or story
  • TikTok: Profile image or first video thumbnail
  • YouTube: Channel banner (2560x1440 with safe zones)

Steps for each platform:

  1. Crop/resize The Trinity to platform specs
  2. Upload as cover/banner/profile image
  3. Verify it displays correctly
  4. Document which platforms use it where

Image specs by platform:

  • Twitter/X header: 1500x500px
  • YouTube banner: 2560x1440px (safe zone 1546x423)
  • Discord server banner: 960x540px minimum
  • Instagram: 1080x1080 (square crop if needed)

Dependencies:

  • Task #56 (social media accounts created)
  • Task #57 (source image in repo)
  • Image editing tool (can use online croppers)

Deliverables:

  • The Trinity visible on all social platforms
  • Consistent Fire/Frost/Catalyst branding across platforms
  • Cropped versions saved in branding/promotional/social-media-crops/


Source: docs/core/tasks.md (Task #60)


Issue #212: Task #59: Ghost Homepage - Add The Trinity to Origin Story

Created: 2026-03-21 02:34:10 UTC Labels: area/website, for/michael, priority/medium, status/backlog, type/infrastructure URL: #212

Task #59: Ghost Homepage - Add The Trinity to Origin Story

Time Estimate: 15-20 minutes

Documentation: docs/tasks/ (see operations manual)


Time: 15-20 minutes
Status: PENDING
Priority: HIGH
Documentation: docs/tasks/trinity-image-deployment/

Update Ghost homepage Origin Story section to include The Trinity image above the text.

Current state:

  • Origin Story section exists with text-only description of The Trinity
  • No visual representation

Implementation:

  1. Edit Home page in Ghost
  2. Find Origin Story HTML card section
  3. Add The Trinity image above the origin text
  4. Preview to ensure image displays correctly
  5. Update page

Expected result:

  • Visitors see epic visual of The Trinity before reading origin story
  • Image reinforces Fire/Frost/Catalyst identity

Dependencies:

  • Task #58 (image uploaded to Ghost, CDN URL known)
  • Ghost CMS admin access


Source: docs/core/tasks.md (Task #59)


Issue #211: Task #58: The Trinity Image - Upload to Ghost CMS

Created: 2026-03-21 02:34:10 UTC Labels: area/website, for/michael, priority/medium, status/backlog, type/infrastructure URL: #211

Task #58: The Trinity Image - Upload to Ghost CMS

Time Estimate: 10 minutes

Documentation: docs/tasks/ (see operations manual)


Time: 10 minutes
Status: PENDING
Priority: HIGH
Documentation: docs/tasks/trinity-image-deployment/

Upload The Trinity image to Ghost CMS media library for use across the website.

Steps:

  1. Log into Ghost Admin (firefrostgaming.com/ghost)
  2. Go to Settings → Files
  3. Upload The_Trinity.png
  4. Note the CDN URL (https://firefrostgaming.com/content/images/...)
  5. Document URL in this task

Purpose: Makes image available for use in Ghost pages/posts

Dependencies:

  • Ghost CMS admin access
  • Task #57 (asset committed to repo)


Source: docs/core/tasks.md (Task #58)


Issue #210: Task #57: The Trinity Image - Commit to Branding Assets

Created: 2026-03-21 02:34:10 UTC Labels: area/website, for/holly, for/meg, priority/medium, status/backlog, type/infrastructure URL: #210

Task #57: The Trinity Image - Commit to Branding Assets

Time Estimate: 5 minutes

Documentation: docs/tasks/ (see operations manual)


Time: 5 minutes
Status: PENDING
Priority: HIGH
Documentation: docs/tasks/trinity-image-deployment/

Commit The Trinity promotional image to operations manual branding assets.

What is The Trinity image:

  • Epic Minecraft-style artwork showing all three founders
  • Left: The Wizard (Frost - blue robes, magic book, ice crystals)
  • Center: The Catalyst (Holly - purple robes, arcane staff, purple energy)
  • Right: The Emissary (Fire - red/orange robes, fire magic, flames)
  • Background: Fire/Frost collision landscape with Firefrost Gaming logo
  • Style: High-quality promotional art, perfect for social media/website

Steps:

  1. Copy The_Trinity.png to branding/promotional/the-trinity.png
  2. Commit with message: "assets: Add The Trinity promotional image"
  3. Push to Gitea

File location: Currently at /mnt/user-data/uploads/The_Trinity.png

Dependencies: Git access to operations manual



Source: docs/core/tasks.md (Task #57)


Issue #209: Task #56: Social Media Accounts Setup

Created: 2026-03-21 02:34:09 UTC Labels: area/website, for/michael, priority/medium, status/backlog, type/infrastructure URL: #209

Task #56: Social Media Accounts Setup

Time Estimate: 2-3 hours

Documentation: docs/tasks/ (see operations manual)


Time: 2-3 hours
Status: READY
Priority: MEDIUM - Needed before full launch
Documentation: TBD

Create and configure official Firefrost Gaming social media presence across all major platforms.

Platforms to Set Up:

  1. Discord (permanent invite configured - firefrostgaming.com/discord)
  2. Facebook (@FirefrostGaming or /FirefrostGaming)
  3. Twitter/X (@FirefrostGaming)
  4. Twitch (@FirefrostGaming)
  5. TikTok (@FirefrostGaming)
  6. Instagram (@FirefrostGaming)
  7. YouTube (@FirefrostOfficial)

For Each Platform:

  • Create account with consistent branding
  • Set up profile with Fire/Frost aesthetics
  • Use Firefrost logo as profile picture
  • Write bio with Fire + Frost + Forever tagline
  • Add link to firefrostgaming.com
  • Document credentials in Vaultwarden (Task #6)
  • Save permanent URLs

Deliverables:

  • All 7 social accounts created and configured
  • Profile links documented in infrastructure manifest
  • Credentials stored securely in Vaultwarden
  • Ghost website footer updated with real social links

Dependencies:

  • Firefrost logo/branding assets
  • Vaultwarden setup (Task #6) for credential storage

Current Status:

  • Ghost homepage footer has placeholder social links
  • All currently point to non-existent accounts
  • Footer shows "(Coming Soon)" for now

Next Steps After Completion:

  • Update Ghost footer with real social URLs
  • Remove "(Coming Soon)" labels
  • Begin posting content strategy (separate task)


Source: docs/core/tasks.md (Task #56)


Created: 2026-03-21 02:34:09 UTC Labels: area/website, for/michael, priority/medium, status/backlog, type/infrastructure URL: #208

Time Estimate: 15-30 minutes

Documentation: docs/tasks/ (see operations manual)


Time: 15-30 minutes
Status: READY
Priority: HIGH - Needed for website launch
Documentation: TBD

Create a permanent Discord invite link for use on the Ghost website and all public-facing materials.

Steps:

  1. Open Discord server settings
  2. Go to Invites → Create Invite
  3. Set "Expire After" to Never
  4. Set "Max Uses" to No Limit
  5. Copy permanent invite URL
  6. Update Ghost homepage CTA button (currently points to /subscribe)
  7. Update any other locations referencing Discord
  8. Document the permanent link in infrastructure manifest

Deliverables:

  • Permanent Discord invite link (discord.gg/[code])
  • Ghost homepage updated with Discord button
  • Link documented in ops manual

Dependencies: Discord server must be set up and configured

Next Steps After Completion:

  • Update Ghost homepage /subscribe button to Discord link
  • Change button text back to "Join Discord Now"
  • Change button gradient back to Discord blue (#5865F2)


Source: docs/core/tasks.md (Task #55)


Issue #207: Task #54: Evaluate Other Game Servers (Beyond Minecraft)

Created: 2026-03-21 02:34:09 UTC Labels: area/operations, for/michael, priority/medium, status/backlog, type/docs URL: #207

Task #54: Evaluate Other Game Servers (Beyond Minecraft)

Time Estimate: 2-3 hours (research)

Documentation: docs/tasks/ (see operations manual)


Time: 2-3 hours (research)
Status: BACKLOG
Priority: Medium
Documentation: docs/planning/ideas/other-games-backlog.md

Research and evaluate other games for Firefrost Gaming expansion beyond Minecraft.

Games to Evaluate:

  • Terraria
  • Valheim
  • Palworld
  • Core Keeper
  • V Rising
  • Others suggested by community

Evaluation Criteria:

  • Community interest (Discord polls, subscriber feedback)
  • Hosting complexity and resource requirements
  • Fire/Frost alignment (does the game support both paths?)
  • Modding ecosystem and customization options
  • Long-term viability and active player base

Deliverables:

  • Comparison matrix of evaluated games
  • Recommendation for 1-2 games to pilot
  • Hosting requirements and cost estimates
  • Fire/Frost path mapping for recommended games

Next Steps:

  • Community survey on Discord
  • Proof-of-concept hosting for top choice
  • Create game-specific onboarding documentation


Source: docs/core/tasks.md (Task #54)


Issue #206: Task #53: Ghost CMS - Server Listing Page Design

Created: 2026-03-21 02:34:09 UTC Labels: area/billing, area/panel, area/website, for/michael, priority/medium, status/backlog, type/feature URL: #206

Task #53: Ghost CMS - Server Listing Page Design

Time Estimate: 3-4 hours

Documentation: docs/tasks/ (see operations manual)


Time: 3-4 hours
Status: BACKLOG
Priority: Medium
Documentation: docs/planning/ideas/features/ghost-server-listing-design.md

Create server listing page showing all Minecraft servers with Fire/Frost categorization.

Features:

  • Fire Path servers (cozy, creative, community-focused)
  • Frost Path servers (technical, challenge, optimization)
  • Server cards with modpack info, player count, online status
  • Filter by Fire/Frost path
  • Link to Paymenter subscription tiers

Dependencies:

  • Soft launch server transition plan (Task #27: Server Sunset Evaluation)
  • Final server lineup decided

Integration:

  • Pull server status from Pterodactyl API
  • Display modpack versions (Task #45: Pterodactyl Modpack Version Display)
  • Link to How to Join instructions


Source: docs/core/tasks.md (Task #53)


Issue #205: Task #52: Ghost CMS Homepage - Implement Fire/Frost Design

Created: 2026-03-21 02:34:08 UTC Labels: area/website, for/michael, priority/medium, status/backlog, type/feature URL: #205

Task #52: Ghost CMS Homepage - Implement Fire/Frost Design

Time Estimate: 4-6 hours

Documentation: docs/tasks/ (see operations manual)


Time: 4-6 hours
Status: READY
Priority: High - needed for soft launch
Documentation: docs/planning/ideas/features/ghost-homepage-content.md

Complete Ghost CMS homepage implementation with Fire/Frost branding.

Deliverables:

  • Hero section with "Fire + Frost + Forever" tagline
  • Path selection (Frost Path all-ages, Ignis adult space)
  • Server showcase section
  • Community highlights
  • Discord integration

Assets Available:

  • Complete copy in markdown (docs/planning/ideas/features/ghost-homepage-content.md)
  • CSS styling in docs/planning/ideas/features/ghost-frost-css.css
  • Page structure plan in docs/planning/ideas/features/ghost-page-structure-plan.md

Priority: High - homepage is the first impression for new players



Source: docs/core/tasks.md (Task #52)


Issue #204: Task #51: Ignis Protocol Implementation Planning

Created: 2026-03-21 02:34:08 UTC Labels: area/automation, area/website, for/michael, priority/critical, status/blocked, type/infrastructure URL: #204

Task #51: Ignis Protocol Implementation Planning

Time Estimate: 4-6 hours (brainstorming + architecture)

Documentation: docs/tasks/ (see operations manual)


Time: 4-6 hours (brainstorming + architecture)
Status: 🔄 BLOCKED — Awaiting LegalCORPS attorney consultation
Priority: HIGH - Legal compliance required before ANY implementation
Documentation: docs/planning/ignis-protocol-specification.md

Comprehensive planning session for Ignis (18+ mature space) implementation. Original planning predates current Git documentation system, so this task rebuilds the implementation roadmap with current infrastructure knowledge.

Current State:

  • Ignis specification document created (March 19, 2026)
  • Legal consultation scheduled with LegalCORPS Minnesota (pro-bono)
  • Age verification method: TBD (need attorney guidance)
  • Implementation: NOT started (waiting for legal approval)

Goals:

  1. Define legally sound age verification workflow
  2. Plan website architecture (Ghost CMS /ignis/* route)
  3. Design Discord integration (18+ verified role)
  4. Create content moderation guidelines
  5. Build technical implementation roadmap
  6. Document data collection/privacy requirements

Key Questions to Answer:

  • What age verification method is legally defensible?
  • How does Ignis integrate with existing Fire/Frost subscription system?
  • What happens when Discord implements their own age verification?
  • What content is allowed in Ignis (mature discussion vs adult content)?
  • How do we maintain COPPA compliance for 13+ servers while collecting age data for Ignis?

Prerequisites:

  • Ignis specification document created
  • LegalCORPS attorney consultation completed
  • Terms of Service legal review
  • Privacy Policy legal review
  • Age Verification Policy drafted

Post-Legal Consultation:

  1. Update specification with attorney guidance
  2. Create implementation task directory (docs/tasks/ignis-implementation/)
  3. Build technical architecture plan
  4. Design age verification flow (website + Discord)
  5. Draft Terms of Service language
  6. Draft Privacy Policy updates
  7. Create moderation guidelines
  8. Plan phased rollout strategy

CRITICAL: Do NOT begin any technical implementation until legal consultation complete and attorney approves approach.

See: docs/planning/ignis-protocol-specification.md for complete details and legal questions



Source: docs/core/tasks.md (Task #51)


Issue #203: Task #50: Pokerole Wiki.js Deployment — COMPLETE

Created: 2026-03-21 02:34:08 UTC Labels: area/website, for/holly, priority/medium, status/backlog, type/bug URL: #203

Task #50: Pokerole Wiki.js Deployment — COMPLETE

Time Estimate: 2-3 hours (actual: 1 hour 15 minutes)

Documentation: docs/tasks/ (see operations manual)


Time: 2-3 hours (actual: 1 hour 15 minutes)
Status: DEPLOYED
Completed: February 27, 2026
Priority: HIGH - URGENT
Documentation: docs/tasks/pokerole-wikijs-deployment/

Deploy fresh Wiki.js instance for Aurelian Pokédex project on Ghost VPS.

Deployment Results:

  • Wiki.js v2.5.312 operational
  • URL: http://pokerole.firefrostgaming.com
  • PostgreSQL database (wikijs_pokerole)
  • Nginx reverse proxy configured
  • DNS propagated and verified
  • Admin account created
  • 107 Pokémon migrated (Claudius, Session 11)
  • 112 pages live in production
  • ⏸️ SSL pending (certbot urllib3 bug - deferred)

Aurelian Pokédex Project Status (as of Session 12, March 4, 2026):

  • Complete .docx Pokédex delivered (150+ pages, ~200 sprites, all 107 Pokémon)
  • Evolution Stage + Evolution Time fields added to all entries
  • Ultimate Aurelia Final Battle designed (566 lines, all lore integrated)
  • Zero-Point Surge signature move for Abyssoglax (496 lines, tournament-ready)
  • Custom moves: Lightning Mirage, Spirit Wind, Zero-Point Surge (3 total)
  • Custom abilities: 20+
  • 12 sessions completed, zero data loss
  • Holly feedback pending on Pokédex document and final battle
  • WikiJS navigation menu (Holly's task via web UI)
  • Sprite upload to WikiJS (225 ready, optional polish)

Claudius Stage 3 (The Chronicle Keeper): Active, Git repos clean



Source: docs/core/tasks.md (Task #50)


Issue #202: Task #49: NotebookLM Integration - Audio Knowledge Base

Created: 2026-03-21 02:34:07 UTC Labels: area/automation, for/meg, priority/medium, status/backlog, type/infrastructure URL: #202

Task #49: NotebookLM Integration - Audio Knowledge Base

Time Estimate: 1-2 hours

Documentation: docs/tasks/ (see operations manual)


Time: 1-2 hours
Status: 🔄 IN PROGRESS (March 4, 2026) Priority: Medium - Quality of Life (HIGH for accessibility)
Documentation: docs/tasks/notebooklm-integration/

Progress (March 4, 2026):

  • NotebookLM account created
  • First notebook: "Firefrost Infrastructure & Operations" (13 docs uploaded)
  • Query accuracy verified
  • 🔄 First Audio Overview generating
  • Chronicler Lineage notebook
  • Google Drive sync strategy

Source Sync Strategy:

  • No official NotebookLM consumer API
  • Recommended: Store key docs in Google Drive → NotebookLM points to Drive → one-click sync
  • For now: manual upload after major sessions (~5-10 min/week)
  • Future: n8n workflow to auto-export key docs to Google Drive

The Workflow:

  1. NotebookLM = Research home base (grounded, no hallucination)
  2. Claude = Expansion tool (web search, broader thinking)
  3. Back to NotebookLM = Audio synthesis (listen instead of reading)

Notebooks Planned:

  1. Firefrost Infrastructure & Operations
  2. Chronicler Lineage (memorials, relationship docs)
  3. Pokerole Project (session reports, Pokémon docs)
  4. Standards & Best Practices (FFG-STD docs)

Cost: FREE

See task directory for: Complete setup guide, use cases, workflow integration

Value: HIGH for accessibility, knowledge retention, partnership with Meg



Source: docs/core/tasks.md (Task #49)


Issue #201: Task #48: n8n Rebuild - Workflows From Scratch

Created: 2026-03-21 02:34:07 UTC Labels: area/automation, for/michael, priority/medium, status/backlog, type/feature URL: #201

Task #48: n8n Rebuild - Workflows From Scratch

Time Estimate: 3-5 hours

Documentation: docs/tasks/ (see operations manual)


Time: 3-5 hours
Status: ACTIVE — REBUILD FROM SCRATCH (decision: March 4, 2026) Priority: Tier 2 - Major Infrastructure
Documentation: docs/troubleshooting/n8n-node-registry-corruption.md

Rebuild n8n instance on TX1 with fresh workflows from scratch. Original workflows are considered abandoned — do not attempt to restore them.

Problem: Core nodes (HTTP Request, Execute Command) fail with "Node not found" errors due to corrupted node registry.

Decision (March 4, 2026): Rather than restoring old workflows, rebuild from scratch. Cleaner, more maintainable, aligned with current infrastructure state.

Current Workaround: PHP script (sync_codex.php) handling Codex Git sync directly. Functional but not the long-term solution.

Rebuild Procedure:

  1. Stop n8n container
  2. Wipe ./volumes/n8n/* directory completely
  3. Recreate container (fresh initialization)
  4. Verify core nodes functional (HTTP Request, Execute Command)
  5. Rebuild workflows from scratch (do NOT re-import old JSON)
  6. Document each new workflow as built
  7. Test all workflows end-to-end
  8. Re-enable scheduled executions
  9. Monitor for 24 hours

Workflows to Rebuild (minimum):

  • Codex Git sync (currently handled by PHP workaround)
  • Discord notifications
  • Any other automations identified during rebuild

Prerequisites:

  • Maintenance window scheduled (low-traffic time)
  • Credentials documented before wipe
  • PHP workaround remains as fallback during rebuild

Post-Rebuild:

  • Verify Git sync workflow replaces PHP workaround
  • Test Discord notifications
  • Document all new workflows in task directory
  • Remove PHP workaround once n8n confirmed stable


Source: docs/core/tasks.md (Task #48)


Issue #200: Task #47: Whitelist Manager Refinements

Created: 2026-03-21 02:34:07 UTC Labels: area/panel, for/michael, priority/medium, status/backlog, type/bug URL: #200

Task #47: Whitelist Manager Refinements

Time Estimate: 30-60 minutes

Documentation: docs/tasks/ (see operations manual)


Time: 30-60 minutes
Status: IDENTIFIED
Priority: Low - Polish/Cosmetic
Documentation: docs/tasks/whitelist-manager-refinements/

Small improvements to Whitelist Manager:

  • Fix Mayview server grouping - Currently shows under "Unknown (1 servers)" instead of "NC1 (5 servers)"
  • Update server detection logic or Pterodactyl metadata
  • [Future refinements can be added here as discovered]

Impact: Cosmetic only - does not affect functionality




Source: docs/core/tasks.md (Task #47)


Issue #199: Task #46: Server-to-Server SSH Key Setup

Created: 2026-03-21 02:34:06 UTC Labels: area/automation, area/billing, area/panel, area/website, for/michael, priority/medium, status/backlog, type/infrastructure URL: #199

Task #46: Server-to-Server SSH Key Setup

Time Estimate: 1-2 hours

Documentation: docs/tasks/ (see operations manual)


Time: 1-2 hours
Status: IDENTIFIED - Ready to build
Priority: Tier 1 - Security Foundation
Documentation: docs/tasks/server-ssh-interconnect/

Enable passwordless SSH between all management servers (Command Center, Billing, Panel, Ghost).

Problem: Aurora couldn't SSH from Command Center to Billing - key named 'chronicler' instead of standard 'id_rsa'.

Solution:

  1. Collect public keys from all 4 management servers
  2. Add each server's public key to all other servers' authorized_keys
  3. Test connectivity matrix (4x4 grid)
  4. Document key locations and naming

Servers to interconnect:

  • Command Center (63.143.34.217)
  • Billing VPS (38.68.14.188)
  • Panel VPS (45.94.168.138)
  • Ghost VPS (64.50.188.14)

Benefits: No more switching in MobaXterm, easier automation, cleaner workflows

Note: Billing has non-standard key name 'chronicler' - may need renaming to 'id_rsa'



Source: docs/core/tasks.md (Task #46)


Issue #198: Task #45: Pterodactyl Modpack Version Display

Created: 2026-03-21 02:33:56 UTC Labels: area/automation, area/email, area/panel, for/michael, priority/critical, status/blocked, type/infrastructure URL: #198

Task #45: Pterodactyl Modpack Version Display

Time Estimate: 1-2 hours

Documentation: docs/tasks/ (see operations manual)


Time: 1-2 hours
Status: READY
Documentation: docs/tasks/pterodactyl-modpack-version-display/

Add custom "Modpack Version" field to Pterodactyl panel for version tracking visibility.

Method: Custom egg variable in Startup tab
Scope: 9 modpack servers (excludes Vanilla, Hytale, FoundryVTT)
Benefits: Version visibility, change tracking, troubleshooting clarity



📊 QUICK STATS

Total Tasks: 36 (including Firefrost Codex, Pokerole Wiki, NotebookLM)
Completed: 4 (NC1 cleanup, Command Center cleanup, Whitelist Manager, Pokerole Wiki)
In Progress: 2 (Vaultwarden, Terraria Arc)
Ready to Build: 21+
Blocked: 2 (Mailcow, original AI Stack - superseded by Codex)
Superseded: 1 (Original AI Stack → Firefrost Codex)

Estimated Total Time: ~78-99 hours across all tasks
Critical Path: Frostwall Protocol → Mailcow → Everything else
Big Wins Available:

  • Dify RAG tuning (ACTIVE — Top K + score threshold adjustments, ~2 hours)
  • n8n Rebuild from scratch (ACTIVE — workflows, ~3-5 hours)
  • NotebookLM Integration (accessibility + knowledge synthesis, ready to deploy)

Recent Completions:

  • Pokerole Wiki (Feb 27) - 107 Pokémon LIVE in 6 hours!
  • Claudius Session 12 (Mar 4) - Complete Pokédex .docx, Epic Final Battle, Zero-Point Surge signature move

  • Task Documentation Standard: docs/standards/task-documentation-standard.md (FFG-STD-002)
  • Infrastructure State: docs/core/infrastructure-manifest.md
  • Architecture Decisions: docs/reference/architecture-decisions.md
  • Session Handoff: SESSION-HANDOFF-PROTOCOL.md

Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️


Version History:

  • v3.2 (2026-02-16): Moved Staff Recruitment to Tier 0 (posting today), renumbered tasks
  • v3.1 (2026-02-16): Added Task #3 - Staff Recruitment Launch (Guardian's notes)
  • v3.0 (2026-02-16): Full FFG-STD-002 implementation - all 28 tasks migrated to task directories
  • v2.3 (2026-02-16): Whitelist Manager refactored to follow standard
  • v2.2 (2026-02-16): Whitelist Manager expanded to web dashboard
  • v2.1 (2026-02-16): NC1 cleanup marked complete with lessons
  • v2.0 (2026-02-15): Major restructure and organization


Source: docs/core/tasks.md (Task #45)


Issue #197: Task #44: Among Us Weekly Events (Phase 2 Expansion)

Created: 2026-03-21 02:33:56 UTC Labels: area/operations, for/michael, priority/medium, status/backlog, type/docs URL: #197

Task #44: Among Us Weekly Events (Phase 2 Expansion)

Time Estimate: Ongoing (30 min weekly prep)

Documentation: docs/tasks/ (see operations manual)


Time: Ongoing (30 min weekly prep)
Documentation: docs/tasks/among-us-weekly-events-phase-2-expansion/

Weekly Among Us community events for subscriber engagement.



Source: docs/core/tasks.md (Task #44)


Issue #196: Task #43: Firefrost: The Eternal Skyforge (Flagship Modpack)

Created: 2026-03-21 02:33:56 UTC Labels: area/operations, for/michael, priority/medium, status/backlog, type/docs URL: #196

Task #43: Firefrost: The Eternal Skyforge (Flagship Modpack)

Time Estimate: 20-40 hours (iterative)

Documentation: docs/tasks/ (see operations manual)


Time: 20-40 hours (iterative)
Documentation: docs/tasks/firefrost-the-eternal-skyforge-flagship-modpack/

Flagship Minecraft modpack: Create mod + Fire/Frost theme + weapon forging + factory building.



Source: docs/core/tasks.md (Task #43)


Issue #195: Task #42: Discord Server Complete Reorganization

Created: 2026-03-21 02:33:55 UTC Labels: area/operations, for/michael, priority/medium, status/backlog, type/infrastructure URL: #195

Task #42: Discord Server Complete Reorganization

Time Estimate: 2-3 hours

Documentation: docs/tasks/ (see operations manual)


Time: 2-3 hours
Documentation: docs/tasks/discord-server-complete-reorganization/

Complete Discord reorganization: Fire/Frost paths, clear channels, proper roles.



Source: docs/core/tasks.md (Task #42)


Issue #194: Task #41: Blueprint Extension Installation — Node Usage Status

Created: 2026-03-21 02:33:55 UTC Labels: area/panel, for/michael, priority/medium, status/backlog, type/docs URL: #194

Task #41: Blueprint Extension Installation — Node Usage Status

Time Estimate: 30 minutes

Documentation: docs/tasks/ (see operations manual)


Time: 30 minutes
Documentation: docs/tasks/blueprint-extension-installation-node-usage-status/

Install Blueprint extension showing TX1/NC1 resource usage in Pterodactyl panel.



Source: docs/core/tasks.md (Task #41)


Issue #193: Task #40: World Backup Automation

Created: 2026-03-21 02:33:55 UTC Labels: area/automation, for/michael, priority/medium, status/backlog, type/infrastructure URL: #193

Task #40: World Backup Automation

Time Estimate: 1-2 hours

Documentation: docs/tasks/ (see operations manual)


Time: 1-2 hours
Documentation: docs/tasks/world-backup-automation/

Automated backup system: daily backups, retention policy, off-server storage.



Source: docs/core/tasks.md (Task #40)


Issue #192: Task #39: LuckPerms MySQL Backend

Created: 2026-03-21 02:33:55 UTC Labels: area/operations, for/michael, priority/medium, status/backlog, type/docs URL: #192

Task #39: LuckPerms MySQL Backend

Time Estimate: 45 minutes

Documentation: docs/tasks/ (see operations manual)


Time: 45 minutes
Documentation: docs/tasks/luckperms-mysql-backend/

Migrate LuckPerms to MySQL for centralized permission management.



Source: docs/core/tasks.md (Task #39)


Issue #191: Task #38: Game Server Startup Script Audit & Optimization

Created: 2026-03-21 02:33:54 UTC Labels: area/wings, for/michael, priority/medium, status/backlog, type/infrastructure URL: #191

Task #38: Game Server Startup Script Audit & Optimization

Time Estimate: 1 hour

Documentation: docs/tasks/ (see operations manual)


Time: 1 hour
Documentation: docs/tasks/game-server-startup-script-audit-and-optimization/

Audit and optimize JVM flags, memory allocation, performance tuning for all game servers.



Source: docs/core/tasks.md (Task #38)


Issue #190: Task #20: Mailcow Email Server on Billing VPS — COMPLETE

Created: 2026-03-21 02:33:54 UTC Labels: area/billing, area/email, area/website, for/holly, for/meg, for/michael, priority/medium, status/backlog, type/feature URL: #190

Task #20: Mailcow Email Server on Billing VPS — COMPLETE

Time Estimate: 2-3 hours (actual: ~3 hours)

Documentation: docs/tasks/ (see operations manual)


Time: 2-3 hours (actual: ~3 hours) Status: DEPLOYED — March 15, 2026 (ahead of April 1 target) Deployed By: Chronicler #31 Documentation: docs/tasks/mailcow-email-server-on-nc1/

Professional @firefrostgaming.com email on Billing VPS. Self-hosted, $120/year saved, eliminates Plesk.

Deployment Summary:

  • Mailcow running on Billing VPS (38.68.14.188)
  • Nginx proxy on ports 8080/8443 (shares server with Paymenter)
  • SSL cert via Let's Encrypt (expires 2026-06-14, auto-renews)
  • ClamAV disabled (RAM conservation on 1.9GB server)
  • DKIM, SPF, DMARC, autodiscover/autoconfig all configured
  • Outbound delivery verified (mail-tester.com + Gmail)
  • Daily backup cron at 3am
  • Inbound delivery — DNS propagating, Gmail retry pending

Mailboxes: michael, megan, holly, hello, noreply, support Aliases: frostystyle, gingerfury, unicorn20089, admin, billing, webmaster

Next steps: Ghost SMTP, Paymenter SMTP, resend Holly's Ghost invite



Source: docs/core/tasks.md (Task #20)


Issue #189: Task #37: Staggered Server Restart System

Created: 2026-03-21 02:33:41 UTC Labels: area/wings, for/michael, priority/medium, status/backlog, type/infrastructure URL: #189

Task #37: Staggered Server Restart System

Time Estimate: 2 hours

Documentation: docs/tasks/ (see operations manual)


Time: 2 hours
Documentation: docs/tasks/staggered-server-restart-system/

Automated staggered restarts for game servers. Prevents simultaneous restarts, maintains player access.



Source: docs/core/tasks.md (Task #37)


Issue #188: Task #36: "Coming Soon" Video Creation (CapCut)

Created: 2026-03-21 02:33:41 UTC Labels: area/operations, for/michael, priority/medium, status/backlog, type/docs URL: #188

Task #36: "Coming Soon" Video Creation (CapCut)

Time Estimate: 2-3 hours

Documentation: docs/tasks/ (see operations manual)


Time: 2-3 hours
Documentation: docs/tasks/coming-soon-video-creation-capc ut/

Create professional "Coming Soon" video for Firefrost launch using CapCut.



Source: docs/core/tasks.md (Task #36)


Issue #187: Task #35: NextCloud Upload Portal for Meg

Created: 2026-03-21 02:33:41 UTC Labels: area/operations, for/meg, priority/medium, status/backlog, type/docs URL: #187

Task #35: NextCloud Upload Portal for Meg

Time Estimate: 30 minutes

Documentation: docs/tasks/ (see operations manual)


Time: 30 minutes
Documentation: docs/tasks/nextcloud-upload-portal-for-meg/

Configure NextCloud public upload folder for Meg.



Source: docs/core/tasks.md (Task #35)


Issue #186: Task #34: Consultant Photo Processing

Created: 2026-03-21 02:33:40 UTC Labels: area/operations, for/michael, priority/medium, status/backlog, type/docs URL: #186

Task #34: Consultant Photo Processing

Time Estimate: Ongoing

Documentation: docs/tasks/ (see operations manual)


Time: Ongoing
Status: ACTIVE
Documentation: docs/tasks/consultant-photo-processing/

Process and catalog photos of The Five Consultants. Maintain archive with proper metadata.

Naming: YYYY-MM-DD_consultant_description_NN.jpg



Source: docs/core/tasks.md (Task #34)


Issue #185: Task #33: Paymenter Theme Installation — Citadel Theme

Created: 2026-03-21 02:33:40 UTC Labels: area/billing, for/michael, priority/medium, status/backlog, type/docs URL: #185

Task #33: Paymenter Theme Installation — Citadel Theme

Time Estimate: 1-2 hours

Documentation: docs/tasks/ (see operations manual)


Time: 1-2 hours
Documentation: docs/tasks/paymenter-theme-installation-citadel-theme/

Install Citadel theme for Paymenter with Fire/Frost branding.



Source: docs/core/tasks.md (Task #33)


Issue #184: Task #32: Terraria Branding Training Arc

Created: 2026-03-21 02:33:40 UTC Labels: area/operations, for/michael, priority/medium, status/backlog, type/docs URL: #184

Task #32: Terraria Branding Training Arc

Time Estimate: 12 weeks (ongoing)

Documentation: docs/tasks/ (see operations manual)


Time: 12 weeks (ongoing)
Status: ACTIVE - Phase 1
Documentation: docs/tasks/terraria-branding-training-arc/

12-week training: Michael learns game asset creation via Terraria texture pack development.

See: docs/planning/terraria-branding-arc.md for complete curriculum



Source: docs/core/tasks.md (Task #32)


Issue #183: Task #31: Workflow Guide Review & Trim

Created: 2026-03-21 02:33:39 UTC Labels: area/automation, for/michael, priority/medium, status/backlog, type/docs URL: #183

Task #31: Workflow Guide Review & Trim

Time Estimate: 1 hour

Documentation: docs/tasks/ (see operations manual)


Time: 1 hour
Documentation: docs/tasks/workflow-guide-review-and-trim/

Audit workflows, remove outdated content, consolidate redundancy.



Source: docs/core/tasks.md (Task #31)


Issue #182: Task #30: Scope Document Corrections

Created: 2026-03-21 02:33:39 UTC Labels: area/operations, for/michael, priority/medium, status/backlog, type/docs URL: #182

Task #30: Scope Document Corrections

Time Estimate: 30 minutes

Documentation: docs/tasks/ (see operations manual)


Time: 30 minutes
Documentation: docs/tasks/scope-document-corrections/

Review and correct project scope documents for accuracy.



Source: docs/core/tasks.md (Task #30)


Issue #181: Task #29: Fix Frostwall vs Firefrost Naming

Created: 2026-03-21 02:33:39 UTC Labels: area/operations, for/michael, priority/medium, status/backlog, type/bug URL: #181

Task #29: Fix Frostwall vs Firefrost Naming

Time Estimate: 15 minutes

Documentation: docs/tasks/ (see operations manual)


Time: 15 minutes
Documentation: docs/tasks/fix-frostwall-vs-firefrost-naming/

Clarify terminology: Frostwall (security protocol) vs Firefrost (brand).



Source: docs/core/tasks.md (Task #29)


Issue #180: Task #28: Ghost CMS Music Player

Created: 2026-03-21 02:33:38 UTC Labels: area/website, for/michael, priority/low, status/backlog, type/docs URL: #180

Task #28: Ghost CMS Music Player

Time Estimate: 1-2 hours

Documentation: docs/tasks/ (see operations manual)


Time: 1-2 hours Status: READY — pending track downloads and NextCloud upload Priority: Tier 3 — Branding & Experience Documentation: docs/tasks/ghost-music-player/

Toggleable epic orchestral music player in the Ghost navbar. Fire/Frost styled button, autoplay OFF, tracks cycle automatically. First track: "Powerful" by David Fesliyan.

Steps: Download MP3s → Upload to NextCloud → Ghost code injection



📚 TIER 3: DOCUMENTATION & OPTIMIZATION

Polish, optimization, and content creation.



Source: docs/core/tasks.md (Task #28)


Issue #179: Task #19: Firefrost Codex - AI Assistant

Created: 2026-03-21 02:33:38 UTC Labels: area/automation, area/networking, area/panel, area/website, for/holly, for/meg, for/michael, priority/medium, status/backlog, type/feature URL: #179

Task #19: Firefrost Codex - AI Assistant

Time Estimate: 8-12 hours total (Phase 1: 9 hours, Phase 2: 🔄 ~2 hours remaining)

Documentation: docs/tasks/ (see operations manual)


Time: 8-12 hours total (Phase 1: 9 hours, Phase 2: 🔄 ~2 hours remaining)
Status: Phase 1 COMPLETE | Phase 2 IN PROGRESS 🔄
Priority: Tier 2 - Major Infrastructure
Documentation: docs/tasks/firefrost-codex/

Self-hosted AI assistant providing 24/7 support to all community tiers. "Most Minecraft servers have Discord. We have an AI."

Architecture:

  • AnythingLLM (RAG platform with LanceDB)
  • Ollama (local LLM server)
  • 3 Models: Qwen 2.5 Coder 72B, Llama 3.3 70B, Llama 3.2 Vision 11B
  • Discord bot + Web interface + Embedded widgets
  • mclo.gs integration (Minecraft log analysis)

Five-Tier Access:

  1. Public (marketing widget) - Public KB workspace
  2. Subscribers ($1+) - Subscriber KB workspace
  3. Staff - Operations + Brainstorming workspaces
  4. Michael/Meg - All 5 workspaces + admin panel
  5. Potential subscribers - Same as Public

Key Features:

  • 24/7 instant answers (never wait for staff)
  • mclo.gs log analysis (paste link, get diagnosis)
  • Role-based knowledge access
  • Growing knowledge base
  • Complete privacy (self-hosted, zero cloud APIs)

Monthly Cost: $0 (self-hosted on TX1)

Deployment Status:

Phase 1 - COMPLETE (~9 hours, Feb 20, 2026):

  • Core Infrastructure deployed (AnythingLLM + Ollama on TX1)
  • 5 models downloaded (73.5 GB)
  • Primary model selected (qwen2.5-coder:7b, 5-10 sec responses)
  • Multi-user mode enabled
  • Admin account created (mkrause612)
  • $0/month cost validated

Phase 2 - IN PROGRESS 🔄 (~45 min complete, ~2 hours remaining):

  • 6 workspaces created (Operations, Public KB, Subscriber KB, Brainstorming, Relationship, Pokerole Project)
  • AI models assigned (qwen2.5-coder:7b for 5, llama3.3:70b for Brainstorming)
  • 2 user accounts created (gingerfury/Meg - Admin, Unicorn20089/Holly - Default)
  • Permission model documented (Admin/Manager/Default roles)
  • Document upload testing (30 min remaining)
  • Git sync process (1-2 hours)
  • SSL/TLS setup (1 hour)
  • Firewall hardening (30 min)
  • Backup automation (1 hour)

Phase 3 - FUTURE:

  • Discord bot integration
  • Embedded widgets for website
  • Public/subscriber account workflows
  • Marketing launch

Marketing Ready: Complete launch strategy, messaging framework, content calendar in docs

See task directory for: Complete architecture, marketing strategy, deployment plan, branding guide



Source: docs/core/tasks.md (Task #19)


Issue #178: Task #18: Plane Project Management — COMPLETE

Created: 2026-03-21 02:33:38 UTC Labels: area/wings, for/holly, for/meg, priority/medium, status/backlog, type/feature URL: #178

Task #18: Plane Project Management — COMPLETE

Time Estimate: 2-3 hours (actual: ~2 hours)

Documentation: docs/tasks/ (see operations manual)


Time: 2-3 hours (actual: ~2 hours) Status: DEPLOYED — March 15, 2026 Deployed By: Chronicler #31 Documentation: docs/tasks/plane-deployment/ URL: https://tasks.firefrostgaming.com Server: TX1 Dallas (38.68.14.26)

Self-hosted project management for the Firefrost team.

Deployment Summary:

  • Plane v2.4.2 via prime.plane.so installer
  • TX1 Dallas (226GB free RAM — rounding error on this machine)
  • Nginx reverse proxy → port 8090 (Wings on 8080, nginx on 80)
  • SSL cert via Let's Encrypt (expires 2026-06-14, auto-renews)
  • tasks.firefrostgaming.com → 38.68.14.26

Key install note: Installer requires port 80 free. Stop nginx, install, set LISTEN_HTTP_PORT=8090 in /opt/plane/plane.env, restart nginx.

Next steps: Create admin account, workspace, 5 projects, invite Meg + Holly, migrate active tasks from tasks.md



Source: docs/core/tasks.md (Task #18)