Release 0.3.2

[KennethWussmann]

Why

The 0.2.2 publish never made it to npm. The v0.3.0 and v0.3.1 releases were created by hand against commits that still carried version 0.2.2, so npm publish kept retrying an already-published version and failing. Those two releases have been deleted along with their tags.

This repo's release flow is package.json-driven: bumping the version on main is what makes onPushToMain.yml create the tag and the GitHub release, which in turn triggers the publish. So the bump is the trigger, not a follow-up to a release.

What

• Bumped version to 0.3.2.
• Regenerated the README command docs, so the See code: permalinks point at v0.3.2 instead of v0.2.2.
• package.json also picked up a trailing newline, which it was missing before.

Note on merging

Merging this to main will create the v0.3.2 tag and release automatically, which then runs the publish workflow. There is no separate release step to perform afterwards.

The README was regenerated with oclif readme followed by markdown-toc -i README.md. The version npm script only runs the first of those, which collapses the table of contents; running both keeps it matching what prepack produces.

Written by Claude Opus 5 via Pi