On a machine with both `brave-bin` and `brave-origin-bin` installed and only brave-origin running, `omarchy theme set <name>` never returns. Every theme change hangs — the menu, `omarchy theme set`, and anything scripted on top of them.

## Cause

`bin/omarchy-theme-set-browser`:

```bash
refresh_running_browser() {
  local process="$1"
  local command="$2"
  local pgrep_args="${3:--x}"

  if omarchy-cmd-present "$command" && pgrep $pgrep_args "$process" >/dev/null; then
    "$command" --refresh-platform-policy --no-startup-window &>/dev/null
  fi
}
...
refresh_running_browser brave brave
# Match on the binary path: the running process is named plain "brave", and a
# bare -f brave-origin pattern would also match the installer's own terminal.
refresh_running_browser /opt/brave-origin-bin/ brave-origin -f
```

`refresh_running_browser brave brave` gates on `pgrep -x brave`. Both packages install a binary named `brave` (`/opt/brave-bin/brave` and `/opt/brave-origin-bin/brave`), so that match fires on brave-origin's processes. `omarchy-cmd-present brave` is also true, so the guard passes and the script runs `/opt/brave-bin/brave --refresh-platform-policy --no-startup-window`.

With no brave-bin instance to hand the message to, that does not ping-and-exit — it cold-starts a full windowless browser that never exits. The call is not backgrounded and has no timeout, so `omarchy-theme-set-browser` blocks on it indefinitely, and `omarchy-theme-set` waits on it via `run_parallel`.

The comment directly below notes this same binary-name collision; the path-specific fix was applied only to the `brave-origin` line.

## Reproduce

1. Install both `brave-bin` and `brave-origin-bin`.
2. Run brave-origin. Do not run brave-bin.
3. `omarchy theme set nord` — never returns.

Observed process tree:

```
omarchy-theme-set nord            do_wait
  omarchy-theme-set-browser       do_wait
    /opt/brave-bin/brave --refresh-platform-policy --no-startup-window   <- never exits
```

## Evidence

```
$ pgrep -cx brave
18
$ for p in $(pgrep -x brave); do readlink /proc/$p/exe; done | sort -u
/opt/brave-origin-bin/brave
```

All 18 matches are brave-origin; not one brave-bin process is running, yet the `brave` branch fires.

Verified on omarchy 4.0.3 (`brave-bin 1:1.94.121-1`, `brave-origin-bin 1:1.94.121-1`, Arch, Hyprland). The code is unchanged on `quattro` @ 8ea51516. Uninstalling `brave-bin` resolves it, which confirms the branch is the trigger.

## Suggested fix

Make the check path-specific, matching what the `brave-origin` line already does, and bound the refresh so a future mis-detect degrades instead of hanging:

```diff
-refresh_running_browser brave brave
+refresh_running_browser /opt/brave-bin/ brave -f
```

```diff
-    "$command" --refresh-platform-policy --no-startup-window &>/dev/null
+    timeout 10 "$command" --refresh-platform-policy --no-startup-window &>/dev/null
```

The timeout matters independently of the pgrep fix: any browser in this list that fails to hand off will wedge every theme change on the system with no error surfaced.