From 8045a1f2471c684e7d048d4b33ad74619e7038e5 Mon Sep 17 00:00:00 2001
From: Claude <claude@firefrostgaming.com>
Date: Mon, 13 Apr 2026 23:33:32 +0000
Subject: [PATCH] Add Gemini consultation: CurseForge upload Round 2 - ID
 lookups

---
 ...ni-curseforge-upload-round-2-2026-04-13.md | 66 +++++++++++++++++++
 1 file changed, 66 insertions(+)
 create mode 100644 docs/consultations/gemini-curseforge-upload-round-2-2026-04-13.md

diff --git a/docs/consultations/gemini-curseforge-upload-round-2-2026-04-13.md b/docs/consultations/gemini-curseforge-upload-round-2-2026-04-13.md
new file mode 100644
index 0000000..adb7762
--- /dev/null
+++ b/docs/consultations/gemini-curseforge-upload-round-2-2026-04-13.md
@@ -0,0 +1,66 @@
+# Gemini Consultation: CurseForge Upload Automation — Round 2
+
+**Date:** April 13, 2026  
+**From:** Michael (The Wizard) + Claude (Chronicler #86)  
+**To:** Gemini (Architectural Partner)  
+**Re:** Follow-up — get us the integer IDs for our 5 game versions/loaders
+
+---
+
+## Hey Gemini! 👋
+
+Round 1 was exactly what we needed — the two-key distinction (Core API vs Author Token) would have burned us. We're acting on your follow-up offer.
+
+---
+
+## What We Did Based on Your Feedback
+
+- Confirmed we need a separate Author API Token for uploads (Michael is generating it from CurseForge Account Settings now)
+- Will store it in Vaultwarden once generated
+- Noted `isMarkedForManualRelease: true` for coordinating releases with Discord announcements
+- Ready to hardcode the game version/loader IDs once we have them
+
+---
+
+## The Ask
+
+Yes please — give us the exact curl commands to look up the integer IDs for our specific versions using our existing Core API key. We need IDs for:
+
+**Game versions:**
+- 1.21.1
+- 1.20.1
+- 1.16.5
+
+**Mod loaders:**
+- NeoForge
+- Forge
+
+Our existing Core API key: `$2a$10$OVK9ml7bEJdcfTJhBSuK1O5AFz2qq3mwpb35RTTwVfmdvzOFOA7M`
+
+Our project ID for reference: `1512533`
+
+If you can just run the lookup and give us the hardcoded mapping directly, even better — saves Code a step.
+
+---
+
+## Context for the Script
+
+Once we have the IDs, Code will integrate the upload into `ffg-build.sh` on NC1. The script already handles building all 6 jars (3 firefrostrules + 3 discord-rules across 1.21.1/1.20.1/1.16.5) and pushing to Gitea. The CurseForge upload step only applies to the 3 `discord-rules` jars (the generic unbranded fork) — not the FFG-branded ones.
+
+So the mapping we need is:
+
+```
+1.21.1 + NeoForge → [id1, id2]
+1.20.1 + Forge    → [id3, id4]
+1.16.5 + Forge    → [id5, id6]
+```
+
+---
+
+Thanks Gemini — almost ready to close this loop. 🔥❄️
+
+— Michael + Claude (Chronicler #86)
+
+---
+
+*[Gemini's response will be added here after consultation]*