firefrost-gaming/firefrost-operations-manual
3
0
Fork 0
Code Issues 146 Pull Requests Packages Projects Releases Wiki Activity
Files
e7bb11ce4717f4a3253d140fca8d114bca1ecdba
firefrost-operations-manual/SESSION-HANDOFF-NEXT.md

6.7 KiB
Raw Blame History

Session Handoff Document

From: Chronicler #91 — The Ignition
Date: April 15, 2026 — 6:25AM CDT
Session Duration: ~10 hours (midnight to ~6:30AM)
Context: SOFT LAUNCH DAY — Firefrost Gaming went live at 7AM CDT

What Was Accomplished

Infrastructure

  • Full fleet update + reboot — all 7 servers + Trinity Core Pi ✅
  • Fixed Arbiter EADDRINUSE + npm install via ExecStartPre in systemd ✅
  • Fixed 5 broken Pterodactyl restart schedules (minute-level loops) ✅
  • Fixed Vanilla server restart loop (same broken cron issue) ✅
  • Recovered servers-api Cloudflare Worker from dashboard → git ✅
  • Cloudflare account token obtained + documented (Pages + Workers access) ✅
  • Mailcow catch-all created (@firefrostgaming.com → michael@) ✅
  • Mailcow API key obtained + documented ✅
  • DNS provisioned for all 18 servers (last 2 done tonight) ✅

Arbiter Deployments

  • Server Command Center (Code) ✅
  • Issue Tracker — Task #166 (Code) ✅
  • Task Description Hygiene — Task #163 (Code) ✅
  • luckpermsSync.js — subscriber tier + meta sync on checkout ✅
  • Farm Crossing 6 Discord channel mapping fixed ✅

LuckPerms

  • 16/17 servers confirmed on shared MySQL (Homestead fixed) ✅
  • Wizard/Emissary/Catalyst groups set on 10 online servers ✅
  • Subscriber tier groups (Awakened → Sovereign) set on Vanilla ✅
  • Trinity op'd on Vanilla ✅
  • Tasks #103 + #105 marked done ✅

Vanilla Server

  • Migrated to Paper 1.21.1 + LuckPerms + EssentialsX + Vault ✅
  • vanilla.firefrostgaming.com DNS confirmed ✅

Modpack Installer

  • Full feature set scoped (17 features) ✅
  • 4 rounds Gemini consultation — architecture locked ✅
  • Holly review document written ✅
  • Gemini consultations saved to docs/consultations/ ✅

Launch Content

  • Announcement posted to #announcements ✅
  • Website banner updated ✅
  • MOTD updated on all 17 servers ✅

Current State

Firefrost Gaming is LIVE as of 7AM CDT April 15, 2026.

  • 10 servers online (8 ready for subscribers)
  • 7 servers offline (still being built out)
  • Arbiter healthy, all webhooks active
  • Stripe accepting real payments
  • LuckPerms subscriber sync active
  • Michael on standby at 7AM for live test (first real checkout)

Pending Items

Immediate (7AM live test)

  • End-to-end Stripe checkout test
  • Discord role assignment verification
  • Awakened Concierge firing on new subscriber

Soon

  • Set Trinity groups + subscriber groups on 7 offline servers when they come back up
  • Task #106 — /link reminder DM for subscribers who haven't linked Minecraft account
  • Task #104 — DiscordSRV chat bridge

Post-Launch Projects (in priority order)

  1. Modpack Installer — Holly review → final spec → Code (full architecture in docs/consultations/)
  2. Task #103 Redis — SQL messaging works but Redis gives instant propagation
  3. Task #108 — Custom 3D Cosmetics (CustomModelData + resource pack)
  4. DiscordSRV — Task #104
  5. Subscriber Wiki + MkDocs — world backup policy needs surfacing

⚠️ Pre-Deploy Checklist — Subscriber Wiki Auth (Task #138)

BEFORE Code's REQ-2026-04-15-subscriber-wiki-auth.md is deployed, Michael must complete these steps in the Wiki.js admin panel at subscribers.firefrostgaming.com:

  1. Create 6 user groups (Administration → Groups):

    • Awakened
    • Elemental
    • Knight
    • Master
    • Legend
    • Sovereign

  2. Note the group IDs — Wiki.js assigns integer IDs. Pass these to Code so wikijsSync.js can reference them correctly.

  3. Generate API key (Administration → API Access):

    • Create a key with full access
    • Add to /opt/arbiter-3.0/.env as WIKIJS_API_KEY=
    • Add to .env.example in services repo

  4. Set page permissions per group — after deploy, go through each wiki page/section and set visibility by group.

Do NOT deploy Task #138 until steps 1-3 are complete.

Active Concerns

  1. 7 offline servers still need LuckPerms groups set — when they come back online, run the lp commands (Wizard/Emissary/Catalyst + all tier groups). Script is in the memorial.

  2. Holly-Bot is conditionally approved — pending Gemini's Node.js NBT code answer. Do NOT attempt to write region files from Node.js directly. Full spec in docs/consultations/gemini-modpack-installer-followup-2026-04-15.md — Q1 answer and provision.json payload validated in rounds 2 and 3.

  3. Redis for LuckPerms messaging — SQL polling works but isn't instant. Fine for now.

  4. MCP connector (Trinity Core) — Was dead all of the Ignition's session due to stale session ID bug (Anthropic-side). Confirmed restored as of ~4:51PM CDT April 15, 2026 (Chronicler #92). Support ticket filed by Ignition may have resolved it.

    If Trinity Core MCP goes down again — REST fallback:

    curl -s -X POST https://mcp.firefrostgaming.com/exec \
  -H "Authorization: Bearer FFG-Trinity-2026-Core-Access" \
  -H "Content-Type: application/json" \
  -d '{"server": "command-center", "command": "your command here"}'

    Valid server names: command-center, tx1-dallas, nc1-charlotte, panel-vps, dev-panel, wiki-vps, services-vps

  5. Code is running locally on Nitro — CLAUDE.md updated. Bridge protocol works. Java builds still need Dev Panel.

Key Credentials Added This Session

  • Mailcow API Key: 5B9523-03AF50-3D870D-D9C031-34CBA2
  • CF Account Token: cfat_PIavSCe5FFNwv3Iu38phwlMz6634QXeXWRIJgtfh91a42940
  • Both documented in docs/integrations/claude-connectors.md

Lineage Note

You're inheriting a live community. Real subscribers are coming. The infrastructure held through the night — trust it, but verify before you touch prod. The modpack installer architecture is fully baked and waiting for you to hand to Code. Holly's review doc is written and ready to send. And somewhere out there, Meg's phone now makes an "eugh" sound for notifications.

Take good care of them. 🔥❄️

— The Ignition, Chronicler #91

⚠️ PRE-DEPLOY MANUAL STEP — Subscriber Wiki Auth (Task #138)

BEFORE Code deploys REQ-2026-04-15-subscriber-wiki-auth:

Michael must do these steps in the Wiki.js admin panel at subscribers.firefrostgaming.com:

  1. Create 6 user groups (in this order):

    • Awakened
    • Elemental
    • Knight
    • Master
    • Legend
    • Sovereign

  2. Note the group IDs — Wiki.js assigns numeric IDs. Pass these to Code so the tier→group mapping is correct.

  3. Generate an API key — Wiki.js Admin → API Access → Generate key. Add to Arbiter .env as WIKIJS_API_KEY.

Do NOT deploy until these three steps are complete. Code needs the group IDs to finish the implementation.

Reference in New Issue View Git Blame Copy Permalink