chore: release v0.8.52

[vanceingalls]

Release PR for v0.8.52. Merging publishes npm and cuts the GitHub release from the merge SHA.

Studio's interface now runs on one shared set of buttons, tabs, menus and popovers, so controls look and behave the same everywhere. Undo and redo move into the timeline toolbar, and a dead project id in the URL no longer blocks editing for the rest of the tab.

• 16 changes since v0.8.51 — full changelog
• Release notes: releases/v0.8.52.md

No visible change

The only watched paths in this diff are two version bumps — packages/studio/package.json and packages/player/package.json, 4 lines total, no .tsx/.css/.html. A release PR carries no behaviour of its own; the shipped changes were each captured in their own PR.

Checked against evaluate() in scripts/check-pr-captures.mjs before pushing, and mutation-tested both ways: dropping the heading fails, and adding a .tsx to the file list fails even with the heading present.

This will recur. The captures gate (#4131) landed after v0.8.51 was cut, so this is the first release PR to meet it, and every future one bumps the same two files. Worth teaching release:prepare to print this section with its gh pr create instructions — a separate change, not one to smuggle into a release commit.

Note for reviewers

The first draft of this changelog was wrong and was regenerated. bun run release:prepare creates a local tag, and the publish workflow then tags the merge SHA — so after a squash merge the local v0.8.51 tag points at a commit that is not on main. git fetch --tags will not overwrite an existing local tag, so the drafter walked back to v0.8.50 and re-listed ~100 already-released commits. Fixed with git fetch origin --tags --force before drafting.

🤖 Generated with Claude Code

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Sep 19, 2026, 9:45 PM

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

[miguel-heygen]

Approving to ship 0.8.52 with the film fix (#4198) and the CI hang fixes (#4204, #4206) folded in from main.

[terencecho]

APPROVING at e778100b — release-only diff (17 pure version bumps 0.8.51→0.8.52 + 2 docs files). All four claimed folds are merged on main and reachable from this head. One non-blocking documentation gap noted below.

Clean-promotion audit — no smuggled source

Full diff is 18 files, all fall into one of two buckets:

Pure "version": "0.8.51" → "version": "0.8.52" bumps (17 files, 1-line-in / 1-line-out each):

• .claude-plugin/plugin.json, .codex-plugin/plugin.json, .cursor-plugin/plugin.json
• packages/{aws-lambda,cli,core,engine,gcp-cloud-run,lint,parsers,player,producer,sdk,shader-transitions,studio-server,studio}/package.json

Each hunk is textually just the version field; nothing else in any package.json moves. No source files (*.ts, *.tsx, *.js, *.mjs, *.py, *.go) appear in the diff at all.

Docs / release notes (2 files):

• docs/changelog.mdx (+38/0) — new <Update label="HyperFrames v0.8.52"> block appended above the v0.8.51 entry.
• releases/v0.8.52.md (+37/0, new file) — the same release notes in a standalone file.

No smuggled source. Passes Home's clean-promotion gate.

Folded PRs — all four merged to main, reachable from this head

Verified via gh and via the merge commit's parents:

• #4198 — merged 21:57:17Z as 038851c7a85d076b93141c113bd663e7423dfb68 (HTML bundler inlineAssets opt-in; launch-film fix).
• #4185 — merged 22:08:30Z as 0cde88433071eb0572ebe84f3b5c1680f54f537c (macOS 12 Chrome 150 ceiling).
• #4204 — merged 22:32:55Z as 420fc118ccc0990c85293cb72a14de5086080044 (regression CI bun-install hang bound).
• #4206 — merged 22:33:07Z as 2060e13f2d9c25c4a208d2bb271889ad6443f5fe (Cloud Run bun-install hang bound).

Miguel's merge-of-main commit e778100b48 (authored 22:33:29Z, committed via web-flow) has parents 4d62e80921 (Vance's release cut) + 2060e13f2d (= #4206's merge commit, current main tip at the time). Because 2060e13f2d sits on top of the three prior merges, all four folded PRs are ancestors of this head.

Last-pusher / gate mechanics

Miguel's Slack said "the last pusher (home), so a bot stamp merges it." Verified in GitHub: the merge commit is authored by miguel-heygen with web-flow as committer (the standard "Update branch" pattern from the PR page); "home" is not a GH account, so the label was ChatGPT-dispatch shorthand. Current reviewDecision: APPROVED (Miguel's own approval at e778100b) with mergeStateStatus: CLEAN — the gate is already satisfied without this stamp. tai (terencecho) ≠ miguel-heygen, so my APPROVE stacks cleanly regardless of how the branch's require_last_push_approval setting interprets Miguel's own approval.

Non-blocking follow-up — changelog under-documents the fold

Vance drafted the changelog and releases/v0.8.52.md against the initial 16 PRs (#4196, #4187, #3624, #4191, #4186, #3622, #4184, #4177, #4180, #3623, #4188, #4181, #4176, #4056, #4182, #4189) — all of which landed before the release-cut commit. The subsequent merge-of-main at e778100b48 folded four additional PRs (#4198, #4185, #4204, #4206) into the branch, but neither docs/changelog.mdx nor releases/v0.8.52.md was regenerated to include them. So v0.8.52 will ship WITH the launch-film asset fix, macOS 12 Chrome ceiling, and both bun-install hang bounds, but the human-facing release notes do not name them. The compare/v0.8.51...v0.8.52 link at the bottom of each notes file WILL show the full 20-PR range once the release tag lands, so the ground truth is discoverable. Not a stamp blocker — the shipping code is correct and Vance's PR body already acknowledges changelog regen was a known step during drafting. Worth a post-release note-patch or a v0.8.52.1 changelog PR.

Stamp mechanics

reviewDecision: APPROVED / mergeStateStatus: CLEAN / all required checks: 59/59 SUCCESS / NEUTRAL / SKIPPED at e778100b. Vance vanceingalls and Miguel miguel-heygen both on trusted stamp list; this release PR carries only their content plus already-reviewed folded PRs. Stamping publishes v0.8.52 to the public OSS npm packages.

— Review by tai (pr-review)