### System details

ASUS ExpertBook B9406CAA, Intel Core Ultra X7 358H, FocalTech fingerprint reader (`2808:a97a`), Omarchy 4.0.4-1, libfprint-git 1.94.100.r10, fprintd 1.94.5

### What's wrong?

The FocalTech fingerprint reader on this laptop has two separate problems.

## 1. Reader is not detected by `omarchy-hw-fingerprint`

**Symptom**
`omarchy-setup-security-fingerprint` exits with `No fingerprint sensor detected.`, and the post-update fingerprint setup notification never appears.

**Finding**
```
Bus 003 Device 004: ID 2808:a97a Focal FocalTech FT9349 ESS
```
libfprint-git and fprintd drive the reader fine. `fprintd-list` reports it as "Focaltech MOC Sensors (press)", and enrolling and verifying both work. No kernel driver is bound to its interface. The detection misses it for two reasons:
- Vendor `2808` (FocalTech) is not in `fingerprint_vendors`.
- The product string `FocalTech FT9349 ESS` contains neither "fingerprint" nor "biometric".

**Suggested fix**
Add `2808` to `fingerprint_vendors` in `omarchy-hw-fingerprint`. The existing `has_kernel_driver` check still keeps FocalTech touchscreens and touchpads (which bind usbhid) from matching.

**Workaround**
Put a stub `omarchy-hw-fingerprint` that exits 0 first on `PATH`, then run `omarchy-setup-security-fingerprint`.

## 2. Lock screen fingerprint unlock fails after resume from suspend

**Symptom**
After waking from suspend (s2idle), the lock screen doesn't accept the fingerprint. Only the password works.

**Finding**
The lock screen starts `pam_fprintd` verification before suspend, and the suspend interrupts it:
```
fprintd: Device reported an error during verify: Cannot run while suspended.
quickshell: pam_fprintd(omarchy-lock-fingerprint:auth): ReleaseDevice failed: Release failed with error: The device is still busy with another operation, please try again later.
```
After resume, fprintd is still stuck on that claim. The 250ms `fingerprintRetryTimer` in `plugins/lock/Service.qml` keeps re-arming PAM, and every attempt fails right away:
```
quickshell.service.pam.subprocess: Error while authenticating: "Authentication service cannot retrieve authentication info" (code 9)
```
In one case this went on for about 15 seconds (~55 attempts) until I unlocked with my password.

**Suggested fix**
Either of these should work:
- Ship a systemd sleep hook that restarts fprintd around suspend (shown below), or
- Have the lock screen abort the fingerprint `PamContext` before suspend (e.g. on logind `PrepareForSleep`) and re-arm it after resume.

**Workaround (tested, works)**
`/usr/lib/systemd/system-sleep/fprintd-resume`:
```sh
#!/bin/sh
case "$1" in
  pre)  systemctl stop fprintd.service ;;
  post) systemctl restart fprintd.service ;;
esac
```
With this hook in place, the first PAM attempt after resume still fails with code 9 while fprintd restarts. The next retry succeeds, and fingerprint unlock works about 1 second after resume.