Issue #4037 (phase 3 of #4098). An existing member pane can now be
dragged back onto its own workspace to rearrange it, landing with the
same snap-in split semantics an orphan drop gets.
- domain: add pure movePaneInWorkspace(root, sessionId, hint) composing
the existing prune + insert conventions (no-op for unknown/single-pane
self-drops; prune-first keeps target-inside-subtree drops correct).
- state: moveWorkspacePane / moveWorkspacePaneInWorkspaces touch only
workspaces[].root — session ids, tab order, focus fields and every AI
binding (anchorChatId etc.) are untouched by construction.
- drop flow: handleWorkspaceDrop routes same-workspace member drops to
the move op; cross-workspace drops stay rejected (#4098 policy) and
orphan drops are unchanged.
- preview: member panes drag via pointer events, so the split-hint
preview and drop are mirrored on the pointer stream while a member of
the active workspace is dragged; dropping a pane onto itself previews
and drops as a no-op.
Identity guarantee: a move never changes session ids, workspace id,
anchorChatId, focusedSessionId (focus is keyed by session id, so it
visually follows the moved pane), focusSessionOrder or tab order; the
moved tree roundtrips through netcatty_session_restore_v1 unchanged.