* 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>
* 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>
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(engine): a background image that never finishes decoding no longer stalls the frame
* fix(engine): capture tolerates a page that returns no list of late background images
* fix(engine): a background decode timeout is reported at every caller, url redacted
* fix(engine): a relative background url keeps only its path in the decode timeout report
* 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>
* test(engine): pixel invariants for capture blur against blur off
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): fixtures for every capture blur failure class seen so far
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): nested canvas fixture reproduces #6975, sharp-tile fixtures have no moving times
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): capture blur must match blur off outside the trail and the shutter average inside it
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): differential tests pin known bugs by symptom, history test checks the reference frame
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): a playing preview keeps changing with blur on
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(producer): a multi-worker blur render must match blur off outside the trail
Renders five blur fixtures through the real producer as a PNG sequence with 4
workers (contiguous blocks, three of them starting mid-film, the #6967
condition): blur off twice, blur on once. Outside the trail of everything that
moved, blur on must equal blur off in every frame with two neighbours. The
callbacks and scroll-list known differences are pinned by symptom.
Import route: a relative import of blurDifferential.ts, fixtures.ts and
thresholds.ts from packages/engine/src/services/__fixtures__. The producer
tsconfig excludes test files, so I type-checked the file with a temporary
tsconfig (rootDir widened); no error. No package subpath was needed.
RENDER_OUTSIDE_MAX_MAE: render noise is 0 (blur off, twice, bit-identical), the
rewind mutation measured 111.085 when caught, so the 1.0 floor applies.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(producer): render callbacks with workers that start between its calls
With 4 workers the blocks started at 0, 15, 30, 45, each on a call, so the
rewind mutation showed in a render only 3 times in 5. Seven workers over 60
frames start at 0, 9, 18, 27, 36, 45 and 54, two of them strictly between the
calls at frames 16 and 30; the mutation then fails callbacks in 8 of 8 runs
(worst MAE 97.02), the clean build in none.
A new case checks the partition with distributeFrames. The #list and #label
rects now come from the fixture's markup, and MEASURED_RENDER_REWIND_MUTATION
is 97.02.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): blur pins bound the symptom, liveness detector reports blindness, fixtures time out
Pinned known bugs now require every bad tile inside the pinned region and a worst
MAE within half to double of the measured one. tileTouches, Rect and the band check
move into blurDifferential.ts with a dpr 2 unit test. The blank-frame census counts
canvases it cannot read and asserts none, and names both readings when no blank frame
is seen. No console.info on passing runs. Fixtures cases get a 30 s timeout.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(producer): scroll-list render case bounds the race, pins share the engine helpers
The scroll-list loss depends on timing per worker block, so the case now requires
frames 2..27 clean and any later bad tile inside #list, without requiring the loss.
The callbacks pin keeps requiring its symptom, bounds it to the label and to half to
double of its measured size, and its message names the entry to delete. Wording says
multi-worker, not 4-worker.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* build(engine): keep the blur test helpers out of the published tarball
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): print the worst outside tile of each arm to explain the CI text diff
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test: both arms draw grayscale text so host subpixel settings are not read as blur
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(producer): run the multi-worker blur render alone so it cannot skew other Chrome tests
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test: re-pin the producer lane runner after splitting out the heavy blur render
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): read the blank-frame pin from a wrap observer, not an animation frame poll
The pin sampled in requestAnimationFrame, so it could miss the gap between the
wrap and the first draw. A MutationObserver now reads the output canvas the
moment the root is wrapped, which is deterministic, and every fixture must
report a wrapped root.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): drop the blurs field no fixture could set to false
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* ci: give the flake gate 60 minutes, it budgets runs by file count not time
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(engine): a full disk during frame extraction says so, not that the video is broken
* fix(engine): a pass that filled the disk is not decoded again in software
* feat(engine): a script-load failure names where the script came from and why it failed
* fix(engine): keep the script-load cause helpers private and within the engine size budget
* fix(core): motion blur notices a WebGL canvas the Studio page touched first
When a same-origin host page (Studio) reaches a preview element before the
scene does, for example through a MutationObserver record, Chrome gives that
element the host's prototype. The scene's getContext("webgl") then ran the
host's unpatched getContext, so the canvas never reached the accelerated
canvas set, capture motion blur stayed on, and the WebGL canvas froze during
preview playback.
The tracker now records a canvas in the set of the canvas's own window, and
installs itself in a same-origin parent too, compiled with the parent's own
Function. Cross-origin parents are skipped.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(studio): track accelerated canvases in Studio's window, not the embedder's
The preview runtime no longer installs the canvas tracker in its parent
window. That ran on every preview boot, so any same-origin page embedding
the player got its getContext wrapped, and a host CSP without
unsafe-eval reported a violation on each load. Studio now installs the
tracker in its own window when its Player module loads, and core
exposes it at @hyperframes/core/page-motion-blur.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* chore: keep the comment share of the touched files from rising
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): snapshot stops Chrome decoding videos it already replaces with extracted frames
* fix(cli): a held video keeps its intrinsic size in snapshot, as in render
* fix(cli): shorten a comment line in the held-video hints
* perf(engine): skip the screenshot on frames the page reports unchanged in beginframe capture
* fix(engine): beginframe reuse never returns a frame older than a cross-frame page change
* fix(engine): the BeginFrame reuse test gets a headless shell in the flake gate
* fix(ci): run the headless shell installer through its package
* fix(ci): install the headless shell with bunx, npx finds no bin in the workspace
* feat(engine): a chunk-fed encoder and the rule for which films may use it, off by default
* test(engine): end the chunk encoder's ffprobe call with --
* fix(producer): a render stops when a capture session sees every composition script fail
* fix(producer): only capture workers decide a script failure; prep sessions stop without recording it
* fix(producer): a script failure in a capture worker still reports as the composition-script error
* style(producer): format the script-failure test
* feat(producer): report browser-computed reference backgrounds
Preserve one initial root/page reference across local, streamed and distributed
render results without guessing from film pixels.
— Jerrai
* fix(producer): preserve plan compatibility and optional inspection
Keep reference metadata outside the v2 manifest hash and read it from the
verified execution-plan artifact. Static planning uses a non-gating page
inspection instead of requiring render-worker capabilities.
— Jerrai
* fix(producer): poll readiness independently of animation frames
Use timed polling while the render clock parks animation frames. Cover readiness
that changes after the first check with a short real-browser regression.
— Jerrai
* fix(producer): budget measured reference metadata runtime growth
Producer adds 2,228 compressed bytes over current main. Tests, fixtures and source
maps are already absent from its dist-only tarball. Allow 7,766 bytes of headroom
above the verified 837,234-byte payload while retaining the unpacked limit.
— Jerrai
* fix(engine): a scene that has ended gives up its WebGL context so the next scene is not slowed
* build(engine): raise the engine package size budget for the WebGL release module
* chore(engine): shorten the WebGL release comment
* fix(engine): a scene gives up its WebGL context only when the runtime says its window ended
* chore(engine): drop a comment the type already says
* chore(engine): shorten a comment line
* fix: cache paths follow HYPERFRAMES_CACHE_DIR
Every place HyperFrames keeps downloaded or built files now takes its
folder from one helper, hyperframesCacheDir() in @hyperframes/core. The
default stays ~/.cache/hyperframes; HYPERFRAMES_CACHE_DIR moves it.
* fix: register the cache-dir subpath for bun and node, and build inspector from core source
* test: the cache-dir override test uses a folder that is absolute on every platform
* fix: the opencv cache follows HYPERFRAMES_CACHE_DIR
* fix(cli): npm installs run in their staging dir, so no cache path reaches a command line
* fix(cli): whisper.cpp is cloned inside its build dir, so no cache path is a git argument
* test(cli): the whisper clone test finds no system whisper on Windows either
* fix(engine): GPU renders use the NVENC preset names the host's ffmpeg lists
* fix(engine): one ffmpeg stdout reader for encoder detection and preset listing
* ci(engine): raise the engine unpacked size budget for the NVENC preset reader
* fix(engine): passthrough output follows the page frames and holds a short video's last frame
* test(engine): a film whose audio outlasts its video still qualifies for passthrough
* test(engine): passthrough encodes one output frame per page frame when the video is shorter
* test(engine): end the ffprobe options before the file in the passthrough frame count test
* feat(engine): composite a source video inside the streaming encoder
* feat(engine): opt-in flag and rule for compositing a lone full-timeline video
* feat(producer): opt-in video layer passthrough for a lone full-canvas video
* feat(producer): launch the probe, drop its page and capture PNG when passthrough is on
* refactor(engine): trim the passthrough doc comments to one line
* fix(producer): refuse passthrough when a wrapper or sub-composition paints a background
* chore(producer): mark the in-page layout check as one deliberate unit
* fix(engine): a video left out of capture no longer blocks static-frame dedup
* refactor(engine): shorten two long comments in the static-frame eligibility scan
* refactor(engine): one builder for the video frame filter chain
* refactor(engine): keep the filter chain builder module-private until it has a caller
* fix(producer): a failed video extraction names which clip files failed
* fix(producer): the extraction source label hides scheme payloads and drive paths
* style(producer): format the extraction source label