Writing a transform to a node

Rotation and scale, written onto the Babylon node itself, in the RUNTIME layer because both the instantiator and the editor need them and the dependency may only point one way: the editor may import the runtime, never the reverse. Putting these in transform-write.ts — where they belong by subject — would drag the whole editor into a game's bundle, which tree-shaking.test.ts exists to prevent.

Rotation is the element's; scale is the element's when it can be

For years a library-backed piece could be neither turned nor scaled through its element: b3d-destroyable forwarded only position to library.instantiate, and size is the placeholder cube's edge. We wrote both onto the node. tosijs-3d 0.8.1 fixed both (#47, #48), so:

A plain node (no element) has nothing managing it, so applyScale writes it directly; the editor's node path rotates it directly too.