CmdPal: list hover actions on list rows (design discussion)

Summary

Proposal: show a small set of quick-action icons when hovering or keyboard-selecting list rows in Command Palette, sourced from existing MoreCommands / context menu commands.

Related PR (implementation reference, may be revised after discussion): #48863

Problem / motivation

• Context menu works but adds steps: right-click → scan menu → click
• Frequent actions (edit, pin, delete, run as admin) are repeated often in extension lists
• Keyboard users currently need the context menu or shortcuts for secondary actions

Proposal (high level)

• Trailing hover strip on list rows (extension lists + optional home row quick actions)
• Same commands as context menu, not a parallel action system
• User master toggle in Settings → Appearance (EnableListHoverActions)
• Extension SDK controls: HoverActionsMode, ShowInHoverActions, HoverOrder, page/provider/home overrides
• Backward compatible: extensions that opt out behave as today (context menu only)

UX concerns to discuss

1. Fragmentation — does this compete with the existing context menu, or complement it as a fast path for 1–3 actions?
2. Defaults — should list hover actions be on or off by default for new installs?
3. Scope — extension list rows only vs. CmdPal home top-level extension rows?
4. Host commands — pin/dock/move are host-injected and excluded from hover unless explicitly flagged; is that the right boundary?

Demo

https://github.com/user-attachments/assets/737a46ed-aa93-463f-a0f8-0e855a461807

Open questions for maintainers

• Preferred process outcome: close/revise PR after consensus here, or keep PR open as draft while discussing?
• Any alternative UX the team prefers (e.g. context menu only, keyboard hints, secondary command chord only)?

/cc @michaeljolley @jiripolasek

No files or tests are named. Start by reviewing the existing MoreCommands/context-menu behavior and PR #48863, then follow the CmdPal list-row and extension SDK entry points referenced there. Done means the maintainers reach consensus on scope, defaults, and interaction design before implementation proceeds.