A floating dock group in its own OS window now moves through a window move
gesture the app runs, which reports Begin, Update, Commit and Cancel like a
layer's move, so the dock marks the target under the pointer and docks the
whole window on release.
- macOS (Caps::OS_MOVES_TRACKED): the OS moves the window (StartMove), and the
app follows the system pointer, button and Cmd through SystemWindows, the
running platform's WindowSystem in craft-window. The hand-off ends when the
system reports the button up.
- X11 and Windows: the app moves the window with SetOuterPosition so the
pressed point stays under the pointer; Escape puts it back.
- A drag started by a container shown in its own OS window follows that
window's pointer, not its parent's.
- The runtime's end hook sets NSWindow.movable for every window; a window
whose move the app runs is never moved by AppKit from its band.
cl test failed for craft-ui-panels, canvas, patterns and shell: their canonical set named craft-ui-contract/snapshot, and cargo lets a command name a feature only of a direct dependency, which the runtime is not for crates above widgets. craft-ui-contract's testing now includes snapshot (the resolved feature set of the runtime in a test build is the same three features as before, so no unit changes), and the canonical sets drop the snapshot entries. cl doctor resolves every crate's canonical set against cargo metadata, with no build: a plain feature must be the crate's own, a dep/feature must name a direct dependency and a feature it has. docs/development.md states what CI covers (ui.yml for the seven ui crates, theme.yml, docs.yml, path-filtered workflows for some leaf crates) and what it does not (the domain crates on the framework, the gallery, the renderer, the umbrella crate, any workspace-wide build).