Cleanup

assets/snapline/core/README.md

@@ -26,26 +26,33 @@ npm install @snap-engine/core @snap-engine/snapline
 
 ```ts
 import {
-  GroupNodeComponent,
-  NodeComponent,
+  GroupNodeMirror,
+  NodeMirror,
   getParentGroup,
   setGroupMembershipResolver,
 } from "@snap-engine/snapline";
 ```
 
-After assigning a Vanilla-rendered element, call `syncDomGeometry()`. Svelte
+After assigning a Vanilla-rendered element, call `remeasureDomGeometry()`. Svelte
 and React adapters perform that synchronization automatically.
 
+Live gesture geometry stays outside framework state. Nodes and groups write
+their retained element transforms and resize dimensions directly. Line,
+selection, and placement renderers register one imperative
+`bindGeometryWriter(...)`; semantic observers and commit callbacks remain
+separate. A custom line renderer should mount its SVG/Canvas structure once,
+bind a writer, and call the returned cleanup function when it unmounts.
+
 When another interaction system applies transient transforms inside a node,
 call `connector.requestDomGeometrySync()` for each affected connector. The
 request is coalesced into the next read/write cycle and updates every connected
 line without coupling SnapLine to the external system.
 
 Surface strategies decouple connection hit testing from visible connector
 elements. They can activate from a node border, rank shape-specific target
-hits, and resolve preview and settled anchors from cached geometry. Independent
-connector capabilities allow the same logical surface to start and accept
-connections. `onPointerDown` runs when a connector claims the primary pointer,
+hits, and resolve preview and settled anchors from cached geometry. Symmetric
+connector rules (`maxOutgoing`/`maxIncoming`, `"unlimited"` explicit) let the
+same logical surface start and accept connections. `onPointerDown` runs when a connector claims the primary pointer,
 before the drag threshold, so consumers can preserve click selection or other
 gesture-start UI for headless surfaces.
 
@@ -54,10 +61,13 @@ surface strategies, collider radius, edge-pan behavior, or the line class
 without replacing the connector or its existing lines. `name` is
 construction-only because it is the connector's key in its parent node.
 
-For a framework-owned graph, use `onConnectionRequest` to create the domain
-edge and return its stable ID as an opaque line payload. Pass that payload
-directly when hydrating with `connectToConnector`; programmatic connections do
-not invoke the creation request.
+Topology is always controlled: attach the graph owner with
+`attachControlledGraph(engine, { onLineChangeRequest })` (or mount the
+adapter `ControlledGraph` component), push your `LineRecord`s through
+`setCanonicalGraph`, and apply each gesture's atomic proposal to your
+records — adopting the proposed line id settles the dragged line in place.
+Hydration never invokes your request handler, so restoring a saved graph
+cannot duplicate application edges.
 
 Groups maintain an exclusive direct parent. Ordinary nodes use center
 containment, nested groups use full-bounds containment, and the smallest safe

assets/snapline/core/package.json

@@ -18,7 +18,10 @@
     "./select": "./src/select.ts",
     "./group": "./src/group.ts",
     "./placement": "./src/placement.ts",
-    "./query": "./src/query.ts"
+    "./query": "./src/query.ts",
+    "./graph-mirror": "./src/graph-mirror.ts",
+    "./line-reconciler": "./src/line-reconciler.ts",
+    "./geometry": "./src/geometry.ts"
   },
   "files": [
     "src",