Release 0.2.1

0.2.1 (2026-07-28)

Bug Fixes

• latch animateTo issued before the first host view registers (3a1155e)

An animateTo that raced its own host's Fabric mount used to hit the
registry's zero-views path: it stored the target as latest, emitted
finished: true and dropped the animation, so the host that mounted a
moment later statically applied the target and the clip jumped to its end
state. The animation is now latched (held out of the render/frame path) and
started by the first view registration, with its clock rebased so it runs
its full duration from the moment a frame can show it.

Behaviour change: an animateTo whose host never mounts now completes late
with finished: false (on replacement, cancel, take-ownership write or
driver destruction) instead of immediately with finished: true. Exactly
one completion per animation id still holds, and the public API is
unchanged.

Full write-up in docs/pending-animation-latch.md.