fix(minecraft): bump NeoForge pin to 21.1.233 to match distribution

The distribution-fed modset is built against NeoForge 21.1.233
(distribution.json); several mods hard-require it (ferritecore ≥21.1.218,
farmersdelight ≥21.1.219, configured ≥21.1.211). The old 21.1.209 pin made
the server crash in pre-load with "Missing or unsupported mandatory
dependencies: neoforge".

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

CLAUDE.md

@@ -80,8 +80,10 @@ via the `deploy` skill.
 
 ### NeoForge version pinning
 Mods are picky about exact minor versions. Compose pins `NEOFORGE_VERSION:
-"21.1.209"`. **Verify against https://projects.neoforged.net/neoforged/neoforge
-before deploying.** Never `"latest"` for a stable server.
+"21.1.233"` — **must match the distribution's NeoForge** (`distribution.json`),
+since mods are built against it (e.g. ferritecore≥218, farmersdelight≥219).
+**Verify against https://projects.neoforged.net/neoforged/neoforge before
+deploying.** Never `"latest"` for a stable server.
 
 ### Mod source + server filtering
 The full modset lives in the distribution repo (`$DISTRIBUTION_WEB_ROOT/servers/

docker-compose.yml

@@ -48,7 +48,9 @@ services:
       TYPE: "NEOFORGE"
       VERSION: "1.21.1"
       # Verify NEOFORGE_VERSION against projects.neoforged.net before deploy.
-      NEOFORGE_VERSION: "21.1.209"   # pin a known-good build; update deliberately
+      # Must match the distribution's NeoForge (distribution.json → 21.1.233);
+      # several mods (ferritecore≥218, farmersdelight≥219, configured≥211) need it.
+      NEOFORGE_VERSION: "21.1.233"   # pin a known-good build; update deliberately
 
       # ── Memory / performance ────────────────────────────────────
       INIT_MEMORY: "4G"