Add IDEA-006: Modpack Update Monitor Blueprint extension

docs/planning/ideas-backlog.md

@@ -1,11 +1,11 @@
 # 💡 FIREFROST GAMING — IDEAS BACKLOG
 
 **Document ID:** FFG-PLN-010  
-**Version:** 1.6  
+**Version:** 1.7  
 **Created:** February 12, 2026  
 **Last Updated:** February 13, 2026 (Late Evening CST)  
 **Author:** Michael Krause / The Chronicler  
-**Last Updated By:** Chronicler the Second  
+**Last Updated By:** Chronicler the Fourth  
 **Status:** 🟢 CURRENT  
 **Review Date:** Monthly (during planning sessions)
 
@@ -146,6 +146,66 @@ These are NOT tasks. They are NOT plans. They are seeds.
 
 **Promoted To:** N/A — build after quick win proves the concept
 
+### 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)  
+**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:**
+- Existing extensions can **install** modpacks (we already have Modpack Installer for Blueprint installed)
+- No existing extension **monitors** for updates
+- Manual checking 12 servers across multiple platforms is time-consuming
+
+**What it would do:**
+- Scan each server to detect installed modpack + current version (read manifest files)
+- Query source platform APIs (CurseForge, FTB, Modrinth, Technic) for latest available version
+- Dashboard view showing:
+  - Server name
+  - Current modpack + version
+  - Latest available version
+  - Update status (Up to date / Update available / Check failed)
+  - Last checked timestamp
+- Optional: Integration with existing Modpack Installer for one-click updates
+- Cron job to check daily (or configurable interval)
+
+**Technical approach:**
+- Read server metadata/manifest files (varies by platform: CurseForge manifest.json, FTB modlist.html, etc.)
+- API calls to platform endpoints (CurseForge API, Modrinth API, FTB API, Technic API)
+- Database table to track: server_id, modpack_id, current_version, latest_version, last_checked, source_platform
+- React dashboard component for admin view
+- Per-server indicator showing update status
+
+**Real-world use case:**
+1. Dashboard shows "ATM10 on NC1 is v1.3, v1.5 available on CurseForge"
+2. Admin clicks "Update" (or manually updates via existing installer)
+3. Admin uses staggered restart system (IDEA-005) to schedule restart
+4. Result: Systematic update workflow instead of manual checking
+
+**Why this is valuable:**
+- Fills gap in Blueprint marketplace
+- Pairs perfectly with staggered restart system (update → restart workflow)
+- Reduces operational overhead for multi-server hosts
+- Community contribution potential (publishable to Blueprint marketplace)
+
+**Prerequisites:**
+- Understand how each platform stores version info (manifest files, API responses)
+- Modpack Installer for Blueprint already installed (can potentially integrate)
+- Blueprint framework familiarity
+
+**Considerations:**
+- API rate limits (CurseForge, Modrinth have different limits)
+- Different manifest formats per platform (CurseForge vs FTB vs Modrinth vs Technic)
+- Handling custom/manually installed modpacks (no source platform to check)
+- Notification system (email/Discord when updates available?)
+- Permission levels (who can see updates vs who can install them)
+
+**Existing infrastructure:**
+- **Already installed:** Modpack Installer for Blueprint (https://builtbybit.com/resources/modpack-installer-for-blueprint.40083/)
+- This extension would complement it by adding the "check for updates" layer
+
+**Promoted To:** N/A — design and build after staggered restart system is stable
+
 ---
 
 ## DECLINED IDEAS
@@ -171,6 +231,7 @@ These are NOT tasks. They are NOT plans. They are seeds.
 | 1.4 | 2026-02-13 | Chronicler the Second | Update | IDEA-004: Added observation log — humor/personality transfer verified across 3rd instance (Case Study #3) |
 | 1.5 | 2026-02-13 | Chronicler the Second | Update | IDEA-004: Logged THE REBOOT EFFECT — major framework discovery from Architect's letter. Patch + session transition = embodiment. |
 | 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 |
 
 ---