**Description**

The waybar update-checker script (`bin/omarchy-update-available`) permanently reports an update is available even when the local install is on the actual latest release tag.

**Root cause**

```bash
latest_tag=$(git ls-remote --tags origin | grep -v "{}" | awk '{print $2}' | sed 's#refs/tags/##' | sort -V | tail -n 1)
```

`sort -V` (GNU version sort) does not implement SemVer pre-release ordering. It ranks `v4.0.0-beta3` above `v4.0.0`, because it's comparing byte-wise rather than treating `-beta3` as a pre-release qualifier that should sort before its corresponding release.

**Reproduction**

```bash
$ git ls-remote --tags origin | grep -v "{}" | awk '{print $2}' | sed 's#refs/tags/##' | sort -V | tail -n 3
v3.8.4
v4.0.0
v4.0.0-beta3
```

With a fully up-to-date checkout on `v4.0.0`:

```bash
$ omarchy-update-available
Omarchy update available (v4.0.0-beta3)
```

This will affect every user on `v4.0.0` for as long as `v4.0.0-beta3` remains the lexically/version-sort-"highest" tag in the repo — the waybar icon and `omarchy-update` prompt never clear.

**Suggested fix**

Filter out pre-release tags before taking the max, e.g.:

```bash
latest_tag=$(git ls-remote --tags origin | grep -v "{}" | awk '{print $2}' | sed 's#refs/tags/##' | grep -vE -- '-[A-Za-z]' | sort -V | tail -n 1)
```

(or swap in a proper SemVer-aware comparator if pre-release tags need to be considered under different circumstances).

**Environment**
- Omarchy version: v4.0.0
- OS: Arch Linux