### What happens

Clicking a toast notification from **Telegram Desktop** (running) dismisses the toast but never focuses/raises Telegram's window. Nothing visible happens. The same flow works for e.g. WhatsApp Web (notifications sent by Chrome).

### Why — two independent defects

**1. A registered `default` action is trusted blindly and skips the focus fallback.**

In `shell/plugins/notifications/Service.qml`, `invokePopupDefault()` invokes the notification's `"default"` action when the app registers one, and then only runs `if (!invoked) focusApp(entry)`. Telegram Desktop registers a `default` ("Open") action but does **not** raise its window when it receives `ActionInvoked` on Linux — so the click visibly does nothing.

**2. The focus fallback fails when appName differs from the window class.**

`focusApp()` passes only `entry.app` to `bin/omarchy-hyprland-focus-app`, which substring-matches the app name against the Hyprland window class. Telegram sends appName `"Telegram Desktop"` while its window class is `org.telegram.desktop` — the space makes the match fail and the helper exits 1 silently. `entry.appIcon` (which equals the class here) is never tried.

Chrome-sent notifications (WhatsApp Web) work only because appName `Chrome` happens to substring-match class `chrome-web.whatsapp.com__-Default`.

### Evidence

`dbus-monitor` while clicking a real Telegram toast:

```
Notify(...) actions: ["default", "Open", "mail-mark-read", "Mark as read"]
ActionInvoked(id=10, "default")     <- shell invokes it
NotificationClosed(id=10, 2)        <- toast dismissed, window never raised
```

### Deterministic reproduction

No mouse needed (`omarchy-shell notifications invokeLast` runs the same code path as clicking the toast); watch focus with `hyprctl activewindow -j | jq -r .class`:

```bash
N() { gdbus call --session --dest org.freedesktop.Notifications \
  --object-path /org/freedesktop/Notifications \
  --method org.freedesktop.Notifications.Notify "$@" ; }

# A: Telegram-like — appName "Telegram Desktop", app_icon set, default action that nobody handles
N "Telegram Desktop" 0 "org.telegram.desktop" "Repro A" "body" "['default','Open']" {} 0
omarchy-shell notifications invokeLast          # -> focus unchanged

# B: no default action, appName != window class
N "Telegram Desktop" 0 "org.telegram.desktop" "Repro B" "body" [] {} 0
omarchy-shell notifications invokeLast          # -> focus unchanged

# C: appName == window class -> works
N "org.telegram.desktop" 0 "org.telegram.desktop" "Repro C" "body" [] {} 0
omarchy-shell notifications invokeLast          # -> Telegram focused
```

### Validated fix (tested locally by cloning the plugin)

- In `invokePopupDefault()`: still invoke the `default` action when present (it may do useful side work), but **always** call `focusApp(entry)` — a toast click must always jump to the app.
- In `focusApp()`: try `entry.appIcon` as a first match candidate (it is typically the desktop-file id and usually equals the window class), then fall back to `entry.app`:

```qml
function focusApp(entry) {
  if (!entry) return
  var candidates = []
  if (entry.appIcon && String(entry.appIcon).length > 0) candidates.push(String(entry.appIcon))
  if (entry.app && String(entry.app).length > 0) candidates.push(String(entry.app))
  // run the helper once per candidate until one matches (exit 0)
}
```

With this patch, clicking real Telegram toasts focuses the Telegram window reliably (verified against live notifications).

### Minor related

Clicking entries in the notification **history** panel never opens/focuses the app — only live toasts are wired. Fine if intentional, but worth a look.

### System

Omarchy 4.0.3-1 · Hyprland 0.56.2 · kernel 7.2.3-arch1-3 · AMD Ryzen 7 5700U (Lucienne iGPU).
The relevant code on current `master` (`bin/omarchy-hyprland-focus-app`, `shell/plugins/notifications/Service.qml`) matches the packaged 4.0.3.

Happy to submit a PR if the approach sounds good.