* fix(producer): a clip whose file name has a space or accent is mixed into the export once
* fix(producer): compare a clip's src decoded, keeping the authored spelling either way
* fix(studio-server): save an edit Windows briefly holds without freezing the app
* fix(studio-server): keep later edits behind a held one, one backup per replay
* fix(studio-server): send a held cut again, and keep the sync retry for rollbacks
* fix(cli): an unknown flag's list leaves out hidden rename shims
The list pointed agents at init's --template, --video-legacy and --agent,
which only print an error. It now shows the flags --help shows.
* fix(cli): an unknown flag never suggests a hidden rename shim
The did-you-mean search still used every spelling, so '--templat' on init
was pointed at the hidden --template. It now uses the same visible flags
the list shows.
* fix(studio-server): check and render keep their history on a drive without hard links
The history lock had its own list of the errors that mean a drive cannot
hard-link, and it lacked EISDIR, which Windows returns on a Google Drive
folder. Every check report and render record there failed. The lock now
uses core's list, the one owner, which also gains ENOSYS from the lock.
* fix(engine): downloads and plan blobs publish on a drive without hard links
The producer's plan publisher kept a third list of no-hard-link errors
without EISDIR, and the downloader had no fallback, so both failed on a
Google Drive folder. Both now use core's cannotHardLink; the downloader
copies into an exclusively created file, so it still never overwrites.
* fix(engine): a download on a drive without hard links publishes atomically
Instead of copying into an exclusively created file, the fallback renames
the staged download into place under the cache path lock when nothing is
there yet, so a killed run never leaves a truncated file to reuse.
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.
* fix(registry): caption-highlight clears a short word's highlight when the word ends
On a word shorter than 0.05 s the 0.15 s fade-in outlived the fade-out, so
a frame inside that tail lit the highlight again until the phrase ended.
* fix(registry): leave the generated caption-highlight catalog files to the generator
check copies each canvas into a 2D context to see whether it moved. On WebGL
that readback makes Chrome log a GL driver Performance note, which check then
listed as a console warning from the composition.
* feat(core): a folder with index.html is one a step can work on, apart from finding projects
isHyperframesProject needs index.html and a marker file, which is right for finding projects on a computer (a
website's folder must not be listed) but not for what a step works on. isCompositionFolder says that: any folder
whose index.html is the composition.
* build(core): raise core's unpacked size budget for the step folder rule
* fix(cli): check times a line held across a split clip as one hold
A clip split in two hands its line to a second element at the same place.
line_unread timed each element alone, so the first half warned while the
same text stayed on screen.
* refactor(cli): name the split-clip line hand-off instead of commenting it
* fix(studio-server): an edit to a read-only project file is refused and leaves it unchanged
* test(core): read the refused file without a stat check first
* fix(engine): an unrecognised capture failure is unknown, not the author's fault
* fix(engine): carry the extractor's disk-full words in a name, not a comment
* fix(core): at full quality a 4K clip plays a copy at the size the preview shows it
* fix(core): names carry the copy rule, not comments
* fix(core): a clip whose copy fails is left held as it was, so its decoder is still freed when idle
* fix(core): the copy hold lives with the copy code, keeping core inside its size budget
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
`hyperframes docs rendering` said workers run 1-8, but the engine
clamps an explicit value to 24, and it never mentioned --format or
--gif-loop. The options now match render.ts and the engine limit.
Fixes#7668
duplicate_audio_track said two overlapping clips on one data-track-index
"cause layered audio playback" and suggested moving one to another track.
The render's mixer never reads data-track-index (every audible clip is its own
amix input) and the docs call the attribute a Studio lane only, so the two
clips are layered whatever their tracks: rendering a whoosh and a hit on
track 6, then with the hit on track 7, gives byte-identical audio. The message
now says both play and that the overlap is two clips sharing one Studio lane;
the hint says splitting tracks leaves the mix unchanged, and that a leftover
duplicate should be removed or moved. lint-rules.mdx said the audio "doubles
up"; it now says the same as the message.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
`hyperframes init --non-interactive` closes with `cd <name> && npm run …`
lines for the person or agent to paste. The name went in as typed, so a
name with a space or a quote printed a command that fails as written:
`cd my first video` (bash: "cd: my: No such file or directory", zsh: "too
many arguments") and `cd it's mine` (an unterminated quote).
A new `shellArg` quotes a word only when a shell would split or expand
it: double quotes, or single quotes when the text holds `$`, a backtick,
`\`, `"` or `!`; on Windows, double quotes, with `\` paths left bare.
`hyperframes open` / `preview --stop` hints (desktopApp's `shownDir`)
already quoted whitespace with JSON.stringify and now use it too, so a
name like `it's` or `a&b` is covered there as well.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The settings line printed the encoder tier, so the default render said
"30fps · standard · …" while it encoded the looks preset at CRF 16, and
-q delivery said "high". A long-form render that came out at ~40 Mbps
read as "standard quality" in its own log.
The line now prints the --quality name as asked for and the CRF or
bitrate in effect: "looks (CRF 16)" by default, "looks (CRF 20)" with
--crf 20, "looks (10M)" with --video-bitrate 10M, "draft", "delivery".
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
A color-graded <video> is painted into a canvas the runtime inserts after it,
with a runtime-generated id (__hf_color_grading_<video id>). Layout findings on
that canvas (e.g. container_overflow for a punch-in inside an overflow:hidden
box) named the canvas, so the fix hint "mark intentional overflow with
data-layout-allow-overflow" pointed at an element the author never wrote.
The audit already reads flags from the authored video (authoredElement);
uniqueSelectorFor now names that element too, so the finding's selector,
data attributes and source file are the video's.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
skills/gsap was folded into the animation skill in #1349, but build-copy
still listed it, so every CLI build printed "[build-copy] skill not found,
skipping: skills/gsap". Drop the entry, and add a test that every bundled
skill name has a SKILL.md so the next rename fails CI instead of warning.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): edit clips added to a project outside Studio
A clip written into a composition after its ids were last stamped (a hand
edit, an outside agent) has a data-hf-id only in the served preview. The
timeline's client-side patch looked that id up in the file's raw bytes, so
Hide, Mute, move, resize and attribute saves failed with "Unable to patch
timeline element ... (by hf-id; no file on the clip)".
Resolve the target against the file stamped in place the way the preview
stamps it, as the server's own saves and the GSAP save already do. The save
then persists that id.
* fix(studio): save volume on several clips added outside Studio
The multi-clip attribute save (gain or volume on a selection) patched each
clip in the file's raw bytes, so a clip with no ids on disk was skipped and
the save reported success with nothing written.
The by-target read and patch helpers now resolve a clip by the id the
preview served it with, so every caller finds it. The multi-clip save goes
through the same batch patch as the other timeline saves, which refuses a
clip the file does not hold; the error reaches the person instead of a
silent no-op. The preview picker finds the file holding an unstamped
element the same way.
A caller that runs several renders at once sets HYPERFRAMES_OWNER to a per-run id; every browser the CLI or
engine launches and the warm check server carry --hyperframes-owner=<id>, so the caller can tell one run's
leftovers from another's.
* fix(core): stop a cancelled audio envelope from crashing the page
cancelParamLane held the value with AudioParam.cancelAndHoldAtTime. In
Chromium before 160 that call hits NOTREACHED in
AudioParamHandler::EventToString and takes the page down when the hold
lands inside a value curve whose end marker sits before it. The lane now
reads the value it reached, clears the param and writes that value back.
* fix(core): keep the audio automation comment share flat
* fix(core): fold the cancelParamLane doc comment to two lines
A paused preview's loadedmetadata handler put a reloaded video back at the playhead by resyncing every clip and re-deciding every timed element in the film. It now syncs and decides only the video that reloaded.
* 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(core): free a preview clip's decoder when the playhead leaves it
* fix(core): keep audio buffered when the playhead leaves it, free only video decoders
* fix(core): leave Safari's loaded video alone when the playhead leaves it
`catalog --type widget` exited 1 with a runtime_error. A bad flag value
is a usage mistake, so it now throws CliUsageError: exit 2, and under
--json a usage_error envelope with the same message.
Closes#7669
Claude-Session: https://claude.ai/code/session_01M3Xbw44WYGyVqg4AjkzFxj
Co-authored-by: Claude <noreply@anthropic.com>
* fix(cli): reject invalid check numeric flags as usage errors (#7672)
--samples, --max-issues, --max-transition-samples and --tolerance fell
back to their defaults on any value they could not parse, and parseInt
read 5abc as 5. A bad value now exits 2 with a usage_error that names the
flag and the value. Absent flags keep their defaults.
* fix(cli): drop added comment to satisfy the comment ratchet
* feat(studio): drag and resize on an opaque preview start from one gesture-start read
A gesture on a preview frame Studio cannot script read nothing from the
frame as it started. A drag snapped to nothing; a layer GSAP holds moved by
a CSS translate that its save then dropped; a resize grew from the overlay
rect, the layer's GSAP scale included; and the pointer reached the element
only through the canvas zoom.
The runtime answers a new `gesture-start` request. For each pressed element
it gives the overlay geometry, the transform-free layout size, how far the
centre moves per px of translate (probed the way a draft draws it, every
transform above it applied), and GSAP's x/y when GSAP owns its position,
with whether a tween moves it. It also lists the boxes of the page the
gesture can snap to, walked by the rule Studio's own snap collection now
takes from core.
On an opaque preview every press waits for that one read, on the existing
waiting-press path, and the gesture starts from it: the snap targets, the
move route and GSAP base (so the save writes GSAP's x plus the drag, not the
drag alone), the pointer-to-offset matrix, and the resize's base size. A
layer a tween moves is refused with a notice, since saving that move still
reads the frame.
Same-origin frames do not change: their presses start at once from the
element, and their snap collection walks the same elements by the same rule.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(inspector): raise the packed size budget for the gesture-start runtime
The inspector bundles core's preview runtime. Main alone packs to 866206
bytes, 420 under the 1% tolerance on the old 858046 budget; the
gesture-start request adds 713 bytes (866919), which tipped the merge
queue's Build over. Set the budget to 880000 to leave room for the
remaining opaque-preview requests.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): a looping preview keeps playing when a scene reloads during a hold for data
A Studio preview unloads scenes far from the playhead. On a long film, the
loop's wrap back to the start lands while the first scene is reloading: the
film holds for its video, then the scene swap re-seeks with keepPlaying. The
seek read the held film as paused, dropped the hold and parked the film at the
start, so the loop stopped after its second pass.
A seek that keeps playing now counts a hold for data as playing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(core): name the playing-or-held check and drop history from its test comment
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Raise the direct ranges so the workspace and published packages resolve
patched releases: tar 7.5.22, hono 4.13.16, @hono/node-server 2.1.6,
adm-zip 0.6.1, sharp 0.35.5 and postcss-selector-parser 7.1.7. The CLI's
on-demand sharp install moves to 0.35.5 with them.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>