v0.2.0

fix(ci): write the lockfile the pinned Bun can read

The lockfile was regenerated with a Bun 1.4 canary, which writes
lockfileVersion 2. CI pins bun 1.3.14 — via packageManager and the pantry
action — and 1.3.14 cannot parse v2, so every job that runs
'bun install --frozen-lockfile' failed to install and the v0.2.0 release never
published.

Regenerated with 1.3.14 itself, so it is version 1 again. Verified
--frozen-lockfile is satisfied under both 1.3.14 and 1.4, so working on a
newer local Bun stays fine as long as the lockfile is not rewritten by it.