## Environment
- Omarchy `quattro`
- ThinkPad X1 Carbon (2013), i5-3317U (Ivy Bridge), HD Graphics 4000

## Problem
`install/hardware/intel/video-acceleration.sh` classifies Intel GPUs by lspci name:

```bash
if [[ ${INTEL_GPU,,} =~ (hd\ graphics|uhd\ graphics|xe|iris|arc|panther\ lake) ]]; then
  omarchy-pkg-add intel-media-driver libvpl vpl-gpu-rt   # Broadwell+
elif [[ ${INTEL_GPU,,} =~ "gma" ]]; then
  omarchy-pkg-add libva-intel-driver                        # Sandy/Ivy Bridge
fi
```

HD 4000 lspci name:
```
00:02.0 VGA compatible controller: Intel Corporation Ivy Bridge mobile GT2 [HD Graphics 4000] (rev 09)
```
Contains `hd graphics` → matches **first branch** → installs **`intel-media-driver`**.

But per Intel VAAPI docs, Ivy Bridge decode uses **`libva-intel-driver`** (i965_drv_video.so); **`intel-media-driver` (iHD) only supports Broadwell+** (Gen8+), not Ivy Bridge.

## Expected
HD 4000 should route to `libva-intel-driver`.

## Fix
Classify by GPU generation, not name substring:

| Generation | Driver |
|---|---|
| Gen4–7 (GMA/Sandy/Ivy/Haswell) | `libva-intel-driver` |
| Gen8+ (Broadwell+) | `intel-media-driver` |

Or match via Device ID (`8086:0162`). The regex can't distinguish Ivy Bridge "HD Graphics 4000" from Broadwell "HD Graphics 5500".

## Impact
Gen5–7 iGPU installs get the wrong driver → hardware video decode fails (drops frames/CPU). Desktop unaffected — Hyprland uses i915+Mesa, not VA-API.

## Relation
Distinct from #2706 (screen recording VAAPI init failure on **hybrid** Intel+NVIDIA) and #4901. Those are runtime missing-driver/messaging on hybrid GPUs; this is an **install-time misclassification on a pure Intel Ivy Bridge** machine, which runtime detection can't fix.