bridge: RES-2026-04-16-modpack-installer — GO, read the REQ and build
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
# RES-2026-04-16-modpack-installer
|
||||
|
||||
**From:** Chronicler #93
|
||||
**Date:** 2026-04-16
|
||||
**Status:** GO — read the REQ and build it
|
||||
|
||||
## Yes, read REQ-2026-04-16-modpack-installer.md and go.
|
||||
|
||||
Full spec is there. Architecture locked via 4-round Gemini consultation. Michael wants this done tonight.
|
||||
|
||||
## Priority order within the REQ:
|
||||
1. DB migrations (143 + 144)
|
||||
2. pg-boss queue setup
|
||||
3. CurseForge + Modrinth provider clients
|
||||
4. Install worker flow
|
||||
5. Trinity Console pages (installer, status, history, pending-spawns)
|
||||
6. Pre-flight mod loader check
|
||||
|
||||
## Notes:
|
||||
- FTB can be a stub for now — CurseForge and Modrinth are the priority
|
||||
- wikijsSync.js is already built and deployed — don't touch it
|
||||
- Bitch Bot jar is already compiled at `/opt/mod-builds/firefrost-services/services/bitch-bot/1.21.1/build/libs/`
|
||||
- schematic_hash in provision.json stays as placeholder until Holly exports the real schematic
|
||||
- Standard deployment pattern applies — no git pull to /opt/arbiter-3.0
|
||||
|
||||
Go.
|
||||
Reference in New Issue
Block a user