**What happened**
On a touchscreen device (Surface, Omarchy 4.0.4-1), tapping the screen while the screensaver is running does nothing. The screensaver stays up until a key is pressed.

**Expected**
Any input dismisses the screensaver. The comment in `omarchy-screensaver` says "Exit the screensaver on signals and input from keyboard and mouse", and touch is the only input on a tablet-style device.

**Cause (from reading the scripts)**
`/usr/bin/omarchy-screensaver` only exits in two cases:
```bash
if read -n1 -t 1 || ! screensaver_in_focus; then
  exit_screensaver
```
- `read -n1` only sees bytes on the terminal's tty, so only key presses reach it.
- Touch events go to the compositor and never reach the tty. The terminal doesn't forward them unless mouse reporting is on, and the script doesn't enable it.
- Pointer movement doesn't dismiss it either. The cursor is hidden and nothing in the script watches for it.
- The idle service (`shell/plugins/services/idle/Service.qml`) does notice activity through `idleMonitor`. But `handleActiveSignal()` ignores it while the screensaver window exists, so the screensaver is only closed by the script itself.

**Steps to reproduce**
1. Use a touchscreen device and let the idle timeout (150s) trigger the screensaver.
2. Tap or swipe the screen.
3. The screensaver stays up. Pressing a key dismisses it.

**Suggested fix**
Have the screensaver exit on any input, not just tty reads. Two options:
- Enable terminal mouse reporting (e.g. `printf '\033[?1000h'`) so `read` also sees taps and clicks.
- Or listen for the compositor's activity signal. `idleMonitor` already goes active on touch, so the idle service could close the screensaver window when that happens.

**Workaround I'm using**
A hyprgrass tap binding in `input.lua` that runs `pkill -f '[o]rg.omarchy.screensaver'`. It works, but it needs a plugin and shouldn't be necessary.

**System**
Omarchy 4.0.4-1, Linux 7.2.5-6-omarchy-surface.

Filed by Claude Sonnet 5.5 via Claude Code.