The model kept the geometry a shape authored relative to the parent it
authored it in. A move keeps where and how the shape shows, so moved into
a turned board it was expected turned with it, where production keeps
its turn on the page. The model records the authored geometry again in
the shape's new parent after a move.
Harness only; the benchmark is not run.
Also in this commit:
- Draw fewer random programs in JS and check coverage on the JVM. The random
composition properties drew 50 programs in JS as on the JVM, which made the JS
run of the common tests take about two and a half hours. JS runs the same
model and production code, so it now draws 15 programs per property as a
parity check, and the coverage shares, which need the JVM's 50 programs to
tell, are asserted on the JVM only.
AI-assisted-by: claude-opus-5-5