docs: #127 CLOSED — the brick was hypridle eating its own resume path

The incident was misdated: it did not happen before 12:51:34 Jul 15
(that boot was healthy all day) — it ended the previous boot at 10:54:22
with the power button. In that boot, running the pre-fix generation:
idle cascade on schedule (lock 10:21, dpms off 10:26, suspend correctly
skipped on AC), then hypridle logs "BUG THIS: inhibit locks < 0: -1" at
10:36:29 and its rule state is corrupted from there — the fired DPMS
listener's on-resume, then the session's ONLY dpms-on caller, never
dispatches again despite provable real input (two blind hyprlock PAM
attempts) and three output remove/re-add cycles. The wedged-compositor/
DRM-master lead is contradicted: Hyprland tracked hotplug live through
the whole window, PAM worked, kernel spotless. The shipped fix (a2151f4,
input wakes DPMS compositor-side) closes exactly this mechanism.

Filed upstream with the full trace: hyprwm/hypridle#208 (0.1.7; their
closed #104/#128 are the same class). Watch folded into #146.

Sweep: BACKLOG #127 deleted (NOW keeps only the install-findings context
stub, flagged to Bernardo); ROADMAP gains "The idle brick's CAUSE found"
and both stale "cause still open" tails patched; checked-off #127
HARDWARE-QUEUE blocks pruned, their method lessons moved to MEMORY
§ Gotchas.

Verification: V0 (docs/backlog only). The evidence is journal forensics
on the incident hardware (two Sonnet passes, verdict on Fable), quoted
in the ROADMAP entry; the fix itself was V3-proven 2026-07-16.

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

agent/JOURNAL.md

@@ -19,6 +19,27 @@ Template:
 
 ---
 
+## 2026-07-17 — #127 CLOSED: the brick was hypridle eating its own resume path
+- **Task:** BACKLOG #127 (NOW). Two Sonnet forensics passes over the machine's
+  journal; interpretation, verdict and close-out here. Bernardo ruled: close +
+  file upstream.
+- **Did:** found the incident was misdated — it ended the Jul 15 **10:54:22**
+  boot via power button (unclean end), not the healthy 12:51 boot every prior
+  timeline used. In that boot: `dpms off` 10:26; hypridle logs `BUG THIS:
+  inhibit locks < 0: -1` at 10:36:29; from then the fired DPMS listener's
+  `on-resume` never dispatches again despite provable input (blind PAM
+  attempts) — and it was the session's only `dpms on` caller (pre-fix gen).
+  Compositor provably alive throughout → the DRM-wedge lead is dead. Filed
+  upstream (hypridle 0.1.7, trace attached); watch folded into #146. BACKLOG
+  entry deleted; ROADMAP gained "The idle brick's CAUSE found" and its two
+  stale "cause still open" tails were patched; [x] #127 HW-queue blocks
+  pruned (method lessons moved to MEMORY §Gotchas).
+- **Verified:** V0 (docs/backlog); the *evidence* is journal forensics on the
+  incident hardware, quoted in ROADMAP. The fix itself was V3-proven 07-16.
+- **Pending:** upstream issue is a watch (#146). NOW is empty except the
+  install-findings context stub — flagged to Bernardo.
+- **Next suggestion:** #134 (NEXT, decided shape) is the queue head.
+
 ## 2026-07-17 — Hardware hints: the second (and last) first-session toast
 - **Task:** PROPOSED "Post-install hardware hints" (VISION § B), promoted by
   Bernardo in-session.