* fix(engine): offset clips from a WAV with a wrong byte rate play the right sound to their end
A WAV header that states twice its real byte rate sent the mixer's input seek
to twice the clip's in-point: the clip played later words, then silence. Such a
source is now cut by decoded timestamps instead of by a byte seek.
* refactor(engine): let the byte-rate flag's name carry the seek rule
Long caption overlays plan thousands of verification screenshots, so the
verification budget clamped at its 300 s ceiling in every render worker. That
equals the producer's 300 s first-frame and session-init stall floor, so the
stall always won and the render failed before its first frame. Verification
fails closed on exhaustion (dedup is disabled for unverified runs and normal
capture proceeds), so a lower ceiling costs only some frame reuse.
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* 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>
* fix(lint): flag a script that calls gsap before GSAP loads, and say so when a render fails on it
* fix(lint): judge the first gsap call by when it runs, so a listener after a deferred GSAP passes
* fix(lint): keep the gsap timing helper's comment to two lines
* fix(producer): build the render job before taking a render slot
A request whose options fail the strict render-request validator now gets
a 400 on both the blocking and streaming routes, and its inline project
directory is removed. Validate workers up front like the other overrides.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): write compiled sub-compositions only inside the compiled directory
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): keep media work files inside their directory for any element id
Map a media element id to one plain path segment before it names a frame
directory or an intermediate audio file. Ids that already are one plain
segment map to themselves, so existing paths stay the same; the producer
and the distributed plan derive the same segment.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): listen on loopback by default in the engine file server
The file server feeds the co-located capture browser, which loads it from
localhost. A caller that wants another interface passes hostname.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): refuse cross-origin browser posts to the standalone render server
A web page on another origin can no longer start a render or lint through
the server's POST routes. Requests without an Origin header (CLI tools,
server-to-server callers) and same-origin pages are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(engine): trim comments on the media path segment and file server host
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): trust the browser's Sec-Fetch-Site verdict for render server posts
A same-origin page behind a reverse proxy that rewrites the Host header sent an
Origin that no longer matched Host, so the cross-origin guard refused it. The
guard now uses Sec-Fetch-Site when the browser sends it and falls back to the
Origin and Host comparison only for browsers that do not.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): keep generated media path names apart from plain ids and within filename limits
A plain media id that already ends like a generated name now takes the hashed
branch too, so it can no longer share frame folders or audio work files with
the unsafe id that produced that name. The readable part of a generated name
is capped at 64 UTF-8 bytes before the digest, so long or multibyte ids that
contain separators stay within the 255-byte filename limit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* test(engine): split the frame extractor tests so each file stays under the flake gate budget
* test(engine): cut the comments the frame extractor test split carried over
* fix(engine): a clip shows a new source frame on every output frame it covers
* refactor(engine): shorten the frame count doc to two lines
* style(engine): collapse the single-pass ffmpeg call the formatter wants on one line
* fix(engine): short clips from Apple-encoded videos keep their last frame
* refactor(engine): name the end-of-source hold and frame bound instead of commenting them
* fix(engine): frame ranges past a source's end stay empty with the held final frame
* test(engine): move the final-frame test into its own file
* test(engine): nightly motion blur run over generated compositions
A seeded generator of text-free compositions combines 19 features (nested
canvas, overflow, clip path, scroll container, callbacks, a last-child rule)
and checks the two pixel invariants on auto: outside the trail at two holds
and at a moving time, inside the trail at a moving time. The runtime lane
runs seeds 1 to 3; motion-blur-nightly.yml runs 200 a day on the Chrome 153
pin and on stable, and opens one issue per failing seed.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): the nightly records every failure, ignores noisy references, caps its issues
A crash, a timeout or a launch failure is recorded before the job goes red; a
failing check whose blur-off reference disagrees with itself is reported as
unstable instead of failing; the report job moves into a tested script that
fetches open titles once, caps first, and opens one systemic issue above 5 seeds.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): the nightly report resists injected failure text and keeps a crashed leg's record
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(engine): nightly report escapes backslashes, test strips tags to a fixpoint
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(cli): staging folders beside a project path no longer fail past 260 characters on Windows
mkdtemp does not get the long-path prefix that mkdir does, so every staging folder
made beside a project or output path failed once its full path passed 260 characters.
They now come from one helper, createStagingDir in @hyperframes/core/atomic-file, and a
scan test fails on a new mkdtemp beside a path.
* fix(cli): give mkdtemp the long-path form instead of replacing it
CodeQL treats mkdtemp as the safe way to make a folder under the system temp dir and
flagged every file written into a folder from the mkdir-based helper. createStagingDir
now calls mkdtemp with the long-path form of the path on Windows, so both hold.
* fix(cli): leave non-Windows paths alone when making a staging folder
The long-path form is now chosen by the shape of the path, not process.platform,
so tests that pretend to be Windows keep working and the comment share does not rise.
* fix(core): a staging folder keeps a Windows path that already names its namespace
* fix(core): a staging folder keeps a Windows device path as the caller gave it
* fix(core): the staging folder helper's comment fits the line limit
* fix(engine): hlg footage with a large header sei also tone-maps at hlg's white
* fix(engine): say in the read's own doc line why it streams
* test(engine): the header-SEI HLG fixture encodes without b-frames, so it muxes on windows
* fix(producer): page timers during a render run on film time
* test(producer): a regression film whose timer bars must follow film time
* test(producer): schedule the timers regression film in CI shards
* fix(producer): keep setup timers on the wall clock until the page reports ready
* fix(producer): keep the renderer's own waits and deadlines on the wall clock
* test(engine): fail CI on a bare timer in code the engine runs in the page
* fix(core): type the wall-clock timers like the global timers they replace
* chore(engine): drop the comment on the shim's window type
* fix(producer): a failure before the first frame reports frame capture as its stage
* fix(producer): a failure after the effect scan reports frame capture, with a stable code
* fix(engine): a render no longer finishes without an image that loaded late
* style(engine): format the frame gate
* fix(engine): an image outside the frame no longer stops a render
* fix(engine): a render stops and warns when a frame's image never arrives, with no cloud retries
* fix(producer): a cloud chunk keeps the missing image's error name so retries stop
* fix(engine): a gpu-less linux host falls back from drawElement instead of hanging self-verify
On a GPU-less Linux headless shell asked for browserGpuMode "hardware", Chrome has
GPU args and no GPU, so getContext("webgl") returns null. detectGpuBackend read that
as { isSwiftShader: false }, the SwiftShader gate let drawElement engage on a
BeginFrame-launched browser, and self-verify on its truth page then stalled until
the render failed after about 300 s, with no fallback.
drawElementGate now decides the init-time fallback, each with a named deGateReason:
- swiftshader: any software GL (SwiftShader, llvmpipe, lavapipe, softpipe, Microsoft
Basic Render Driver), from one shared token list. Detection on real GPUs is unchanged.
- webgl_unavailable: no WebGL context could be created (null, or getContext throws).
- beginframe_no_self_verify: the browser was launched for BeginFrame. Its self-verify
truth page has no BeginFrame driver, so drawElement frames could not be checked, and
a Linux host with a GPU would stall the same way. HF_FORCE_DRAWELEMENT bypasses only
this gate.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): windowed frames runs drawElement through self-verify and a recycle
Adds a drawElement case to the windowed-frames integration test: drawElement capture,
self-verify through the on-demand hook, and a browser recycle. It covers that hook
only on a macOS or Windows host with a GPU. Linux always gates drawElement away
(headless-shell launches for BeginFrame, which has no self-verify), and so does any
host with no GPU; there the case asserts the named gate fallback (swiftshader,
webgl_unavailable or beginframe_no_self_verify) and prints that drawElement did not
run. HF_TEST_REQUIRE_DRAWELEMENT=1 turns that fallback into a failure, for the hosts
that are meant to run it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* 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>
* test(engine): blur browser tests fail on CI when their browser cannot run
On CI a missing Chrome, a missing core runtime build or a Chrome without drawElementImage
fails the suite's beforeAll instead of skipping every case. Off CI the suites still skip.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): every inside-the-trail case proves blur drew, not only held-card
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): the liveness test watches held-card through its slide-out
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(producer): stateful-callback joins the multi-worker blur render, split across five suites
The render differential's suite moves into __test_utils__/blurRender.ts and five files run it
over one or two fixtures each, so none nears the flake gate's 120 s cap. Every fixture that
moves must now blur more than insideMaxMae, not only held-card, and CI fails instead of
skipping when ffmpeg is missing.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(producer): each blur render file imports its runner so the test classification reads it
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* feat(core): auto motion blur draws with the filter tier
Capture stays available as data-motion-blur-tier="capture". auto now draws with the
filter tier (reasonCode tier-auto), so the capture-only defects leave the default path.
Removes the translation-only hand-off and its Discovery field, adds a filter arm to the
differential, and updates the check, guide, skill and Blur panel label.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* docs(core): measured cost and known limits of the filter tier, the new auto default
spacex-launch (77 movers) takes 2.9x the CPU of no blur on the filter tier and 1.7x on
capture; say so, and list the filter tier's measured limits (sweep D, E, F, I, O, B).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* docs(core): word the filter tier's cost and limits as measured, not as mechanism
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* docs(core): do not say every filter-tier limit is pinned by a sweep test
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): split the blur differential so each file fits the flake gate's 120 s run
The filter arm moves to its own file and skips fixtures that already draw with the filter
tier; inside cases get their own file; a fixture's blur-off page is opened once per file.
Shared helpers live in __fixtures__/motionBlur/differentialPage.ts.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(core): a mover holding a fixed child stays sharp in the filter tier
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(core): a fixed-child mover is skipped only on frames it is not already a containing block
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(core): blur quiets discrete callbacks instead of undoing what they wrote
#7191 undid the DOM a callback wrote during the blur scan with a mutation journal. That
regressed once-guarded and memoized timeline callbacks: the callback ran, its guard flipped,
and the journal put the DOM back, so the real seek never wrote it again.
Mute GSAP's onStart, onComplete, onReverseComplete and onRepeat for the scan and for eventful
pose reads, then restore them. onUpdate keeps firing, so movers driven from it are still found.
muteDiscreteCallbacks replaces a callback with a no-op rather than clearing it
(hasZeroDurationCallbackTween reads typeof vars.onComplete), walks tween.timeline for staggers
and keyframes, and skips an animation already muted because scene timelines nest in the root.
The journal (journalDom, landThenUndoDom, putBack) is deleted. The loud rewind through 0 stays.
Measured in the spike (mute-spike-report.md, "Probe matrix and fresh worker"): every GSAP
pattern matches blur off in label and fire count; 8 of 300 comparisons differ, all the non-GSAP
row, against 248 of 300 on main. This supersedes the limit #7191 accepted. Mute and restore over
2002 animations is 0.2 ms.
Limits:
- A mover that exists only because a muted callback set it up is found only if that callback
fired before the scan. A worker starting before the call leaves that mover sharp while a later
worker blurs it; positions stay right.
- tl.call(() => gsap.to(...)) movers are never found and stay sharp.
- A non-GSAP adapter that ignores suppressEvents (adapters/animejs.ts) and writes DOM on a
once-only completion shows it early. Pinned by a KNOWN LIMIT test.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(producer): drop the once-guard-label block-start guard that pins a block that cannot fail
The guard required a block start in [1, 15], the worker at frame 9, and the comment said it
paints on both sides of the call at 16. Its frames after the call (16, 17) sit inside the
trail mask at the label, so that block cannot show the bug. The outside-the-trail case on the
7-worker partition is what catches the mutant; the fixture stays in FIXTURE_NAMES.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): split the callbacks matrix in three and share one blur-off run per row
The matrix file took 247 s on an idle Mac and timed out at the flake gate's 120 s in all 10 reruns.
Each row now compares the arms against one blur-off page painted in order and one fresh page, not
a new blur-off page per arm and sequence; the in-order sequence is the first paints of the page that
goes back to the first time; rows run their pages together; the paint skips the full-frame PNG that
only the pixel tests read. Only the two arms with an onUpdate mover stay (both tiers): they run the
scan's mute and the per-frame mute, which the arms without a mover do not.
The rows and harness move to __fixtures__/motionBlur/callbackRows.ts and the matrix is split over
three files so each run fits the gate. Rows a to y, the three sequences, both tiers, row y and the
KNOWN LIMIT test are all kept; no assertion changed.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* chore: release v0.9.17
* chore(producer): raise the unpacked size budget for windowed video frames
The new modules and this version bump put the unpacked package 49 bytes
past the 1% tolerance. No tests or source maps are in the tarball.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* 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.
* 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(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>