Uptime Kuma successfully migrated from TX1 to Command Center VPS:
- Node.js upgraded (18.20.8 → 20.20.0) for compatibility
- All monitors operational at status.firefrostgaming.com
- Data preserved (kuma.db + config)
- SSL certificate configured
- 100% uptime on all monitored services
NEW BEST PRACTICE: Update Cloudflare DNS BEFORE running Certbot
- Prevents SSL cert validation failures
- Added to workflow-guide.md
Migration Progress: 3/3 services complete (Gitea, Automation, Uptime Kuma)
Total session time: 5.5 hours
Game server impact: ZERO
Data loss: ZERO
NC1 monitoring: Still excluded (datacenter routing limitation)
Remaining: Ghost VPS cluster (MkDocs, Wiki.js, NextCloud)
Command Center VPS now serving:
- git.firefrostgaming.com (Gitea)
- status.firefrostgaming.com (Uptime Kuma)
- Automation daemon (connected to Gitea)
Established:
- When Claude should remind (pivots, deployments, major changes)
- Which files need updating most often
- The reminder format for end-of-session
- Michael's commitment to always update when reminded
Ensures: Project files stay fresh, no documentation drift
Established core principle: 'Always revise ALL documents when changes occur'
Documented:
- Why documentation drift is harmful
- What triggers updates (pivots, deployments, decisions)
- Which documents to check (scope, handoff, memory, instructions)
- The 4-step update workflow
- Examples of good discipline
- Anti-patterns to avoid
- The 5-minute rule
Prevents: Technical debt, context loss, future confusion
Ensures: Fast session starts, clear audit trail, team collaboration
Established core principle: 'Always revise ALL documents when changes occur'
Documented:
- Why documentation drift is harmful
- What triggers updates (pivots, deployments, decisions)
- Which documents to check (scope, handoff, memory, instructions)
- The 4-step update workflow
- Examples of good discipline
- Anti-patterns to avoid
- The 5-minute rule
Prevents: Technical debt, context loss, future confusion
Ensures: Fast session starts, clear audit trail, team collaboration
Created new single source of truth:
- FIREFROST-PROJECT-SCOPE-V2.md (complete vision)
- Archived 13 outdated/superseded documents
- Updated INDEX.md with clear navigation
- Reflects current state (60% Phase 0.5, automation system)
Key updates:
- Three-tier documentation architecture documented
- Automation system fully described
- Authentication phased approach included
- BookStack→MkDocs pivot captured
- Clear current vs future priorities
All historical docs preserved in archive for reference.
Clean slate for moving forward.
Added comprehensive automation workflow:
- Complete architecture diagram
- Step-by-step workflow explanation
- GitHub mirror integration details
- Usage instructions for future Claude sessions
- Medical context (why this system exists)
System reduces manual paste operations by 95%
Critical for Michael's hand limitations and marathon sessions
Deployed: February 9, 2026 10:15 AM CST
Initial automation framework:
- executor.sh: Runs queued tasks and commits results
- automation-daemon.sh: Watches Git for new tasks every 10s
- queue/: Tasks from Claude (*.sh files)
- results/: Execution results committed back
- logs/: Execution logs and completed tasks
System enables Claude to commit operations to Git,
TX1 pulls and executes automatically, then commits results back.
Reduces manual copy/paste from Michael to ONE command at session start.
Built for marathon sessions and medical accessibility needs.
Phase 1 complete - ready for testing
New policy: 30-day public download for deleted server worlds
- Minimum 48hr notice before deletion
- World backup provided via public link
- 30-day availability, then permanent deletion
- Subscriber notification via Discord + email
Servers deleted today (no backup - policy starts now):
- Peace of Mind (NC1)
- Sandbox in a Vacuum (NC1)
- Farming Crossing 5 (NC1)
Policy effective immediately for future deletions
