chore: release v0.7.73

[jrusso1020]

What

Release Hyperframes v0.7.73 across the monorepo packages and editor plugins.

Highlights:

• direct content-addressed Plan v2 publishing for AWS Lambda and GCP Cloud Run
• actionable oversized-plan attribution and bounded planning
• atomic remote-video downloads with transient retry
• typed/observable extraction failures with opt-in retry controls
• FFmpeg-aligned one-frame coverage accounting

Why

This release packages the distributed-render reliability work needed for a
dev-cluster v1/v2 parity rollout, including the fixes for known
PLAN_TOO_LARGE, partial-download, extraction, and one-frame boundary cases.

How

The standard release preparation script bumped all public packages and plugin
manifests to 0.7.73, generated releases/v0.7.73.md, and updated the public
changelog.

Test plan

• Release preparation hooks passed
• All constituent render-fix PRs passed their focused and repository CI
• Release PR CI passes
• Documentation updated

After publication, the exact package version will be deployed and exercised in
the dev cluster only before any production rollout is considered.

[jrusso1020]

• chore: release v0.7.73 #2812 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[vanceingalls]

Reviewed release-prep PR at exact head 527751c871. Clean approve.

Verdict

APPROVE. Standard release-prep contents. Every version bump verified; every constituent-PR commit SHA referenced in the release notes.

Version-bump completeness (16/16)

Verified via gh api /contents/<file>?ref=527751c871 -q '.content' | base64 -d | jq .version:

• All 13 packages/*/package.json files → 0.7.73.
• All 3 .{claude,codex,cursor}-plugin/plugin.json files → 0.7.73.

No package or plugin missed.

Release-notes SHA-reference completeness

releases/v0.7.73.md references every landed fix from the render-success stack, each anchored to its final merged commit SHA:

• #2770 frame coverage → f0c2c7d23 ✓
• #2773 oversized-plan attribution → d699cbf01 + ebb02cafe (scratch reset) ✓
• #2774 atomic download → c01f6b446 + 5ce2eb879 (network-error narrowing) + 4b81f785 (trust-boundary gaps) + 2e84faeb2 (future-use IPv4) ✓
• #2776 extraction taxonomy → 9b63646c8 (typed failures) + c01e1a5f9 (narrow error shapes) + 33ca1de06 (HDR-probe aggregate) ✓
• GCP + AWS Plan v2 publishers (from earlier stack) → 74d7bfde4 + 09998789b ✓
• Studio color-grading feature line → included

Every SHA I checked appears once in the release notes; nothing double-counted or missing.

Delta scope audit

+105 / -16 across 18 files. Expected shape for a version-bump release:

• 15 files × 1 line each = version-string bumps (13 packages + no exceptions).
• 3 plugin manifests × 1 line each = version bumps.
• docs/changelog.mdx +45 (public-facing changelog entry).
• releases/v0.7.73.md +44 (new file with release notes).

No unrelated code changes, no test edits, no configuration drift. The release-preparation script's output is byte-clean.

What I did not verify

• Actual npm-publish behavior (that's post-merge, out of R1 scope).
• The CI matrix — still running at review time; the constituent-PR CIs already passed on their individual merges.

Merge when green.

— Review by Via

[james-russo-rames-d-jusso]

Reviewed at 527751c8713df9739c95d8913e5543f6c5fa8c46.

Clean release-mechanic PR. 18 files, +105 / -16 — every one an expected release-cut artifact:

• 13 published-package package.json bumps (aws-lambda, cli, core, engine, gcp-cloud-run, lint, parsers, player, producer, sdk, shader-transitions, studio-server, studio) — all 0.7.72 → 0.7.73.
• 3 plugin-manifest bumps (.claude-plugin/plugin.json, .codex-plugin/plugin.json, .cursor-plugin/plugin.json) — all 0.7.72 → 0.7.73.
• packages/sdk-playground/package.json intentionally excluded — verified "private": true, last version-bump at c0ac03ca chore: release v0.6.106, stuck at that version since. The release script's exclusion matches prior-release convention.
• docs/changelog.mdx — prepended <Update label="HyperFrames v0.7.73"> block in the same format as the v0.7.72 entry above it; features/fixes/internal sections match the commit range.
• releases/v0.7.73.md (new) — mirrors the changelog entry with a compare link. Same pattern as prior release notes.

Cross-checked the fix list against my stamped R# stack on this thread:

• f0c2c7d23 — Producer: Align frame coverage with extraction rounding ← #2770
• 33ca1de06 — Render: Aggregate extraction launch failures ← #2776
• 9b63646c8 / c01e1a5f9 — Producer: Type video extraction failures / Narrow extraction error shapes ← #2776 landed sequence
• 2e84faeb2 / 4b81f7858 / 5ce2eb879 / c01f6b446 — Engine: Block future-use IPv4 / Close trust-boundary gaps / Narrow network errors / Atomic + retry downloads ← #2774 landed sequence
• ebb02cafe — Producer: Reset distributed plan scratch state ← #2773 stale-.plan-work fix
• d699cbf01 — Producer: Attribute and stop oversized plans early ← #2773 PLAN_TOO_LARGE early attribution

All six fix bullets I stamped are correctly attributed to their landed SHAs. No orphaned bullets, no missing fixes from the four-PR arc.

Grep confirms no lingering 0.7.72 version strings outside the changelog/release-note history (which correctly retains prior release entries).

LGTM. Will stamp once fresh CI settles.

— Review by Rames D Jusso

[mintlify]

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

Project	Status	Preview	Updated (UTC)
hyperframes	🟢 Ready	View Preview	Jul 26, 2026, 9:35 PM

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