### Describe the bug

On a default Omarchy install (fcitx5 running via `omarchy-fcitx5.service`), switching the keyboard layout through Hyprland's xkb mechanism — the bar's keyboard-layout widget or a `grp:*` xkb option — **appears to work but has no effect on typing** in most apps.

The bar widget label changes (e.g. `EN` → `FA`), and `hyprctl devices -j` confirms the physical keyboard's `active_keymap` switched, but typed characters still come out in the previous layout in GTK/Qt/Chromium apps.

### Root cause

`omarchy-fcitx5.service` runs fcitx5 by default (installed for XCompose sequences), and Omarchy's environment (`/usr/share/omarchy/default/environment.d/10-omarchy-fcitx.conf`) points GTK/Qt/SDL at it (`INPUT_METHOD=fcitx`, `QT_IM_MODULE=fcitx`, `XMODIFIERS=@im=fcitx`).

Apps using the input-method path get their keys grabbed by fcitx5, which processes them against **its own virtual keyboard** (`hl-virtual-keyboard-fcitx5`) whose keymap stays on `us`. The default fcitx5 profile only contains `keyboard-us` and provides no way for the compositor's xkb layout list (`kb_layout = us,ir`) to be followed. So compositor-side layout switches never reach what fcitx5 commits into the app. The virtual keyboard also holds the `main` flag, so seat-wide reads describe it rather than the typed-on keyboard.

### Steps to reproduce

1. Fresh Omarchy 4.0.2 install (fcitx5 service active, default environment).
2. Set a second layout in `~/.config/hypr/input.lua`:
   ```lua
   hl.config({
     input = {
       kb_layout = "us,ir",
       kb_options = "grp:alt_shift_toggle",
     },
   })
   ```
3. Reload, then press Alt+Shift (or click the bar's keyboard-layout widget).
4. Bar label switches to `FA`; `hyprctl devices -j` shows the physical keyboard's `active_keymap` = "Persian".
5. Type in any GTK/Qt/Chromium app → still English characters.

### Expected behavior

Layout switching should reach all apps, or at minimum the bar widget should not report a switch that doesn't take effect.

### Workaround

```bash
systemctl --user disable --now omarchy-fcitx5.service
```

After that, xkb switching works everywhere immediately (verified: `hyprctl switchxkblayout` + typing produce the new layout in all apps). Cost: losing XCompose dead-key sequences, which fcitx5 was enabled for.

### Suggested fixes (any of)

1. Don't enable fcitx5 by default; enable it only for users who opt into IM input — plain xkb covers Latin + non-CJK layouts (including `ir`) out of the box.
2. Make fcitx5's keyboard engine follow the compositor's per-keyboard layout so the two stay in sync.
3. Have the keyboard-layout widget/`activelayout` handling detect this state (fcitx5 virtual keyboard holding `main` with a single-IM profile) and surface a hint, instead of showing a successful switch.

### System

- Omarchy 4.0.2-1, Hyprland 0.56.2, Wayland
- Debug log (expires in 24h): https://logs.omarchy.org/4NWaUO