<leader>du has no which-key group — 6 DAP UI toggle keymaps are unlabelled and undiscoverable

[ooloth]

Current state

Six keymaps (<leader>dub, <leader>dur, <leader>dus, <leader>dut, <leader>duv, <leader>duw) are defined in lua/config/plugins/specs/nvim-dap.lua (lines 130–135) to toggle individual DAP UI panels. lua/config/plugins/specs/which-key.lua registers group labels for <leader>d, <leader>df, <leader>ds, and <leader>dv (lines 19–22) but not for <leader>du. When a user presses <leader>d in normal mode, the six <leader>du* bindings appear as a flat, unlabelled cluster with no group name indicating they form a cohesive "DAP UI panels" feature.

Ideal state

• Pressing <leader>d in normal mode shows a labelled subgroup entry for u (e.g. "UI panels" or "DAP UI").
• A user unfamiliar with the config can discover that <leader>du* controls DAP UI panel toggles by reading the which-key popup alone, without needing to search source files.

Out of scope

• Changing the keymaps themselves or what they toggle.

Starting points

• lua/config/plugins/specs/which-key.lua lines 19–22: existing group registrations for <leader>d, <leader>df, <leader>ds, <leader>dv
• lua/config/plugins/specs/nvim-dap.lua lines 130–135: the six <leader>du* keymaps

QA plan

1. Open Neovim and press <leader>d in normal mode.
2. Expect a which-key popup entry for u labelled something like "UI panels" or "DAP UI".
3. Press <leader>du and confirm the six panel-toggle keymaps appear with their individual descriptions.

Done when

<leader>du has a named group entry in which-key that a user can read to understand what the six <leader>du* keymaps do.