### System details

Laptop 13 (AMD Ryzen AI 300 Series) (A9)

### What's wrong?

On my system sometimes the screenshoot tool will show up but after taking a screenshoot nothing happened.

Running `omarchy-cmd-screenshoot` throws the following error:

```
Fatal error reading PNG image file: IDAT: CRC error (twice)
```

After some investigation I've found this issue with `hypershot` https://github.com/Gustash/Hyprshot/issues/106, apparently there is a problem `raw` is to slow.

I've updated the script command to use a tmp file:

```bash
#!/bin/bash

[[ -f ~/.config/user-dirs.dirs ]] && source ~/.config/user-dirs.dirs
OUTPUT_DIR="${OMARCHY_SCREENSHOT_DIR:-${XDG_PICTURES_DIR:-$HOME/Pictures}}"

if [[ ! -d "$OUTPUT_DIR" ]]; then
  notify-send "Screenshot directory does not exist: $OUTPUT_DIR" -u critical -t 3000
  exit 1
fi

pkill slurp

# Use temp file with proper wait for hyprshot to finish
TEMP_FILE="/tmp/omarchy-screenshot-$(date +'%Y-%m-%d_%H-%M-%S').png"
hyprshot -m ${1:-region} --freeze --silent -o /tmp -f "$(basename "$TEMP_FILE")"

# Wait for hyprshot to finish writing the file
while [[ ! -f "$TEMP_FILE" ]] || [[ $(stat -c%s "$TEMP_FILE" 2>/dev/null || echo 0) -eq 0 ]]; do
  sleep 0.1
done

# Additional small delay to ensure file is completely written
sleep 0.2

cat "$TEMP_FILE" | satty --filename - \
  --output-filename "$OUTPUT_DIR/screenshot-$(date +'%Y-%m-%d_%H-%M-%S').png" \
  --early-exit \
  --actions-on-enter save-to-clipboard \
  --save-after-copy \
  --copy-command 'wl-copy' &&
  rm "$TEMP_FILE"
```

Is someone else experiencing this issue? Shall I open a pr with this fix?