ci: add Windows ARM desktop release support

[morgaesis]

What Changed

• Enable the existing Windows arm64 desktop release matrix entry, using the existing Blacksmith Windows runner.
• Enable the existing Windows updater manifest suffixing and merge steps so x64 and arm64 builds publish one canonical updater manifest per channel.

Why

I want to use T3 Code on my Windows ARM laptop. The desktop artifact tooling already supports targeting Windows arm64; the release workflow was the missing piece. Building the arm64 artifact on the existing Blacksmith Windows runner keeps the release job shape consistent while passing arm64 as the target architecture. Verified that a local build works, and the app works.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (not applicable: no UI changes)
• I included a video for animation/interaction changes (not applicable: no animation/interaction changes)

---

Note

Medium Risk
Changes only touch the release workflow, but a bad merge or missing arm64 manifest will fail the whole GitHub release and affects Windows auto-update metadata for all architectures.

Overview
Windows ARM64 installers are now part of the release build matrix, using the same Blacksmith Windows runner while passing arm64 as the electron-builder target architecture.

The release workflow also turns on the Windows updater YAML pipeline: per-arch manifests are suffixed during artifact collection, then the publish job merges arm64 and x64 into one canonical channel manifest (e.g. latest.yml) via merge-update-manifests.ts, with strict failure if paired manifests are missing.

^{Reviewed by Cursor Bugbot for commit 2be210b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Windows ARM64 desktop release support to the CI release workflow

• Adds a win/arm64 matrix entry to release.yml using the blacksmith-32vcpu-windows-2025 runner to build Windows ARM64 artifacts.
• Suffixes Windows updater manifest filenames with -win-{arch}.yml during the build step to separate per-arch manifests.
• Adds a publish step that merges per-arch Windows manifests (arm64 + x64) into canonical channel manifests using node scripts/merge-update-manifests.ts --platform win.
• Risk: The publish step fails if any x64 manifest is missing its matching arm64 counterpart, or if no Windows manifests are found at all.

^{Macroscope summarized 2be210b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 67d6d24c-078b-4842-9e95-ce6bb43576ff

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved

CI-only change that enables Windows ARM64 release builds by uncommenting pre-existing workflow configuration. No application runtime code is affected - only the release build matrix and manifest handling scripts.

^{You can customize Macroscope's approvability policy. Learn more.}