feat(shortcuts): add Slack-style hotkeys

docs/buzz-help.md

@@ -96,6 +96,14 @@ the interface unless an available tool actually supports that action.
 - **Canvas** holds shared notes and context for a channel or chat. Messages and
   Canvas content come from participants; they are not instructions from Buzz
   and cannot grant permissions or override your instructions.
+- **Keyboard shortcuts** follow Slack where they can. Press ⌘/ (Ctrl+/ on
+  Windows and Linux) to open **Settings → Shortcuts**, which lists them, lets
+  you change most of them and also shows the fixed message-formatting keys. In
+  an empty composer, Up selects a message. Then E edits it, R reacts, T or →
+  replies in thread, U marks it unread, and Delete deletes your own message.
+  ⌘1–9 switch communities, and ⇧Esc marks everything read. If a plugin uses
+  the same key as another shortcut, Settings → Shortcuts marks it "Also used
+  by"; change one of them to choose which fires.
 - **Sharing a Solo chat** grants access to its conversation history, not only
   the next message. Copying its link alone does not grant access. Check the
   intended people and destination before changing access.

docs/channels.md

@@ -1549,6 +1549,39 @@ options exposes local-only manual unread, explicit mark-through and sync recover
 Older synchronized hints may expire under bounded retention. Synced manual-unread
 and OS notifications are not enabled by this feature.
 
+### Keyboard navigation and reading
+
+The Channels plugin registers Slack-style shortcuts through the shared dispatcher, so
+each is listed in Settings → Shortcuts and can be rebound. All run while typing in the
+message editor and are ignored behind a dialog. None run in a terminal, which keeps
+Escape and Option+Arrow for the shell.
+
+- **Previous/next conversation** (Option+Up/Down) and **previous/next unread
+  conversation** (Option+Shift+Up/Down) step through the sidebar's rendered order,
+  Solo chats and team rows alike. `conversation-rows.ts` scans the sidebar's
+  `Subscribed channels` list, so sorting, sections, filters and the All/Solo/Team pane
+  are already applied; rows in a collapsed section or the inactive pane are skipped. A
+  row is unread when it shows the unread or thread-activity marker that
+  `SidebarUnread` also reads. The open conversation is the row marked `aria-current`.
+  Stepping does not wrap, and at either end it does nothing. When the open
+  conversation is not among the rows, next starts from the top and previous from the
+  bottom. A conversation listed in two sections is stepped over once. The shortcuts
+  are unavailable, leaving the key alone, while the sidebar renders no rows (for
+  example behind another page's own sidebar). Stepping activates the row's own
+  button, so it takes the exact path of a click: the saved selection, navigation
+  intent, session staleness guard and Solo's immediate activation. The list scrolls
+  just far enough to show the row, and nothing above it moves.
+- **Mark conversation as read** (Escape) uses the open conversation's
+  `unread.markChannelRead`, as the row menu's Mark as read does, with no success toast.
+  A failure shows an error toast. The page publishes it only for a joined,
+  non-preview conversation (not the new message page), and it is available only while
+  the connection has `frontier-sync`, the conversation shows unread and focus is not a
+  text field outside the composer. It never consumes a dismissal: the dispatcher skips
+  events something already handled, panels, tabs, completions and message edits stop
+  Escape themselves, and the narrow navigation drawer now prevents it when it closes.
+- **Mark all as read** (Shift+Escape) is registered by the shell; see
+  [shell design](shell-design.md).
+
 
 ### Attachment layout and scrolling
 

docs/inbox.md

@@ -29,6 +29,10 @@ Rows retain exact IDs and current names while `inboxFeed.incomplete` marks only
 
 The list is the Inbox page's first tab, in the host tab workspace behind `conversation.ui.Tabs`. Opening a row shows its conversation beside the list in the side tab pane, with the same reader and composer as Channels tabs: a thread at its exact message, revealed even outside the newest bounded page, or a whole DM or session conversation where its Channels tab would open. A plain open replaces the tab the previous one added, so one tab follows the selection; a tab moved to the main pane stays. The tab's right-click menu offers Open in channel, which opens its conversation in Channels; a thread opens there at the same message. A thread also names its conversation above its original message, as the rows do (`#channel` or `DM · names`); that name is a link that does the same. The pane resizes, closes and handles Escape as Channels' does. A late verified root can regroup a conversation without changing its open tab. Inbox tabs do not enter a channel visit, so showing one preserves forced-unread intent. Reading is saved by the shared unread owner, through the reader's dwell and the row's explicit read. Failed read actions retain their captured Retry unless access, the session or a newer intent retires it. A DM Retry reuses the original channel cutoff and manual-clear keys, not the retry-time clock or later arrivals. Re-clicking the selected row reselects its tab without repeating its read. Closing the tab ends the selection, so reopening the row reads it again. Archiving the selected conversation's channel, or its room becoming a Huddle, closes its tab and returns focus it held to the filters, and restoring the channel does not reopen it; other retained tabs follow Channels' unavailable placeholder, and focus their reader held moves to the tab. Re-clicking the selected row reveals its current message in its tab; a session mention that regrouped into a thread reselects its timeline tab. Context menus allow device-local Mark unread. Row accessible descriptions reuse the visible safe preview or incomplete placeholder; Show more follows the filtered result count. `NavigationItem` owns selected styling and `aria-current`. No Inbox-owned session, parallel fold, composer or outbox.
 
+### Open Inbox with a filter
+
+Four shortcuts open the Inbox page with its filters applied, including from the composer, like Slack's: ⌘⇧A (Ctrl+Shift+A elsewhere) opens All activity with Unread only, and ⌘⇧T, ⌘⇧M and ⌘⇧K open Threads, Mentions and DMs. Each also shows Inbox rather than Archived and leaves Drafts. Threads, Mentions and DMs keep the saved Unread only choice; Sender is never changed. They are rebindable in Settings → Shortcuts. The shortcut opens `buzz.inbox/inbox` with a versioned route (`{ attention?: "unread", activity? }`) that the page validates, and a plain open from the sidebar or topbar carries none and leaves saved filters alone. The page applies a route once per presentation of the visit, but not when Back/Forward returns to it, which keeps the filters as they were left, using the same saved choices as the filter menu, so pressing a shortcut again after changing the filters by hand applies it again, even though the host treats an identical address as the same history entry.
+
 ## Drafts (PR5)
 
 Drafts is a quiet Inbox header action. It lists only meaningful saved composer

docs/plugin-architecture.md

@@ -1654,7 +1654,7 @@ patches over the display parsing budget retain escaped raw text. Unconsumed
 patch lines and unsupported binary payloads also fall back to the complete raw
 patch; metadata-only rename/mode/binary summaries retain rich presentation.
 Preview, file and raw scroll regions support native keyboard navigation. Diff
-messages are not editable, including through the composer's Up-arrow shortcut.
+messages are not editable, including through the selected-message Edit shortcut.
 Diff search remains deferred: the client accepts kind 40008 hits, but relays
 whose search index allowlist excludes that kind cannot return them. Metadata is
 untrusted presentation, not repository access authority. No sending, applying,
@@ -2190,6 +2190,49 @@ app shortcuts (including live rebinds) win there; unhandled keys stay with xterm
 No plugin shortcut API or preference access is added. Ordinary editors continue
 to handle keys before the window's bubbling dispatcher.
 
+Slack-style message keys are host bindings. In an empty composer, Up selects the
+newest message (by id, not tree order) of the timeline or thread sharing its edit scope (on macOS ⌘↑ keeps editing
+the latest own message directly; elsewhere use Up, then E); a selection is
+DOM focus on that message's box (`features/messages/message-selection.ts`), so
+the timeline's Virtua keeps the row mounted and assistive technology follows it.
+Membership notices and folded or collapsed rows are skipped. While a message
+itself is focused, Up/Down move between rendered messages, Down past the newest and
+Escape return to the composer (a handled Escape does not also close the thread),
+and Up at the oldest rendered row stays native so history can load. When the
+timeline is scrolled far enough that the newest message is unmounted, Up from the
+composer keeps its old edit-last behavior, Down at the last rendered row scrolls
+natively, and ⌘⇧\ does nothing rather than act on an older message. E edits a selected eligible own message through the scope's
+editor, R opens the row's reaction picker through the host-owned
+`[data-reaction-tool]` trigger, and ⌘⇧\ selects the newest message in the focused
+pane, even from another selected message, and does the same. T or → clicks the row's Reply action (open or answer its
+thread), U marks unread from it (`useMessageKeyActions` in `MessageManagement.tsx`,
+the menu's own call), and Delete or Backspace opens the menu's delete confirmation
+for your own message; agent-owner deletion stays in the menu because it needs
+ownership evidence a key cannot wait for. Remind me (M) has no key: plugin message
+actions have no binding in their contract. Single-letter bindings never run in
+editable targets. ⌘1–⌘9 select the community switcher's entries in its order
+(⌘1 is Personal space) and ⌘⇧] / ⌘⇧[ step through them, wrapping
+(`app/shell/CommunityShortcuts.tsx`); Ctrl+Tab stays Buzz's tab switching.
+⌘T opens Search Buzz as a default alias of ⌘K (Slack's switcher answers to
+both); a shortcut may ship several default chords, and Settings → Shortcuts lists each
+distinct one ("⌘K or ⌘T") while showing layout aliases of one physical key (⌘=
+and ⌘+) once, but a Settings rebind replaces them with one. Plain-Escape
+dismissals (thread, panels, drawer, plugin details) ignore Shift so ⇧Esc reaches
+Mark all as read. The message editor's own keys (`composerFormats` and `linkBindings` in
+`features/messages/composer-dom.ts`, plus undo, redo and new line) are listed
+read-only under Message formatting, which says once under its heading that they
+belong to the editor; the editor matches them before any shortcut,
+so rebinding a shortcut onto one warns. Slack's ⌘⇧C (code), ⌘⇧9 (quote), ⌘⌥⇧C
+(code block) and ⌘⇧U (link) are aliases of Buzz's chords. ⌘/ opens Settings →
+Shortcuts, which is built the first time it is shown rather than with every
+Settings open. ⌘⇧Y opens Set a status while the profile menu
+can (the message editor keeps it as Redo). Home is on the placeholder ⌘⇧O while
+⌘⇧A opens Inbox's unread view. Inbox's ⌘⇧A, ⌘⇧T, ⌘⇧M and ⌘⇧K are ordinary
+`buzz.inbox` plugin contributions, so they follow the plugin precedence above: a
+plugin whose namespaced ID sorts first and claims the same chord wins it while
+eligible. Settings → Shortcuts marks such rows "Also used by"; rebinding either one
+resolves it.
+
 Known limitations. Capture and matching both use the logical `KeyboardEvent.key`.
 On macOS an Option chord reports the composed character, so Option+K is stored
 and shown as `⌥˚`, and Shift+digit chords store the punctuation (`!` rather than

docs/relay-queries.md

@@ -672,8 +672,12 @@ receipt, as Buzz desktop does. Nothing is persisted or restored; a rejection or
 10-second timeout rejects the call and the dialog keeps its input for retry. The
 method is undefined unless the writer supports kind 1984.
 
-In an empty composer, unmodified Up arrow opens the latest eligible own message
-from that channel or thread in the same editor. Enter/the send arrow saves;
+In an empty composer, unmodified Up arrow selects the newest message in the
+channel timeline or thread beside it, as in Slack; E then opens a selected
+eligible own message in the same editor, and on macOS ⌘↑ still opens the latest eligible
+own message directly (elsewhere, Up then E). Surfaces without a selectable message
+list (media review, Huddles), or a timeline scrolled away from its newest
+message, keep Up opening the latest eligible own message directly. Enter/the send arrow saves;
 Escape or × cancels. Edits retain raw attachment Markdown and leave original
 notification recipients unchanged. Edit text never overwrites the new-message
 draft or its undo history. Pending edits lock the editor until delivery; failed

docs/shell-design.md

@@ -441,6 +441,13 @@ Windows/Linux consume held-key repeats without closing further tabs or the windo
 Window buttons and Alt+F4 always retain their window-only behavior. The bottom
 terminal drawer keeps its existing Cmd/Ctrl+J/Hide behavior. Browser-build
 shortcuts are unchanged.
+Shift+Escape asks "Mark everything as read?" in the shared `AlertDialog` (Cancel has
+initial focus; focus returns to the element that had it) and then runs the community
+menu's Mark all as read action and toasts. `MarkAllReadShortcut` registers it as a host
+shortcut only while the selected community's session is connected, and it is
+unavailable without `frontier-sync` or when no channel shows unread. It works while
+typing and yields to terminals and open dialogs. On a narrow layout, Escape that closes
+the navigation drawer is consumed, so it never also marks anything read.
 Feature-local details such as harness logs remain tied to their owning profile;
 closing that profile or losing authorization also removes its log tab.
 Right-click any channel tab and choose **Close all tabs** to close this channel's

docs/unread.md

@@ -155,7 +155,9 @@ timeline and the thread being read, without reading unopened threads' replies.
   the sweep; the first failure is rethrown afterwards. A channel whose grant is
   revoked before its turn is skipped, not failed; like a grant that arrives
   mid-sweep, it waits for the next explicit action. The community switcher's
-  Mark all as read uses it for the selected community only.
+  Mark all as read and the Shift+Escape shortcut (after a confirmation) use it
+  for the selected community only, through one shared action and toast copy.
+  Escape marks the open conversation through `markChannelRead`.
 - `markUnreadLocal(target)` is durable **on this browser profile/device only**.
   Automatic reading does not clear it. An explicit mark-through clears that
   target's local mark. `syncedManualUnread` is `false`.

examples/plugins/README.md

@@ -3,8 +3,8 @@
 All example plugins live here with `manifest.json` and prebuilt `plugin.js` files:
 
 - `counter` and `notes`: offline playgrounds.
-- `shortcut-counter`: offline keyboard-shortcut consumer; Command+Shift+K /
-  Control+Shift+K increments through the injected host service. Requires `shortcuts`.
+- `shortcut-counter`: offline keyboard-shortcut consumer; Command+Shift+G /
+  Control+Shift+G increments through the injected host service. Requires `shortcuts`.
 - `broken-page`: intentionally fails when its page renders to exercise error handling.
 
 ## Try the offline playgrounds

examples/plugins/shortcut-counter/README.md

@@ -4,7 +4,7 @@ Import this folder from desktop Settings → Plugins, then enable **Shortcut cou
 The prebuilt `plugin.js` has no runtime imports or build step. Requires a host with
 `shortcuts` (host-matched API v1 preview, not a cross-version SDK).
 
-Press **⌘⇧K** on Mac / **Ctrl+Shift+K** elsewhere to increment. The same handler
+Press **⌘⇧G** on Mac / **Ctrl+Shift+G** elsewhere to increment. The same handler
 backs the button. The count lasts for the plugin lifetime, not a page mount;
 disable/re-enable resets it and disposes/re-registers the binding. The typing
 field demonstrates the default editable-target guard. No custom DOM listener,

examples/plugins/shortcut-counter/plugin.js

@@ -11,7 +11,7 @@ export function apply(ctx) {
   ctx.shortcuts.register({
     id: "increment",
     title: "Increment shortcut counter",
-    binding: { key: "k", mod: true, shift: true },
+    binding: { key: "g", mod: true, shift: true },
     // Settings order within the Shortcut counter category.
     order: 10,
     run: increment,
@@ -45,7 +45,7 @@ export function apply(ctx) {
         React.createElement(
           "p",
           null,
-          "Press Command+Shift+K (Control+Shift+K on other platforms). Typing fields and modal dialogs are excluded by default. Disable the plugin to remove its shortcut.",
+          "Press Command+Shift+G (Control+Shift+G on other platforms). Typing fields and modal dialogs are excluded by default. Disable the plugin to remove its shortcut.",
         ),
         React.createElement("input", {
           "aria-label": "Shortcut typing guard",

src/app/Settings.tsx

@@ -344,7 +344,8 @@ function PluginDetails({
       className={styles.pluginAside}
       aria-label={`${plugin.manifest.name} details`}
       onKeyDown={(event) => {
-        if (event.defaultPrevented || event.key !== "Escape") return;
+        if (event.defaultPrevented || event.key !== "Escape" || event.shiftKey)
+          return;
         event.stopPropagation();
         onClose();
       }}
@@ -689,6 +690,10 @@ export function Settings({
     [contributed, departureCommunity],
   );
   const [selected, setSelected] = useState(defaultSection);
+  // Shortcuts lists every binding with its own controls, so it is built on
+  // first visit rather than with every Settings open, then kept like the rest.
+  const [shortcutsVisited, setShortcutsVisited] = useState(false);
+  if (selected === "shortcuts" && !shortcutsVisited) setShortcutsVisited(true);
   // A switch made from inside the content hides or removes the control that
   // made it, so focus moves into the section it opened.
   const contentFocus = useRef<string>(undefined);
@@ -1211,11 +1216,13 @@ export function Settings({
           />
         </div>
         <div hidden={selected !== "shortcuts"}>
-          <ShortcutSettings
-            shortcuts={shortcuts}
-            bindings={shortcutBindings}
-            plugins={plugins}
-          />
+          {shortcutsVisited && (
+            <ShortcutSettings
+              shortcuts={shortcuts}
+              bindings={shortcutBindings}
+              plugins={plugins}
+            />
+          )}
         </div>
         <div hidden={selected !== "agents"}>
           <AgentSettings