# Test run — vX.Y.Z

- **Date:** YYYY-MM-DD
- **ISO:** `veilor-os-43-YYYYMMDD-HHMMSS.iso` (sha256: `...`)
- **Tester:** name / handle
- **Environment:** VM (qemu/q35/ovmf, 4 vCPU, 4G RAM, virtio-vga) — OR — Real HW (model, CPU, GPU)

---

## Result

✅ Pass / ⚠️ Pass-with-issues / ❌ Fail

One-line summary.

---

## Regressions vs previous run

(Things that worked in the prior tagged release but failed here. Empty
if none. Always check this section first when reading the report.)

---

## Per-step results

Walk `test/TESTING.md` step-by-step. Mark each pass/fail with a brief
note when failed.

| # | Step | Result | Notes |
|---|------|--------|-------|
| 1 | Live boot to installer banner | ✅ |  |
| 2 | Installer menu render | ✅ |  |
| 3 | Disk picker | ✅ |  |
| 4 | LUKS + admin passwords | ✅ |  |
| 5 | Locale | ✅ |  |
| 6 | Confirm | ✅ |  |
| 7 | Anaconda transaction | ✅ |  |
| 8 | Reboot | ✅ |  |
| 9 | GRUB single veilor-os entry | ✅ |  |
| 10 | LUKS unlock prompt | ✅ |  |
| 11 | First boot → SDDM → KDE | ✅ |  |
| 12 | Hardening checks | ✅ |  |

---

## Hardening verification

```
$ getenforce
Enforcing
$ systemctl is-active fail2ban usbguard tuned auditd firewalld
active
active
active
active
active
$ cat /proc/cmdline
... rd.luks.uuid=luks-... ...
$ lsblk -f
...
```

Paste real output. If any service is inactive or any cmdline arg is
missing, raise as a Regression above.

---

## Findings

Free-form notes. Cosmetic glitches, slow paths, surprising behaviour.

---

## Action items for next release

- [ ] ...
- [ ] ...

(Linked PRs / commits if you opened any during the test.)