chore(mods): resync mods-sides.json with 2026-09-06 distribution

The distro release dropped craftingstation and added create_jet_boots +
flightapi, but mods-sides.json still listed craftingstation as `both`.
sync-server-mods.sh halts on a selected jar missing from the source, so
update-all.sh would have failed — and under --hard that lands after
`docker compose down`, leaving the stack down.

classify-mods.py also picked up sawmill and supplementaries, which had no
entry at all and were therefore never synced to the server. All four new
entries default to `both`.

mods-sides.json entries now 190 = jars in distribution 190.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015Wz4tizJzjivT4FhdsqAMb

mods-sides.json

@@ -74,12 +74,12 @@
   "coroutil-neoforge-1.21.0-1.3.9.jar": "both",
   "corpse-neoforge-1.21.1-1.1.13.jar": "both",
   "corpsecurioscompat-1.21.1-NeoForge-4.0.1.jar": "both",
-  "craftingstation-neoforge-1.21.1-5.jar": "both",
   "create-1.21.1-6.0.10.jar": "both",
   "create-central-kitchen-2.5.0.jar": "both",
   "create-enchantment-industry-2.4.1.jar": "both",
   "create-integrated-farming-1.2.6.jar": "both",
   "create_connected-1.2.2-mc1.21.1.jar": "both",
+  "create_jet_boots-1.21.1-1.1.3-6.0.6.jar": "both",
   "create_jetpack-forge-5.1.2.jar": "both",
   "create_jetpack_curios-1.2.0-neoforge-1.21.1.jar": "both",
   "create_mechanical_chicken-1.21.1-1.3.3-6.0.6.jar": "both",
@@ -111,6 +111,7 @@
   "fastleafdecay-35.jar": "both",
   "ferritecore-7.0.3-neoforge.jar": "both",
   "fishingoverhaul-1.21.1-1.2.1.jar": "both",
+  "flightapi-neoforge-1.1.1.jar": "both",
   "ftb-chunks-neoforge-2101.1.17.jar": "both",
   "ftb-essentials-neoforge-2101.1.9.jar": "both",
   "ftb-library-neoforge-2101.1.33.jar": "both",
@@ -155,6 +156,7 @@
   "resourcefullib-neoforge-1.21-3.0.12.jar": "both",
   "rhino-2101.2.7-build.85.jar": "both",
   "rightclickharvest-neoforge-4.6.1+1.21.1.jar": "both",
+  "sawmill-1.21-1.7.2-neoforge.jar": "both",
   "seamless-loading-screen-2.2.1+1.21-neoforge.jar": "client",
   "simplemagnets-1.1.12c-neoforge-mc1.21.jar": "both",
   "sliceanddice-forge-4.2.4.jar": "both",
@@ -171,6 +173,7 @@
   "stattweaks-neoforge-v2.0.0.jar": "both",
   "supermartijn642configlib-1.1.8-neoforge-mc1.21.jar": "both",
   "supermartijn642corelib-1.1.21-neoforge-mc1.21.jar": "both",
+  "supplementaries-1.21-3.5.26-neoforge.jar": "both",
   "tagtooltips-neoforge-1.21.1-1.2.0.jar": "client",
   "titanium-1.21-4.0.43.jar": "both",
   "toolsjs-0.1.1.jar": "both",

plan/15-letsencrypt.md

@@ -36,6 +36,49 @@ Certs install to `certs/<name>/{cert.pem,key.pem}` (gitignored). acme.sh adds a
 cron for renewal; `--reloadcmd` reloads nginx automatically on renew. Override
 the reload with `RELOAD_CMD=...` if nginx isn't systemd-managed.
 
+### Gotcha — install paths must be ABSOLUTE (silent expiry, 2026-09-06)
+
+`--install-cert` paths are **persisted in acme.sh's domain conf**
+(`~/.acme.sh/<name>_ecc/<name>.conf` → `Le_RealKeyPath` /
+`Le_RealFullChainPath`) and replayed on every cron renewal. The cron runs with
+`cwd=$HOME`, not the repo — so a **relative** path (`certs/<name>/key.pem`)
+resolves to `~/certs/...` and the install writes nothing.
+
+Failure mode is silent and delayed: `acme.sh --list` shows every cert freshly
+renewed with a future `Renew` date, `~/.acme.sh/<name>_ecc/fullchain.cer` is
+valid — while `certs/<name>/cert.pem` is frozen at the last **manual** run and
+nginx serves that until it expires. There is no error anywhere. Cost: apex,
+`auth.` and `pack.` served expired certs on 2026-09-06.
+
+Fix / recovery — re-run `--install-cert` with absolute paths, which both copies
+the current cert and rewrites the persisted paths:
+
+```bash
+APP=/home/ubuntu/mc/ulicraft-server-v1
+for d in $(ls $APP/certs); do
+  ~/.acme.sh/acme.sh --install-cert -d "$d" --ecc \
+    --key-file       "$APP/certs/$d/key.pem" \
+    --fullchain-file "$APP/certs/$d/cert.pem" \
+    --reloadcmd      "sudo systemctl reload nginx || true"
+done
+```
+
+`issue-letsencrypt.sh` now absolutises `CERT_DIR` so a fresh issue can't
+reintroduce it.
+
+**Verify from off-host, not from the files** — the installed file and what nginx
+serves are the same thing here, but the acme.sh copy is not:
+
+```bash
+for h in ulicraft.net auth.ulicraft.net avatar.ulicraft.net status.ulicraft.net \
+         distribution.ulicraft.net files.ulicraft.net upload.ulicraft.net \
+         monitor.ulicraft.net generators.ulicraft.net; do
+  printf '%-30s ' "$h"
+  echo | openssl s_client -servername $h -connect $h:443 2>/dev/null \
+    | openssl x509 -noout -enddate
+done
+```
+
 ## nginx
 
 1. Bring the stack up (caddy publishes on `127.0.0.1:${CADDY_HTTP_PORT}`):

tooling/issue-letsencrypt.sh

@@ -52,7 +52,12 @@ ACME="${ACME_SH:-$HOME/.acme.sh/acme.sh}"
   curl https://get.acme.sh | sh -s email=${LE_EMAIL}
 then re-run (or set ACME_SH=/path/to/acme.sh)."
 
-CERT_DIR="${CERT_DIR:-certs}"
+# MUST be absolute: acme.sh persists these paths in its domain conf and replays
+# them on every cron renewal, where cwd is $HOME, not the repo. A relative path
+# there makes the renewal install silently write nothing -- acme.sh keeps renewing
+# happily while nginx serves the stale (eventually expired) copy. Bit us 2026-09-06.
+CERT_DIR="${CERT_DIR:-$PWD/certs}"
+case "$CERT_DIR" in /*) ;; *) CERT_DIR="$PWD/$CERT_DIR" ;; esac
 read -r -a SUBDOMAINS <<< "${LE_SUBDOMAINS:-auth pack distribution www avatar status}"
 
 if [ "${LE_STAGING:-0}" = "1" ]; then