@jarenjs/collection 0.84.3 → 0.86.0

package/ARCHITECTURE.md

@@ -8,3 +8,11 @@ only core/view. The component entry owns elements, frames and observers and maps
 The app range coordinator receives a structural provider from the host. Storage
 adapters in linq/db never import app; neither core nor the collection engine
 imports storage or workers. Source resources stay private to the coordinator.
+
+`drag.js` owns serializable drag intent and generation-fenced authority replies.
+The component drag adapter owns pointer capture, keyboard/touch activation,
+client-coordinate hit testing, a portal overlay and bounded auto-scroll. It uses
+collection lifecycle subscriptions and shared focus/pin budgets. DOM resources
+never enter app state and the engine never mutates business data. Native layout
+and capture paths are qualified by the three-engine browser matrix; the headless
+state machine and collection ownership remain in the Node function audit.

package/README.md

@@ -19,6 +19,12 @@ collection.dispose();
 
 See [architecture](ARCHITECTURE.md) and [the collection contract](docs/COLLECTION.md).
 
+`createDragInteraction` supplies stable-key move/copy intent and async authority
+fencing. `mountCollectionDrag` and `createDraggableCollectionWidget` in
+`@jarenjs/collection/component` add pointer, dedicated touch handles, keyboard,
+portal overlays and bounded auto-scroll over the existing virtualizer. See
+[the drag contract](docs/COLLECTION.md#drag-intent-and-authoritative-commands).
+
 ## Public exports
 
 <!--fact:exports.collection-->