## What happened

After the 2026-10-10 `omarchy update` (which pulled Arch's Qt 6.11.2 → 6.12.0 transition together with quickshell 0.3.1 → 0.3.2), pressing SUPER+SPACE shows a **fullscreen opaque black rectangle** instead of the menu. The menu itself is functional (opens/closes, keyboard focus works) — it just renders solid black. Screenshot pixel analysis: 100.0% pure black output while open; normal desktop returns after closing.

Root cause is filed upstream at quickshell-mirror/quickshell#1295: **under Qt 6.12, quickshell's `qs.*` config-module imports resolve singletons to their QML type instead of the instance** (both 0.3.1 and 0.3.2 affected; relative `import "dir"` still works).

Because the Omarchy shell keeps `Color`/`Style`/`Util` in `qs.Commons`, `Color.menu.*` resolves to `undefined`, the menu's `property color scrim` binding fails and keeps the uninitialized default (`#000000` opaque) → the fullscreen scrim is solid black.

## Steps to reproduce

1. Fresh Omarchy 4.0.4-1 install (or any install before 2026-10-10), menu works.
2. Run `omarchy update` with current Arch repos (qt6-base 6.12.0-2, qt6-declarative 6.12.0-1, qt6-wayland 6.12.0-1, quickshell 0.3.2-1) and let it restart/reboot the session.
3. Press SUPER+SPACE → fullscreen black.

## Evidence

- With menu open, screenshot is 100% black (1920×1080, avg RGB (0,0,0)).
- Journal during menu open:
  ```
  omarchy-shell[...]: WARN scene: @Commons/Border.qml[25:-1]: TypeError: Cannot read property 'menu.border-alpha' of undefined
  ```
  (`Color.shellValues` is `undefined`; same class of errors from user plugins: `TypeError: Cannot read property 'background' of undefined`.)
- Minimal quickshell sandbox repro (see quickshell-mirror/quickshell#1295):
  ```
  import qs.Commons
  Color.foreground      -> undefined     (should be "#cacccc")
  Color.menu            -> undefined
  Util.abs(-5)          -> TypeError: Property 'abs' of object Util_QMLTYPE_3 is not a function
  ```
  Same file imported relatively (`import "Commons" as C`) resolves correctly on the same Qt 6.12 runtime — so it is specifically the `qs.*` interception path, not the theme files or the shell config.

## System

- omarchy 4.0.4-1 (stable), quickshell 0.3.2-1 (bug present with 0.3.1-1 too)
- qt6-base 6.12.0-2, qt6-declarative 6.12.0-1, qt6-wayland 6.12.0-1
- Hyprland 0.56.2-4, kernel 7.2.5-3-omarchy
- CPU AMD Ryzen 7 4800H, GPU AMD Renoir (amdgpu)

## Workaround (verified)

Downgrade the Qt stack + quickshell to the 2026-10-10 versions from the pacman cache and restart the shell:

```bash
sudo pacman -U /var/cache/pacman/pkg/{qt6-base-6.11.2-3,qt6-declarative-6.11.2-2,qt6-wayland-6.11.2-1,qt6-shadertools-6.11.2-1,qt6-5compat-6.11.2-1,qt6-svg-6.11.2-1,qt6-positioning-6.11.2-1,qt6-webchannel-6.11.2-1,qt6-multimedia-6.11.2-1,qt6-multimedia-ffmpeg-6.11.2-1,qt6-networkauth-6.11.2-1,qt6-speech-6.11.2-1,qt6-imageformats-6.11.2-1,qt6-tools-6.11.2-2,quickshell-0.3.1-1,fcitx5-qt-5.1.16-1,kcoreaddons-6.30.0-1,kwidgetsaddons-6.30.0-1,kguiaddons-6.30.0-1,knotifications-6.30.0-1,kxmlgui-6.30.0-1,kjobwidgets-6.30.0-1,layer-shell-qt-6.7.5-1}-x86_64.pkg.tar.zst
omarchy restart shell
```

(qt6-translations 6.12.0-1 has no depends and can stay.) After this, menu renders correctly and all singleton TypeErrors disappear (verified: 0 errors from the new shell process; menu screenshot back to theme colors).

## Suggestions

- Until quickshell fixes `qs.*` singleton resolution on Qt 6.12, consider holding qt6/quickshell back in the update path or noting this in the 4.0.x update notes — every Omarchy user who takes the current Arch update hits a black menu.
- Alternatively the shell's own imports could move off `qs.*` singletons (relative imports still resolve correctly), though that's clearly a bigger change.