## Description

Desktop notifications from Microsoft Teams running as a Google Chrome PWA remain on screen indefinitely. Teams' notifications inside the browser dismiss normally, but the corresponding Omarchy desktop notification must be dismissed manually.

The persisted notification state shows Chrome sending routine Teams messages with:

```json
{
  \"app\": \"Google Chrome\",
  \"urgency\": 2,
  \"expireTimeout\": 0
}
```

Private notification content has been omitted.

Omarchy's notification service maps `NotificationUrgency.Critical` to a duration of `0`:

```qml
function durationFor(urgency, expireTimeout) {
  switch (urgency) {
  case NotificationUrgency.Critical:
    return 0
  // ...
  }
}
```

The popup timer only runs when `lifetime > 0`, so these routine Teams notifications never expire. The source already notes that chat apps can abuse critical urgency for DND handling, but critical urgency still produces an unlimited popup lifetime.

## Steps to reproduce

1. Install Microsoft Teams as a PWA in Google Chrome.
2. Allow Teams desktop notifications.
3. Receive a Teams chat notification.
4. Wait beyond the normal notification timeout.

## Expected behavior

A routine Teams/Chrome notification dismisses automatically after the normal popup duration. Genuine critical system alerts can remain persistent.

## Actual behavior

The desktop notification remains until manually dismissed. Right-click dismissal works.

## Suggested direction

Apply a finite popup lifetime to browser/chat notifications marked critical, while preserving persistent behavior for trusted critical system alerts. This could reuse or extend the existing sender-aware logic used for DND bypass decisions.

## System information

- Omarchy: 4.0.4-1
- Kernel: 7.2.5-3-omarchy
- Hyprland: 0.56.2
- Quickshell: 0.3.1-1
- Google Chrome: 154.0.8037.57-1
- Session: Wayland
- Hardware: Lenovo ThinkPad P1 Gen 5, Intel i7-12800H, Intel Iris Xe + NVIDIA RTX A1000

Diagnostics were gathered using `omarchy debug --no-sudo --print`. No relevant shell errors appeared; persisted notification state directly confirms the critical urgency and zero requested timeout.