Proposal: feat(editor): command palette for v2 editor and run view

[mvanhorn]

Motivation

The v2 editor is an IDE: File/View/Runs/Windows/Node menus, dockable windows, and a KeyboardStore that already stores labeled shortcuts. Jumping to a task, invoking auto-layout, or opening the pipeline tree still takes a menu hunt. Dagster ships Cmd/Ctrl-K global search.

This repo already depends on cmdk and exports CommandDialog with default title "Command Palette" from src/components/ui/command.tsx, but nothing opens it. Cmd-K is free (open-pipeline is Ctrl-O; focus-mode is Cmd-Alt-slash; auto-layout is Cmd-Shift-L).

This is not component-search-v2 (library search), not LearnSearchBar, and not AI chat.

Proposed solution

Add a v2 Command Palette opened by Cmd-K / Ctrl-K (and a View menu item). Reuse CommandDialog. Groups:

1. Commands: every KeyboardStore shortcut (id plus label plus ShortcutBadge), invoking keyboard.invokeShortcut(id).
2. Windows: currently registered windows (open/focus).
3. Go to: tasks, graph inputs, and graph outputs from navigation.activeSpec, selecting the node and fitting the viewport.
4. Editor-only extras: Open, New pipeline, View YAML, Auto-layout — only if those shortcuts are registered. Do not duplicate handlers.

Behaviour notes:

• No new nav item and no new dockable window. Modal CommandDialog only.
• allowInEditable false so typing in argument editors is not stolen.
• Run view gets the same palette with run-view shortcuts and read-only graph tasks. Do not offer mutating editor commands there.
• No new feature flag. This is a View-menu command on shipped v2.

Out of scope: dashboard-wide pipeline/run search, AI chat from the palette, inserting a new component from the library, shortcut cheatsheet overlay.

Happy to open a draft PR if this shape looks right. Looking for maintainer signal before writing code.