Sidebar: Move to top / Move to bottom in the thread context menu

[joshka]

Problem. In the web and desktop sidebar, you can put threads in your own order only by dragging. That makes some moves awkward. Moving a thread from the bottom of a long Active list to the top means dragging it past the edge so the list auto-scrolls. On touch, dragging competes with scrolling and tapping. Pinning is no substitute: it moves the thread to another section, when you just want it first in the section it's already in.

Proposal. Add Move to top and Move to bottom to the thread context menu.

• They apply only where order is manual: Pinned, and Active when it isn't sorted by time. Settled and Snoozed have no manual order, so the items don't appear there.
• An item is hidden when the thread is already in that position.
• The result is identical to dragging the thread to that end of its section. It uses the same order keys and commands, and syncs the same way across clients.

Scope. Web and desktop, single thread. Mobile has no manual thread ordering yet (#14358). Applying these to a multi-selection could follow later.

Implementation sketch. handleThreadDragEnd in apps/web/src/components/Sidebar.tsx already takes a drop target and plans the move with planSidebarThreadDrop. That target is a section plus a key order. The menu items would build the same target with the thread's key moved to the front or the end, then run through the same path. Drag and menu would share one reorder function. No contract or server changes.

Related.

• #6473 / #6985: manual thread ordering in Sidebar V2. This proposal adds a non-drag way to do the same thing.
• #14685: reaching row actions on touch. A menu reorder would help touch users the same way.
• #6819: automatic ordering of finished threads. That's a different feature; this one only moves the thread you pick.

🤖 Claude Opus 5.5