fix(dashboard-release): create release once, eliminating arch-split drafts

v0.8.3 came out split across TWO draft releases for one tag: each matrix leg
called tauri-action with releaseDraft:true + tagName, so when two legs started
simultaneously they both found no existing release and each created its own
draft. The x64 legs landed on one draft, arm64 on another, and deploy-updater
grabbed only one draft's latest.json — shipping an x64-only updater manifest that
404'd (draft assets) and omitted Apple Silicon entirely.

Fix (the documented tauri-action multi-platform pattern):
- New create-release job makes the draft ONCE (reuses on re-run), outputs its id.
- Build matrix  and uploads via releaseId (not tagName),
  so every leg targets the same release and tauri-action merges one complete
  latest.json across all 6 platforms.
- release-dashboard.sh asset floor 10 -> 24: a full run is 25 assets; 24 catches
  an arch split (~12-14) as a backstop even if the race ever recurs.

v0.8.3 itself was already consolidated + republished manually (25 assets, full
17-platform updater manifest live); this prevents recurrence.

Co-authored-by: Alfonso [Magic Context] <288211368+alfonso-magic-context@users.noreply.github.com>

Author: ualtinok

.github/workflows/dashboard-release.yml

@@ -13,8 +13,47 @@ env:
   FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
 
 jobs:
+  # Create the draft release ONCE, up front, and hand its id to every build leg.
+  # The previous design let each matrix leg create-or-find the release by tagName;
+  # when two legs started simultaneously they both saw "no release yet" and each
+  # created its own draft, splitting the platform assets (and the per-arch
+  # latest.json) across two drafts for the same tag. Creating it here first means
+  # every leg uploads into the same release, so tauri-action merges one complete
+  # latest.json across all architectures.
+  create-release:
+    name: Create draft release
+    runs-on: ubuntu-latest
+    outputs:
+      release_id: ${{ steps.create.outputs.result }}
+    steps:
+      - id: create
+        uses: actions/github-script@v7
+        with:
+          result-encoding: string
+          script: |
+            const ref = process.env.GITHUB_REF_NAME;
+            const { owner, repo } = context.repo;
+            // Reuse an existing release for this tag (re-runs), else create a draft.
+            try {
+              const ex = await github.rest.repos.getReleaseByTag({ owner, repo, tag: ref });
+              core.info(`Reusing existing release ${ex.data.id} for ${ref}`);
+              return String(ex.data.id);
+            } catch (e) {
+              if (e.status !== 404) throw e;
+            }
+            const created = await github.rest.repos.createRelease({
+              owner, repo,
+              tag_name: ref,
+              name: `Dashboard ${ref}`,
+              draft: true,
+              prerelease: false,
+            });
+            core.info(`Created draft release ${created.data.id} for ${ref}`);
+            return String(created.data.id);
+
   build:
     name: Build Dashboard (${{ matrix.settings.label }})
+    needs: create-release
     # Harden cargo against the transient crates.io drops we hit in the wild
     # ("download of … failed / curl … Connection reset by peer" mid-build, which
     # killed a single matrix leg ~23s in despite the code being fine). Retry hard
@@ -130,9 +169,10 @@ jobs:
           tauriScript: bunx tauri
           args: --target ${{ matrix.settings.target }}${{ matrix.settings.bundles && format(' --bundles {0}', matrix.settings.bundles) || '' }}
           updaterJsonPreferNsis: true
-          tagName: ${{ github.ref_name }}
-          releaseName: "Dashboard ${{ github.ref_name }}"
-          releaseDraft: true
+          # Upload into the single pre-created draft (see create-release). Using
+          # releaseId (not tagName) guarantees every leg targets the same release,
+          # so there is exactly one release and one merged latest.json per tag.
+          releaseId: ${{ needs.create-release.outputs.release_id }}
           assetNamePattern: magic-context-dashboard-[platform]-${{ matrix.settings.arch }}[ext]
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

scripts/release-dashboard.sh

@@ -256,7 +256,11 @@ fi
 # Sanity: the run succeeded, so every leg uploaded its asset. Confirm the count
 # before publishing (a defensive check, not a wait — the run is already green).
 ASSET_COUNT=$(gh release view "$TAG" --repo cortexkit/magic-context --json assets --jq '.assets | length' 2>/dev/null || echo "0")
-MIN_ASSETS=10
+# A full run produces 25 assets (6 platforms × installers/sigs + latest.json).
+# A floor of 24 catches an architecture split (which yields ~12-14), the failure
+# mode where the matrix legs landed on two separate releases. The single
+# create-release job now prevents that, but keep the count as a backstop.
+MIN_ASSETS=24
 if [[ "$ASSET_COUNT" -lt "$MIN_ASSETS" ]]; then
   echo "  ⚠ Workflow succeeded but only $ASSET_COUNT/$MIN_ASSETS assets are attached."
   echo "  → https://github.com/cortexkit/magic-context/releases/tag/$TAG"