[miguel-heygen]

What

Cuts HyperFrames v0.9.16: bumps every package and plugin manifest to 0.9.16 and adds the release notes (releases/v0.9.16.md, docs/changelog.mdx). It carries the fix that makes the studio cancel route reply once the agent's stop has settled (#7221) and the capture retry for a refused screenshot (#7222), along with the other fixes and two features merged since v0.9.15.

No visible change

No product or UI change in this pull request itself: only version numbers and release notes.

What I did

bun run release:prepare 0.9.16 --from v0.9.15 (drafted the notes and bumped the versions), then replaced the draft's TODO summary and removed its style-bar comment in both files. The --from flag was needed because my build host had no tags; v0.9.15 is the latest tag on main.

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Nov 5, 2026, 12:31 PM

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

[heygengenesis]

Verdict: COMMENT (review only, release decision left to the release owner) · 0 blocker · 1 important · 0 nits · head abb8a37

• important: releases/v0.9.16.md and the docs/changelog.mdx block do not list #7217, which merged to main (0180c603) after this branch was cut. The merge queue squashes onto current main, so #7217 will ship in v0.9.16 without a note. Re-running scripts/draft-changelog.ts 0.9.16 --from v0.9.15 --to origin/main gives exactly one missing line:
  - **Producer:** Resolve template sub-composition entries in the shared compile stage ([0180c603d](https://github.com/heygen-com/hyperframes/commit/0180c603d1902de32ca14543cdac710c87a676b2), [#7217](https://github.com/heygen-com/hyperframes/pull/7217)).
  Every other PR in the range is listed.

Scope

• Diff is 21 files: 19 one-line 0.9.15 → 0.9.16 bumps, plus the notes and the mdx. The bumps match scripts/set-version.ts PACKAGES and PLUGINS (14 packages and 5 plugin manifests). No code changes.
• The mdx block and releases/v0.9.16.md list the same PRs.
• No included PR body declares a release prerequisite or merge hold.
• CI on this head passed (CI, regression, Windows render verification, Lambda arm64 image, Docs). Comments was skipped.
• This review does not approve or queue the release. Publishing to npm can't be undone, so that call belongs to the release owner.

[heygengenesis]

Requesting changes at abb8a37c.

Blocker: four merged fixes would ship in v0.9.16 without release notes.

This branch was cut from b96d3c8b (#7231). Since then, four PRs have merged to main:

PR	Merged (UTC)	Change
#7217	10:04	producer: resolve template sub-composition entries in the shared compile stage
#7224	11:13	cli: previews and every per-user cache follow HYPERFRAMES_CACHE_DIR
#7225	11:23	core: keep long WebKit sources and unloaded clips on the audio clock
#7229	11:51	cli: every settings file follows HYPERFRAMES_CONFIG_DIR

publish.yml checks out pull_request.merge_commit_sha, so the npm publish uses the queue's squash onto current main, and all four would go out as 0.9.16. Neither releases/v0.9.16.md nor the docs/changelog.mdx block lists them. The earlier bot review caught only #7217; the other three merged after it.

#7224 and #7229 change where the CLI reads caches and settings. Desktop depends on that, so the "release gate passed against Desktop" result only covers these changes if the gate ran on a SHA that includes them. If it ran on the branch base, it does not cover them. A publish can't be undone, so this needs fixing before merge.

Fix: rebase release/v0.9.16 onto current main, re-run release:prepare 0.9.16 --from v0.9.15 (or draft-changelog --to origin/main) to add the four lines, and confirm the Desktop gate ran on a SHA that includes #7224 and #7229. An alternative is to hold #7224, #7225 and #7229 for 0.9.17, but the queue squash would ship them anyway, so rebasing is simpler.

Checked and fine:

• 19 one-line version bumps (14 packages and 5 plugin manifests). No "0.9.15" is left outside the notes.
• The notes and the mdx block list the same 27 PRs. That is exactly v0.9.15..b96d3c8b: nothing missing, nothing extra.
• CI passed on this head.

[heygengenesis]

Approving at b29cb2b7. The blocker from my review at abb8a37c is fixed.

• Rebased on current main: the merge base is 5f7b85c5, which is the tip of origin/main. Nothing is on main that isn't on this branch, so the squash publishes exactly what the notes describe.
• Notes are complete: releases/v0.9.16.md lists every PR in v0.9.15..5f7b85c5 (33): nothing missing and nothing extra. The docs/changelog.mdx block lists the same PRs. The new lines cover #7217, #7224, #7225 and #7229, which I flagged, plus #7226 and #7233, which merged later.
• Version bumps: the branch diff is 21 files, 134+/19−. That is 19 one-line 0.9.15 → 0.9.16 bumps plus the two notes files. No "0.9.15" is left. sdk-playground stays at 0.6.106, as at v0.9.15, because it isn't in set-version.ts.
• CI passed on this head: CI, regression, Windows render verification, Lambda arm64 image, Docs and CodeQL.
• Desktop release check: I couldn't see this result from here. It isn't a GitHub Actions run or commit status on this repo, so I'm relying on the PR's statement that it passed on b29cb2b7 and covers #7224 and #7229.