chore: drop empty changeset so the release workflow publishes pending 0.2.2

[nicosampler]

Summary

No related issue. The empty changeset added in #30 was meant to satisfy the
changeset check without bumping the version, but changesets/action treats
"only empty changesets" as pending work: it neither opens a Version PR nor
publishes. Removing it unblocks the publish of the already-versioned 0.2.2.

Changes

• Delete .changeset/puny-knives-roll.md (empty changeset)

Acceptance criteria

• On merge, the Release workflow publishes @bootnodedev/canton-barebones@0.2.2 with provenance

Test plan

Automated tests

No automated tests added — no package code changes.

Manual verification

npx changeset status --since=origin/main passes (no package changes require a changeset). After merge, watch the Release run publish 0.2.2.

Breaking changes

None.

Checklist

• Self-reviewed my own diff
• Tests added or updated
• Docs updated (if applicable)
• No unrelated changes bundled in

Screenshots

None.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.