### System details

- CPU: Intel Core i5-1145G7
- GPU: Intel Iris Xe Graphics (TigerLake-LP GT2)
- Omarchy: 4.0.0-1
- omarchy-settings: 4.0.0-1
- Hyprland: 0.56.2-1
- Stock Omarchy Alt+Tab bindings; no user override

### What's wrong?

With three or more windows open on one workspace, `Alt+Shift+Tab` alternates between only two windows instead of cycling backward through every window. `Alt+Tab` correctly cycles forward through all windows.

### Steps to reproduce

1. Open three tiled windows on one workspace.
2. Press `Alt+Tab` repeatedly: focus visits all three windows.
3. Press `Alt+Shift+Tab` repeatedly: focus alternates between two windows and never reaches the third.

Expected: `Alt+Shift+Tab` traverses the same window cycle as `Alt+Tab`, in reverse.

Actual: it toggles between two windows.

### Isolation / likely cause

The shipped binding defines two actions for each shortcut:

```lua
o.bind("ALT + TAB", "Focus on next window", hl.dsp.window.cycle_next())
o.bind("ALT + SHIFT + TAB", "Focus on previous window", hl.dsp.window.cycle_next({ next = false }))
o.bind("ALT + TAB", "Reveal active window on top", hl.dsp.window.bring_to_top())
o.bind("ALT + SHIFT + TAB", "Reveal active window on top", hl.dsp.window.bring_to_top())
```

Source: https://github.com/basecamp/omarchy/blob/945549699026df6c888a6b1bd4e06fbf55a67595/default/hypr/bindings/tiling.lua#L44-L47

I isolated the actions using Hyprland's Lua dispatcher:

- Repeating only `hl.dsp.window.cycle_next({ next = false })` cycles through all three windows correctly.
- Repeating reverse `cycle_next` followed by `bring_to_top()` reproduces the two-window loop.
- Forward `cycle_next()` followed by `bring_to_top()` still cycles through all three.

This suggests that raising the newly focused window changes the ordering used by the next reverse traversal, making it return to the former window. Removing the reverse shortcut's `bring_to_top()` action makes reverse cycling work, though floating-window stacking may need a different solution.