* fix(core): snapshot and preview show a clip on the frame render shows it
* fix(cli): snapshot pulls a video's frame on the same on-screen rule
* refactor(cli): drop two doc lines the names already carry
* fix(producer): an export over the peak ceiling loses only what it must
The delivery limiter cut every peak over -1 dBTP down to -3, a fixed 2 dB margin for its detector. It now limits at -1, measures the encode, and lowers the ceiling only by what that encode measured over.
* fix(producer): the delivery limit test runs in CI and one pass is its own step
* test(producer): build the loudness reference from the 16-bit track the mixer reads
* fix(lint): every selector in a comma list counts as hidden by authored CSS
* fix(lint): keep gsap.ts's comment share where it was
* fix(lint): the transform conflict check reads every selector of a comma list too
* fix(core): the bundle's contract check reads a timeline registered in a local script
* fix(lint): collectExternalStyles is internal now that linkedSources is the export
* fix(cli): an unknown command answers in a few lines and says what to run instead
* fix(cli): shorten the captions pointer and drop the redirect doc comments
* fix(cli): point the captions hint at the hyperframes skill's guide, and test the path exists
* chore(cli): regenerate the skills manifest for the hyperframes-cli skill edit
* 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(core): hlg footage tone-maps to sdr at the bt.2408 reference white
* fix(core): an HLG clip whose stream leaves its transfer unset keeps HLG's white
An SPS with an unspecified transfer takes the stream's tag, as its frames do; a failed keyframe read is not cached; the grey test needs ffmpeg 8.
Two holes in `billing subscribe` / `billing add-credits`:
- After paying on the pricing page, "Press Enter to pay" was still waiting. Pressing it before the
next 2-second poll opened a second Stripe checkout. Enter now reads the plan again: nothing opens
when the page has already covered it, and a partial top-up on the page is priced from the new
balance.
- One failed first plan read made the account look like Free with 0 credits: it offered Pro to a
Pro account and priced add-on credits for the whole run, not the shortfall. The first read is
retried; if the plan still can't be read, no terminal checkout opens and the page finishes it.
Claude-Session: https://claude.ai/code/session_01HebQXN7wsMK6GqT3MNtqXw
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): read a video's length from its packets when its headers state none
* fix(engine): ignore the cut first line of a long packet scan and count N/A as a frame
* chore(engine): trim the packet scan comments and put its doc back on the function
* style(engine): format the packet duration test
* 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(core): keep long WebKit sources and unloaded clips on the audio clock
* fix(core): drop the comments the ratchet counts
* fix(core): shorten the decode helper comment
* 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
The distributed planner compiled the raw entry file, so a <template>-wrapped
sub-composition rendered alone had no live root, timeline or duration and failed
with "Composition has zero duration". Entry resolution now lives in
runCompileStage, which both the in-process renderer and plan() call.
— Jerrai
* fix(core): a multi-worker render replays overlapping tweens behind the timeline stand-in
The overlap and landing-mark walks compared tween parents with the stand-in the producer's GSAP stub hands out, never met it, and lost the overlaps and step times. Both now compare with the real timeline behind the stand-in.
* fix(core): drop the moved helper's comment so the file's comment share holds
* fix(cli): capture takes a refused screenshot once more before naming it
* fix(cli): keep the screenshot retry's doc to one line
* test(cli): refuse the same capture shot twice now that one refusal is retried
* fix(studio-server): the cancel route replies once the adapter's stop has settled
* fix(studio-server): shorten the cancel route comments
* fix(studio-server): drop the added cancel comments so the comment share stays down
* fix(studio-server): the cancel route clears its timer when the stop throws
* fix(engine): headline a pending setup as a setup timeout, not zero duration
When the runtime never reaches render-ready, __hf.duration reads 0 because
the bridge masks it, so pollHfReady's timeout reported "Composition has zero
duration" even for compositions with a declared data-duration whose
window.__hf.buildReady promise was still pending. Headline that case as
"Composition setup did not finish within <timeout>ms", skip the duration
inference hint that cannot apply yet, and note that the render clock stays
at 0 until the first frame. Keep its transient retry classification and give
it its own CLI diagnostic code.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(engine): name animation frames in the setup-timeout hint
Setup that awaits requestAnimationFrame hits the same render-clock rule as
setup that waits on Date or performance.now: frames only fire on a seek, and
the first seek waits for setup. Say so, and point at the waits that work.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(engine): stop suggesting scheduler.yield() for setup waits
Chrome runs scheduler.yield() continuations ahead of ordinary tasks, so a
setup loop that polls with it starves the setTimeout-driven work it waits on
(Three's compileAsync polls with setTimeout(10)) and never finishes. Plain
headless Chrome 152 hangs on a ten-line page that does exactly that. Point
authors at setTimeout and say why yield-polling does not work.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(engine): point setup waits at the library's readiness promise
HyperFrames guidance is no system timers, so the hint should not tell authors
to wait with setTimeout. Point them at the library's own readiness promise
(Three.js renderer.compileAsync) and keep the warning about scheduler.yield()
polling loops.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(engine): keep the setup-timeout hint to what it can diagnose
A scheduler.yield() polling loop starves the page, so the readiness poll never
returns and the render reports a capture stall instead of this message. Drop
that sentence; the hint covers animation-frame and clock waits only.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat(registry): add path-traced-3d example with raster preview and path-traced export
An opt-in Three.js starter: previews with raster rendering and exports with
three-gpu-pathtracer, from one scene file. three 0.180.0, three-gpu-pathtracer
0.0.24 and three-mesh-bvh 0.9.5 ship as one local, pinned ES module with their
licences and a rebuild recipe, so renders make no network requests and 2D
projects never load the tracer.
Setup is one buildReady promise that awaits library readiness promises only
and ends with a throwaway frame and a one-pixel readback. Frames are drawn in
the hf-seek listener through waitUntil, each time from zero with a fixed
sample count. Math.random is seeded while the scene and tracer are built,
because object ids order light sampling and the tracer's noise textures come
from it.
Adds a skill reference and a docs guide for the setup and seek contract, the
frozen clock, why scheduler.yield() waits hang, and sample/bounce cost.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(registry): list path-traced-3d in CLI docs and tighten its notes
Add the example's section to the CLI examples doc, which docs.test.ts
requires for every registry example. Throw if the tracer reports compiling
but exposes no compile promise, instead of spinning renderSample(). Say that
three's object uuids set the tracer's sort order, that later-created objects
need the seed too, and that Date and performance.now read the current seek
time during a render rather than staying at 0.
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(core): blur scan and eventful reads put back the DOM a timeline call changed
With data-motion-blur-events on, the mover scan runs the timeline to the end with
callbacks on and rewinds with callbacks on. GSAP fires a tl.call on a backward
crossing too, so the rewind left the earliest call's DOM effect in place: the
callbacks fixture showed label "B" from frame 0, before its 0.5 s call.
Calls cannot be un-fired, so the scan (and eventful per-frame reads) now journal
DOM mutations with a MutationObserver, land on the frame with callbacks on as
before (keeping JS-side call parity), then undo the journal back to the
pre-scan DOM, which is what a plain seek to the frame produced.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine,producer): callbacks label-early pins become ordinary outside cases
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* perf(core): the DOM undo skips attributes and text already back at their old value
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(cli): billing stops checkout work once the payment wait ends, and a token refresh can't hang it
The wait for a purchase ends when the account shows it or at --timeout.
Checkout work still in flight then kept going: a price read that answered
late still created and printed a checkout, an Enter-time checkout that
answered late still opened Stripe, and the command waited on that work
past the purchase or the deadline. A token refresh with no deadline could
hold any of these reads forever.
readPlan, readOffer and createCheckout take the wait's stop signal, joined
with their own deadline, and stop waiting on a sign-in refresh once it
fires. Billing checks it after the price read and after each checkout
before printing or opening anything. The token refresh POST gives up
after 20 s.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXN7wsMK6GqT3MNtqXw
* refactor(cli): billing's checkout failure and its two billing reads each live in one place
The comment-share ratchet and the fallow audit failed on #7216: a new comment
in billing.ts, readPlan and readOffer repeating the same eight-line request,
and offerCheckout over the complexity threshold. The reads share getBilling,
the failure report moves to reportCheckoutFailure, and the comment goes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXN7wsMK6GqT3MNtqXw
* fix(cli): billing's stop signal fires at --timeout, not only when the poll returns
The checkout path stopped once the polling task ended, but the poll's
readPlan carried no signal. A poll read stalled across the deadline kept the
signal live, so a held offer could still create and print a checkout after
--timeout. A timer now aborts the controller at the deadline on its own, the
initial and polling plan reads take the same signal, and the deadline counts
from the start of the command.
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>
* feat(cli): a paywall refusal carries its page link in its own url field
An agent hit the Pro paywall, found the link only inside the fix sentence,
and handed the person a shell command instead of the page. The link now
also comes as url.
* fix(cli): auth status says hyperframes is the plan, not the HeyGen app's
An agent read user.subscription.plan (the HeyGen app's pro) as the
HyperFrames plan and ran past Free. With the HyperFrames plan read,
billing_notice now names which is which.
* fix(cli): a paywall refusal with url null names no purchase link
HeyGen sends url: null when it can't sell to this account right now. The
refusal now says so and carries no link, as reverse start does since #7031;
a missing url (older server) still gets the plans or credits page.
* 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>
A crop on yuv420p rounds an odd size or offset down to even. readClip
split the 32x32 output as 33x33 bytes, so a 10-frame clip came back as
9.4 frames and every frame after the first was misaligned; an odd offset
also shifted the chroma. Raw reads now convert to rgb24 (or gray) before
the crop, which is exact at any size and place. extract and diff stay on
yuv and add exact=1.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Adds 13 text-free fixtures from the 60-composition capture motion blur
sweep and one test per defect, each pinned by its current symptom so it
fails once the fix lands. Pins use the existing outside and inside
invariants where they see the defect, and a second check against the
engine's 32-sample sub-frame blur where they do not (E, J, K, M).
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(core): a scrolled list keeps its offset when blur moves the root
Chrome resets a scrolled container's offset when the root leaves or enters the
document, so the first blurred frame of a fresh page or render worker drew the
list at offset 0. Offsets are read at move time and put back before the re-seek,
so a container that became scrollable after the scan is covered too.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): scroll-list is an ordinary outside case, not a pinned known bug
The scroll offset now survives the root's move, so the three engine differential
cases and the multi-worker render case expect blur on to equal blur off, and the
measured constants for the old symptom go.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* chore(core): drop the scroll-offset comment, the comment-share ratchet may only fall
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(cli): check skips a contrast sample measured over a layer that is mid-motion
* fix(cli): move the backdrop overlap read out of sampleOf, and add no comment lines
* fix(cli): shorten the measuredInMotion comment
* feat(studio): alt marquee removes the covered items from the selection
Shift already adds marquee hits to the selection on the canvas and the
timeline; there was no way to take a few items back out of a large
selection. Both marquee paths now carry a MarqueeSelectionMode
(replace | add | subtract) resolved from the pointer modifiers in one
helper, with Alt winning over Shift. Subtracting the primary re-anchors
on a surviving member; subtracting everything clears the selection. The
band and candidate outlines turn the danger colour while subtracting.
Closes#5586
* fix(studio): same alt marquee rules on the canvas and the timeline
Both surfaces now let the modifiers held at release decide: the timeline
re-applies the marquee from the pointerup event before it finishes, so
letting go of Alt mid-drag turns a subtract back into a replace, as the
canvas already did. Alt at pointerdown no longer bakes a timeline base
mode; Cmd/Ctrl still sets add. While subtracting, the canvas outlines
only candidates that are in the current selection, so the band never
suggests removing something that is not selected. The timeline commit
helpers move to timelineMarqueeCommit.ts to keep the hook under the
file-size cap.
Some hosts drop a connection to a closed loopback port instead of refusing it
(WSL 2 mirrored networking, a firewall in stealth mode). The Vite Studio probe
on 127.0.0.1:5190 then waits for fetch's 10 s connect timeout, and since
every render, check and snapshot looks for a Studio through the history owner,
each of them paid 10 s. Aborting the fetch does not help: the connect attempt
keeps its socket, and the process, alive for the full 10 s.
The default probe now connects with node:net under a 1 s bound and destroys
the socket, then fetches only from a host that accepted.
Co-authored-by: Whoosh <nhatkha1407@gmail.com>
A piped, non-quiet local render now writes one versioned @hf-result JSON line
after success. Batch manifest rows carry the same reference_background value.
A rejected window.__hf.buildReady hold now sets window.__hfStartupError naming the key and the
reason, so render, snapshot and check fail instead of capturing a scene that was never built.
Fixes#5603
* fix(cli): a browser install goes on when Windows holds a file for a moment
* chore(cli): shorten the lock-retry comment
* fix(cli): keep the lock check private
* chore(cli): wrap the lock-check comment
* fix(producer): pad/trim audio from the delivery PCM, not its own AAC
The assemble stage's duration fix decoded audio.m4a and encoded it again.
That second AAC generation read about 2 dB hotter on a measured mix
(-1.8 dBTP out of the audio stage, +0.2 after the trim), so the whole-mix
cut then lowered an already compliant film by 3.4 dB, overshooting to
-2.5 dBTP. A sibling project with a slightly louder music bed escaped the
cut, so the two landed about 4 LU apart.
- The local render keeps the audio stage's PCM in the work dir until
assembly; pad/trim and any peak correction there encode from it.
- A whole-mix cut in the audio stage is applied to that PCM too, so it
still encodes to exactly the delivered AAC. If it cannot be rewritten
it is removed and assembly falls back to the AAC.
- The distributed plan does not keep the PCM, so its plan dir is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(producer): name the assemble stage's PCM input by what it is
The comment-ratchet does not let assembleStage.ts gain a comment line, so
the new input says what it holds in its name instead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXN7wsMK6GqT3MNtqXw
* fix(producer): assembly never reuses a PCM whose delivered cut was not applied
When the audio stage cuts the whole mix and then fails to rewrite the kept
PCM, it tries to delete the PCM. Deletion is best-effort and can be refused,
for example on Windows, so the uncut PCM could stay on disk. The audio stage
handed it to assembly because the file still existed, and assembly would
then re-encode a mix louder than the AAC that was actually delivered.
The cut now reports when the PCM no longer matches the delivered AAC. The
audio stage keeps the PCM only on an explicit success, not because the file
exists, and assembly otherwise falls back to the verified AAC.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXN7wsMK6GqT3MNtqXw
* test(producer): the fake-FFmpeg PCM rewrite writes its output
The true-peak correction now rewrites the kept PCM with FFmpeg and reports
the PCM as stale when that output never appears. The fake FFmpeg in this
test answered the rewrite without writing anything, so a correct run looked
like a failed rewrite. The fake now writes the output, as real FFmpeg does.
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>
* feat(core): data-motion-blur-phase sets when the shutter opens
Page motion blur always centres the shutter on the frame. Add a phase in degrees of a
frame, -360 to 360: the window starts at t + phase / 360 / fps and lasts shutter / 360 /
fps. Unset stays centred, so a page without the attribute renders the same bytes.
Both tiers take the window from one place, shutterTimes in frames.ts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(core): the motion blur report carries the shutter phase
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* chore(core): drop the phaseDeg doc comment, the comment-share ratchet may only fall
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>