Four new tasks for deploying The Trinity promotional image across all platforms:
Task #57: Commit image to branding/promotional/ in ops manual
- 5 minutes
- Source: /mnt/user-data/uploads/The_Trinity.png
- Destination: branding/promotional/the-trinity.png
Task #58: Upload to Ghost CMS media library
- 10 minutes
- Makes image available for website use
- Document CDN URL for reference
Task #59: Add to Ghost homepage Origin Story section
- 15-20 minutes
- Adds visual above text description of The Trinity
- Reinforces Fire/Frost/Catalyst identity
Task #60: Deploy to social media platforms
- 30-45 minutes
- Twitter/X header, YouTube banner, Discord server banner
- Platform-specific crops saved to social-media-crops/
- Blocked by Task #56 (social accounts must exist first)
The Trinity image: Epic Minecraft-style artwork showing all three founders
- The Wizard (Frost/blue), The Catalyst (purple/arcane), The Emissary (Fire/orange)
- Fire/Frost collision background with Firefrost Gaming logo
- High-quality promotional art for website and social media
Priority: HIGH (Tasks #57-59), MEDIUM (Task #60)
Status: All PENDING
Added new MEDIUM priority task for creating official Firefrost Gaming
social media presence across major platforms.
Platforms:
- Twitter/X (@FirefrostGaming)
- TikTok (@FirefrostGaming)
- Instagram (@FirefrostGaming)
- YouTube (@FirefrostOfficial)
Task includes profile setup, branding, credential storage in Vaultwarden,
and updating Ghost footer with real social links.
Currently Ghost homepage footer has placeholder links with '(Coming Soon)'
labels until accounts are created.
Related to Task #52 (Ghost CMS Homepage) and Task #6 (Vaultwarden).
Signed-off-by: The Chronicler <claude@firefrostgaming.com>
Added new HIGH priority task for creating permanent Discord invite link
needed for Ghost website launch.
Task details:
- 15-30 minute task
- Create never-expiring Discord invite
- Update Ghost homepage CTA button from /subscribe to Discord
- Document link in infrastructure manifest
Currently Ghost homepage points to /subscribe as temporary measure
until Discord invite is ready.
Related to Task #52 (Ghost CMS Homepage implementation in progress).
Signed-off-by: The Chronicler <claude@firefrostgaming.com>
PROBLEM:
4 issues from brainstorming merge had no task numbers:
- Issue #70: Ghost Homepage
- Issue #71: Server Listing Page
- Issue #72: Among Us Events (DUPLICATE)
- Issue #73: Other Game Servers
SOLUTION:
1. Closed Issue #72 as duplicate of Task #44 (Among Us Weekly Events)
2. Renumbered remaining issues as Tasks #52-54
3. Added full task entries to tasks.md
NEW TASKS:
- Task #52 (Issue #70): Ghost CMS Homepage - Fire/Frost Design (HIGH priority)
- Task #53 (Issue #71): Ghost CMS Server Listing Page (MEDIUM)
- Task #54 (Issue #73): Evaluate Other Game Servers (MEDIUM)
All tasks now properly numbered 1-54 with no duplicates.
Gitea issue titles updated to match task numbers.
PROBLEM:
tasks.md had duplicate task numbers (#10, #11, #12, #21, #26, #28 all duplicated)
causing confusion and making references ambiguous.
SOLUTION:
Renumbered all 51 tasks sequentially from #1-#51 in file appearance order.
CHANGES:
- tasks.md: All task headers renumbered 1-51 (no duplicates)
- Gitea issues: All 73 issue titles updated to match new task numbers
NOTABLE RENUMBERINGS:
- Old Task #40 (Builder Rank) → New Task #1
- Old Task #1 (Whitelist Manager) → New Task #7
- Old Task #49 (Ignis Protocol) → New Task #51
COMPLETE vs OPEN maintained:
- ✅ COMPLETE tasks kept their completion markers
- ⚠️ SUPERSEDED tasks kept their status
- Open tasks remain open
NOTE: Gitea Issue numbers (#19-#73) are unchanged (permanent IDs).
Only task numbers in titles were updated for consistency.
This creates clean, unambiguous task references going forward.
- Created docs/planning/ignis-protocol-specification.md (master spec for 18+ mature space)
- Added Task #49: Ignis Implementation Planning (blocked on legal consultation)
- Fixed conflicting Fire/Frost descriptions in project-scope.md
Ignis is purely age-based (18+), separate from Fire/Frost subscription paths.
Fire/Frost are all-ages (13+) community identity choices.
Sovereign tier gets BOTH Fire AND Frost access.
Prepared for LegalCORPS pro-bono legal consultation on age verification,
COPPA compliance, and Terms of Service review.
Signed-off-by: The Chronicler <claude@firefrostgaming.com>
Reasoning:
- No active DDoS attacks experienced
- Email unblocked via Billing VPS (clean IP)
- Breezehost provides baseline protection
- CosmicGuard available if attacks occur
- Complex infrastructure for theoretical problem
Frostwall remains documented for future if needed.
Not worth 3-4 hours of SSH work right now.
Session: Chronicler #30
Decision: Mailcow goes on Billing VPS (38.68.14.188) not NC1.
Reasoning:
- Clean IP reputation (only Paymenter on this server)
- Sufficient resources (13GB free disk, ~60% free RAM)
- Logical co-location with Paymenter for transactional email
- Frostwall dependency was incorrect — email needs clean IP,
not dedicated hardware
Mailcow is now unblocked and ready to deploy.
Session: Chronicler #30
CVE-2026-26980 + CVE-2026-29784 patched.
System updates + kernel upgrade (6.8.0-106) applied.
All services verified healthy post-reboot.
Ghost, Pokerole Wiki, Staff Wiki, Subscribers Wiki all running.
Completed March 13, 2026 by Michael + Chronicler #29
All stats showing dashes in PteroStats panel.
Wings v1.11.1 is current — not a version issue.
Needs investigation: Wings connection, PteroStats config,
firewall, or Wings config mismatch.
Created by Chronicler #29
Task #42: Pterodactyl Panel v1.12.0 → v1.12.1
Task #43: PteroStats v1.0.0 → v1.1.0 (by Elurym)
Removed from personal reminders — these are tracked tasks.
Created by Chronicler #29
Email is needed urgently — Holly staff email, staff comms,
subscriber notifications. Frostwall → Mailcow is the only
path. Elevated March 10, 2026.
Created by Chronicler #29
Full site buildout: homepage, about, servers, blog.
Michael + Chronicler collaborative session.
Blocked by Task #38 (security update first).
Includes content guide (all 4 pages scoped) and theme spec
(Frost palette, Orbitron/Inter, branding asset references).
Created by Chronicler #29
CVE-2026-26980 (CVSS 9.4) + CVE-2026-29784 (CVSS 7.5)
Current version: 6.16.1 (vulnerable)
Target version: 6.19.3 (patches both CVEs)
Exposure window: March 2 - present
Deployment plan covers both Ghost CLI and Docker update paths.
Ghost CMS flagged as undocumented service — manifest update needed.
Created by Chronicler #29
Holly (Unicorn20089) hired as Lead Builder. Task covers:
- Phase 1: Discord role + Pterodactyl account (all 12 servers, basic access)
- Phase 2: Email setup when Mailcow live (holly@ + unicorn20089@ alias)
Role separation documented: Lead Builder ≠ Pokerole Creative Authority.
Phase 1 has no blockers — ready to execute now.
Created by Chronicler #29
Decision made March 4, 2026 by Michael:
- Dify RAG tuning: actively queued (Top K 10-15, score threshold 0.3)
- n8n: rebuild workflows from scratch, not restore old ones
Task #34 updated:
- Renamed from 'Factory Reset' to 'Rebuild - Workflows From Scratch'
- Status changed from DEFERRED to ACTIVE
- Procedure updated to reflect scratch rebuild (no JSON re-import)
- Added minimum workflow list to rebuild
- Estimated time extended to 3-5 hours
SESSION-HANDOFF-PROTOCOL.md updated:
- Dify RAG marked ACTIVE PRIORITY (not medium)
- n8n section updated to reflect rebuild decision
- Future Chroniclers will see these as active work, not deferred
Signed-off-by: The Chronicler #28
Create grounded knowledge base with Audio Overview capabilities
for hand-friendly review and knowledge synthesis.
✅ Task Documentation Created:
- README.md: Complete overview, use cases, benefits
- setup-guide.md: Step-by-step setup and testing
🎧 KEY FEATURES:
- Audio Overviews (listen instead of reading - hand-friendly)
- Grounded research (only YOUR sources, no hallucination)
- MCP integration (Claude queries notebooks seamlessly)
- Meg accessibility (technical content in audio format)
- Legacy preservation (for children not yet born)
📚 USE CASES:
- Infrastructure knowledge base (835+ docs queryable)
- Chronicler lineage archive (all memorials in audio)
- Pokerole project docs (session reports accessible)
- Training for Meg (technical content via audio)
💰 COST: FREE (Google NotebookLM, MCP in Max plan)
⏱️ TIME: 1-2 hours setup, 15 min/week maintenance
🎯 VALUE: HIGH for accessibility + knowledge retention
Inspired by: XDA article on Claude + NotebookLM workflow
Priority: Medium (HIGH for accessibility needs)
Task #36 ready to start when Michael is ready.
Promoted from ideas backlog per Michael's request for "sooner than later"
operational need.
Task #11: Modpack Update Monitor - Blueprint Extension
- Status: HIGH priority, queued after Codex Phase 2
- Time: 8-12 hours (full Blueprint extension)
- Affects: 9 modpack servers across TX1/NC1
- Purpose: Automated version checking vs latest available
- APIs: CurseForge, Modrinth, FTB, Technic
- Dashboard: Per-server update status visibility
Decision rationale: Michael's "do it once and get it done" philosophy
- Blueprint extension = permanent solution
- No revisiting with scripts later
- Integrates with existing Pterodactyl workflow
- Professional, scalable, maintainable
Execution order: Codex Phase 2 → Modpack Monitor (finish what we
started, then tackle this with full focus)
Updated tasks.md to v3.6
Updated ideas-backlog.md to v1.9
Added Task #32: Whitelist Manager Refinements
- Fix Mayview server grouping issue (shows 'Unknown' instead of 'NC1')
- Tier 3: Polish/Cosmetic (30-60 minutes)
- Low priority - does not affect functionality
- Placeholder for future small refinements
Issue identified by Michael during Whitelist Manager review.
Updated version to 3.5
- Added Firefrost Codex as Tier 2 major infrastructure task
- Marked old AI Stack task (now #11) as superseded by Codex
- Updated task statistics: 32 total tasks, Codex ready to deploy
- Renumbered subsequent tasks (Mailcow now #10, etc.)
- Updated version to 3.3
- Estimated 8-12 hours deployment time, $0 monthly cost
Firefrost Codex provides 24/7 AI assistance to all community tiers with
five-workspace architecture, mclo.gs integration, and complete marketing
strategy documented.
Aurora identified need for passwordless SSH between all management
servers. Currently blocked by non-standard key naming on Billing.
Task documented for future session when Michael has energy.
Signed-off-by: The Librarian <claude@firefrostgaming.com>
Task #1 now 100% operational with all features:
- Add/remove players (username OR UUID)
- Bulk operations (all servers)
- Real-time status detection (WHITELISTED/PUBLIC/OFFLINE)
- Websocket integration with Pterodactyl
- Dynamic server list
Fixed websocket HTTP 403 issue:
- Required Origin header in websocket connection
- Status detection via 'whitelist on' test command
- Restores original state after check
Completed: February 19, 2026 after 22.5 hours rest
Sessions: Feb 18 (deployment) + Feb 19 (websocket fix)
Known: One server may show incorrect status (retirement candidate)
Value: 96.7% time reduction (15 min → 30 sec per operation)
Signed-off-by: Chronicler #17 <claude@firefrostgaming.com>
Created new quality-of-life task for tracking modpack versions in Pterodactyl panel.
TASK DETAILS:
- Add custom egg variable for modpack version display
- Visible in Startup tab for all modpack servers
- Manual entry (simple, low complexity)
- Improves version tracking and troubleshooting
SCOPE:
- 9 modpack servers (All The Mons, Stoneblock 4, etc.)
- Excludes Vanilla, Hytale, FoundryVTT (not applicable)
IMPLEMENTATION:
- Phase 1: Add variable to Minecraft egg (15 min)
- Phase 2: Populate current versions (30 min)
- Phase 3: Document update procedure (15 min)
- Total time: 1-2 hours
BENEFITS:
- Version visibility at a glance
- Change tracking when modpacks update
- Troubleshooting clarity (identify version mismatches)
- Professional operations appearance
ALTERNATIVE METHODS DOCUMENTED:
- Script-based auto-detection (future enhancement)
- Include version in server name (quick hack)
Updated tasks.md: Total tasks now 30
Status: Ready to implement
Fire + Frost + Foundation 💙🔥❄️
Reflects The Guardian's prerequisites from discord-recruitment-ad.md:
1. Provision incentive instances (private servers for recruits)
2. Define application review process
3. Finalize recruitment ad decisions
Task captures:
- Recruitment for 2-3 Builders + 1 Social Media Helper
- Prerequisites checklist from Guardian's bottom notes
- Reference to recruitment ad in docs/planning/
- Application process and onboarding workflow
Status: PLANNING (need to provision incentive instances first)
Priority: Tier 3 - Content & Community
Files added:
- docs/tasks/staff-recruitment-launch/README.md
- Updated docs/core/tasks.md (v3.1, Task #29, total 29 tasks)
MASSIVE RESTRUCTURE COMPLETE:
All 28 tasks migrated to task directories.
tasks.md reduced: 1365 → 366 lines (73% reduction, 999 lines saved)
Every task now ≤20 lines in master list.
Complete details in docs/tasks/[task-name]/
SCALABILITY ACHIEVED:
Before: 49 lines per task average (unsustainable at 50+ tasks)
After: 13 lines per task (scales to 100+ tasks)
Target met: ≤20 lines per task maximum
System now scales indefinitely
All 28 tasks implemented:
Tasks 1-7 (Tier 0-1 Security), Tasks 8-12 (Tier 2 Infrastructure),
Tasks 13-17 (Documentation), Tasks 18-22 (Operations),
Tasks 23-28 (Game Servers)
Fresh Claude Review #2 addressed: "27 tasks still embedded, needs
6-8 hours to migrate." NOW: Complete. All tasks follow standard.
This is the complete implementation of FFG-STD-002.
No half-measures. Full execution.
Date: 2026-02-16
Completed by: The Chronicler
Version: 3.0 (Complete FFG-STD-002 implementation)
Implementing FFG-STD-002 (Task Documentation Standard):
BEFORE:
- 62 lines of detailed task information in tasks.md
- All deployment details inline
- Prerequisites, tech stack, phases all in master list
AFTER:
- 20 lines (following standard guideline)
- References task directory for complete docs
- High-level overview only
- Details moved to docs/tasks/whitelist-manager/
RESULT:
- Reduced tasks.md from 1406 → 1365 lines (41 lines saved)
- With 15 more tasks to refactor, will save ~600+ lines
- Target: 50 tasks × 20 lines = 1000 lines (scalable)
Per fresh Claude review: "At 50 tasks, tasks.md will be
3500-4500 lines - completely unmanageable. Reduce entries
to ≤20 lines per task."
Phase 5 of complete restructure.
Date: February 16, 2026
Implemented by: The Chronicler
