Make the Install menu architecture-aware on Apple Silicon

[kasimali59]

Problem

The Quattro Install menu currently exposes a number of upstream x86-only or repo-unavailable recipes on Apple Silicon. On aarch64, omarchy-pkg-add skips unavailable packages, but several callers continue to launch or configure the missing application. The result can look like a successful install even though no usable app was installed.

Tested on:

• M1 / aarch64
• Omarchy 4.0.1-2
• kernel 7.1.6-1-1-ARCH

I audited the fixed entries in default/omarchy/omarchy-menu.jsonc against the configured omarchy-aarch64, Asahi Alarm, Arch Linux ARM, and Omarchy repositories, then checked AUR arch metadata for missing packages.

Confirmed menu problems on aarch64

• Browser: Edge is x86-only.
• Services: Dropbox and Spotify are x86-only; the Bitwarden GUI package is absent (only the CLI is available).
• Editors/terminals: Zed and Ghostty are absent. Cursor has an existing ARM installer, but the menu bypasses it and requests cursor-bin directly.
• AI: Grok Bot, LM Studio, and T3 Code are x86-only; the menu's Ollama package names are absent.
• Gaming: the official Minecraft and Heroic packages are x86-only; Battle.net and Lutris recipes require unavailable Wine/UMU packages; NVIDIA documents the Linux GeForce NOW app for x86/x64 CPUs; Windows VM is already hard-coded as unsupported.
• Xbox Controllers requests linux-headers, while this system needs the available linux-asahi-headers package.
• RetroArch mostly works, but libretro-ppsspp and libretro-uae-git are skipped.
• Restore Preinstalls still requests unavailable pinta and obsidian package names, even though the fork provides obsidian-appimage.

Suggested approach

Make the fixed Install menu architecture-aware rather than presenting actions that are known to fail:

1. Add aarch64 visibility guards for entries without a usable ARM route.
2. Route Cursor through the existing omarchy-install-cursor ARM branch.
3. Replace the official Minecraft launcher with native prismlauncher on ARM.
4. Install linux-asahi-headers before the Xbox controller recipe on Apple Silicon.
5. For Spotify, consider offering both the web fallback from Use Spotify web player on aarch64 #327 and native spotify-player as a clearly labelled Premium-only terminal option. spotify-player, spotifyd, and ncspot are all currently available as aarch64 packages.
6. Require a command/package postcondition before showing success or running follow-up configuration. This complements the focused work in Make VS Code installation truthful on aarch64 #328 and Prevent false-success Dropbox setup on aarch64 #329.
7. Add a test that ensures every fixed package-backed menu action is either installable for the current architecture or explicitly guarded/routed.

Local validation

I tested the approach using the supported user extension file at ~/.config/omarchy/extensions/omarchy-menu.jsonc:

• 18 overrides parsed successfully through MenuModel.js.
• 14 incompatible entries were hidden.
• Four ARM replacements (Cursor, Spotify Player, Prism Launcher, and Xbox Controllers) passed shell syntax and repository-availability checks.
• omarchy menu refresh, omarchy menu ping, and omarchy menu summon install all returned ok against the running shell.

Related open work: #327 (Spotify web fallback), #328 (VS Code truthful installation), and #329 (Dropbox false-success prevention).