docs(agent): close #76 — hibernate→resume V3 PASSED on TuringMachine

Bernardo ran the real power-cycle on the T14s (LUKS + btrfs @swap
swapfile): hibernate → power off → single LUKS unlock → session
restored. BACKLOG #76 deleted; HARDWARE-QUEUE resume entry pruned
(outcome recorded in the remaining no-swap-notify entry, JOURNAL, and
the ROADMAP ✓-entry); Decisions hibernation note marked shipped. The
no-swap Hibernate notify check remains the one open leftover.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

agent/HARDWARE-QUEUE.md

@@ -216,27 +216,11 @@ the **T14s** (webcam case).
       screenshot loaded. Check that the UI draws on the current theme palette
       (tools colored properly) and hitting save places the screenshot in
       `~/Pictures/Screenshots/` while hitting copy places it in the clipboard.
-- [ ] **#76 hibernate→resume on a real Nomarchy install** — the V2 VM test
-      proves the resume mechanism + zram coexistence, but QEMU can't feed a
-      boot-time `resume_offset` for a btrfs *swapfile* nor drive the LUKS
-      initrd unlock, so this triple needs hardware. **The dev box qualifies
-      since 2026-07-11**: TuringMachine (T14s) migrated to Nomarchy per
-      docs/MIGRATION.md — it now exercises Nomarchy's oom.nix/rofi wiring,
-      not just the layout.
-      1. ✓ Confirm the wiring on the Nomarchy box: `swapon --show` lists
-         `/swap/swapfile` (Type file) **and** `/dev/zram0` at priority 100;
-         `cat /proc/cmdline` shows `resume_offset=…` + `resume=` the btrfs UUID.
-         (**Verified on TuringMachine 2026-07-11**: swapfile 34G file-type,
-         zram0 prio 100, `resume_offset=533760`.)
-      2. Open apps, note an unsaved in-RAM state. `nomarchy-menu → Power →
-         Hibernate` (or `systemctl hibernate`). Machine writes image, **powers
-         off**.
-      3. Power on: unlock LUKS **once** in the themed prompt; land back in the
-         **same session** — state restored, not a fresh login.
-      4. **Pass** = session restored after full power-off + single unlock.
-         Fail (fresh boot / stuck initrd) → NOW bug in BACKLOG (capture
-         `journalctl -b -1 | grep -i -E 'hibernat|resume|swap'`).
-- [ ] **#76 no-swap Hibernate notify** — on a **Nomarchy** machine installed
+- [ ] **#76 no-swap Hibernate notify** (#76 itself is closed — the
+      hibernate→resume power-cycle **PASSED on TuringMachine 2026-07-12**:
+      Bernardo ran the full hibernate → power off → single LUKS unlock →
+      session-restored cycle "flawlessly"; this notify check is the one
+      remaining leftover) — on a **Nomarchy** machine installed
       with `swap = 0` (or temporarily `sudo swapoff -a` on one): `nomarchy-menu
       → Power → Hibernate` must surface a desktop notification ("Couldn't
       hibernate — likely no swap is configured. See docs/MIGRATION.md →