### System details

Intel Core i7-12700K, NVIDIA GeForce RTX 5060 Ti (610.57.04), Omarchy 4.0.2-1

- Hyprland 0.56.2-1, commit `efb50993780079460b0cbed1363e2166a2de1d9f`
- Linux 7.1.9-arch1-2
- Fcitx5 5.1.21-1 with fcitx5-rime 5.1.14-1
- Alacritty 0.17.0-1, native Wayland
- Herdr 0.8.2-1 running Codex
- Monitor scale: 1.25

### What's wrong?

#### Summary

The Fcitx5 candidate popup is not rendered when a native Wayland terminal is put into Hyprland's true internal fullscreen using Omarchy's default `SUPER+F` binding.

Composition and commit still work: Alacritty shows the preedit text and the selected Chinese text can be committed, but the candidate list itself is invisible. Pressing the screenshot key makes the candidate popup appear while the screenshot overlay is active, which initially made this look like a repaint problem.

This was reproduced in Alacritty while Herdr/Codex was using the full terminal viewport. The decisive state is Hyprland internal fullscreen, not Herdr's pane zoom mode.

#### Steps to reproduce

1. Start the stock Omarchy Wayland session with Fcitx5 and Rime enabled.
2. Open native Wayland Alacritty and run Herdr/Codex.
3. While tiled, type pinyin in the Codex input: the Fcitx5 candidate popup is visible.
4. Press Omarchy's default `SUPER+F` binding to enter true fullscreen.
5. Type pinyin again.

Expected: the candidate popup remains visible next to the preedit text.

Actual: the candidate popup is invisible, although composition and commit continue to work. Pressing the screenshot key temporarily reveals the popup.

#### Isolation

Failing state reported by `hyprctl -j activewindow`:

```json
{
  "class": "Alacritty",
  "fullscreen": 2,
  "fullscreenClient": 2,
  "xwayland": false
}
```

`render:direct_scanout` is disabled, so this does not appear to be direct scanout.

The candidate popup becomes visible immediately after switching away from internal fullscreen state 2. This locally verified workaround keeps the terminal close to fullscreen while still telling the client it is fullscreen:

```lua
hl.dsp.window.fullscreen_state({ internal = 1, client = 2 })
```

Omarchy's existing `SUPER+CTRL+F` “Tiled full screen” helper also avoids internal fullscreen state 2 by using `internal = 0, client = 2`.

#### Upstream status

This matches Hyprland issue #16010 exactly:

- https://github.com/hyprwm/Hyprland/issues/16010

That report was automatically closed by the issue-policy bot rather than fixed. It notes that Hyprland PR #15646 (`render IME above all desktop components`) does not cover the internal-fullscreen render path.

#### Why report this to Omarchy?

The underlying rendering bug is in Hyprland, but it is reproducible with Omarchy's shipped versions and default `SUPER+F` binding, while Fcitx5 is part of the supported Omarchy setup. Similar upstream IME regressions are already tracked in Omarchy issues #7346 and #7559.

Could Omarchy track this until the upstream fix lands and, in the meantime, consider documenting the `SUPER+CTRL+F` workaround or exposing an IME-safe maximized-fullscreen action (`internal = 1, client = 2`) for terminal users?

A full local `omarchy-debug --no-sudo --print` log and before/after screenshots are available if needed.