fix(docking): the undock keyword is inert, not raced; escalate to reload

Round 7 FAILED: 5-6 consecutive unplugs on the dev box, the panel never came
back. Round 6's retry could not have worked, because round 6's diagnosis was
wrong — and so was the "phantom re-add" theory I brought to this session.

With ZERO enabled outputs — panel disabled by the dock, external gone —
Hyprland 0.55.4 accepts `hyprctl keyword monitor eDP-1,preferred,auto,1`,
prints `ok`, exits 0, and never flushes it: the rule waits for a DRM event
that is not coming. It is inert, not raced. Retrying it 25x/poll for 6 polls
bought 30s of black screen and nothing else.

What made this survive two rounds is worth more than the fix: every
`transition=undock result=ok` in the round-6 journal was Bernardo plugging
the cable back in because the screen was black. His hotplug flushed the
queued rule and the next poll took the credit. Success was indistinguishable
from the user working around the failure, so the logs confirmed whichever
story we brought to them. Ten minutes of probing on hardware killed both.

Probed live 2026-07-14 (dev box, cable out): keyword inert across 4s and 5s
in two runs; `dispatch forcerendererreload` inert too; only `hyprctl reload`
escapes — 99ms and 289ms. So: issue the keyword (enough whenever another
output is still enabled, e.g. the menu's Dock mode), and escalate to reload
only when `monitors` proves it inert. After a reload, re-assert the rule so a
config that parks the panel off cannot undo the undock, and restore per-device
keyboard layouts — a reload re-reads the config and drops the runtime
`device[<name>]:kb_layout` an external board depends on. The menu's `enable`
now proves itself against `monitors` too, instead of cheering for an exit code.

Verified V3 (partial): the fixed transition driven through a real unplug —
panel on, workspaces 1-3 home, 1.8s, `keyword=inert escalate=reload` ->
`enable=via-reload` -> `result=ok`. V2: nix flake check --no-build; docking-ux
+ dock-audio; monitor-fallback.nix; shellcheck clean on display-transition.

NOT proven, and queued as HARDWARE-QUEUE round 8: the watcher-driven path
(exec-once + baked store path = relogin required, the round-5 trap) and
repetition. The keyboard-restore path is untested — the dev box's keyboard
hangs off the dock's hub, so it leaves with the cable; round 8 adds a check
with a keyboard in the laptop. The VM harness still cannot reach any of this:
QEMU aborts Hyprland if the last active output is deleted while the DRM output
is disabled, which is the same zero-output degeneracy from the other side.

New BACKLOG #114 (PROPOSED): tuigreet ignores per-device keyboard layouts —
a VT has one keymap, so the greeter cannot honour `device[]:kb_layout`.
Bernardo hit it logging out while docked; not a regression, a design gap.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

agent/BACKLOG.md

@@ -222,6 +222,26 @@ high-ROI, etc.) live in the journal + ROADMAP — not here.*
 
 ### Product / day-2
 
+### 114. Greeter ignores per-device keyboard layouts
+
+Found by Bernardo 2026-07-14: logging out while docked lands on tuigreet,
+where his external keyboard (remembered as `us` via
+`settings.keyboard.devices`) types the session layout `gb` — so the password
+prompt fights him. Not a regression and not docking-related: per-device
+layouts are applied with `hyprctl keyword device[<name>]:kb_layout`, which
+only exists inside a running Hyprland session, while tuigreet draws on a
+kernel VT whose single keymap comes from `console.useXkbConfig` ←
+`services.xserver.xkb.layout`. A VT structurally cannot do per-device
+layouts, so this is a design gap, not a bug to patch. Options, cheapest
+first: (a) document it and stop there; (b) a greeter layout-cycle key
+(tuigreet has no such feature — would need the keymap swapped under it);
+(c) host tuigreet inside a small Wayland compositor (cage/labwc), which
+*does* get per-device XKB and would let the greeter honour the same
+in-flake state the session uses — real work, and it changes the greeter's
+whole rendering path (`modules/nixos/greeter.nix` themes tuigreet through
+the 16 ANSI console slots, so (c) is not a drop-in). Worth deciding whether
+the greeter is meant to be layout-aware at all before costing it.
+
 - **NVIDIA first-class options** — **deferred past v1** (Bernardo
   2026-07-10). Keep #59 commented install guidance; no
   `nomarchy.hardware.nvidia.*` until a hybrid maintainer + queue.