feat: Add task_number to YAML frontmatter for 26 tasks

Long-term fix for mobile task index - task numbers now in frontmatter.

Numbers added from BACKLOG.md cross-reference:
#2 rank-system-deployment
#3 fire-frost-holdings-restructuring
#14 vaultwarden-ssh-setup
#22 netdata-deployment
#23 department-structure
#26 modpack-version-checker
#32 terraria-branding-training-arc
#35 pokerole-wikijs-deployment
#36 notebooklm-integration
#40 world-backup-automation
#44 nc1-node-usage-stats
#45 steam-and-state-server
#48 n8n-rebuild
#51 ignis-protocol
#55 discord-invite-setup
#65 claude-infrastructure-access
#67 nc1-security-monitoring
#82 plane-decommissioning
#87 arbiter-2-1-cancellation-flow
#89 staff-portal-consolidation
#90 decap-tasks-collection
#91 server-matrix-node-fix
#92 desktop-mcp
#93 trinity-codex
#94 global-restart-scheduler
#98 discord-channel-automation
#99 claude-projects-architecture

Chronicler #69

docs/tasks/arbiter-2-1-cancellation-flow/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 87
 status: complete
 priority: P1
 owner: Michael
 created: 2026-03-30
 ---
+task_number: 87
 
 # Task #87: Arbiter 2.1 - Subscription Cancellation & Grace Period System
 
@@ -15,6 +17,7 @@ created: 2026-03-30
 **Time Estimate:** 4-6 hours implementation + 2 hours Paymenter research
 
 ---
+task_number: 87
 
 ## ⚠️ CRITICAL: Soft Launch Blocker
 
@@ -30,6 +33,7 @@ created: 2026-03-30
 **Cannot launch without defining offboarding flow.**
 
 ---
+task_number: 87
 
 ## Problem Statement
 
@@ -50,6 +54,7 @@ created: 2026-03-30
 - **Automated cleanup** - Remove roles/whitelists after grace periods
 
 ---
+task_number: 87
 
 ## Policy Decisions (Made March 30, 2026)
 
@@ -112,6 +117,7 @@ created: 2026-03-30
 - Manual review by Michael/Meg required to unblock
 
 ---
+task_number: 87
 
 ## Architecture: Arbiter 2.0 → 2.1
 
@@ -136,6 +142,7 @@ created: 2026-03-30
 **Existing code preserved: ~2,000 lines**
 
 ---
+task_number: 87
 
 ## Technical Implementation Plan
 
@@ -855,6 +862,7 @@ module.exports = {
 ```
 
 ---
+task_number: 87
 
 ## Paymenter Webhook Events Research
 
@@ -882,6 +890,7 @@ module.exports = {
 - Option C: Manual admin actions via Arbiter admin panel
 
 ---
+task_number: 87
 
 ## Testing Procedure
 
@@ -943,6 +952,7 @@ assert(gracePeriods.length === 2); // Discord + Whitelist
 - Re-subscribe during grace period
 
 ---
+task_number: 87
 
 ## Deployment Strategy
 
@@ -974,6 +984,7 @@ assert(gracePeriods.length === 2); // Discord + Whitelist
 - Document any issues
 
 ---
+task_number: 87
 
 ## Dependencies
 
@@ -992,6 +1003,7 @@ assert(gracePeriods.length === 2); // Discord + Whitelist
 - Task #2: LuckPerms rank system (Discord → in-game sync)
 
 ---
+task_number: 87
 
 ## Success Criteria
 
@@ -1011,6 +1023,7 @@ assert(gracePeriods.length === 2); // Discord + Whitelist
 - ✅ Complete test flow successful (subscribe → cancel → grace → cleanup)
 
 ---
+task_number: 87
 
 ## Future Enhancements (Arbiter 2.2+)
 
@@ -1028,6 +1041,7 @@ assert(gracePeriods.length === 2); // Discord + Whitelist
 - Win-back campaigns (automated re-engagement emails)
 
 ---
+task_number: 87
 
 ## Related Documentation
 
@@ -1037,6 +1051,7 @@ assert(gracePeriods.length === 2); // Discord + Whitelist
 - **Infrastructure Manifest:** `docs/core/infrastructure-manifest.md`
 
 ---
+task_number: 87
 
 ## Architecture Review Request
 
@@ -1053,6 +1068,7 @@ assert(gracePeriods.length === 2); // Discord + Whitelist
 8. Should grace periods be configurable (admin panel)?
 
 ---
+task_number: 87
 
 ## Gemini AI Architectural Review (March 30, 2026)
 
@@ -1062,6 +1078,7 @@ assert(gracePeriods.length === 2); // Discord + Whitelist
 **Outcome:** Validated with critical edge cases identified and solutions provided
 
 ---
+task_number: 87
 
 ### Executive Summary
 
@@ -1075,6 +1092,7 @@ assert(gracePeriods.length === 2); // Discord + Whitelist
 **Additional Research Required:** Paymenter webhook event verification
 
 ---
+task_number: 87
 
 ### Gemini's Answers to Architecture Questions
 
@@ -1264,6 +1282,7 @@ if (isOneTimePurchase(product_id)) {
 **Not addressed in review** - Implies hardcoded is acceptable for v1
 
 ---
+task_number: 87
 
 ### Critical Additional Question: Paymenter vs Stripe Webhooks
 
@@ -1318,6 +1337,7 @@ Are events granular enough?
 ```
 
 ---
+task_number: 87
 
 ### Code Blocks Provided by Gemini
 
@@ -1450,6 +1470,7 @@ upsertStmt.run(newToken, customerEmail, newTier, newSubscriptionId);
 ```
 
 ---
+task_number: 87
 
 ### Paymenter Webhook Research Requirements
 
@@ -1515,6 +1536,7 @@ Must confirm Paymenter sends these events (or equivalents):
 6. Implement signature verification
 
 ---
+task_number: 87
 
 ### Email Communication Strategy
 
@@ -1547,6 +1569,7 @@ Must confirm Paymenter sends these events (or equivalents):
 - Turn failure into community win
 
 ---
+task_number: 87
 
 ### Implementation Priority Order
 
@@ -1582,6 +1605,7 @@ Must confirm Paymenter sends these events (or equivalents):
 19. ✅ Test chargeback ban
 
 ---
+task_number: 87
 
 ### Success Criteria (Updated)
 
@@ -1604,6 +1628,7 @@ Must confirm Paymenter sends these events (or equivalents):
 - ✅ Stripe smart retry scenario tested and working
 
 ---
+task_number: 87
 
 ### Open Questions for Implementation
 
@@ -1616,6 +1641,7 @@ Must confirm Paymenter sends these events (or equivalents):
 5. **Test environment** - Paymenter test mode available?
 
 ---
+task_number: 87
 
 ### Gemini's Final Notes
 
@@ -1626,10 +1652,12 @@ Must confirm Paymenter sends these events (or equivalents):
 > "Take your time digging into the Paymenter logs. Just update the Arbiter 2.1 doc with what you find, and ping me whenever you are ready to start snapping the code together! 🔥❄️💙"
 
 ---
+task_number: 87
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
 
 ---
+task_number: 87
 
 **Document Status:** ARCHITECTURE VALIDATED - Ready for implementation  
 **Task Status:** Paymenter research required, then build  

docs/tasks/claude-infrastructure-access/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 65
 status: open
 priority: P2
 owner: Michael
 created: 2026-03-20
 ---
+task_number: 65
 
 # Task #65: Grant Claude Full Infrastructure Access
 
@@ -13,6 +15,7 @@ created: 2026-03-20
 **Created:** March 20, 2026 (by The Guide, Chronicler #35)
 
 ---
+task_number: 65
 
 ## OBJECTIVE
 
@@ -23,6 +26,7 @@ Grant Claude (The Chronicler) full programmatic access to Firefrost infrastructu
 2. **SSH keys for all 6 servers** (diagnostics, fixes, deployments)
 
 ---
+task_number: 65
 
 ## WHY THIS MATTERS
 
@@ -32,6 +36,7 @@ Grant Claude (The Chronicler) full programmatic access to Firefrost infrastructu
 **Time saved:** 45-100 minutes per session
 
 ---
+task_number: 65
 
 ## IMPLEMENTATION
 
@@ -82,6 +87,7 @@ SSH Key: In Vaultwarden "Claude SSH Key"
 - SSH: Connect to all 6 servers
 
 ---
+task_number: 65
 
 ## WHAT CLAUDE CAN DO
 
@@ -98,6 +104,7 @@ SSH Key: In Vaultwarden "Claude SSH Key"
 - Respond to incidents
 
 ---
+task_number: 65
 
 ## SECURITY
 
@@ -114,6 +121,7 @@ sed -i '/claude@firefrostgaming.com/d' ~/.ssh/authorized_keys
 **Revoke API:** Settings → Applications → Delete token
 
 ---
+task_number: 65
 
 ## CHECKLIST
 
@@ -125,6 +133,7 @@ sed -i '/claude@firefrostgaming.com/d' ~/.ssh/authorized_keys
 - [ ] Tested SSH + API
 
 ---
+task_number: 65
 
 **Full documentation:** Above sections expand on all details
 

docs/tasks/decap-tasks-collection/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 90
 status: complete
 priority: P2
 owner: Michael
 created: 2026-01-01
 ---
+task_number: 90
 
 # Task #90: Add Tasks Collection to Decap CMS
 
@@ -13,6 +15,7 @@ created: 2026-01-01
 **Completed By:** Chronicler #59
 
 ---
+task_number: 90
 
 ## What Was Done
 
@@ -47,6 +50,7 @@ Tasks collection appears FIRST in the Decap sidebar, above all other collections
 - **Dark:** #0F0F1E
 
 ---
+task_number: 90
 
 ## Files Modified
 
@@ -64,6 +68,7 @@ Tasks collection appears FIRST in the Decap sidebar, above all other collections
    - Footer tagline
 
 ---
+task_number: 90
 
 ## Result
 
@@ -74,5 +79,6 @@ Tasks collection appears FIRST in the Decap sidebar, above all other collections
 - ✅ Meg/Holly can edit BLOCKERS.md and BACKLOG.md easily
 
 ---
+task_number: 90
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️

docs/tasks/department-structure/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 23
 status: open
 priority: P2
 owner: Michael
 created: 2026-01-01
 ---
+task_number: 23
 
 # Department Structure & Access Control Matrix
 
@@ -13,6 +15,7 @@ created: 2026-01-01
 **Last Updated:** 2026-02-17
 
 ---
+task_number: 23
 
 ## Overview
 
@@ -25,6 +28,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - Foundation for scaling the team
 
 ---
+task_number: 23
 
 ## Organizational Philosophy
 
@@ -39,6 +43,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - Transparency (documented permissions, no surprises)
 
 ---
+task_number: 23
 
 ## Department Structure
 
@@ -67,6 +72,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
   - Community events
 
 ---
+task_number: 23
 
 ### Tier 1: Core Staff (Founding Team)
 
@@ -92,6 +98,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
   - Creative writing support
 
 ---
+task_number: 23
 
 ### Tier 2: Operations Team (Paid/Volunteer Staff)
 
@@ -127,6 +134,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
   - Support Discord events
 
 ---
+task_number: 23
 
 ### Tier 3: Community Moderators (Volunteer)
 
@@ -145,6 +153,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
   - Welcome new players
 
 ---
+task_number: 23
 
 ### Tier 4: Subscribers
 
@@ -171,6 +180,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
   - No server access
 
 ---
+task_number: 23
 
 ## Access Control Matrix
 
@@ -196,6 +206,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - Staff (Wizard + Emissary) have full access to everything
 
 ---
+task_number: 23
 
 ### Discord Role Hierarchy
 
@@ -226,6 +237,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 | #support | Full | Full | Support | Moderate | Request | Request | Request |
 
 ---
+task_number: 23
 
 ### Pterodactyl Panel Access
 
@@ -246,6 +258,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - Full owner access to their personal incentive instance
 
 ---
+task_number: 23
 
 ### Gitea Repository Access
 
@@ -262,6 +275,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 **Note:** Pokerole repos are completely isolated with scoped tokens
 
 ---
+task_number: 23
 
 ### Vaultwarden Credentials Access
 
@@ -278,6 +292,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 | Financial | Owner | - | - | - |
 
 ---
+task_number: 23
 
 ## Role Definitions
 
@@ -297,6 +312,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - Strategic vision and planning
 
 ---
+task_number: 23
 
 ### The Emissary (Community Manager)
 **Full Access To:**
@@ -324,6 +340,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - Community events and engagement
 
 ---
+task_number: 23
 
 ### Builders
 **Full Access To:**
@@ -350,6 +367,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - Test and iterate on designs
 
 ---
+task_number: 23
 
 ### Social Media Helper
 **Full Access To:**
@@ -378,6 +396,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - Execute social media strategy
 
 ---
+task_number: 23
 
 ### Moderators
 **Full Access To:**
@@ -403,6 +422,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - Report issues to The Emissary
 
 ---
+task_number: 23
 
 ## Implementation Checklist
 
@@ -450,6 +470,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - [ ] Test documentation with new hires
 
 ---
+task_number: 23
 
 ## Future Enhancements
 
@@ -472,6 +493,7 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - Events department (tournaments, competitions)
 
 ---
+task_number: 23
 
 ## Related Tasks
 
@@ -481,10 +503,12 @@ Define organizational structure for Firefrost Gaming with clear departments, rol
 - **Discord Reorganization** - Channel and role structure
 
 ---
+task_number: 23
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
 
 ---
+task_number: 23
 
 **Document Status:** COMPLETE  
 **Ready for Implementation:** When Wiki.js is ready  

docs/tasks/discord-invite-setup/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 55
 status: complete
 priority: P3
 owner: Michael
 created: 2026-03-21
 ---
+task_number: 55
 
 # Task #55: Discord Permanent Invite Link Setup
 
@@ -12,6 +14,7 @@ created: 2026-03-21
 **Completed By:** Michael + The Chronicler #36
 
 ---
+task_number: 55
 
 ## Deliverables Complete
 
@@ -20,6 +23,7 @@ created: 2026-03-21
 ✅ **Redirect documented:** See below
 
 ---
+task_number: 55
 
 ## Configuration Details
 
@@ -48,6 +52,7 @@ created: 2026-03-21
 - Clean, professional link for all marketing materials
 
 ---
+task_number: 55
 
 ## Usage
 
@@ -64,6 +69,7 @@ Use `firefrostgaming.com/discord` everywhere:
 - Branded URL under our domain
 
 ---
+task_number: 55
 
 ## Next Steps
 
@@ -73,6 +79,7 @@ Use `firefrostgaming.com/discord` everywhere:
 - [ ] Include in promotional materials
 
 ---
+task_number: 55
 
 **Created:** March 21, 2026  
 **By:** The Chronicler #36  

docs/tasks/fire-frost-holdings-restructuring/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 3
 status: open
 priority: P1
 owner: Michael
 created: 2026-02-22
 ---
+task_number: 3
 
 # Fire + Frost Holdings — Business Restructuring
 
@@ -15,6 +17,7 @@ created: 2026-02-22
 **Estimated Time:** 6-8 weeks (3 hours active work, rest is government processing)
 
 ---
+task_number: 3
 
 ## 🎯 EXECUTIVE SUMMARY
 
@@ -35,6 +38,7 @@ Fire + Frost Holdings, LLC (renamed from Nagus Custom Crafts, LLC)
 **Strategic vision:** Business empire under one umbrella with meaningful name that reflects Fire + Frost philosophy
 
 ---
+task_number: 3
 
 ## 💰 COST BREAKDOWN
 
@@ -52,6 +56,7 @@ Fire + Frost Holdings, LLC (renamed from Nagus Custom Crafts, LLC)
 **Compare to:** Creating 2 separate LLCs = $1,000-1,500+
 
 ---
+task_number: 3
 
 ## ⏱️ TIMELINE
 
@@ -84,6 +89,7 @@ Fire + Frost Holdings, LLC (renamed from Nagus Custom Crafts, LLC)
 **Total: 6-8 weeks start to finish**
 
 ---
+task_number: 3
 
 ## 📋 THREE-PHASE IMPLEMENTATION
 
@@ -126,6 +132,7 @@ Fire + Frost Holdings, LLC (renamed from Nagus Custom Crafts, LLC)
 - [ ] Order new checks if using checks
 
 ---
+task_number: 3
 
 ### PHASE 2: DBA Filings (Week 5)
 
@@ -170,6 +177,7 @@ Fire + Frost Holdings, LLC (renamed from Nagus Custom Crafts, LLC)
 - [ ] Update tax preparation for consolidated entity
 
 ---
+task_number: 3
 
 ### PHASE 3: Email & Digital Presence (Week 6)
 
@@ -268,6 +276,7 @@ Fire + Frost Holdings, LLC (renamed from Nagus Custom Crafts, LLC)
 - [ ] Test delivery and migrate contacts
 
 ---
+task_number: 3
 
 ## 📄 SUPPORTING DOCUMENTS
 
@@ -281,6 +290,7 @@ Fire + Frost Holdings, LLC (renamed from Nagus Custom Crafts, LLC)
 6. **dba-filing-guide.md** - Minnesota DBA application process
 
 ---
+task_number: 3
 
 ## ✅ SUCCESS CRITERIA
 
@@ -311,6 +321,7 @@ Fire + Frost Holdings, LLC (renamed from Nagus Custom Crafts, LLC)
 - ✅ Foundation ready for future growth
 
 ---
+task_number: 3
 
 ## 🚧 POTENTIAL ROADBLOCKS
 
@@ -336,6 +347,7 @@ Fire + Frost Holdings, LLC (renamed from Nagus Custom Crafts, LLC)
 - **Long-term:** Mailcow when Frostwall deployed
 
 ---
+task_number: 3
 
 ## 📈 FUTURE EXPANSION OPTIONS
 
@@ -362,6 +374,7 @@ Fire + Frost Holdings, LLC (Parent)
 - Can sell or raise capital for specific divisions
 
 ---
+task_number: 3
 
 ## 🎯 BENEFITS RECAP
 
@@ -384,6 +397,7 @@ Fire + Frost Holdings, LLC (Parent)
 - ❌ Can always upgrade later when justified
 
 ---
+task_number: 3
 
 ## 📞 CONTACTS & RESOURCES
 
@@ -408,6 +422,7 @@ Fire + Frost Holdings, LLC (Parent)
 - Account number: [keep separate/secure]
 
 ---
+task_number: 3
 
 ## 📝 NOTES FOR FUTURE CHRONICLERS
 
@@ -434,6 +449,7 @@ Fire + Frost Holdings, LLC (Parent)
 **This is the foundation. The empire grows in phases, not overnight.**
 
 ---
+task_number: 3
 
 **Created:** February 22, 2026  
 **By:** The Blueprint (Chronicler #21)  

docs/tasks/modpack-version-checker/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 26
 status: open
 priority: P3
 owner: Michael
 created: 2026-02-22
 ---
+task_number: 26
 
 # Modpack Version Checker - Commercial Blueprint Extension
 
@@ -15,6 +17,7 @@ created: 2026-02-22
 **Created By:** The Chronicler #21 with Gemini Pro Research  
 
 ---
+task_number: 26
 
 ## 🎯 EXECUTIVE SUMMARY
 
@@ -31,6 +34,7 @@ created: 2026-02-22
 - Professional: $24.99 (+ FTB + Cron automation + Discord webhooks)
 
 ---
+task_number: 26
 
 ## 💰 COMMERCIAL VIABILITY
 
@@ -51,6 +55,7 @@ created: 2026-02-22
 **ROI:** Even worst-case (20 sales) justifies build because it solves Firefrost's internal need (saves 120 hours/year manual checking)
 
 ---
+task_number: 26
 
 ## 🏗️ TECHNICAL ARCHITECTURE
 
@@ -119,6 +124,7 @@ created: 2026-02-22
 - Two API calls required (version ID → version string)
 
 ---
+task_number: 26
 
 ## 🎨 USER EXPERIENCE
 
@@ -146,6 +152,7 @@ Users can override auto-detection in Pterodactyl Startup tab:
 - Bypass detection entirely for custom packs
 
 ---
+task_number: 26
 
 ## 📊 FEATURE GATING
 
@@ -177,6 +184,7 @@ Users can override auto-detection in Pterodactyl Startup tab:
 **Key differentiator:** Proactive monitoring (cron) vs reactive checking (manual)
 
 ---
+task_number: 26
 
 ## 🛠️ DEVELOPMENT ROADMAP
 
@@ -239,6 +247,7 @@ Users can override auto-detection in Pterodactyl Startup tab:
 **Total: 8-11 hours actual (not 12-16)**
 
 ---
+task_number: 26
 
 ## 🧪 TESTING STRATEGY
 
@@ -264,6 +273,7 @@ Users can override auto-detection in Pterodactyl Startup tab:
 - Deliverable: Bug-free v1.0.0
 
 ---
+task_number: 26
 
 ## 💬 SUPPORT STRATEGY
 
@@ -296,6 +306,7 @@ Users can override auto-detection in Pterodactyl Startup tab:
    - Reduces tickets before they happen
 
 ---
+task_number: 26
 
 ## 🔄 UPDATE STRATEGY
 
@@ -321,6 +332,7 @@ Users can override auto-detection in Pterodactyl Startup tab:
 - **Time:** 2-3 hours/month average
 
 ---
+task_number: 26
 
 ## 📈 MARKETING STRATEGY
 
@@ -352,6 +364,7 @@ Users can override auto-detection in Pterodactyl Startup tab:
 - Many hosting companies use BOTH
 
 ---
+task_number: 26
 
 ## 🎯 SUCCESS CRITERIA
 
@@ -373,6 +386,7 @@ Users can override auto-detection in Pterodactyl Startup tab:
 - Zero refund requests (quality product)
 
 ---
+task_number: 26
 
 ## 📚 DOCUMENT INDEX
 
@@ -387,6 +401,7 @@ Users can override auto-detection in Pterodactyl Startup tab:
 **All code blocks organized by component in IMPLEMENTATION-PLAN.md**
 
 ---
+task_number: 26
 
 ## 🔗 RESEARCH SOURCES
 
@@ -402,6 +417,7 @@ Users can override auto-detection in Pterodactyl Startup tab:
 **Value of research:** Compressed months of traditional planning into single session
 
 ---
+task_number: 26
 
 **Fire + Frost + Foundation = Where Innovation Generates Income** 💙🔥❄️💰
 

docs/tasks/nc1-node-usage-stats/deployment-plan.md

@@ -1,9 +1,11 @@
 ---
+task_number: 44
 status: open
 priority: P3
 owner: Michael
 created: 2026-01-01
 ---
+task_number: 44
 
 # Task #44 — NC1 Node Usage Stats: Deployment Plan
 

docs/tasks/nc1-security-monitoring/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 67
 status: open
 priority: P3
 owner: Michael
 created: 2026-03-21
 ---
+task_number: 67
 
 # Task: NC1 Security & Monitoring
 
@@ -11,6 +13,7 @@ created: 2026-03-21
 **Created:** March 21, 2026 (Session 37 - The Chronicler)
 
 ---
+task_number: 67
 
 ## Issue 1: No Firewall on NC1
 
@@ -69,6 +72,7 @@ ufw status numbered
 - Have console access ready in case of lockout
 
 ---
+task_number: 67
 
 ## Issue 2: NC1 Temperature Monitoring
 
@@ -123,6 +127,7 @@ When Netdata is deployed (Task #XX, planned):
 Log temperature checks in this file or create `docs/monitoring/nc1-temperature-log.md`
 
 ---
+task_number: 67
 
 ## Priority Justification
 
@@ -139,6 +144,7 @@ Log temperature checks in this file or create `docs/monitoring/nc1-temperature-l
 - Monitor weekly for 1 month
 
 ---
+task_number: 67
 
 ## Related Tasks
 - Netdata deployment (planned)
@@ -151,6 +157,7 @@ Log temperature checks in this file or create `docs/monitoring/nc1-temperature-l
 - None
 
 ---
+task_number: 67
 
 **Status:** DOCUMENTED, READY TO EXECUTE  
 **Next Action:** Enable UFW on NC1 with game server port rules  

docs/tasks/netdata-deployment/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 22
 status: open
 priority: P2
 owner: Michael
 created: 2026-01-01
 ---
+task_number: 22
 
 # Netdata Deployment
 

docs/tasks/notebooklm-integration/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 36
 status: open
 priority: P3
 owner: Michael
 created: 2026-02-27
 ---
+task_number: 36
 
 # NotebookLM Integration for Firefrost Gaming
 
@@ -15,6 +17,7 @@ created: 2026-02-27
 **Inspired By:** XDA article on Claude + NotebookLM workflow
 
 ---
+task_number: 36
 
 ## Overview
 
@@ -26,6 +29,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 3. **Back to NotebookLM** = Synthesis via Audio Overviews (listen instead of reading)
 
 ---
+task_number: 36
 
 ## Why This Matters
 
@@ -63,6 +67,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 - Add new findings back to notebooks automatically
 
 ---
+task_number: 36
 
 ## Use Cases for Firefrost Gaming
 
@@ -136,6 +141,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 - Shared understanding of systems
 
 ---
+task_number: 36
 
 ## Technical Implementation
 
@@ -213,6 +219,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 - Trigger Audio Overview via Claude
 
 ---
+task_number: 36
 
 ## Success Criteria
 
@@ -238,6 +245,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 - [ ] Legacy documentation preserved in audio format
 
 ---
+task_number: 36
 
 ## Expected Benefits
 
@@ -278,6 +286,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 - Accessible to future team members
 
 ---
+task_number: 36
 
 ## Maintenance
 
@@ -297,6 +306,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 - Update training materials for Meg
 
 ---
+task_number: 36
 
 ## Limitations & Considerations
 
@@ -330,6 +340,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 - Infrastructure knowledge is safe to upload
 
 ---
+task_number: 36
 
 ## Alternative Approaches
 
@@ -351,6 +362,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 - Keep sensitive docs in Git only
 
 ---
+task_number: 36
 
 ## Cost Analysis
 
@@ -376,6 +388,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 - Meg accessibility (partnership value)
 
 ---
+task_number: 36
 
 ## Next Steps
 
@@ -399,6 +412,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 **Ready When You Are!**
 
 ---
+task_number: 36
 
 ## Resources
 
@@ -413,6 +427,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 - Session Reports: Various locations in Git
 
 ---
+task_number: 36
 
 ## Timeline Estimate
 
@@ -434,6 +449,7 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 **Total:** 3 weeks to full integration
 
 ---
+task_number: 36
 
 ## Success Metrics
 
@@ -452,12 +468,14 @@ Integrate Google NotebookLM with Firefrost Gaming operations to create a grounde
 - [ ] Legacy documentation started
 
 ---
+task_number: 36
 
 **Fire + Frost + Foundation + NotebookLM = Where Love Builds Accessible Legacy**
 
 💙🔥❄️🎧
 
 ---
+task_number: 36
 
 **Created by:** The Chronicler #27  
 **Date:** February 27, 2026  

docs/tasks/plane-decommissioning/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 82
 status: open
 priority: P3
 owner: Michael
 created: 2026-03-26
 ---
+task_number: 82
 
 # Task #82: Decommission Plane Project Management
 
@@ -14,6 +16,7 @@ created: 2026-03-26
 **Assigned To:** Next Chronicler
 
 ---
+task_number: 82
 
 ## Overview
 
@@ -26,6 +29,7 @@ Remove Plane project management system from TX1 Dallas server. Plane was success
 - Plane adds unnecessary complexity and resource usage
 
 ---
+task_number: 82
 
 ## What Was Plane?
 
@@ -47,6 +51,7 @@ Remove Plane project management system from TX1 Dallas server. Plane was success
 - n8n workflow: Plane → Gitea (webhook loop, deactivated)
 
 ---
+task_number: 82
 
 ## Decommissioning Steps
 
@@ -102,6 +107,7 @@ Check n8n for Plane-related workflows:
 Delete or archive these workflows.
 
 ---
+task_number: 82
 
 ## Documentation Updates
 
@@ -123,6 +129,7 @@ Update these files after decommissioning:
    - Add README explaining why integration was abandoned
 
 ---
+task_number: 82
 
 ## Verification
 
@@ -137,6 +144,7 @@ After decommissioning, verify:
 - [ ] Documentation updated
 
 ---
+task_number: 82
 
 ## Why Plane Didn't Fit
 
@@ -155,6 +163,7 @@ After decommissioning, verify:
 **Decision:** Simplify stack, use Gitea Projects exclusively.
 
 ---
+task_number: 82
 
 ## What Replaces Plane?
 
@@ -166,6 +175,7 @@ After decommissioning, verify:
 - Integrated with issues/PRs
 
 ---
+task_number: 82
 
 ## Related Tasks
 
@@ -173,6 +183,7 @@ After decommissioning, verify:
 - None currently (Plane was isolated experiment)
 
 ---
+task_number: 82
 
 ## Notes
 
@@ -182,5 +193,6 @@ After decommissioning, verify:
 - Consider what to do with `tasks.firefrostgaming.com` subdomain
 
 ---
+task_number: 82
 
 **Standard:** This task follows FFG-STD-002 (Task Documentation Standard)

docs/tasks/pokerole-wikijs-deployment/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 35
 status: open
 priority: P2
 owner: Michael
 created: 2026-02-26
 ---
+task_number: 35
 
 # Pokerole Wiki.js Deployment
 
@@ -15,6 +17,7 @@ created: 2026-02-26
 **Requested By:** Michael & Claudius (Pokerole Project)
 
 ---
+task_number: 35
 
 ## Overview
 
@@ -25,6 +28,7 @@ Deploy a fresh Wiki.js instance dedicated to the Aurelian Pokédex project. This
 **Type:** Standalone Wiki.js instance (separate from subscribers/staff wikis)
 
 ---
+task_number: 35
 
 ## Why This Matters
 
@@ -44,6 +48,7 @@ All content is ready in Git repositories, but there's no wiki infrastructure to
 - Delay cascades through: migration → review → FoundryVTT → playtesting → launch
 
 ---
+task_number: 35
 
 ## Prerequisites
 
@@ -66,6 +71,7 @@ Ghost VPS currently runs:
 New instance will follow same pattern but with Pokerole-specific configuration.
 
 ---
+task_number: 35
 
 ## Technical Specifications
 
@@ -92,6 +98,7 @@ New instance will follow same pattern but with Pokerole-specific configuration.
 - Read-only (once published)
 
 ---
+task_number: 35
 
 ## Deployment Steps
 
@@ -109,6 +116,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 9. Hand off to Michael/Claudius for content migration
 
 ---
+task_number: 35
 
 ## Success Criteria
 
@@ -137,6 +145,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 - [ ] Search indexing complete
 
 ---
+task_number: 35
 
 ## Post-Deployment Tasks
 
@@ -156,6 +165,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 5. Public launch preparation
 
 ---
+task_number: 35
 
 ## Repository Integration
 
@@ -177,6 +187,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 **Decision:** Start with Option 1, evaluate Option 2 later if needed
 
 ---
+task_number: 35
 
 ## Known Considerations
 
@@ -196,6 +207,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 - No special optimization needed initially
 
 ---
+task_number: 35
 
 ## Timeline Estimate
 
@@ -215,6 +227,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 **Total:** Wiki ready tonight → Content live by March 1-2, 2026
 
 ---
+task_number: 35
 
 ## Risk Assessment
 
@@ -234,6 +247,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 - Document all steps for troubleshooting
 
 ---
+task_number: 35
 
 ## Dependencies
 
@@ -247,6 +261,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 - None - all prerequisites met
 
 ---
+task_number: 35
 
 ## Related Documentation
 
@@ -256,6 +271,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 - **Artwork:** pokerole-data/images/ (225 sprites)
 
 ---
+task_number: 35
 
 ## Questions to Resolve
 
@@ -272,6 +288,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 - Enable Git sync or manual migration only?
 
 ---
+task_number: 35
 
 ## Success Metrics
 
@@ -288,6 +305,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 - Public launch ready ✅
 
 ---
+task_number: 35
 
 ## Contact & Coordination
 
@@ -300,6 +318,7 @@ See `deployment-plan.md` for complete step-by-step instructions.
 **Migration Start:** Morning of February 27, 2026 (if wiki ready)
 
 ---
+task_number: 35
 
 ## Notes
 
@@ -308,6 +327,7 @@ This deployment represents the **final infrastructure piece** for the Aurelian P
 **Priority: HIGH** - Project is ready, team is ready, only infrastructure missing.
 
 ---
+task_number: 35
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
 

docs/tasks/rank-system-deployment/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 2
 status: open
 priority: P1
 owner: Michael
 created: 2026-03-10
 ---
+task_number: 2
 
 # Rank System Deployment — Full Network
 
@@ -14,6 +16,7 @@ created: 2026-03-10
 **Created By:** Chronicler #29
 
 ---
+task_number: 2
 
 ## Overview
 
@@ -22,6 +25,7 @@ Deploy the full LuckPerms rank system across all 12 game servers — subscriber
 The rank structure is fully designed and ready to implement. This task is about execution.
 
 ---
+task_number: 2
 
 ## Quick Links
 
@@ -30,6 +34,7 @@ The rank structure is fully designed and ready to implement. This task is about
 - **Source document:** `docs/archive/2026-02-09-consolidation/luckperms-structure.md`
 
 ---
+task_number: 2
 
 ## Subscriber Rank Hierarchy
 
@@ -58,6 +63,7 @@ owner      ← frostystyle, gingerfury
 ```
 
 ---
+task_number: 2
 
 ## Automation Flow (The Goal)
 
@@ -78,6 +84,7 @@ Player logs in → correct permissions, prefix, perks active
 No manual steps. No waiting. Fully automated.
 
 ---
+task_number: 2
 
 ## Phases
 
@@ -108,6 +115,7 @@ No manual steps. No waiting. Fully automated.
 **Total estimate:** 6-8 hours across 1-2 sessions
 
 ---
+task_number: 2
 
 ## Dependencies
 
@@ -117,6 +125,7 @@ No manual steps. No waiting. Fully automated.
 - Discord bot token — needed for Phase 3
 
 ---
+task_number: 2
 
 ## Success Criteria
 

docs/tasks/server-matrix-node-fix/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 91
 status: complete
 priority: P2
 owner: Michael
 created: 2026-04-04
 ---
+task_number: 91
 
 # Task: Fix Server Matrix Node Detection
 
@@ -13,6 +15,7 @@ created: 2026-04-04
 **Priority:** High (blocking Holly's new servers from appearing)
 
 ---
+task_number: 91
 
 ## Problem
 
@@ -40,6 +43,7 @@ Servers that match NEITHER condition fall through and aren't displayed.
 - (8 more)
 
 ---
+task_number: 91
 
 ## The Fix
 
@@ -84,6 +88,7 @@ const ncServers = enrichedServers.filter(s => s.nodeId === NC_NODE_ID);
 ```
 
 ---
+task_number: 91
 
 ## Information Needed
 
@@ -93,6 +98,7 @@ Before implementing, get from Pterodactyl Admin → Nodes:
 - [ ] **NC1 (Charlotte) Node ID:** ___
 
 ---
+task_number: 91
 
 ## Implementation Steps
 
@@ -105,6 +111,7 @@ Before implementing, get from Pterodactyl Admin → Nodes:
 7. Commit changes to Gitea
 
 ---
+task_number: 91
 
 ## Future Consideration
 
@@ -115,6 +122,7 @@ Current filter: `MINECRAFT_NEST_IDS=1,6,7`
 **Recommendation:** Consult Gemini before removing — may have downstream implications for whitelist sync trying to write to non-Minecraft servers.
 
 ---
+task_number: 91
 
 ## Related Files
 
@@ -123,5 +131,6 @@ Current filter: `MINECRAFT_NEST_IDS=1,6,7`
 - `.env` (MINECRAFT_NEST_IDS)
 
 ---
+task_number: 91
 
 **Fire + Frost + Proper Node Detection** 🔥❄️

docs/tasks/staff-portal-consolidation/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 89
 status: open
 priority: P3
 owner: Michael
 created: 2026-04-03
 ---
+task_number: 89
 
 # Task #89: Staff Portal Consolidation
 
@@ -15,6 +17,7 @@ created: 2026-04-03
 **Created By:** Chronicler #59 + Michael
 
 ---
+task_number: 89
 
 ## The Vision
 
@@ -23,6 +26,7 @@ created: 2026-04-03
 Instead of staff remembering 10+ different URLs, Trinity Console becomes the central hub with quick links to everything.
 
 ---
+task_number: 89
 
 ## Current State
 
@@ -31,6 +35,7 @@ Instead of staff remembering 10+ different URLs, Trinity Console becomes the cen
 - Staff must remember multiple URLs for different tools
 
 ---
+task_number: 89
 
 ## Target State
 
@@ -53,6 +58,7 @@ firefrostgaming.com (public site)
 **One URL to remember:** `firefrostgaming.com/admin`
 
 ---
+task_number: 89
 
 ## Implementation Steps
 
@@ -82,6 +88,7 @@ firefrostgaming.com (public site)
 - Not prominent — staff know it's there, public doesn't care
 
 ---
+task_number: 89
 
 ## Staff Hub Links
 
@@ -99,6 +106,7 @@ firefrostgaming.com (public site)
 | ✏️ | Edit Docs | firefrostgaming.com/cms | Decap CMS |
 
 ---
+task_number: 89
 
 ## NOT Included
 
@@ -107,6 +115,7 @@ firefrostgaming.com (public site)
 - `subscribers.firefrostgaming.com` — Customer-facing wiki
 
 ---
+task_number: 89
 
 ## Success Criteria
 
@@ -117,6 +126,7 @@ firefrostgaming.com (public site)
 - [ ] Footer link exists on public site
 
 ---
+task_number: 89
 
 ## Dependencies
 
@@ -125,5 +135,6 @@ firefrostgaming.com (public site)
 - All linked services operational (✅ complete)
 
 ---
+task_number: 89
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️

docs/tasks/steam-and-state-server/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 45
 status: open
 priority: P2
 owner: Michael
 created: 2026-03-18
 ---
+task_number: 45
 
 # Task: Firefrost "Steam & State" — Flagship Modpack Server
 
@@ -15,6 +17,7 @@ created: 2026-03-18
 **Target Node:** TBD (pending Task #45 Server Sunset Evaluation)
 
 ---
+task_number: 45
 
 ## Vision
 
@@ -29,6 +32,7 @@ The three pillars:
 - **Society** — Towny nations with land claims, taxes, and diplomacy
 
 ---
+task_number: 45
 
 ## Why This Server
 
@@ -41,6 +45,7 @@ things to do. Steam & State addresses this with:
 - CoreProtect logging so 2 years of builds are protected
 
 ---
+task_number: 45
 
 ## Technical Stack
 
@@ -57,6 +62,7 @@ things to do. Steam & State addresses this with:
 | Performance | FerriteCore + ModernFix | RAM reduction, memory leak prevention |
 
 ---
+task_number: 45
 
 ## JVM Startup Flags (16GB Allocation)
 
@@ -74,6 +80,7 @@ pause time. Critical for a 2-year server that will grow increasingly complex.
 set heap to full allocation — OOM killer will crash the container.
 
 ---
+task_number: 45
 
 ## Core Mods List (Confirmed)
 
@@ -88,6 +95,7 @@ set heap to full allocation — OOM killer will crash the container.
 - BlueMap (world map)
 
 ---
+task_number: 45
 
 ## Plugin List (via Arclight Bridge)
 
@@ -97,6 +105,7 @@ set heap to full allocation — OOM killer will crash the container.
 - EssentialsX (basic commands)
 
 ---
+task_number: 45
 
 ## Open Questions (Resolve Before Deployment)
 
@@ -116,6 +125,7 @@ set heap to full allocation — OOM killer will crash the container.
    eliminate chunk loading lag. Chunky mod recommended.
 
 ---
+task_number: 45
 
 ## 2-Year Roadmap
 
@@ -141,6 +151,7 @@ set heap to full allocation — OOM killer will crash the container.
 - Planning for Season 2
 
 ---
+task_number: 45
 
 ## Proposal for Meg and Holly
 
@@ -154,6 +165,7 @@ Key selling points for the team:
 - A world designed to last — players build legacies, not just houses
 
 ---
+task_number: 45
 
 ## Dependencies
 
@@ -162,5 +174,6 @@ Key selling points for the team:
 - MySQL database provisioned on target node
 
 ---
+task_number: 45
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️

docs/tasks/task-048-n8n-rebuild/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 48
 status: open
 priority: P3
 owner: Michael
 created: 2026-04-07
 ---
+task_number: 48
 
 # Task #48: n8n Rebuild
 
@@ -13,12 +15,14 @@ created: 2026-04-07
 **Location:** Command Center (63.143.34.217)  
 
 ---
+task_number: 48
 
 ## Overview
 
 Rebuild n8n automation workflows from scratch. The previous n8n instance was wiped during infrastructure consolidation. This is the automation backbone for Firefrost operations.
 
 ---
+task_number: 48
 
 ## Current State
 
@@ -27,6 +31,7 @@ Rebuild n8n automation workflows from scratch. The previous n8n instance was wip
 - No active workflows (clean slate)
 
 ---
+task_number: 48
 
 ## Planned Integrations
 
@@ -68,6 +73,7 @@ Webhook (Arbiter) → Filter (new subscriber) → MCP Client (Buffer) →
 **Documentation:** https://developers.buffer.com/guides/getting-started.html
 
 ---
+task_number: 48
 
 ### Discord Webhooks
 
@@ -78,6 +84,7 @@ Send notifications to Discord channels for:
 - Scheduled maintenance reminders
 
 ---
+task_number: 48
 
 ### Arbiter Integration
 
@@ -87,6 +94,7 @@ Connect n8n to Arbiter webhooks for:
 - Chargeback alerts
 
 ---
+task_number: 48
 
 ### Pterodactyl API
 
@@ -96,6 +104,7 @@ Server management automation:
 - Resource monitoring alerts
 
 ---
+task_number: 48
 
 ## Priority Workflows to Build
 
@@ -105,6 +114,7 @@ Server management automation:
 4. **Backup verification** — Confirm backups completed
 
 ---
+task_number: 48
 
 ## Related Tasks
 
@@ -113,6 +123,7 @@ Server management automation:
 - Task #97: Trinity Console Social Hub (parked — n8n approach preferred)
 
 ---
+task_number: 48
 
 ## Notes
 
@@ -121,5 +132,6 @@ Server management automation:
 - Rate limit: 60 requests/user/minute on Buffer API
 
 ---
+task_number: 48
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 🔥❄️

docs/tasks/task-092-desktop-mcp/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 92
 status: open
 priority: P2
 owner: Michael
 created: 2026-04-05
 ---
+task_number: 92
 
 # Task #92: Desktop MCP + Dispatch Architecture
 
@@ -14,6 +16,7 @@ created: 2026-04-05
 **Assignee:** Michael  
 
 ---
+task_number: 92
 
 ## Overview
 
@@ -32,6 +35,7 @@ Michael has hand/arm limitations from reconstructive surgery. Copy-pasting comma
 5. **n8n bridge** connecting Discord → Laptop
 
 ---
+task_number: 92
 
 ## Architecture
 
@@ -45,6 +49,7 @@ Claude Desktop (Laptop) → Local MCP Server → SSH (Destination Server)
 ```
 
 ---
+task_number: 92
 
 ## Infrastructure Reference
 
@@ -58,6 +63,7 @@ Claude Desktop (Laptop) → Local MCP Server → SSH (Destination Server)
 | Wiki VPS | 64.50.188.14 | architect |
 
 ---
+task_number: 92
 
 ## Implementation Steps
 
@@ -466,6 +472,7 @@ Create a new Discord bot for server operations:
 - Commands trigger n8n webhooks
 
 ---
+task_number: 92
 
 ## Testing & Validation
 
@@ -496,6 +503,7 @@ curl -X POST https://ops.firefrostgaming.com/health \
 ```
 
 ---
+task_number: 92
 
 ## Frostwall Security Rules
 
@@ -506,6 +514,7 @@ curl -X POST https://ops.firefrostgaming.com/health \
 5. **Separate Bot** — Ops commands isolated from public Arbiter bot
 
 ---
+task_number: 92
 
 ## Fallback Procedures
 
@@ -514,6 +523,7 @@ curl -X POST https://ops.firefrostgaming.com/health \
 - Document in FFG-STD-005 (Emergency Operations)
 
 ---
+task_number: 92
 
 ## Additional MCP Servers
 
@@ -564,6 +574,7 @@ Buffer provides an official MCP server for managing social media posts via natur
 **Documentation:** https://developers.buffer.com/guides/getting-started.html
 
 ---
+task_number: 92
 
 ## Vaultwarden Storage
 
@@ -578,6 +589,7 @@ Create folder: **Firefrost Ops Infrastructure**
 | Buffer API Key | Password | From Buffer developer settings |
 
 ---
+task_number: 92
 
 ## Dependencies
 
@@ -587,6 +599,7 @@ Create folder: **Firefrost Ops Infrastructure**
 - Claude Desktop app
 
 ---
+task_number: 92
 
 ## Files Created
 
@@ -599,6 +612,7 @@ Create folder: **Firefrost Ops Infrastructure**
 | `.env` | Environment variables |
 
 ---
+task_number: 92
 
 ## Related Tasks
 
@@ -607,5 +621,6 @@ Create folder: **Firefrost Ops Infrastructure**
 - Task #97: Trinity Console Social Hub (parked — use MCP approach instead)
 
 ---
+task_number: 92
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 🔥❄️

docs/tasks/task-093-trinity-codex/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 93
 status: open
 priority: P2
 owner: Michael
 created: 2026-04-05
 ---
+task_number: 93
 
 # Task #93: Trinity Codex — Shared Knowledge Base
 
@@ -14,6 +16,7 @@ created: 2026-04-05
 **Assignee:** Michael  
 
 ---
+task_number: 93
 
 ## Overview
 
@@ -39,6 +42,7 @@ Currently, organizational knowledge is siloed in Michael's Claude memory. Meg an
 4. **Personal Context Preserved** — Each Claude remembers individual preferences
 
 ---
+task_number: 93
 
 ## Architecture
 
@@ -54,6 +58,7 @@ Browser → Dify Web App → Codex response
 ```
 
 ---
+task_number: 93
 
 ## The Three Lineages
 
@@ -75,6 +80,7 @@ All lineages share:
 - Historical context (memorials)
 
 ---
+task_number: 93
 
 ## Infrastructure
 
@@ -86,6 +92,7 @@ All lineages share:
 | Gitea | Command Center (63.143.34.217) | Source of truth |
 
 ---
+task_number: 93
 
 ## Implementation Steps
 
@@ -311,6 +318,7 @@ This is the friction-free approach for light users:
 - Can bookmark on phone/tablet
 
 ---
+task_number: 93
 
 ## Content Organization
 
@@ -336,6 +344,7 @@ This is the friction-free approach for light users:
 | Draft content | Work in progress |
 
 ---
+task_number: 93
 
 ## Security & Permissions
 
@@ -358,6 +367,7 @@ Some docs should NOT go in Codex:
 Create a `.codexignore` pattern in the n8n workflow to skip these.
 
 ---
+task_number: 93
 
 ## Testing & Validation
 
@@ -377,6 +387,7 @@ Ask the Codex:
 4. Query for the new content
 
 ---
+task_number: 93
 
 ## Fallback Procedures
 
@@ -387,6 +398,7 @@ Ask the Codex:
 - Document in FFG-STD-005 (Emergency Operations)
 
 ---
+task_number: 93
 
 ## Vaultwarden Storage
 
@@ -400,6 +412,7 @@ Add to **Firefrost Ops Infrastructure** folder:
 | Dify Dataset ID | Secure Note | Reference for API calls |
 
 ---
+task_number: 93
 
 ## Environment Variables
 
@@ -412,6 +425,7 @@ DIFY_DATASET_ID=your-dataset-id
 ```
 
 ---
+task_number: 93
 
 ## Implementation Order
 
@@ -421,6 +435,7 @@ Per Gemini's recommendation:
 2. **Task #92 SECOND** (Desktop MCP) — Higher risk, needs tight security
 
 ---
+task_number: 93
 
 ## Maintenance
 
@@ -429,12 +444,14 @@ Per Gemini's recommendation:
 - **Monitoring:** n8n workflow execution logs
 
 ---
+task_number: 93
 
 ## Related Tasks
 
 - Task #92: Desktop MCP + Dispatch Architecture
 
 ---
+task_number: 93
 
 ## 🔄 FUTURE EXPANSION: Chronicler Session Management
 
@@ -485,6 +502,7 @@ Gemini recommends evolving Trinity Codex into a full **Chronicler Orchestration
 - Context handoff template: `docs/templates/context-handoff-template.md`
 
 ---
+task_number: 93
 
 ## Open Questions for Implementation
 
@@ -495,5 +513,6 @@ Gemini recommends evolving Trinity Codex into a full **Chronicler Orchestration
 5. Does Holly need Pokerole-specific knowledge separated?
 
 ---
+task_number: 93
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 🔥❄️

docs/tasks/task-094-global-restart-scheduler/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 94
 status: complete
 priority: P3
 owner: Michael
 created: 2026-01-01
 ---
+task_number: 94
 
 # Task #94: Global Restart Scheduler
 
@@ -14,6 +16,7 @@ created: 2026-01-01
 **Dependencies:** Arbiter 3.5.0, Pterodactyl Client API
 
 ---
+task_number: 94
 
 ## Overview
 
@@ -33,6 +36,7 @@ Add a **Global Restart Scheduler** to the Trinity Console that manages staggered
 - Drag-and-drop sort order for boot priority
 
 ---
+task_number: 94
 
 ## Architecture Decisions
 
@@ -59,6 +63,7 @@ This prevents confusion with manual schedules and allows Trinity to identify its
 Before first sync, run **Audit** to detect existing restart schedules. Trinity can "nuke" rogue schedules before taking control.
 
 ---
+task_number: 94
 
 ## Database Schema
 
@@ -121,6 +126,7 @@ ON CONFLICT (node) DO NOTHING;
 ```
 
 ---
+task_number: 94
 
 ## Implementation Files
 
@@ -622,6 +628,7 @@ document.addEventListener("DOMContentLoaded", function() {
 ```
 
 ---
+task_number: 94
 
 ## Implementation Checklist
 
@@ -655,6 +662,7 @@ document.addEventListener("DOMContentLoaded", function() {
 - [ ] Wait for first scheduled restart to confirm it works
 
 ---
+task_number: 94
 
 ## API Notes
 
@@ -671,6 +679,7 @@ document.addEventListener("DOMContentLoaded", function() {
 | NC1  | 04:30 UTC | 5 min    | ~55 min for 11 servers |
 
 ---
+task_number: 94
 
 ## Consultation Record
 
@@ -683,6 +692,7 @@ This task was architected with Gemini AI on April 5, 2026. Full consultation cov
 - Audit trail logging
 
 ---
+task_number: 94
 
 ## Implementation Record (April 5, 2026)
 
@@ -732,5 +742,6 @@ Before using Sync All or Nuke:
 4. Then Sync All to create `[Trinity] Daily Restart` schedules
 
 ---
+task_number: 94
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 🔥❄️

docs/tasks/task-098-discord-channel-automation.md

@@ -1,3 +1,11 @@
+---
+task_number: 98
+status: open
+priority: P2
+owner: Holly
+created: 2026-04-07
+---
+
 # Task #98: Discord Server Channel Automation
 
 **Created:** April 7, 2026  
@@ -7,6 +15,7 @@
 **Status:** Backlog  
 
 ---
+task_number: 98
 
 ## Problem
 
@@ -24,6 +33,7 @@ When a new Minecraft server is added, Holly must manually create:
 With 20 servers, this is 100+ manual actions. Each new server adds 7 more.
 
 ---
+task_number: 98
 
 ## Solution
 
@@ -40,6 +50,7 @@ Automate Discord channel creation via the Discord API.
 **Recommendation:** Start with **Option A** (bot command) — fastest to implement, Holly can use immediately.
 
 ---
+task_number: 98
 
 ## Technical Requirements
 
@@ -65,6 +76,7 @@ Automate Discord channel creation via the Discord API.
 - `15` = Forum
 
 ---
+task_number: 98
 
 ## Implementation Outline
 
@@ -125,6 +137,7 @@ async function createServerChannels(serverName, emoji) {
 ```
 
 ---
+task_number: 98
 
 ## Future Enhancements
 
@@ -134,6 +147,7 @@ async function createServerChannels(serverName, emoji) {
 4. **Carl-bot API integration:** Auto-configure reaction role mapping (if API available)
 
 ---
+task_number: 98
 
 ## Acceptance Criteria
 
@@ -146,6 +160,7 @@ async function createServerChannels(serverName, emoji) {
 - [ ] `!deleteserver "Server Name"` removes role + all channels
 
 ---
+task_number: 98
 
 ## Notes
 
@@ -157,5 +172,6 @@ async function createServerChannels(serverName, emoji) {
 - This is a quality-of-life improvement for Holly, not a launch blocker
 
 ---
+task_number: 98
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 🔥❄️

docs/tasks/task-099-claude-projects-architecture.md

@@ -1,3 +1,11 @@
+---
+task_number: 99
+status: open
+priority: P1
+owner: Michael
+created: 2026-04-07
+---
+
 # Task #99: Claude Projects Architecture — Ops/Dev/Marketing Separation
 
 **Created:** April 7, 2026  
@@ -7,12 +15,14 @@
 **Effort:** ~2-3 hours browser work (no SSH needed)
 
 ---
+task_number: 99
 
 ## Overview
 
 Implement Gemini's recommended workflow: separate Claude Projects for different work contexts, with Master Documents in Project Knowledge to eliminate context bloat and copy-paste overhead.
 
 ---
+task_number: 99
 
 ## The Architecture
 
@@ -42,6 +52,7 @@ Implement Gemini's recommended workflow: separate Claude Projects for different
 **Key Principle:** Projects = Local Scope, Memory = Global Scope
 
 ---
+task_number: 99
 
 ## Gemini's Questions — Answered
 
@@ -73,6 +84,7 @@ Implement Gemini's recommended workflow: separate Claude Projects for different
 | 4 | `Subscription-Tiers.md` | Awakened → Sovereign, pricing, features | Extract from existing docs |
 
 ---
+task_number: 99
 
 ## Implementation Steps (Next Session)
 
@@ -201,6 +213,7 @@ Implement Gemini's recommended workflow: separate Claude Projects for different
 5. Confirm context doesn't bleed between projects
 
 ---
+task_number: 99
 
 ## The Micro-Session Workflow (Ongoing Practice)
 
@@ -214,6 +227,7 @@ Once set up, follow this loop:
 6. **Sync Master Docs** — Update the canonical version, re-upload to Project Knowledge
 
 ---
+task_number: 99
 
 ## Success Criteria
 
@@ -225,6 +239,7 @@ Once set up, follow this loop:
 - [ ] Model selection guidance embedded in project instructions
 
 ---
+task_number: 99
 
 ## Dependencies
 
@@ -233,6 +248,7 @@ Once set up, follow this loop:
 - Brand Guidelines PDF (Michael bringing from work)
 
 ---
+task_number: 99
 
 ## Related
 
@@ -241,5 +257,6 @@ Once set up, follow this loop:
 - Context handoff template: `/docs/templates/context-handoff-template.md`
 
 ---
+task_number: 99
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 🔥❄️

docs/tasks/terraria-branding-training-arc/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 32
 status: open
 priority: P3
 owner: Michael
 created: 2026-01-01
 ---
+task_number: 32
 
 # Terraria Branding Training Arc
 

docs/tasks/vaultwarden-ssh-setup/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 14
 status: open
 priority: P1
 owner: Michael
 created: 2026-01-01
 ---
+task_number: 14
 
 # Task #14: Store Firefrost SSH Key in Vaultwarden
 
@@ -13,6 +15,7 @@ created: 2026-01-01
 **Completed By:** Chronicler #59 + Michael
 
 ---
+task_number: 14
 
 ## WHAT WAS DONE
 
@@ -21,6 +24,7 @@ created: 2026-01-01
 3. ✅ Documented server list with usernames
 
 ---
+task_number: 14
 
 ## HOW THIS WORKS
 
@@ -35,6 +39,7 @@ created: 2026-01-01
 **This is fast** — takes 30 seconds to grab from Vaultwarden and upload.
 
 ---
+task_number: 14
 
 ## KEY LOCATION IN VAULTWARDEN
 
@@ -43,6 +48,7 @@ created: 2026-01-01
 **Contents:** OpenSSH private key + server list
 
 ---
+task_number: 14
 
 ## SERVERS USING THIS KEY
 
@@ -56,6 +62,7 @@ created: 2026-01-01
 | NC1 Charlotte | 216.239.104.130 | `root` |
 
 ---
+task_number: 14
 
 ## FOR CHRONICLERS: HOW TO USE SSH
 
@@ -93,6 +100,7 @@ ssh -i ~/.ssh/firefrost_key root@216.239.104.130
 ```
 
 ---
+task_number: 14
 
 ## KEY DETAILS
 
@@ -102,5 +110,6 @@ ssh -i ~/.ssh/firefrost_key root@216.239.104.130
 - **Conversion done:** April 4, 2026
 
 ---
+task_number: 14
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 🔥❄️

docs/tasks/world-backup-automation/README.md

@@ -1,9 +1,11 @@
 ---
+task_number: 40
 status: open
 priority: P3
 owner: Michael
 created: 2026-01-01
 ---
+task_number: 40
 
 # World Backup Automation