## Description

`omarchy toggle bar on` hides the bar and `omarchy toggle bar off` shows it. The arguments are inverted.

`omarchy-toggle-bar` passes its argument straight to the `bar-off` flag:

```bash
omarchy-toggle bar-off "${1:-toggle}"
```

In `omarchy-toggle`, `on` creates the flag and `off` removes it. Because the flag is named `bar-off`, `on` creates `bar-off` (hiding the bar) and `off` removes it (showing the bar). The plain `toggle` action works correctly. Only the explicit `on`/`off` arguments, which the script's own `omarchy:args` and `omarchy:examples` advertise, have the wrong meaning.

## Steps to reproduce

1. With the bar visible, run `omarchy toggle bar on`.
2. The bar slides off screen and `~/.local/state/omarchy/toggles/bar-off` is created.
3. Run `omarchy toggle bar off`.
4. The bar comes back and the flag is removed.

**Expected:** `on` shows the bar and `off` hides it.

This makes recovery confusing: if the bar gets hidden and the user runs `omarchy toggle bar on` to bring it back, the bar stays hidden. It also looks like the "stranded off screen" problem described in the script comment, so restarting the shell seems like the fix, but that doesn't help either because the flag is still set.

## Suggested fix

Invert the explicit arguments before passing them to the flag:

```bash
case "${1:-toggle}" in
  on) action=off ;;
  off) action=on ;;
  *) action="${1:-toggle}" ;;
esac

omarchy-toggle bar-off "$action"
```

## System

- Omarchy 4.0.4-1
- Hyprland, 3 monitors (eDP-2 plus 2 DP outputs)