chore: release v0.8.163

[miguel-heygen]

What

Release v0.8.163: version bump and changelog.

Changes in this release

• Capture writes inline SVG logos whole, and parakeet takes long audio (fix(cli): capture writes inline SVG logos whole and parakeet takes long audio #5662).
• Timed SVG clips hide outside their window (fix(core): timed svg clips hide outside their window #5661).
• Publishing asks you to log in when it needs an account (fix(cli): ask to log in when publishing needs an account #5670).
• check judges text behind a transparent video by its decoded alpha (feat(cli): judge text behind a transparent video by its decoded alpha in check #5657).
• Render telemetry reports how busy the machine's CPU was (feat(cli): render telemetry reports how busy the machine's CPU was #5646).
• Skill bundle fingerprints skip runtime by-products (fix(cli): skip runtime by-products when fingerprinting a skill bundle #5654).

No visible change

Version bump and changelog only; each change was captured in its own PR.

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Oct 16, 2026, 12:18 AM

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

[github-actions]

Edit accuracy: accurate 271 (base branch 271), smooth 200 of those

The gate passes.
Smoothness is reported in the artifact, not gated. A case fails only if it fails 2 of 3 runs.

Quarantined, measured but not gated (0)

[terencecho]

Reviewed exact HEAD e5aad499a91897666ba185a366458f269b4a7e3c against API/effective merge-base 917ee5d31342f8c8a4a14659679762489cafe665.

Verdict: APPROVE — no introduced blocker established in the bounded release/version/changelog diff and the inspected publication interfaces.

• All 14 public package manifests and five plugin manifests move together from 0.8.162 to 0.8.163. Independent raw-byte checks establish that each manifest changes only its top-level version. Export maps, dependency declarations and package membership are unchanged; the private sdk-playground is not part of the fixed-version public release set.
• Player's runtime CDN pin derives from its package version and agrees with Core. CLI/Producer build defines and the inspected Studio version consumers remain aligned. The portable-plugin packager reads committed manifests and archives the committed tree, so the publication workflow's temporary CLI name rewrite does not substitute dirty metadata into that archive.
• The new MDX entry and release-note file agree on version/date/summary, ordered seven bullets and compare range. The cited seven commits belong to the previous-release-to-BASE range. This verifies release-content provenance, not a fresh semantic re-review or runtime certification of those earlier feature PRs.
• The unchanged publish workflow was read through its actual merged-release-PR route: immutable event merge-SHA checkout, channel validation, matching tag, build/package verification, npm publication, GitHub release notes and plugin attachment. The request explicitly discloses that merging publishes. This approval is a review action, not a separate authorization or claim that I triggered merge, build, publication or release.

Audited: Two independent bounded source passes fully cover the 20 non-changelog changed paths, the entire new changelog insertion and its surrounding MDX boundary. All 21 changed paths/41 present versions and the added file's BASE absence are tree/blob-bound. Cross-manifest, content and publication-interface pairs were inspected. Parent independently reconstructed both current trees, rehashed all changed versions, checked all 19 exact version-only deltas, rebound acquired publication consumers and read the targeted production publication/build/plugin paths. Parent's work is targeted adjudication, not a third complete semantic pass.

Trusting / limits: Historical changelog is PARTIAL: the unchanged tail has byte-equality proof, not semantic transfer from unread history. No whole-repository or historical-feature completeness claim. Repository tests, compilers, build/pack/frozen install, registry/CDN state, native/browser execution and actual release artifacts were not exercised. Public bot status/accuracy receipts remain attributed reports, not my CI execution. No credential access, source edits, direct merge or workflow trigger was performed.

— tai