fix: point DEFAULT_CLIENT_FILE_API at packages.dandanton.com CDN

Use https://packages.dandanton.com/tdlm-client/latest (same relative
layout as Pack's tdlm-client/latest). Document TDLM_CLIENT_FILE_API
alignment and the Pack publish/mirror caveat.

.github/workflows/publish-tdlm.yml

@@ -157,7 +157,8 @@ jobs:
               "- %s/HMCL.jar\n\n"
               "TDLMPack does not Maven-resolve this launcher; point the pack README / install docs at these URLs "
               "instead of hand-copying exe/jar.\n"
-              "Client pack updates stay on tdlm-client/latest (unchanged).\n"
+              "Client pack fileApi default: https://packages.dandanton.com/tdlm-client/latest\n"
+              "(Pack must publish/mirror the same layout; see docs/TDLM_CONSUME.md).\n"
           ) % (package_root, package_root)
 
           quoted = urllib.parse.quote(tag, safe="")

HMCL/src/main/java/org/jackhuang/hmcl/Metadata.java

@@ -141,9 +141,9 @@ public final class Metadata {
         return null;
     }
 
-    /// Default client Server Modpack fileApi published by TDLMPack (Gitea generic package `latest`).
+    /// Default client Server Modpack fileApi (CDN mirror of Pack's `tdlm-client/latest` layout).
     public static final String DEFAULT_CLIENT_FILE_API =
-            "https://git.nest.potatolab.uk:8443/api/packages/TDLM/generic/tdlm-client/latest";
+            "https://packages.dandanton.com/tdlm-client/latest";
 
     /// Stable client update root (`server-manifest.json` and `overrides/` live under this URL).
     ///

docs/TDLM_CONSUME.md

@@ -1,8 +1,8 @@
 # TDLMPack consume path for TDLM/HMCL
 
 TDLMPack does **not** pull this launcher via Maven, a version pin, or a pack-build download step.
-The pack build only publishes the HMCL Server Modpack client (`server-manifest.json` + `overrides/`)
-to Gitea generic `tdlm-client/latest`. Players install the launcher separately.
+The pack build publishes the HMCL Server Modpack client (`server-manifest.json` + `overrides/`)
+under the `tdlm-client/latest` layout. Players install the launcher separately.
 
 ## After this repo’s publish workflow
 
@@ -34,13 +34,26 @@ Assets on each tag: `HMCL.exe`, `HMCL.jar`, plus `.sha256` files.
 In `TDLM/TDLMPack` README §启动, replace the repo-only “安装 TDLM/HMCL” step with one of the URLs above.
 **Do not** add HMCL as a Gradle/Maven dependency of the pack — pack CI stays pack-only.
 
-### 4. Unchanged: client pack → launcher data
+### 4. Client pack fileApi (CDN)
 
-HMCL still reads the pack fileApi (default):
+HMCL default (`Metadata.DEFAULT_CLIENT_FILE_API`):
 
 ```text
-https://git.nest.potatolab.uk:8443/api/packages/TDLM/generic/tdlm-client/latest/server-manifest.json
+https://packages.dandanton.com/tdlm-client/latest
 ```
 
-Override: `-Dhmcl.client.fileApi=…` or jar attribute `hmcl.client.fileApi`.
-That path is pack content for the already-installed launcher, not how the pack obtains `HMCL.exe`.
+First install / updates fetch `{fileApi}/server-manifest.json` (and `overrides/**` under that root).
+Override at runtime: `-Dhmcl.client.fileApi=…` or jar attribute `hmcl.client.fileApi`.
+
+**TDLMPack must use the same URL** so `server-manifest.json` embeds it:
+
+```text
+TDLM_CLIENT_FILE_API=https://packages.dandanton.com/tdlm-client/latest
+```
+
+Set that as the Gitea Actions **variable** on `TDLM/TDLMPack` (pack.yml already passes `vars.TDLM_CLIENT_FILE_API`).
+
+**Publish caveat:** Pack’s current workflow PUTs the client tree to whatever `TDLM_CLIENT_FILE_API` is (upload root = fileApi). Today that defaults to Gitea generic
+`https://git.nest.potatolab.uk:8443/api/packages/TDLM/generic/tdlm-client/latest`.
+If you only change the HMCL default to the CDN and leave Pack publishing to Gitea, players will 404 unless you **mirror/sync** Gitea → `packages.dandanton.com/tdlm-client/latest`.
+If you set `TDLM_CLIENT_FILE_API` to the CDN URL, Pack CI must be able to PUT to that CDN (or you must split “upload origin” from “public fileApi” in Pack — not implemented today). Do not point HMCL at the CDN without one of those two ops paths.