8853cdd0c6
Two gaps closed on the recipe tree editor based on user feedback: 1. Explicit Move Up / Move Down buttons on every non-recipe node row, driven by a new POST /fp/recipe/node/move_sibling endpoint. DnD already existed but couldn't reliably move a node above a sibling when the drop zone overlapped the node being dragged. The button-based flow sidesteps that entirely and makes "nudge one slot" a single click. 2. Inline "Import from recipe" toolbar that appears when the Import button is clicked in the header. User picks a source recipe from a dropdown (POST /fp/recipe/list, excludes the current one), toggles "Skip duplicate names", and clicks Import. POST /fp/recipe/node/import_children deep-copies every top-level child of the source under the current recipe, preserving the sub-tree structure. Dedupe is on by default so re-running the import on an already-populated recipe is a no-op; users who want to merge identical-named branches can untick the checkbox. Controller endpoints: - /fp/recipe/list (list recipe roots for the picker) - /fp/recipe/node/move_sibling (swap with neighbour by direction) - /fp/recipe/node/import_children (deep-copy subtree with dedupe) Smoke verified on entech: 5-child recipe imported cleanly, dedupe blocks re-import, sequence swap works. fusion_plating → 19.0.7.0.0 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>