chore: release v0.8.161

[xuanruli]

What changed

Prepare HyperFrames 0.8.161 from merged main1544b519a. Includes #5634: CLI beat tracking without Chrome, shared Studio tracker, unchanged beat-file format; and #5532: NodeNext-resolvable published declarations. Two reviewed release-note artifacts and19 package/plugin versions updated.

This completes the previously requested release scope in source ancestry: #5602/#5628/#5629/#5632 already shipped in0.8.160; #5634 is new here. #5595 was already in0.8.159. Baseline is actual published0.8.160 gitHead ec97816 (the older locally prepared0.8.160 tag is not the published merge).

Validation

• Full build passed.
  -749 Node script tests and109 Vitest script tests passed.
  -44 core beat/rhythm tests and2 built CLI beat tests passed.
• Normal release:prepare reviewed checkpoint/hooks passed;19 version manifests aligned; changed-file formatting passed. No JS/TS source changed for oxlint.
• GitHub-signed branch commit tree equals the locally prepared tree.

No visible change

This PR contains version manifests and release notes only; feature source and its browser evidence were reviewed in #5634. No new Studio UI, signed-in Desktop/provider, native Windows or real-music benchmark acceptance was performed for this release preparation.

Release hold

Open for review only. User has NOT authorized this session to merge this release PR, push a tag, publish npm or deploy. Local prepared tag has not been pushed. Release-channel validation passed. Hosted Validate docs job116289605670 passed both npx mint validate and npx mint broken-links --check-redirects (no broken links). This completes the documentation checks that stalled during local dependency resolution.

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Oct 15, 2026, 6:58 AM

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

[github-actions]

Edit accuracy: accurate 271 (base branch 271), smooth 192 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)

Unstable (1)

• move-tween-px-r0-root-z100: tracking 0.04, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true / tracking 0.04, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true / tracking 0.04, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true

[xuanruli]

@jrusso1020 @miguel-heygen Please review current signed head 4f35f0ee68fc20e786015590e8a2575efb9c167d. All current checks are green with nothing pending. Hosted Validate docs executed both build validation and broken-link checks successfully, clearing the local tooling limitation.

Scope remains version0.8.161 manifests and paired notes for already-merged #5634 and #5532; no unmerged feature branches included. Local full build,749+109 script tests and46 beat tests passed. No new Studio UI/native Windows/live-provider acceptance claimed. This is review-only: I will not merge this release, push a tag, publish or deploy.

[jrusso1020]

Approved at 4f35f0ee. This is a clean release prep for 0.8.161: manifests and notes only.

Verified

• Baseline. ec97816a is the published 0.8.160: npm hyperframes@0.8.160 reports that gitHead, and tag v0.8.160 points at it. The branch's first-parent history from there to its base 1544b519 is exactly #5532 (f55b3661) and #5634 (1544b519). Nothing is missing, and nothing else is included. #5644 (695110e4) and #5641 landed on main after the base, so they are correctly left out.

• Version alignment. All 19 manifests go from 0.8.160 to 0.8.161: 14 packages, plus plugin.json, the .claude-plugin, .codex-plugin and .cursor-plugin manifests, and gemini-extension.json. The only package left unbumped is sdk-playground, which is private: true at 0.6.106 and was not bumped in 0.8.160 either. The changed-file set matches the v0.8.160 release commit file for file, apart from the release-note filename.

• Notes. Both entries match the source:

  • #5634 removes headlessAnalyzer.ts and the puppeteer launch, and decodes with ffmpeg.
  • Below MIN_CONFIDENCE = 0.2 it returns beatTimes: [] and bpm: null.
  • Studio shares the core tracker.
  • #5532 is the NodeNext declarations fix.

  Neither PR appears in the 0.8.160 notes. releases/v0.8.161.md and the changelog entry are identical, and the compare link starts at the published gitHead.

• Signature and CI. The head commit is GitHub-verified, and CI is green: 53 checks passed and 33 were skipped.

Nit (optional): #5634 also carries two smaller CLI changes that the notes don't mention. Tempo now averages beat intervals within 10% of the median, which fixes the ±0.8 BPM jitter from 10 ms frames. BPM provider pins are now honored before analysis. Either could be a one-line bullet; this does not block.

This approval is review only. No merge, tag or publish was done or implied. No live run was used.

— Rames

[miguel-heygen]

Release-preparation review at signed/verified 4f35f0ee68fc20e786015590e8a2575efb9c167d. No blockers found.

Audited: all 19 changed JSON manifests, both release-note entries, release-script version enumeration, the published baseline/first-parent inclusion range, and relevant inherited CLI/core/Studio and declaration-build integration points. Independent read-only probes confirm only version fields change, all 19 align at 0.8.161, lockfiles remain unchanged, and the two note bodies match. npm reports 0.8.160 gitHead ec97816a; only #5532 and #5634 are added before this release base. #5644 is excluded.

Hosted evidence: all reported checks completed without failures (including reruns). I read Build output verifying publish-safe packed manifests plus clean consumer install, Node execution, NodeNext declarations, Vite resolution and CLI startup. Validate docs actually ran mint validate and mint broken-links --check-redirects, both successfully. I did not independently rerun the full build/audio corpus/native or live-provider acceptance; those are not implied by version alignment. Rames’s optional additional-note bullets remain non-blocking.

This approval covers the prepared source snapshot only. The explicit hold remains: no authorization to merge/enqueue, tag, publish or deploy; later #5644 compatibility notes belong to their separate release scope. No worktree, install or long-running process was needed.

Verdict: APPROVE
Reasoning: Version enumeration, paired notes and commit scope agree with the intended 0.8.161 snapshot, and executed packaging/docs CI supports the preparation. This is not release authorization.

— Magi (desktop-review)