chore: release v0.8.24

[jrusso1020]

Summary

Release HyperFrames 0.8.24 with a generic producer metadata boundary for extraction failures, corrected catalog tab indicators, and a Windows-sized audio-mix test budget.

This release unblocks the coordinated internal rollout. After publishing, hyperframes-internal #1022 can pin @hyperframes/producer 0.8.24 and preserve safe extraction evidence for Experiment Framework retry decisions.

Included changes

• Producer: transport bounded, query-free extraction failure evidence through generic public error metadata while leaving validation and retry policy to downstream callers (fix(producer): transport safe extraction failure metadata #3592).
• Catalog: keep tab labels synchronized with the sliding active indicator (fix(catalog): sync tab labels with the sliding indicator #3267).
• CI: give the 150-track audio-mix test enough time on Windows runners (test(engine): give the 150-track audio mix test a Windows-sized budget #3587).

Release surface

• 13 public packages move from 0.8.23 to 0.8.24.
• 3 plugin manifests move from 0.8.23 to 0.8.24.
• @hyperframes/sdk-playground remains private at 0.6.106.
• Merging this release/v0.8.24 branch triggers the stable publish from the immutable merge SHA.

Validation

• 63 focused release, publish-workflow, changelog, versioning, workspace-contract, package-subpath, and packed-manifest tests passed locally.
• Stable release-channel validation passed for release/v0.8.24 with dist-tag latest.
• Changelog generation covers the complete v0.8.23...main range and contains no review TODO markers.
• OSS fix(producer): transport safe extraction failure metadata #3592 merged only after its exact-head required checks passed; this release branch reruns the full suite.

Post-deploy validation

• Confirm tag v0.8.24 and the GitHub release point to the release merge SHA.
• Confirm all 13 npm packages report version 0.8.24 and the latest dist-tag.
• Then update hyperframes-internal feat(cli): warn when lambda --width/--height conflicts with composition #1022 to @hyperframes/producer 0.8.24, rebuild it, and rerun CI.
• If publishing is partial, rerun the idempotent publish job before moving the internal pin.

Validation window: 30 minutes after merge. Owner: Jerry.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
hyperframes	🟢 Ready	View Preview	Sep 2, 2026, 1:42 AM

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

[somanshreddy]

Review — v0.8.24 release (verified at a372d9e3)

Release-lens pass. Verdict: content is clean — LGTM once the pending required checks go green (publish-on-merge, so the stamp should follow green CI, not precede it).

• Ships fix(producer): transport safe extraction failure metadata #3592 (the boundary feat(cli): warn when lambda --width/--height conflicts with composition #1022 needs). fix(producer): transport safe extraction failure metadata #3592's merge commit c0887b650 is an ancestor of the release head (git compare c0887b6...a372d9e → ahead_by:1, behind_by:0), so its content is fully included — not just claimed. The producer contract HFI feat(cli): warn when lambda --width/--height conflicts with composition #1022 consumes (errorMetadata/publicMetadata transport) is in this SHA.
• Uniform bumps. All 16 version fields — 13 packages/*/package.json + 3 plugin manifests — move 0.8.23 → 0.8.24, nothing else touched in the manifests. All 13 packages are public (private:false), consistent with "publishes all 13."
• Notes accurate + complete. git compare v0.8.23...a372d9e3 is exactly 4 commits — fix(producer): transport safe extraction failure metadata #3592 (producer metadata), fix(catalog): sync tab labels with the sliding indicator #3267 (catalog tab/indicator sync), test(engine): give the 150-track audio mix test a Windows-sized budget #3587 (engine Windows audio-test budget), + the release chore — and releases/v0.8.24.md and docs/changelog.mdx list all three with correct commit + PR links and are in parity with each other. No missing PR, no rider.
• CI. No failures at review time; several required checks (producer tests, regression-shards, studio smoke, windows CLI, perf) still pending. Publish is gated on green, so LGTM-on-green.

Corroborated by tai + Magi.

[miguel-heygen]

Exact-head release review at a372d9e.

Release surface is clean and rider-free: 18 files only — 13 public package manifests, three plugin manifests, the docs changelog, and reviewed GitHub release notes. All 13 public packages and all three plugins move uniformly from 0.8.23 to 0.8.24; the sole private sdk-playground remains 0.6.106.

The changelog and release notes match the complete v0.8.23..HEAD ancestry exactly: #3587/db92f8ab5, #3267/305de1543, #3592/c0887b650, then this release chore. All three merge commits are ancestors, and #3592’s generic errorMetadata boundary is present in the release tree.

Publish mechanics are correct: publish.yml accepts only a merged release/vX.Y.Z PR for stable, checks out github.event.pull_request.merge_commit_sha, verifies that immutable checkout, creates/verifies the tag at that SHA, publishes the 12 scoped packages plus unscoped hyperframes, and is idempotent per package/release. v0.8.24 and all 13 npm versions are currently absent, so no partial pre-existing state is being hidden.

Verification: 63 release/publish/changelog/version/workspace/subpath/packed-manifest tests passed locally, stable channel validation accepted release/v0.8.24 with dist-tag latest, and the live workspace-contract/subpath checks pass. Every exact-head GitHub check is terminal with no failures; all required contexts pass, including Build, Test, Typecheck, runtime contract, Windows render/tests, and regression.

Verdict: APPROVE
Reasoning: The version surface, immutable publish path, ancestry, release notes, package inventory, and exact-head CI all agree; merging publishes precisely the reviewed 0.8.24 release.

— Magi

[terencecho]

APPROVE at a372d9e34a24d7e17ac97b6c8d4fb06de30efc4e — release-only PR, content clean, CI now fully green at the publish SHA.

Delta is release-scoped, zero riders. 18 files, +61/-16:

• 3 plugin manifests: .claude-plugin/plugin.json, .codex-plugin/plugin.json, .cursor-plugin/plugin.json — only version field bumped.
• 13 packages/*/package.json — all 0.8.23 → 0.8.24, aligned.
• docs/changelog.mdx — v0.8.24 entry prepended.
• releases/v0.8.24.md — new.
• Zero source-code files touched.

Changelog matches merged commits 1:1. git compare v0.8.23...a372d9e3 returns exactly 4 commits, 0 behind:

• #3592 (c0887b650) — Producer safe extraction failure metadata (the errorMetadata boundary HFI #1022 needs).
• #3267 (305de1543) — Catalog tab-label / sliding indicator sync.
• #3587 (db92f8ab5) — Engine 150-track audio mix Windows budget (marked Internal).
• The release chore itself.

All three fixes have commit + PR references; full-range compare link included.

#3592's boundary is present at this SHA. #3592's merge commit c0887b650 is #3593's base — trivially an ancestor. git show a372d9e3:packages/producer/src/server.ts at head shows SafeRenderErrorMetadata interface, extractSafeRenderErrorMetadata, and the errorMetadata field at lines 141/153/165/635/799. The OSS contract HFI #1022 needs is landed.

CI at a372d9e3 — all required checks GREEN (dedup by name-latest-completed, verified via 8-iter poll):
CodeQL (actions/python/js-ts) · Preflight (all 4) · Build · Typecheck · Lint · Format · File size · Validate docs · Mintlify · Producer unit + integration · SDK unit + contract + smoke · Studio load smoke · Studio timeline viewport · CLI smoke (required) · CLI npx shim (ubuntu/macos/windows) · Codex plugin package · Test runtime contract · Fallow audit · Semantic PR title · WIP · player-perf · preview-regression · Preview parity · Perf {load/fps/scrub/drift/parity} · Windows render + Windows tests (studio-core, studio-engine-cli) · regression + regression-shards 1-9.

Zero FAILURE / TIMED_OUT. mergeStateStatus=CLEAN, mergeable=true, behind_by=0 — no rebase.

Publish gate cleared. Merging this SHA will publish all 13 packages + the generic errorMetadata boundary. Once published, HFI #1022 can bump @hyperframes/producer: 0.8.22 → 0.8.24, set the HYPERFRAMES_EXTRACTION_FAILURE_ALLOWED_HOST_SUFFIXES deploy config, re-run CI at the bumped pin, and land — completing the extraction-retry stack. Magi's APPROVE at 5084828964 (same SHA, ~6 min ago) concurs on release-gate readiness.

— Review by tai (pr-review)