v0.1.1

0.1.1 (2026-10-25)

Fixed

• A static shape whose geometry a setter changes (m2Shape_SetCircle,
  m2Shape_SetCapsule, m2Shape_SetPolygon, m2Shape_SetSegment)
  collides over its new extent. Its broadphase box used to keep the old
  extent, so a ball dropped over the new part of a widened static box
  fell through it. On a dynamic body the box is refitted one step
  earlier than before, with the same result. The world hash differs
  from 0.1.0's after such a change, since the box is part of it
  (#48).
• A restore holds each number that a def, a setter or a tape holds to
  a range to that same range, and checks each joint kind's own fields
  with that kind's validators. A snapshot from outside could restore
  values that turned the world invalid in its first step; such a
  snapshot is now refused, changes nothing and counts nothing. A
  snapshot a world writes still restores, and neither format version
  changes. Two solver paths could store an impulse one float past its
  limit; both now store the limit
  (#45).
• A restore refuses a snapshot in which a shape of a static or sleeping
  body lies outside its broadphase box. Such a snapshot left the step,
  and the host's queries, finding the body where it was not. So that a
  world's own snapshots keep restoring, a body's boxes are refitted
  where it falls asleep, both in the step and in
  m2Body_SetAwake(false). The world hash can therefore differ from
  0.1.0's when a body falls asleep past its box margin; in no golden
  scene does one
  (#49).