chore: release v0.7.110

[miguel-heygen]

What

Stable release v0.7.110. Bumps all 13 packages in lockstep and adds the release notes.

Merging this PR is what publishes: the workflow checks out the merge SHA, creates the v0.7.110 tag there, publishes to npm on the latest dist-tag, and cuts the GitHub Release. No tag was pushed from a laptop.

Why

Five commits have landed since v0.7.109 and none of them are released. The catalog fix in particular only reaches anyone through a published CLI, since agents run npx hyperframes.

How

bun run release:prepare 0.7.110, twice as designed: the first run drafted releases/v0.7.110.md and the changelog entry and stopped for review, the second created the release commit after the summary was written.

Contents, from the generated changelog:

• Features — Studio preview volume control (feat(studio): add a preview volume control #3282).
• Fixes — temp dirs created with mkdtemp rather than a Date.now() name (fix: create temp dirs with mkdtemp, not a name built from Date.now() #3241).
• Catalog — unreachable-registry survival plus the search-gap report (fix(catalog): survive an unreachable registry, and ask for the gap #3299); avatar promo and Slack notification templates (feat(registry): add avatar promo and Slack notification templates #3279).
• Docs — anime.js v3-in-v4 syntax correction in the adapter guidance (docs(skills): fix anime.js v3 syntax in v4 adapter guidance #3064).

Patch bump rather than minor, following the convention of the last several releases: 0.7.107 through 0.7.109 each carried feat: commits and stayed on a patch.

Test plan

• Unit tests added/updated
• Manual testing performed
• Documentation updated (if applicable)

No product code changes here, so there is nothing new to unit test. What was checked:

• All 13 package.json versions read 0.7.110, along with the three plugin manifests.
• releases/v0.7.110.md and the docs/changelog.mdx entry both carry a written summary with the TODO marker removed. release:prepare refuses to tag otherwise, and that gate was exercised on the first run.
• Every commit in the range appears in the notes: git log v0.7.109..main is exactly the five entries listed above.

The code being released was verified on its own PRs. CI on this branch is the gate for the release commit itself.

Note for reviewers

CONTRIBUTING.md still documents the older tag-push flow for stable releases (git push origin v<version>). The release:prepare script now prints the release-PR instructions instead and explicitly says not to push the local tag. The doc is stale rather than wrong about this PR, and worth correcting separately.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
hyperframes	🟢 Ready	View Preview	Aug 17, 2026, 7:04 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.