chore(main): release 3.2.1

[bitwise-fast-forward-merge]

🤖 I have created a release beep boop

3.2.1 (2026-06-29)

Bug Fixes

• ci: verify committed dist/ after build; drop redundant npm ci (aaa75ed)
• release: verify dist/ in CI, not after the release is cut (f68fb68)

---

This PR was generated with Release Please. See documentation.

[github-actions]

Note

Merging this PR: this repository merges by fast-forward so every
commit keeps its original signature. The GitHub merge button is not used.
Once this PR is approved and all checks pass, a maintainer merges it by
commenting /merge on the PR.

The branch must be up to date with main (rebased and re-signed) to
fast-forward. If /merge reports it is not fast-forwardable, rebase onto
main and comment /merge again.

[dmccaffery]

/auto-merge

[bitwise-fast-forward-merge]

Note

Auto-merge armed. Once this PR is approved and every required check
passes, it will be fast-forwarded into the base branch automatically,
preserving every commit signature.

Remove the auto-merge label to cancel. If the branch is not
fast-forwardable, rebase onto the base branch and re-sign — CI re-runs
and the merge retries.

[bitwise-fast-forward-merge]

Cannot /merge this PR yet:

• checks not passing: analyze / Analyze (actions) (pending)

[bitwise-fast-forward-merge]

Fast-forwarded main to 5a07255dbaf1 — original signature preserved, no re-sign.

[bitwise-fast-forward-merge]

🤖 Created releases:

• v3.2.1

🌻