docs(tech): add post-firmware benchmark and complete GXA7801Q update docs

- Post-update fio benchmark: random read +12.4%, write +15.9% IOPS
- Latency reduced 10-14% for random workloads
- SMART health unchanged: 0 media errors, 0 error log entries
- Firmware research status updated to complete
- Pre-benchmark checklist marked done

docs/tech/firmware-update-research.md

@@ -51,7 +51,7 @@ last_updated: '2026-04-02'
 | **Latest** | **GXA7801Q** (non-SED, `00B00`) |
 | Source | [GitHub: samsung-nvme-firmware](https://github.com/lolyinseo/samsung-nvme-firmware) |
 
-**Status**: **Update applied 2026-04-02.** GXA7801Q is the correct firmware for non-SED PM9A1 drives (model `00B00`). Reboot pending to activate.
+**Status**: **Complete 2026-04-02.** GXA7801Q is the correct firmware for non-SED PM9A1 drives (model `00B00`). Activated and verified. See `nvme-benchmark-post-gxa7801q.md` for before/after comparison.
 
 > **Important**: GXA7802Q is for SED drives (model `00B07`) only. Our non-SED drive (MZVL2512HCJQ-**00B00**) requires GXA7801Q.
 > The OVHCloud mirror only hosts GXA7802Q, which was rejected as "Invalid Firmware Image".
@@ -101,7 +101,7 @@ sudo reboot
 nvme list
 ```
 
-**Update applied**: 2026-04-02 10:51 CET. All three nvme-cli steps succeeded. Reboot pending.
+**Update applied**: 2026-04-02 10:51 CET. All three nvme-cli steps succeeded. Reboot completed, GXA7801Q verified active. Random IOPS improved +12-16% post-update.
 
 **Firmware file**: SHA256 `76ad2b0c35581cb71bd4c5a5fd358a15c4432aa38e9e983acc2349d2b24b5a11`
 
@@ -251,7 +251,7 @@ fwupdmgr update           # Apply available updates
 
 | # | Action | Risk | Downtime |
 |---|--------|------|----------|
-| 4 | ~~Update NVMe firmware to GXA7801Q~~ | ~~Medium (power loss risk)~~ | **Applied 2026-04-02, reboot pending** |
+| 4 | ~~Update NVMe firmware to GXA7801Q~~ | ~~Medium (power loss risk)~~ | **Complete 2026-04-02. GXA7801Q active. +12-16% random IOPS.** |
 
 ### No Action Needed