In `smart` mode (the default for both `omarchy screenshot` and `omarchy capture screenrecording`), slurp is fed the monitor and window rectangles and highlights the one under the pointer. Click a window without dragging and you get the whole monitor instead of the window that was highlighted.

## Why

`omarchy-capture-region` treats a selection under 20px² as a bare click and snaps it to a rectangle itself:

```bash
while IFS= read -r rect; do
  ...
  if ((click_x >= rect_x && click_x < rect_x + rect_width && ...)); then
    SELECTION="${rect_x},${rect_y} ${rect_width}x${rect_height}"
    break
  fi
done <<<"$RECTS"
```

It takes the **first** containing rectangle. `$RECTS` comes from `get_rectangles()`, which prints `monitor_rects` before `window_rects`, and a monitor contains every click on it — so the loop always stops on the monitor and never reaches the windows behind it.

The rest of the file already knows the right rule. `resolve_rect_at()` picks the *smallest* containing rectangle, with the comment "slurp highlights the smallest box containing the point and keeps the first one on a tie, so overlapping rectangles resolve the same way here", and `geo_at_cursor()` deliberately tries `window_rects` before `monitor_rects` for the same reason. Only the click-snap path disagrees.

## Reproduce

Press the screenshot key, hover a window until slurp highlights it, and click without dragging. The saved PNG is the full monitor.

Same for `omarchy capture screenrecording` — the recording is started with `-w <monitor geometry>` rather than the window's.