The error only said to run --help, so an agent guessed another flag. It now
names every long flag the command declares, and --search points to --query.
capture read --timeout with parseInt, so `--timeout 1s` became a 1 ms
page-load timeout. grade-compare dropped an invalid value without a
warning. Both now use the shared parseTimeoutMs helper that check and
snapshot already use, keeping their defaults of 120000 ms and 5000 ms.
Fixes#7671
* feat(cli): check warns when text leaves the 9:16 social safe areas
* feat(core): safe areas owned by core; check adds --safe-zone standard
* style(cli): format
* refactor(core): name the safe-area band fields
* fix(cli): defects outrank safe-zone warnings at the issue cap
* style(cli): format
* test: read the safe-box constants from core
* fix(cli): copy only media, font, CSS and JS files from outside the project
Publish, cloud render and feedback now copy an outside reference into _ext/
only when its extension is an image, video, audio, font, CSS or JS type,
taken from studio-server's MIME map (new ./mime subpath; .avif added).
Anything else outside the project is left out with a warning and a
left_out entry whose reason is file_type; telemetry counts it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep the new outside-type file under its package's comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): copy the outside media cloud render re-encodes or converts
The outside allowlist now also takes the video, audio and still-image
extensions cloud render re-encodes or converts (.avi, .ogv, .aiff, .tif,
.bmp and the rest), from one shared list offload imports too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): cloud render --json lists the files an upload leaves out
`cloud render --dry-run --json` now reports `left_out`: each file outside the
project that the upload leaves out, with the file that points at it, the
reference as written, its path from the project, the reason (blocklisted or
received) and how many folders above the project it is. A wrapper can ask
before uploading. A full `--json` run carries the same list in its result and
prints a `{"event":"left_out"}` line on stderr for each, beside the warning a
person reads.
Publish, cloud render and feedback's repro send `cli_upload_left_out` when an
upload leaves something out: counts and folder depths only, never a name or
a path.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(cli): keep the left-out report's comment share at its package's
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): launch Chrome with only the env it needs
Every Chrome HyperFrames starts (render, GPU probe, HDR capture, startup
diagnosis, version and shell probes, CLI browsers, inspector) now gets an
allowlisted environment from @hyperframes/core/chrome-env instead of the
whole process env. HYPERFRAMES_CHROME_ENV_PASSTHROUGH names any extra
variable a host needs.
Refs #7623
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): keep the Chrome env passthrough across repeat filtering
The CLI GPU probe filters its env twice, which dropped the names
HYPERFRAMES_CHROME_ENV_PASSTHROUGH adds, so the probe and the render
saw different envs. Keep the passthrough variable itself.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): keep Chrome's sandbox on for local renders where the host supports it
Chrome launched with --no-sandbox on every host. Keep the sandbox on
macOS, Windows and non-root Linux outside containers; drop it as root,
in Docker/Podman/Kubernetes, on Lambda and Cloud Run, and where Linux
restricts unprivileged user namespaces. --no-zygote now ships only with
--no-sandbox, since Chrome refuses it while sandboxed. A sandboxed Linux
launch that fails at startup retries once without the sandbox and warns.
HYPERFRAMES_CHROME_SANDBOX=1|0 overrides the choice.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): cover the Linux sandbox retry in managed browser launches
The off-macOS closed-pipe case now passes --no-sandbox, so it still
pins "no seatbelt relaunch" rather than the new Linux sandbox retry,
which gets its own case.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): honor HYPERFRAMES_CHROME_SANDBOX=1 and latch the fallback on clear evidence only
With the override set to 1, a sandboxed launch Chrome refuses now fails
instead of retrying unsandboxed. A bare startup exit (TargetCloseError)
retries that launch without the sandbox but only latches the sandbox off
after a second one, so a single unrelated early kill no longer disables
it for the rest of a long-lived process. Chrome naming the sandbox in its
error still latches at once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix: track local Studio sharing CTA intent
* fix: tag local Studio and CLI share upgrade links with where they came from
The local Studio share modal's Upgrade to Pro link opens
/pricing?from=cli&entry=local_studio_share, and hyperframes share's source-files
notice links /pricing?from=cli&entry=cli_share, so the pricing page can tell
which link a visit came from and return the visitor to their terminal. The
modal accepts its own pricing page with any query, still only on
hyperframes.dev's two origins. share_upgrade_clicked carries
cta=share_modal_upgrade.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: name the local Studio upgrade CTA and drop the explaining comments
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep the local Studio upgrade link's return page unchanged
Only entry=local_studio_share is added to the local Studio share window's
Upgrade to Pro link. from=cli would have told these buyers to go back to their
terminal after checkout, but they return to a browser tab. hyperframes share's
link keeps from=cli, as the CLI's other upgrade links do.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Local Studio mode runs Vite in the resolved @hyperframes/studio folder, so the
project folder decided which config and binary ran. Use it only when the
project resolves to the same Studio the CLI itself resolves (a source checkout
running its own build) or when HYPERFRAMES_LOCAL_STUDIO=1 is set; otherwise
serve the embedded Studio.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): share rendered videos through unified reviews (#7135)
* feat(share): attach editable project sources to reviews (#7137)
* feat(share): measure local sharing outcomes (#7138)
* feat(cli): stage the sixty-day publish transition (#7136)
* feat(studio): share review pages from local preview (#7140)
Advertise the CLI sharing bridge before bootstrapping it so standalone Studio does not
request unsupported routes. Preserve origin and session checks.
Budget the intended sharing artifact: clean main packs at 8,060,519 bytes versus
8,162,979 with sharing (8,169,168 in CI). Required policy and Unicode tables, bundled
sharing code, and Studio controls account for the growth. Set the packed-only budget
to 8,577,627, following the 5% headroom convention; retain the unpacked cap and all
package checks.
* fix(share): persist refusals and improve CLI retry feedback
* fix(ci): restore render diagnostics and include sharing workspace
* fix(cli): keep sharing owner error codes stable
* fix(share): clarify update feedback and align audience changes
* fix(share): clarify updates and avoid scratch-file rerenders
* fix(cli): report active shares and preserve update channels
* fix(cli): resolve update channel when checking registry
* fix(ci): refresh sharing package budgets after rebase
* fix(share): require consent before uploading project files
* feat(engine): decouple transparent background from png capture format
PNG capture used to imply a cleared page background. A new
CaptureOptions.transparentBackground lets lossless opaque PNG capture
(4:4:4 MP4 output) keep the page background. Absent, it still follows
format === "png", so alpha output and motion blur are unchanged.
Opaque PNG skips drawElement, whose verification and worker-encode
paths are JPEG-only.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(engine): add 4:4:4 chroma option to getEncoderPreset
getEncoderPreset takes an optional chromaSubsampling ("420" by
default). "444" returns yuv444p for SDR MP4, so libx264 encodes the
High 4:4:4 Predictive profile and odd sizes need no even padding.
WebM, MOV and HDR presets ignore it. The ChromaSubsampling type is
exported for the producer.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(producer): chromaSubsampling render option with lossless png capture
RenderConfig.chromaSubsampling ("420" by default) opts an SDR MP4
render into 4:4:4. "444" encodes libx264 yuv444p and captures every
frame as opaque PNG: Chrome's quality-100 JPEG is already 4:2:0 on
beginFrame and screenshot capture, and drawElement can fall back to
screenshot mid-render, so PNG is the only capture that keeps the
colour. drawElement is turned off for these renders.
The probe and main capture options share resolveCaptureSurface, so
they cannot disagree on format, quality or background.
Formats other than mp4, GPU encoding and HDR output are rejected
before any work starts, auto-detected HDR sources fail before capture,
and distributed requests refuse 444. The default render is unchanged.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(producer,studio-server): accept chromaSubsampling on render routes
The shared parseEncoderOptions validates chromaSubsampling and answers
400 for "444" with a non-mp4 format, gpu, or force-hdr, so a request
that would come back 4:2:0 never starts a render. The Studio render
route, both Studio adapters and the producer HTTP server forward it.
The producer server also refuses "444" with outputDynamicRange "hdr",
which parseEncoderOptions cannot see.
No Studio UI control; the option is route-level like crf and hdrMode.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): add --chroma-subsampling flag
`hyperframes render --chroma-subsampling 444` opts an SDR MP4 render
into full-resolution chroma (yuv444p with lossless PNG capture). The
default stays 420. The plan rejects 444 with a non-mp4 format, --gpu
or --hdr before anything renders, with a usage error that names the
conflicting flag.
The value reaches the local render request and, only when it is 444,
the Docker argv, so default Docker invocations are unchanged.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: document 4:4:4 chroma subsampling
Add a "4:4:4 masters" section to the rendering guide: when to use
--chroma-subsampling 444, why it captures PNG, the measured chroma gain
(large for text and UI, none for footage and gradients), its limits,
and a player compatibility table to be filled in from testing.
Document the flag in the CLI reference, the built-in rendering docs and
the hyperframes-cli skill reference (with the regenerated skills
manifest), and the chromaSubsampling option in the producer docs.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: add 4:4:4 player compatibility results
Fill the 4:4:4 compatibility table from testing H.264 High 4:4:4
Predictive output. Chrome 155, Edge 155, VLC 3.0, Safari on iOS 26.6
and Safari 26.6 on macOS play it, and so does AVFoundation on macOS
26.6, the framework QuickTime Player plays through. Firefox 157 on
Windows and both Windows media players do not.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: note the measured render cost of 4:4:4 output
Replace the vague "slower capture" note with measured numbers: a text
and UI composition rendered in about twice the default time, full-frame
footage in about three and a half times, because PNG encoding cost grows
with image detail.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): reject chromaSubsampling 444 in distributed render config
Distributed configs have no chroma field and validateDistributedRenderConfig
ignored unknown keys, so a JS caller passing chromaSubsampling: "444" to the
Lambda or Cloud Run SDK got a 4:2:0 file with no error. Reject it, and make
the rendering guide say so precisely.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): check a 444 render reaches the encoder as yuv444p
Every helper had tests, but nothing checked the orchestrator passes
chromaSubsampling through, so dropping it from the encoder preset or capture
surface would turn 444 renders back into 4:2:0 with all tests green. Render a
small fixture with "444" and with the default and check pix_fmt with ffprobe.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(producer): move the 444 drawElement gate into a helper
Keeps runCompileStage under the fallow complexity threshold.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: keep comment share at or below the merge-base
comment-ratchet failed on 11 files this PR touched. Keep the 4:4:4
rationale once in chromaSubsampling.ts, move the distributed-render
reason into its error message, and cut the rest.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): check a 444 render captures full-resolution chroma
The encoder check alone passes when chromaSubsampling is dropped from the
capture surface: frames are captured as JPEG and encoded yuv444p with
4:2:0 colour. Put a red/blue edge at an odd x, inside a 4:2:0 chroma
pair, and require the two pixels to differ in Cb.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): trim the chromaSubsampling.ts header to the package comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: finish switching to capturesAlpha from #6262
The merge that adopted main's transparent / capturesAlpha left these files
uncommitted, so resolveCaptureSurface still returned transparentBackground.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(engine): use transparent / capturesAlpha from #6262
main added CaptureOptions.transparent and capturesAlpha (#6262), which do
what this PR's transparentBackground did. Use them, keep the PNG check in
drawElementWorkerEncodeEligible, and re-pin test-classification.mjs and
the skills manifest against current main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): cut the 4:4:4 comment blocks to one to three lines
The reasoning lives in the PR description with the measurements.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: reconcile 4:4:4 chroma with latest main
Keep main's video-layer capture overrides, template entry resolution,
ProRes profile parsing and blur-differential tests alongside the chroma
option, and fold the encoder sub-parsers into one loop.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: keep main's compile-stage tests and regenerate the skills manifest
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Follow-ups from review on #7443 and #7444:
- The quote hint returned the first run of words that existed, so a
"Final Cut/" folder hid "Final Cut export.mp4". It now names the longest.
- "--compare=my clip.mp4" got no hint; the value after = now starts a run.
- The telemetry section lists the skill a reverse or templates command ran
for, and the HeyGen session id a recorded reverse run carries.
* feat(cli): reverse and templates report their own runs; commands say which skills are installed
Gaps in what skill telemetry can answer for /reverse-any-video and
/style-sampling:
- The skill's beacon fires only when the agent runs it, and agents often
skip it. `reverse start` and `templates pull` now send `skill_invoked`
with `source: command`; beacons carry `source: beacon`. A person counts
once.
- style-sampling renders were never tagged. A pull marks the project the
episode is built in (only a folder that is already a project).
- Installs of an on-demand skill were invisible. `cli_command` carries
`skills_installed` and `skills_outdated`, the names from the cached
background skills check, so "never triggered" and "not installed" can
be told apart.
- `auth status` signed out exits 1 with a bare "Command failed", which
reads like a login failure. It now carries `NotSignedIn`, and an auth
error its own cause.
And a step that gets lost: a reverse started signed out often goes on
without ever trying to sign in. `reverse start` signed out now prints
`login_command` and a `next` line in the JSON the agent reads, not only
in the skill's reference.
* refactor(cli): keep comment share at the base in the reverse telemetry files
* fix(cli): command runs get their own event, counted once per piece of work
Review on the first cut: `skill_invoked` from the commands doubled the
#7176 beacon's single observation, and it fired before any work.
- `reverse start` and `templates pull` send `skill_command_ran`, not
`skill_invoked`; the beacon is back to its #7176 shape.
- `reverse start` sends it after the probe, with `signed_in` and the
reverse `session_id` that keys a retry; a video it cannot probe sends
nothing.
- `templates pull` sends it only when it downloads; a re-pull or a
refused pull sends nothing.
- A skills check that finds no install forgets the installed names.
- `auth status` failures carry only a code, never the auth error's text.
* feat(cli): add 1440p resolution presets to --resolution
Adds landscape-1440p (2560x1440), portrait-1440p (1440x2560) and
square-1440p (1440x1440) next to the existing 4K, 720p and 480p tiers,
with the aliases 1440p, 2k and qhd plus 1440p-portrait and 1440p-square.
1440p joins the aspect-agnostic aliases, like 720p and 480p.
Every validator derives from CANVAS_DIMENSIONS, so no logic changes: a 4K
composition renders down to 1440p through the existing smaller-preset
path, and a 1280x720 composition supersamples to 1440p at an exact 2x.
A 1920x1080 composition is still refused by the non-integer-scale check
(4/3); fractional scale factors are not part of this change.
Refs #6309
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(cli): clarify 1440p aliases and repair skill validation
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-authored-by: James <james.russo@heygen.com>
* feat(cli): check returns an unchanged project's last pass in about a second
* fix(cli): the check cache hashes files without a stat race and its tests run before the signal test
* test(cli): the warm check test compares two real runs, not a run and its cached pass
* feat(cli): check --no-craft skips the craft pass for a render preflight
* fix(cli): the check cache keys on timeout, env and large files and never replays a moved tree
* style(cli): format the check cache
* fix(cli): the large-file cache test waits for the clock tick it depends on
* fix(cli): the check cache keys on the browser and on scripts under .hyperframes
* fix(cli): the check cache ignores the video copies the check itself touches
* fix(check): lint and check skip compositions the project never mounts
* refactor(lint): let two new names stand without doc comments
* test(cli): lint tests that lint unmounted files say so
* fix(check): masked or clipped-away text no longer counts as overlapping
* test(check): name the masked-overlap fixture's headings in plain words
* test(check): word a gradient-stop comment without an acronym
* fix(check): a moved or content-box mask keeps today's overlap verdict
The desktop app can't run an edit while a preview of the project is
running, because the preview holds the project's history lock. Following
the hint that `preview --background` prints therefore left the app's edit
waiting until someone stopped the preview by hand.
`hyperframes open` now stops a background preview of the same project
before handing it to the app, and prints one line saying so. It only
stops a preview it can prove it started (a saved session whose wrapper
process still owns the server). Any other preview is left running, and
`open` prints the exact `preview --stop --port N` command instead. With
--json the result carries a `preview` field.
The hint that `preview` prints now says that `open` stops a background
preview, or that a foreground one must be stopped first. The project
template and the CLI skill's preview reference say the same.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(check): a Chrome that never becomes ready ends the check with a named error
* fix(check): name the Chrome start window in code instead of comments
* feat(cli): audio --read --layer music|sfx|voice reads a one-layer file whole
A caller that knows a file holds a single layer can declare it: the file is
read whole as that layer with no stem separation and nothing uploaded.
Without the flag the read is unchanged. An unknown layer is rejected.
Consumer: heygen-com/experiment-framework#66322. Proposal OK'd by Rory
(C0BEH487Q7R, 2026-11-07).
Co-Authored-By: Jerrai
* chore(cli): drop added comments from audio read layer
Co-Authored-By: Jerrai
* feat(core): motion blur reports what a composition holds, as counts
The runtime scans a composition once per blur scan, on both tiers, and reports
counts of what it holds (canvases, video, frames, custom elements, clips, masks,
scroll containers, 3D, blend modes, and movers that overflow, sit under other
content, hold fixed children or carry pseudo-elements outside their box), plus
whether pose reads need callbacks. Counts only: no ids, classes, text or URLs.
The engine puts the non-zero counts on its [motion-blur] line and hands the
parsed report to the perf summary; the producer aggregates workers (first report
wins, failed frames sum) and the CLI sends motion_blur_* properties on
render_complete, from the CLI and from Studio renders.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(cli): disclose blur counts in telemetry docs, raise inspector budget
The runtime fingerprint code is bundled into @hyperframes/inspector, which
puts its unpacked size 2.2 KB past the 1% tolerance. The telemetry docs now
list the composition counts the CLI sends with a blur render.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* feat(producer): render long videos with windowed source frames, behind HF_VIDEO_FRAME_WINDOW
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): windowed calibration sees real frames, and the late full extraction reports itself
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): windowed frames match a full extraction, frame for frame
Renders ten compositions twice on the segmented route, with and without
HF_VIDEO_FRAME_WINDOW, and compares FFmpeg framemd5 of the two outputs: a
mid-clip start, NTSC 24000/1001, a loop crossing a slice edge, a playback-rate
ramp, a held tail, two clips of one file, a VFR source beside a CFR one, two
workers, auto workers (capture calibration runs), and motion blur, which
declines the window. Each pair must also report the same capture mode.
A separate test samples segment-frames during a four-segment, two-worker
render and holds its peak under workers x segment frames x the largest frame
file x 1.2, and checks the folder is empty once the render closes.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(producer): windowed frames test finds its own work dir and asserts what it claims
Find the render's work dir with resolveRenderWorkDirPrefix and the owner record's pid, so
the peak test works on Linux and never samples or deletes a concurrent render's dir.
Assert the measured worker count, calibration, and the exact up-front frame count of the
VFR video. Retry a dead Chrome only with HF_TEST_RETRY_BROWSER_STALL=1, and fail a case
whose windowed render alone needed it.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(producer): windowed segments honour keep-segments and cleanup never fails a render
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(producer): trim the comments the windowed frames route added
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): the VFR-beside-CFR extraction test moves to the integration lane
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): raise the package size budget for windowed video frames
The new segment frame modules add about 9 KB to the packed producer package.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): windowed frames header says what the real runs measured
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): normalize-audio --reference stops short of the peak ceiling instead of refusing
* docs(cli): the README says normalize-audio stops short of the ceilings instead of refusing
* feat(cli): check --budget stops the whole check in time and reports what it found
* fix(cli): keep check's comment share where it was
* fix(cli): a --budget that runs out before any check step is waiting is not an unhandled rejection
* feat(cli): info --media lists every clip the render hears, on the film's clock
* fix(cli): info --media leaves out a clip that starts past its media's end
* fix(cli): keep the heard-clips doc line within 120 characters
* fix(cli): every settings file follows HYPERFRAMES_CONFIG_DIR
* fix(cli): the media-use skill copy reads its config from HYPERFRAMES_CONFIG_DIR too
* test(cli): expect the config folder as a normalized path on every platform
* chore(skills): refresh the media-use manifest hash
* fix(cli): a moved settings folder starts from ~/.hyperframes, keeping an opt-out
* fix(cli): drop the updater's unused path import
* style(cli): keep the settings-seed comment under 120 characters
* fix(cli): a preview's session follows HYPERFRAMES_CACHE_DIR when it is set
* docs(cli): background previews follow HYPERFRAMES_CACHE_DIR
* test(cli): unstub the preview test's env in a block body
* test(cli): clear HYPERFRAMES_CACHE_DIR in the CLI's test home
* fix(cli): registry cache, search model, catalog and catch-up follow HYPERFRAMES_CACHE_DIR
* style(cli): format the media search cache test
* test(cli): compare the model path against an absolute cache folder on Windows too
* fix(cli): both catalog readers treat an empty HYPERFRAMES_CATALOG_ARTIFACT_DIR as unset
* fix(cli): reverse start makes its --dir project, and init takes the video already in it
Bug bash: production has no reverse/start route yet, so every run came back unrecorded,
and reverse start then made no folder and no hyperframes.json. The agent downloaded the
video into the folder it named, and init refused it as not empty, so agents moved files
around. reverse start now makes --dir and stamps it with the skill when no session is
recorded, and init accepts a folder whose only other files are its --video or --audio.
* refactor(cli): say in names what the comments said, so the comment share holds
* fix(cli): init keeps an in-folder source safe, and saved_to only names a stamped config
- Only an audio or video file in the folder counts as the source; a file named
index.html, meta.json or AGENTS.md is refused, so the scaffold never writes over it.
- An in-folder .mp4 that needs transcoding goes to <name>.h264.mp4 beside it,
instead of being both ffmpeg's input and output.
- reverse start names saved_to only when hyperframes.json now holds the skill;
a broken config is left as it was and saved_to is null.
* fix(cli): init transcodes an in-folder .MP4 beside it on case-insensitive disks too
original.MP4 and original.mp4 are one file on macOS and Windows, so the
same-file check now ignores case. The test's ffprobe call gets its --.
* fix(cli): init tells the source in the folder by the file, not its spelling
On a case-blind disk --video original.mp4 names Original.MP4, so the folder
check and the copy now compare device and inode; a source named in another
case is accepted and never copied onto itself.
* fix(cli): init transcodes only to a name with nothing at it, so a linked alias is never the output
The folder guard admits every alias of the source by file identity, but the
transcode output was chosen by path spelling. A hard link or symlink at
name.mp4 or name.h264.mp4, or a source named through a linked folder, made
FFmpeg (-y) rewrite the original. The output is now the first of name.mp4,
name.h264.mp4, name.h264-2.mp4, ... with nothing at its path (lstat, so a link
counts), which also covers a case-only spelling on a case-blind disk.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXN7wsMK6GqT3MNtqXw
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(cli): remove OpenRouter as a vision provider for capture
* refactor(cli): tidy comment and formatting after OpenRouter removal
* refactor(cli): shorten the thinking-budget comment
* chore(skills): refresh the skills manifest for the film reference
* fix(cli): check stops after 2 minutes of video copies and says how to finish
* fix(cli): check copies only the stretch of a video the composition plays
* docs(cli): check copies only the played stretch of a long video
* docs(cli): shorten two comments on the copy window
* fix(cli): finding crops and frames get the same copy windows as the check
* fix(cli): drop a comment the ratchet counts
* refactor(studio-server): keep runFfmpeg under the complexity gate
* fix(producer): a wedged effect scan or screenshot-session open trips the 60 s stall watchdog
The sequential streaming watchdog raced only the capture call. Session init
(where the fast-capture effect scan runs) and opening the screenshot session
for effect frames waited on CDP's protocol timeout instead, which scales with
output area up to 30 minutes, so a starved page hung a render for ~25 minutes
before the watchdog saw the next frame. The effect scan now gives up when a
chunk outlasts its 120 s budget, opening the effect-frame session gets its own
no-progress window, and session init gets a 300 s one; each trip retries on a
fresh session like any other stall.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): one local render at a time per machine; a second waits and says for whom
Renders started side by side from different sessions starve each other until
frames stop landing. `hyperframes render` now takes a machine-wide slot (a lock
file in the HyperFrames cache directory, held by pid) after its preflight and
holds it for the render or the whole batch. A second render waits and prints
the pid and project it is waiting behind; `--no-wait` fails at once instead.
A holder whose process is gone is taken over, and HYPERFRAMES_RENDER_LOCK=off
restores side-by-side renders. `--workers` is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(lint): flag fonts a cloud render cannot resolve, including the font shorthand
Lint read only `font-family`, so `font: 500 16px "PingFang SC", sans-serif`
passed while the renderer, which reads the shorthand too, drew the installed
Mac font locally and the cloud refused it. The shorthand now counts for
font_family_without_font_face (its parser moves to @hyperframes/parsers so
core and lint share one), and a new font_face_local_only warning names an
@font-face whose only sources are local(): it renders here and falls back in
the cloud. The rule's hint and the format reference stop recommending local()
for OS fonts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): a cloud render that refuses a font says which project files use it
The cloud's "fonts that could not be resolved: PingFang SC" named no
composition. For a render submitted from a local project, the failure now
lists each refused family with the project files that name it, and says how
to ship the font so the cloud can use it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli): keep comment shares and exports within the gates, and split the single-render notes out of executeHeldRender
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(parsers): read a spaced line-height slash and var() before the size in the font shorthand
`font: 16px / 1.5 Inter` was read as the family `/ 1.5 Inter`, and
`font: var(--weight) 16px Inter` as `16px Inter`, because a var() counted as
the size. The parser now follows the shorthand grammar: optional style,
variant, weight and width keywords (or var()), then a length, percentage,
keyword or calc() size, then a `/ line-height` in any spacing. When no size can
be told apart from a var(), it says so: lint skips that declaration instead of
reporting a missing font, and the renderer keeps its best guess.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): say the render slot is one per user account, not per machine
The lock lives in the account's HyperFrames cache folder, so renders by two
user accounts never queued behind each other while the messages, flag help and
docs said "this machine". They now say "per user account" and that
HYPERFRAMES_CACHE_DIR set to a shared folder shares the slot across accounts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): reclaim a render lock or takeover file left half-written
A lock or `.break` file that exists but cannot be parsed (a crash mid-write
where hard links are unavailable) was never reclaimed: a waiting render waited
forever and --no-wait refused forever. Once such a file is older than any real
write (5 s by mtime) it counts as abandoned: the lock goes through the same
`.break` takeover as a dead holder's, and a takeover file is removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): opening the capture session counts against the setup stall budget
The sequential streaming attempt opened its own capture session (Chrome launch
and new page) before the setup watchdog and outside the attempt's cleanup, so a
wedged launch still waited for the protocol timeout. Opening now shares the
300 s setup window with session initialisation, a trip fails the attempt like
any other sequential stall, and a session that finishes opening after its
attempt gave up is closed instead of leaking a browser.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(parsers): keep the shorthand result type module-private
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): reclaim an unreadable render lock only when its writer is provably gone
Where hard links are unavailable the lock is created by an exclusive open and
then written, so a contender paused between the two leaves an unreadable lock
while it is still alive. The 5 s mtime grace took such a lock over, and both
processes then held the slot. Each contender now writes an owner marker under
a name only it can take (pid plus random suffix, holding its process identity)
before it creates the lock, keeps it while it holds the slot, and removes it
otherwise. An unreadable lock or `.break` is reclaimed only when no other
contender's marker belongs to a live process; markers of dead processes, or of
a reused pid, are deleted. No reclaim is decided by time alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: split acquireRenderLock and the streaming-stage session stub under the complexity gate
acquireRenderLock hands contender setup and a single marked claim to their own
functions, and the test stub for createCaptureSession splits its held-open
cases from the fake session it builds, so neither exceeds Fallow's cognitive
or CRAP thresholds. Behaviour is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(ci): raise the CLI and engine size budgets for the watchdog, lock and font-lint additions
Main's CLI unpacked size was already ~0.99% over its budget; the render lock and
owner markers push it past the 1% tolerance. The CLI unpacked budget takes the same
value as #7169 and #7170 (25,159,107) so the PRs merge cleanly. The engine's packed
size grows by about 4.7 KB for the effect-scan and session-open watchdogs; its packed
budget moves to 5% above the measured 467,097, as the budget file's headroom rule sets it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(parsers): a var() size glued to its line height is the shorthand's size
`font: 700 var(--size)/1.1 "Inter"` read as no family at all: the token was
tested whole against var(), and the slash after it hid that it was the size,
so the renderer injected no face for Inter. A var() followed by `/ line-height`
(glued or spaced) can only be the size, and is now read as one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(parsers): split the shorthand size search out of parseFontShorthand
Keeps parseFontShorthand under Fallow's cognitive-complexity gate; behaviour is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): render lock never removes another render's takeover, knows a reused pid, works in a shared folder and on Windows
- A `.break` takeover file is removed only by the render that wrote it. One
whose writer is gone stops the render with the file to delete, instead of
being removed on an earlier reading, which could remove a live `.break`
written since and let two renders hold the slot. The takeover re-reads the
lock under its own `.break` right before replacing it.
- The lock record keeps its holder's process start time, so a pid that now
belongs to another process (an OOM-killed render in a container with a
persisted cache) no longer holds the slot forever.
- The `locks` folder is created writable for every account, so accounts
sharing HYPERFRAMES_CACHE_DIR take turns instead of the second failing with
EACCES; a folder this account cannot write in says how to fix it, and
another account's file that cannot be removed is left, not fatal.
- Windows: no PowerShell start-time lookup per check (pid liveness only), a
file another handle holds (EPERM/EBUSY/EACCES) reads as held, a lock that
vanished is retried once instead of in a tight loop, and a wait stops when
its signal aborts. The tests end every acquire they start before removing
their folder, and the paused contender writes through its open descriptor.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(ci): raise the lint packed size budget for the font-shorthand rule
With main's audio-attribute rule (#7169) merged in, the font-shorthand and
local()-only font findings take @hyperframes/lint's packed tarball to
181925 bytes, over the 179338 budget. The new budget is that measurement
plus the usual 5% headroom.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): an interrupted templates pull leaves no partial folder
Unpacking now runs tar asynchronously and removes its .part folder on
SIGINT/SIGTERM/SIGHUP before re-raising the signal. Part folders carry the
owning pid, and the next pull clears any whose process is gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): auth status and templates pull say when HeyGen cannot be reached
Offline, both commands waited on unbounded requests and then printed only
undici's 'fetch failed'. A new networkFailure helper names the host, the
reason (DNS lookup, no route, refused, no answer in time, dropped) and the
next step. The account and token-refresh requests now time out after 15 s,
the template link after 15 s, and auth status reports an offline refresh at
once instead of retrying with the stale token. describeCauseChain moves into
the helper so the registry and auth share it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): preview leaves the project's HTML files as they are
Opening a project in preview stamped data-hf-id into every composition on
disk. The preview route and every source mutation already mint the same
content-keyed ids in memory, so the startup pass is dropped: files gain ids
only when an edit to them is saved. The .hyperframes folder is still made
before the watcher starts, so the preview cache creating it is not reported
to Studio as a manifest change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): check runs the browser audits past a lint error
A lint error made check skip runtime, layout, motion and contrast, so one
known lint error hid every browser finding. The browser pass now runs
whenever there is a composition to load, and the lint error still fails the
check. Only a root with no data-composition-id skips it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): no desktop-app line for CI or a script reading render output
The 'Keep editing by chatting with Framey' line printed on every render and
preview, including CI and piped runs where nobody can open the app. It now
prints for a person at a terminal, and for a coding agent, which the
hyperframes skill tells to pass the line on; CI and other non-TTY runs get
nothing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): cloud render takes a composition at any aspect ratio
A 1920x960 composition got 'server will default aspect_ratio to 16:9'
although the render kept 1920x960: at 1080p the cloud renders at the
composition's own size and aspect_ratio only picks a 4K preset. The CLI now
names the detected ratio (2:1) and says the size is kept, takes
--aspect-ratio as any W:H checked against the composition, sends only the
16:9, 9:16 and 1:1 the API accepts, and refuses a 4K render of any other
ratio before upload, where no preset fits.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(media-use): a weak sound-effect match says so instead of passing silently
resolve --type sfx returned a HeyGen sound at any score down to 0.4, and a
project file that shared one word of its name with the intent, with nothing
to tell them from a real match. Such a result now carries a match object in
the JSON ({score, min_score, low_confidence} or the matched words and the
intent the file was resolved for) and a low-confidence line on stderr. A
HeyGen search with no hit says so with the min score it used, and a sound
effect nothing matches fails with 'no sound effect matched'.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): media-use avatars lists the film account's avatar looks
Templates had to reach for 'heygen avatar list', a separate sign-in that can
be another account. 'media-use avatars' lists the private looks on the
HyperFrames account making the film (GET /v3/avatars/looks?ownership=private,
following next_token up to --limit) as {avatars: [{avatar_id, name, ...}]},
the id that 'generate --type avatar --avatar' takes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(skills): leave style-sampling's avatar line to #7164, which owns that skill
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): templates pull removes only the part folders it marked as its own
The abandoned-part cleanup deleted any sibling named '<slug>.part-*' whose
next token was not a live pid, so a person's own 'sample.part-notes/',
'sample.part-reference.txt' or a symlink went with it. A pull now writes an
ownership marker (owner tag + pid) into its part folder, and the cleanup
removes only a real directory with the generated '<slug>.part-<pid>-XXXXXX'
name whose marker names a dead pid. Files, symlinks, unmarked folders and
older unmarked parts are left alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): media-use avatars says it is offline when the login refresh cannot reach HeyGen
A network failure while refreshing the stored login was reported as 'no
HeyGen sign-in' with 'auth login' as the fix, though the login was still
there. It now keeps the network failure's message and next step.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(media-use): a reused weak sound keeps its low-confidence advisory
The first resolve of a weak HeyGen sound or a name-matched project file
flagged it, but an identical second resolve hit the project manifest and
returned it with no match object. The advisory is now rebuilt from the
record's provenance (the stored score, or the adopted file's name) on reuse.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(cli): keep the comment share of files this branch touched from rising
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): no check-then-use on pull markers, and the download is never written to disk
CodeQL flagged the downloaded bundle written to a file before tar read it,
and a stat-then-read in the preview test. The verified archive now streams
into tar's stdin, so no network bytes reach a file the CLI writes. The
abandoned-part scan takes the entry type from readdir instead of an lstat,
reads the ownership marker through one O_NOFOLLOW descriptor it fstats, and
the preview test reads each file once instead of stat-checking it first.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(ci): raise the CLI's unpacked size budget to 5% over its measured size
main's @hyperframes/cli was already about 0.99% over its 23722874-byte
unpacked budget, so this branch's additions (networkFailure, the avatars
command, the larger skill references) tip it past the 1% tolerance. This is
the same value #7169 sets, 25159107 bytes (5% headroom over the measured
size), so the two PRs merge cleanly.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(cli): split the pull-marker check and share the token-endpoint POST
Fallow flagged pullOwner (CRAP 49.5, cyclomatic 13) and a 28-line clone
between refreshOnce and exchangeCodeForTokens. pullOwner is now the name
match, the O_NOFOLLOW marker read and the marker check as three small
functions, with the same behaviour. Both token requests go through one
postToTokenEndpoint, which keeps the 15 s timeout and the named network
failure.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): a 4k cloud render checks the exact size against its preset before upload
The aspect detector matches a ratio within ±0.05, so at 4k a 1920x1055
composition was sent as 16:9 and 1000x980 as 1:1, and the producer then
refused both as an aspect mismatch. At 4k the matched ratio's preset
(landscape-4k, portrait-4k, square-4k, the ones the API maps it to) now goes
through the producer's own checkOutputResolutionCompatibility, and a
composition it does not fit is refused locally with the producer's reason
and the 1080p alternative. 1080p, where the render keeps the composition's
own size, is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): surface outdated CLI and skills to agents; add hyperframes update
Single commit of #7094 on top of main (no merge commits through the signed
GraphQL path). Includes: 2h update/skills check interval and stale-cache
recheck; `_meta.checkedAt`, `_meta.skillsOutdated`, `_meta.skillsMissing`;
`_meta.updateNotice`, one sentence for the agent to relay to the person, at
most once a day per project (brew/npx-aware command, omitted under CI, the
update-check opt-out and agent plugins); `hyperframes update [--check]
[--yes] [--json]` (CLI then skills at the installed CLI's tag; brew
version read back); doctor names the running binary and its channel; the
hyperframes-cli skill gets one line to pass the notice on, naming no
command. Keeps main's install-target skills check (#7120) in updateSkills.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): update notice names a command that moves this install
- `_meta.updateNotice` (and `update --check`'s skills command) now name a
command that moves the running install: a global npm/pnpm/bun/brew CLI
runs its own `hyperframes update` (or just its manager's command when
only the CLI is behind), since `npx hyperframes` would run a project's
copy or a fresh npx one; a project-local CLI moves with its project's
manager by lockfile (`npm install`/`pnpm add`/`bun add`/`yarn add
hyperframes@<v>`), which `update --yes` now names too instead of
`npx hyperframes@latest`.
- `update`'s confirmation hint states a fact and names no step for the
agent: "Updating is the person's call; `update --check` only reports."
- `upgrade --json`, `upgrade --project --json` and every `skills` JSON
output leave out `_meta.updateNotice` (NO_UPDATE_NOTICE), like `update`.
- dailyNotice: a null/non-object file reads as empty and is repaired; a
future timestamp is stale; writes go through a 0600 tmp file + rename;
withMeta never throws from the notice.
- Docs: --json without --yes exits 2; plugin `update` exits 1
(plugin_managed); full `_meta` sample; per-install notice commands.
`update --check` says "npm registry not reached" instead of "latest".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): the voice a film uses is listed from the HyperFrames account, never the heygen sign-in
* fix(cli): drop a comment line and an unenforced range from the voices command
* test(cli): check waits as long as snapshot for the composition by default
* fix(cli): check waits for the composition as long as snapshot and render do
* docs(cli): check's --timeout default matches snapshot and render
* fix(cli): check's render-ready warning advises a --timeout above the new default
* fix(cli): drop the doc comment on the render-ready warning suffix
* style(cli): format checkBrowser.ts
* feat(cli): billing top-up becomes add-credits, top-up stays as an alias
* fix(cli): keep the skills manifest and core-skills test in step with add-credits
* revert: leave the core-skills test to its own PR
* feat(cli): billing shows the price and pays from the terminal on Enter
* fix(cli): the top-up page opens at the credit packs
* test(cli): billing tests cover the checkout offer with no terminal
* fix(cli): the purchase wait runs while Press Enter is open
reverse/start answers upgrade_url: null when no plan can be bought right
now. The CLI treated that like a missing field and built its own plans
link, so a Free account under gate "block" was sent to a page where it
can't buy. Now null means no link anywhere: the JSON prints
upgrade_url: null and subscribe_command: null (billing subscribe would
open that same plans page), the refusal says a plan can't be purchased
right now instead of naming the subscribe command, and the skill runs
nothing and passes on no link. Only an absent field (an older server)
falls back to the plans page; a string is used as is.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): no auto-update across 0.x minors; install skills at the CLI's release tag
- autoUpdate: before 1.0 a minor bump counts as a major one, so 0.8.x -> 0.9.x
is a notice, not a silent background install. From 1.0 on, the major alone.
- skills: `skills update` / bare `skills` / `init` install from
heygen-com/hyperframes#v<VERSION>, and `skills check` plus the background
freshness nudge read the manifest at the same tag. A build the repo has no
tag for (dev build) falls back to main, as before.
- skills: run the upstream installer as `npx skills@1.7.4` instead of an
unpinned `npx skills`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep the comment share of the touched files from rising
Comment ratchet: trim the comments added in the previous commit. No code change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): pass the CLI version into the skills check instead of importing it
scripts/clawhub-unlist-retired.mjs loads skillsManifest.ts from source under
plain node, which cannot resolve a relative `../version.js` import. Callers now
pass `cliVersion` (and skillsSourceRef takes it as an argument), so the module
keeps importing only node builtins.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): read skills at the CLI's tag without a probe; pin skills@1.5.13
- A release build reads the manifest at its own tag directly (publish pushes
the tag before npm publish). Only a 404 for that manifest falls back to main;
a timeout, missing git or proxy error now surfaces instead of quietly
comparing against main, so the background nudge can't cache a false
"outdated" count.
- checkSkills returns the ref it read, and skills update installs from that
same ref, so check and install can't disagree within one run.
- Pin skills@1.5.13 (it parses `#<ref>` too) so the pin matches the version
agentDirs.generated.ts and the lock-path notes were checked against.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(cli): split the tag and main manifest fetches
Fallow flagged fetchRemoteManifest's CRAP score (31.6 > 30). The tag fetch
(404 is the only fallback to main) and the SHA-pinned main fetch are now their
own functions. No behaviour change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): never auto-upgrade a Homebrew install
`brew upgrade hyperframes` installs whatever formula the tap holds, so a
background run scheduled for an allowed patch could still cross a 0.x minor.
Homebrew installs now only get the update notice naming `brew upgrade`.
A new test drives the scheduler through the real installer detection and
installer script: no spawn on Homebrew, a versioned npm install for a patch.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli,skills): say a step's credits are its total, and keep cost out of retries
An out-of-credits refusal named what the step needs, and an agent read
that as the shortfall. It now says the number is the step's total.
After its last try, an agent told the person what was spent and what
another try would cost. The HeyGen reference now says not to.
* fix(cli): plan avatar credits from the HyperFrames price rows
An avatar's credits came from its old API price, about five times what
the plan charges, so --max-credits refused calls that fit and a top-up
asked for too much. They now use the Avatar IV photo row plus the
general avatar video row, 950 credits a minute.
* fix(cli): pin the avatar price test and keep pricing under the comment share
* fix(cli): plan avatar seconds on the Avatar IV row alone
The general avatar row is only checked at admission and billed on
seconds left after Avatar IV, so adding it to every second made a 15 s
script plan at 238 instead of 200 and a 220 limit refuse a call that fits.
* feat(skills): creator templates on the HyperFrames plan
A Pro account asks for a video in a creator's format and the agent pulls that
template on demand. The packs sit in the private bucket behind the plan-gated
bundle route, so a Free account gets a 402 and the upgrade step. A pull costs
no credits; making the film spends them as Reverse does.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(skills): make creator-remix the one template skill
SKILL.md holds the catalog, the Pro openings, the pull and the credit
rules. references/remix.md is how to make the episode, from Desktop's
creator-remix with only what the app alone has swapped for the CLI.
The packs now hold only the template, so their hashes change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(skills): the creator-remix skill and its packs
SKILL.md holds the catalog, the Pro openings, the pull and the credit
rules. references/remix.md is how to make the episode, from Desktop's
creator-remix with only what the app alone has swapped for the CLI.
The packs now hold only the template, so their hashes change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(skills): word creator-remix's sign-in steps the way media-use does
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(skills): a creator-remix presenter runs on the plan by default
The person's own HeyGen avatar is recommended, not required: without
one, 小Lin's presenter is made with HeyGen Video 1 from their photo.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): pin template packs whose voice bills the plan first
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): offload media named inside template tags
References in a composition's <template> were never rewritten, because the DOM
query stops at the tag and template.content does not serialize, so the file stayed
in the zip. A stem matched as a plain word and a same-named file elsewhere counted
as a mention too. A 5-minute presented film went from 196 MB to 71 MB.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): lipsync, and avatars that speak a finished voice
Video 1 takes audio as a reference and re-paces it, so a shot's lips follow its
own track and drift up to a second from the voice. generate --type lipsync redoes
the mouth to the exact voice. generate --type avatar takes --audio, and --avatar
for the person's own look, so the lips land on the voice from one job.
Also moves the plan rows to the 2026-10-30 price book, estimates a voice's credits
so --max-credits can hold it, logs jobs from a folder with no project, and describes
the resolve flags.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(skills): presenters go avatar first, and a voice can be stock
The person's own avatar, then Avatar IV from their photo, then Video 1 with
lipsync. With no clone or recording, a stock voice named in the credits. Pins the
five rebuilt packs. The archive test keeps its ../ under GNU tar with -P.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): fix avatar price and sfx provider tests, trim comments
A wav gives the avatar price test an exact length on every platform. The
sfx tests now expect HeyGen first. Comment share is back under the base.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): read a font shorthand whose size nests parentheses
`font: calc(var(--size) * 1px)/1 "X"` cut at the first closing parenthesis, so a
bad family name failed the render.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): one ledger row per job, and search skips a template's own pictures
A job done at once logs one row, transcribe logs to the project, and resolve no
longer offers a component's file for a search. --reuse and --provider get help text.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(skills): pin the tested template packs, and a board needs no voice
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): read the transcribe ledger row as JSON, for Windows paths
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli): pin the Big Questions pack without the film length check
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(skills): call them style templates, and the docs example pulls a real slug
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli): pin the cleaned template packs
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(skills): drop the stock-presenter ban and the no-spend-before-storyboard rule
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli): pin the Paper Trail and Long Story Short packs without the stock-presenter ban
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(skills): rename creator-remix to style-remix, and the five templates to names that say the look
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(skills): style-remix lists the five templates when none is named
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli): pin the Finance Explainer pack that varies its motion graphics
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): media-use generate --type cutout takes a shot out of its background on the plan
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli): pin the Finance Explainer pack without the provisional variety rule
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli): pin the five style packs with variety rules measured on real films
Animated Science gets a worlds-and-boards budget, 3D True Crime a main board and a
brief corner note, 3D Brand caps by measured rate, Finance and Collage set pieces and
more than one look.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(skills): media-use names the on-plan cutout and lipsync commands, not the heygen CLI ones
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): cutout retries dedupe on request_id, uploads carry their real type; style-remix is public
The background-removal route dedupes on the body's request_id and ignores the Idempotency-Key
header, so a retry after a lost answer started a second job: runJob now also sends the key in the
body for such a route. Uploads typed every non-MP4 file as audio, so WebM and MOV inputs were
refused: they now take their type from the extension. Fails without the fix: the new cutout test
in generate.test.ts sees audio/mpeg for WebM and MOV.
style-remix drops metadata.internal and is listed with the other published skills.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli): keep the comment share of the touched files at main's
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: count style-remix in the README and CLAUDE.md skill lists
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(skills): rename style-remix to style-sampling
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): diff --offset compares the original at t with yours at t + offset
Every per-frame measure (SSIM per frame and per cell, frames.tsv, cuts,
missing content) reads yours offset seconds later, and a project folder is
captured at the shifted times. The window keeps to where both sides have
frames and says so in warnings; an offset with no overlap, or one that is
not a number, is refused with a fix. Sound keeps its own offset reading,
duration is reported as not measured, and the result echoes offset.
* refactor(cli): trim diff offset comments under the file's comment share
* fix(cli): rebase full-length diff offsets and reject overflow
Keep offset streams on a zero-based clock even when every frame is selected. Cover an untrimmed delayed render and reject non-finite offsets before file or project processing.
— Jerrai
* refactor(cli): remove redundant offset filter comment
— Jerrai
* fix(skills): reverse on Free opens the upgrade page for the person
* docs(skills): reverse on Free opens the upgrade page with a quoted link
* fix(cli): reverse on Free runs billing subscribe credited to the run
* fix(cli): trim the reverse skill and drop a doc comment for lint budgets
* fix(cli): drop --page-motion-blur from cloud render
The flag sent page_motion_blur to the hosted render API, which never
accepted that field and rejects unknown fields. Motion blur is set in
the composition with data-motion-blur, and the runtime turns it off on
its own when it cannot render correctly, so the cloud flag is removed
with its request plumbing, test and docs row.
Local render keeps its own --page-motion-blur flag.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* chore(ci): allow deleting the cloud render page motion blur test
The deletion guard blocks removed files unless they are listed. The
test file only covered the cloud render --page-motion-blur flag that
this branch removes.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(cli): prefer OAuth session over HEYGEN_API_KEY
A signed-in `hyperframes auth login` session now wins over an API key in
the environment, so a paid plan on the login is used even when the shell
also exports HEYGEN_API_KEY.
New order: HEYGEN_ACCESS_TOKEN (host app), the stored login (refreshed
when expired), HEYGEN_API_KEY, HYPERFRAMES_API_KEY, the saved API key.
The env key still comes first when HEYGEN_API_URL or HEYGEN_API_BASE
names a host app's gateway, and takes over for the rest of the process
when the login cannot be refreshed. The media-use audio helper follows
the same order.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(cli): fall back to the env key only when HeyGen refuses the refresh
A 503, a network error or an overlapping refresh no longer switches the
process to HEYGEN_API_KEY. The fallback now needs a refused grant or an
expired login with no refresh token. A login another process stored since
is re-read first, and refreshes that overlap in one process share one
request. The media-use helper no longer treats HeyGen's own API base as a
gateway.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(cli): keep the login when the refresh reply can't be read
Only a 400/401 from the token endpoint marks the grant as refused and
switches to the env key. A 200 whose body can't be parsed now throws and
leaves the login in place, so the next call refreshes again.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>