### Summary

`omarchy-hw-laptop`'s DMI chassis fallback can never match, because the command substitution it tests always expands to the empty string.

### The bug

`bin/omarchy-hw-laptop`:

```bash
case $(< /sys/class/dmi/id/chassis_type 2>/dev/null) in
8 | 9 | 10 | 14 | 30 | 31 | 32) exit 0 ;;
esac
```

Bash's `$(< file)` fast path applies **only** when the substitution contains nothing but the redirect. Adding `2>/dev/null` turns it into a null command with two redirections, which produces no output at all:

```console
$ echo "[$(< /sys/class/dmi/id/chassis_type)]"
[9]
$ echo "[$(< /sys/class/dmi/id/chassis_type 2>/dev/null)]"
[]
```

So the `case` never matches and the fallback always falls through to `exit 1`.

### Impact

The fallback exists for "laptops that don't expose an ACPI lid button", and it never works for them. On a machine with no `/proc/acpi` at all (any aarch64 machine — this was found on an Apple Silicon MacBook under Asahi), the first probe finds nothing and the fallback silently fails, so `omarchy-hw-laptop` reports "not a laptop" on hardware whose `chassis_type` is `9` and whose `hostnamectl chassis` is `laptop`.

`bin/omarchy-hyprland-monitor-watch` gates its clamshell reconciliation poll on this helper:

```bash
if omarchy-hw-laptop && omarchy-hyprland-monitor-external-active; then
```

so the backstop that recovers clamshell state (e.g. across suspend/resume) never starts on affected hardware.

### Suggested fix

Drop the redirect, or use a form that keeps working with it:

```bash
case $(cat /sys/class/dmi/id/chassis_type 2>/dev/null) in
```

`$(< file)` on a missing file is already silent under `set +e`, so the redirect was not buying anything.

Worth a grep for the same pattern elsewhere in the tree.

### Environment

- Omarchy 4.0.2-mac.1 (`omarchy-dev 4.0.2.r6875.g2afd2ef-1`, built from github.com/maralcbr/omarchy-mx-mac)
- MacBookPro18,3, Asahi, kernel 7.1.6-1-1-ARCH aarch64
- The bash behaviour itself is not platform-specific.

### Related

#8418 reports that Asahi lid handling can never fire (wrong switch name, and `/proc/acpi` absent). This is a third, independent reason clamshell stays broken on that hardware, and unlike the other two it is not Apple-specific: it disables the `omarchy-hyprland-monitor-watch` reconciliation poll, which is the backstop that would otherwise recover clamshell state on its own.