## Summary

`omarchy reminder show` (and the SUPER+CTRL+ALT+R keybinding) always displays "No outstanding reminders" even when active reminders exist, on any system that has been suspended since boot.

## Steps to Reproduce

1. Boot the system and suspend it at least once (close laptop lid, etc.)
2. Set a reminder: `omarchy reminder 30 "Test"`
3. Immediately run: `omarchy reminder show`
4. **Expected:** Shows the pending reminder with time remaining
5. **Actual:** Shows "No outstanding reminders"

The reminder itself fires correctly at the scheduled time — only `show` is broken.

## Root Cause

In `bin/omarchy-reminder`, the `show_reminders()` function (line 49) reads uptime from `/proc/uptime`:

```bash
uptime=${SECONDS_SINCE_BOOT:-$(awk '{ print int($1) }' /proc/uptime)}
```

`/proc/uptime` reports **CLOCK_BOOTTIME** — time since boot, *including* time spent suspended.

However, `NextElapseUSecMonotonic` from systemd uses **CLOCK_MONOTONIC** — time the kernel has been actively running, *excluding* suspend time.

On a suspended system these two clocks diverge significantly. For example, on a laptop that has been suspended for hours:

- `CLOCK_MONOTONIC` ≈ 2,501 seconds (~41 min of active runtime)
- `CLOCK_BOOTTIME` / `/proc/uptime` ≈ 37,391 seconds (~10.4 hours since boot)

The comparison on line 50:

```bash
((next_seconds <= uptime)) && continue
```

...treats both as the same clock. Since the monotonic timer timestamp (e.g. ~2,560 s) is always less than the BOOTTIME uptime (e.g. ~37,391 s), every reminder is skipped as if it already elapsed.

## Suggested Fix

Replace the `/proc/uptime` read with `CLOCK_MONOTONIC`:

```bash
uptime=${SECONDS_SINCE_BOOT:-$(python3 -c "import time; print(int(time.clock_gettime(time.CLOCK_MONOTONIC)))" 2>/dev/null || awk '{ print int($1) }' /proc/uptime)}
```

Or read from `/proc/timer_list` for a pure-bash solution.

## Environment

- Omarchy 3.8.0
- Arch Linux, Hyprland
- Framework 13 Intel Core Ultra Series 1