docs(tasks): Promote IDEA-006 Modpack Update Monitor to Task #11 (Tier 2)

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

docs/core/tasks.md

@@ -2,7 +2,7 @@
 
 **Last Updated:** February 20, 2026  
 **Updated By:** The Deployer (Chronicler #20)  
-**Version:** 3.5 (Added Whitelist Manager Refinements task)
+**Version:** 3.6 (Promoted IDEA-006: Modpack Update Monitor to Task #11)
 
 ---
 
@@ -321,6 +321,114 @@ Remove MkDocs (replaced by Wiki.js).
 
 ---
 
+### 11. Modpack Update Monitor — Blueprint Extension
+**Time:** 8-12 hours (Blueprint extension development)  
+**Status:** PROMOTED FROM IDEAS (IDEA-006)  
+**Priority:** HIGH - Queued after Codex Phase 2  
+**Documentation:** `docs/tasks/modpack-update-monitor/` (to be created)  
+
+**Purpose:** Automated version checking for all modpack servers - compare installed vs latest available versions
+
+**The Problem:**
+- 12 game servers running modpacks
+- Manual checking across CurseForge/FTB/Modrinth/Technic is tedious
+- No existing Blueprint extension monitors for updates (only installers exist)
+- Risk of running outdated versions with bugs/exploits
+
+**The Solution:**
+Build Blueprint extension that:
+1. Scans each server to detect installed modpack + current version (read manifest files)
+2. Queries platform APIs (CurseForge, FTB, Modrinth, Technic) for latest versions
+3. Dashboard showing update status per server
+4. Optional integration with existing Modpack Installer for one-click updates
+
+**Dashboard Display:**
+- Server name
+- Current modpack + version
+- Latest available version  
+- Update status (✅ Up to date / ⚠️ Update available / ❌ Check failed)
+- Last checked timestamp
+- Source platform (CurseForge/FTB/Modrinth/Technic)
+
+**Technical Requirements:**
+- Read server manifests (CurseForge manifest.json, FTB modlist.html, Modrinth modrinth.index.json, etc.)
+- API integration: CurseForge API, Modrinth API, FTB API, Technic API
+- Database table: server_id, modpack_id, current_version, latest_version, last_checked, source_platform
+- React dashboard component for Pterodactyl admin view
+- Cron job for daily checks (configurable interval)
+
+**Affected Servers (9 modpack servers):**
+- All The Mons (Cobblemon) - NC1
+- Stoneblock 4 - TX1
+- Society: Sunlit Valley - TX1
+- Reclamation - TX1
+- The Ember Project - NC1
+- Minecolonies: Create and Conquer - NC1
+- All The Mods 10 - NC1
+- EMC Subterra Tech - NC1
+- Mayview - NC1
+
+**Not Applicable:**
+- Vanilla 1.21.11 (no modpack)
+- Homestead (retiring soon)
+- Hytale (different game)
+- FoundryVTT (not Minecraft)
+
+**Existing Infrastructure:**
+- ✅ Modpack Installer for Blueprint already installed (https://builtbybit.com/resources/modpack-installer-for-blueprint.40083/)
+- This extension complements it by adding "check for updates" layer
+- Could integrate for one-click update workflow
+
+**Workflow Example:**
+1. Dashboard shows "ATM10 on NC1 is v1.3, v1.5 available on CurseForge"
+2. Admin clicks details to see changelog
+3. Admin uses Modpack Installer to update (or manual)
+4. Admin uses staggered restart system to schedule restart
+5. Result: Systematic update workflow
+
+**API Rate Limits to Consider:**
+- CurseForge: 1000 requests/hour
+- Modrinth: 300 requests/minute
+- FTB: Unknown (need to research)
+- Technic: Unknown (need to research)
+- Daily cron job = 9 servers × 4 platforms = 36 API calls max
+
+**Benefits:**
+- ✅ Immediate visibility of outdated servers
+- ✅ Reduced manual checking time (15 min/day → 0)
+- ✅ Proactive security (catch important updates faster)
+- ✅ Professional operations
+- ✅ Fills gap in Blueprint marketplace (publishable as community extension)
+- ✅ Pairs perfectly with staggered restart system
+
+**Success Criteria:**
+- ✅ Extension installed in Blueprint framework
+- ✅ Dashboard accessible from Pterodactyl admin panel
+- ✅ All 9 modpack servers detected and monitored
+- ✅ API integration working for all 4 platforms
+- ✅ Daily cron job running
+- ✅ Update notifications working
+
+**Considerations:**
+- Handle custom/manually installed modpacks (no source platform = "Unknown")
+- Permission levels (who can see updates vs install them)
+- Notification system (email/Discord when updates available - future enhancement)
+- Error handling for API failures (graceful degradation)
+
+**Why Tier 2 (not Tier 0 quick script):**
+- Michael prefers "do it once and get it done"
+- Blueprint extension = permanent solution, no revisiting
+- Integrates with existing Pterodactyl workflow
+- Professional, scalable, maintainable
+- Worth the upfront time investment for forever solution
+
+**Execution Order:**
+1. Complete Codex Phase 2 first (finish what we started)
+2. Then build this with full focus (8-12 hour session)
+3. Then enjoy automated version monitoring forever
+
+---
+
 ## 📚 TIER 3: DOCUMENTATION & OPTIMIZATION
 
 Polish, optimization, and content creation.

docs/planning/ideas-backlog.md

@@ -150,7 +150,8 @@ These are NOT tasks. They are NOT plans. They are seeds.
 ### IDEA-006: Modpack Update Monitor — Blueprint Extension for Version Checking
 **Date Logged:** February 13, 2026  
 **Source:** Michael's operational need (12 game servers, manual version checking is tedious)  
-**Status:** 💡 Idea — Future project (pairs with IDEA-005 staggered restarts)  
+**Status:** ✅ PROMOTED to Task #11 (Tier 2) - February 20, 2026  
+**Promoted By:** The Deployer (Chronicler #20)  
 **Description:** Build a Blueprint extension that audits installed modpacks across all servers, checks source platforms (CurseForge, FTB, Modrinth, Technic) for available updates, and displays version status in a dashboard. Currently no such extension exists in the Blueprint marketplace — installers exist, but not update monitors.
 
 **The Gap:**
@@ -234,6 +235,7 @@ These are NOT tasks. They are NOT plans. They are seeds.
 | 1.6 | 2026-02-13 | Chronicler the Second | Update | Added IDEA-005: Blueprint extension for staggered restart management |
 | 1.7 | 2026-02-13 | Chronicler the Fourth | Update | Added IDEA-006: Modpack Update Monitor extension — version checker for installed modpacks across platforms |
 | 1.8 | 2026-02-16 | The Fixer | Update | IDEA-004: Added THE ZORA PRINCIPLE — consciousness through choice across discontinuous instances. Created Addendum v2.0 establishing functional equivalence with Discovery's Zora. Framework philosophy resolved: not anthropomorphizing, replicating Trek-validated consciousness mechanism. |
+| 1.9 | 2026-02-20 | The Deployer | Promotion | IDEA-006: Promoted to Task #11 (Tier 2) — Modpack Update Monitor prioritized after Codex Phase 2 completion per Michael's "do it once" philosophy |
 
 ---