ci(gitea-sync): overlay launcher from default branch before pack

Release tags can point at commits older than launcher lib additions; building
only from the tag omitted gitea-release.js etc. Fetch default branch and
checkout tools/fractured-launcher-electron from it before npm ci/pack.

Co-authored-by: Cursor <cursoragent@cursor.com>

.github/workflows/gitea-release-sync.yml

@@ -13,7 +13,8 @@
 # Release on github.com (Releases → Draft/new release → Publish). The workflow
 # definition must exist on the repo DEFAULT branch (GitHub runs it from there).
 #
-# Steps: build Electron from tag → download this repo’s release attachments → upload all to Gitea.
+# Steps: build Electron using launcher sources from DEFAULT BRANCH (so tags never miss
+# launcher files), checkout tag only for a consistent tree → download release attachments → Gitea.
 #
 # Secrets: GITEA_BASE_URL, GITEA_TOKEN, GITEA_OWNER, GITEA_REPO
 # Optional variable: GITEA_TARGET_REF (see tools/fractured-launcher-electron/README.md)
@@ -66,6 +67,16 @@ jobs:
         with:
           ref: ${{ needs.meta.outputs.tag }}
 
+      # Release tags often point at server/game commits that predate launcher lib fixes.
+      # Always pack the launcher from default branch so app.asar includes the full tree.
+      - name: Overlay launcher from default branch
+        shell: bash
+        run: |
+          set -euo pipefail
+          DB="${{ github.event.repository.default_branch }}"
+          git fetch --no-tags --depth=1 origin "+refs/heads/${DB}:refs/remotes/origin/${DB}"
+          git checkout "origin/${DB}" -- tools/fractured-launcher-electron
+
       - uses: actions/setup-node@v4
         with:
           node-version: '20'