An AI client could create nodes but had no way to create the areas that
organize them, or to move a node into one (#365).
Four tools, all on the existing /api/v1/nodes endpoints: create_zone
(a groupRect node, with size and border/text colours), list_zones (each
zone plus the ids it contains), add_to_zone and remove_from_zone, both
taking a list of node ids.
The canvas stores a child's position relative to its parent, so
add_to_zone rebases each node on the zone and remove_from_zone restores
absolute coordinates — otherwise a node jumps by the zone's offset the
next time the canvas loads. add_to_zone skips what it cannot move (the
zone itself, a node already inside it, an unknown id, and any node the
zone descends from, which would build a cycle) and reports them back
rather than failing the batch.
groupRect stays out of NODE_TYPES: create_node remains a device tool,
and the enum sync tests keep passing.
ha-relevant: no
Pouzor
1ec7ea7e8e