Commit Graph
1391 Commits
Author SHA1 Message Date
Miguel Ángel 29533f631f fix(engine): hold the render page to the asset download address rules (#7748)
* fix(engine): hold the render page to the asset download address rules

With PRODUCER_RESTRICT_PAGE_NETWORK=true the render page reaches only its own project server and public addresses, checked by host and by resolved address, the rule asset downloads already follow. Unset, nothing changes for local renders.

* fix(engine): keep the page network filter comment within four lines
2026-11-14 16:38:55 +00:00
Miguel Ángel b746a0ee13 fix: check, render and downloads work on a drive without hard links (#7737)
* 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.
2026-11-14 15:47:18 +00:00
Miguel Ángel 43132411c8 chore: release v0.9.46 (#7732) 2026-11-14 13:40:20 +00:00
Miguel Ángel ff9c3b7619 fix(engine): an unrecognised capture failure is unknown, not the author's fault (#7730)
* 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
2026-11-14 10:28:28 +00:00
Miguel Ángel fe8d93056c chore: release v0.9.45 (#7729) 2026-11-14 09:45:48 +00:00
Miguel Ángel 58ef24c6d8 chore: release v0.9.44 (#7708) 2026-11-14 06:22:47 +00:00
Miguel Ángel 798c241e4d feat(cli): name a caller's owner id on the browsers and warm check it starts (#7687)
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.
2026-11-14 02:42:11 +00:00
Miguel Ángel c727e890f2 chore: release v0.9.43 (#7664) 2026-11-13 22:42:53 +00:00
Miguel Ángel 273672ab13 fix(engine): render text without ClearType colour fringes on Windows (#7663) 2026-11-13 20:55:10 +00:00
ClippyandClaude Opus 5.5 f01209d4ae fix(deps): bump tar, hono, @hono/node-server, adm-zip, sharp and postcss-selector-parser (#7656)
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>
2026-11-13 18:18:17 +00:00
Miguel Ángel 30c0935a24 chore: release v0.9.42 (#7655) 2026-11-13 17:54:21 +00:00
ClippyandClaude Opus 5.5 7603215f03 chore(deps): override tinypool to 2.1.2, bump vite and vitest patches (#7653)
oxfmt 0.41 pins tinypool 2.1.0 (GHSA-5gmw-xhrv-c9v3, GHSA-85c8-ppgw-ccpr).
Every oxfmt release before 0.67 pins 2.1.0, and 0.67+ reformats 66 files,
so override tinypool to the drop-in 2.1.2 patch instead of bumping oxfmt.

Also bump vite ^6.4.2 -> ^6.4.5 and vitest/@vitest/coverage-v8
^4.1.11 -> ^4.1.12 (pulls @vitest/mocker 4.1.12).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 17:30:24 +00:00
ClippyandClaude Opus 5.5 9d1e4e54a7 fix(deps): bump puppeteer to 25.13 so chromium-bidi resolves zod 4.6.7 (#7652)
puppeteer-core 25.13.0 moves chromium-bidi to 157.0.8090-0, which depends on
zod ^4.6.5 instead of ^3.24.1. Lifts the engine/producer puppeteer pin from
~25.11.0 to ~25.13.0, keeps one puppeteer-core and one @puppeteer/browsers
(3.2.4) across the workspace, and updates both Lambda runtime locks with a
targeted npm resolution so only the puppeteer subtree changes.

Clears GHSA-mrhx-c7xc-m3w5 in both runtime locks.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 17:30:21 +00:00
renovate[bot] d79e72c024 fix(deps): update dependency undici to v7.30.1 [security] (#6695)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-11-13 15:31:55 +00:00
Miguel Ángel 20084cbe67 chore: release v0.9.41 (#7632) 2026-11-13 04:26:22 +00:00
Miguel Ángel b54e4981f2 fix(engine): keep media ids that differ only by case in separate folders (#7635)
* fix(engine): keep media ids that differ only by case in separate folders

macOS and Windows disks ignore case, and APFS ignores Unicode normalization,
but mediaIdPathSegment passed plain ids through as written. Two clips such as
`s12-vB1` and `s12-vb1` therefore shared one `__hyperframes_video_frames`
folder: whichever was staged first kept it, and the other clip read its
frames. A longer clip then failed mid-render with ENOENT on a frame past the
shorter clip's end; a same-length pair rendered the wrong footage silently.

Only a lowercase, NFC-normalized id now maps to itself. Any other spelling
gets the existing readable~digest form, so every per-id path (frame folders,
the tail probe, audio work files, distributed plans) stays distinct on a
case-insensitive disk.

* fix(engine): name the case-folding check instead of commenting it

Keeps mediaPathSegment.ts at or under its comment share at the merge base.
2026-11-13 03:09:18 +00:00
James RussoandClaude Opus 5.5 9701f4bbf3 fix(engine): diagnose a failed Chrome launch with the env it had (#7634)
The startup diagnosis rebuilt its env from process.env, so a launch that
dropped WAYLAND_DISPLAY or the SwiftShader Vulkan pins was diagnosed with
them restored. The engine and CLI now pass the failed attempt's env through
explainChromeLaunchFailure; process.env stays the fallback when no env is given.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 01:36:12 +00:00
James RussoandClaude Opus 5.5 24d56e6813 fix(engine): launch Chrome with only the env it needs (#7629)
* fix(engine): launch Chrome with only the env it needs

Every Chrome HyperFrames starts (render, GPU probe, HDR capture, startup
diagnosis, version and shell probes, CLI browsers, inspector) now gets an
allowlisted environment from @hyperframes/core/chrome-env instead of the
whole process env. HYPERFRAMES_CHROME_ENV_PASSTHROUGH names any extra
variable a host needs.

Refs #7623

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(core): keep the Chrome env passthrough across repeat filtering

The CLI GPU probe filters its env twice, which dropped the names
HYPERFRAMES_CHROME_ENV_PASSTHROUGH adds, so the probe and the render
saw different envs. Keep the passthrough variable itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 00:53:11 +00:00
James RussoandClaude Opus 5.5 43722355a3 fix(engine): diagnose the launch attempt whose error surfaces (#7630)
When a sandboxed Linux launch fails and the no-sandbox retry also fails,
the startup diagnosis re-ran Chrome with the first attempt's flags, so it
described a launch that was not the one reported. The engine and CLI now
diagnose the flags of the attempt that produced the error.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 00:34:30 +00:00
James RussoandClaude Opus 5.5 400a4e2285 fix(engine): keep Chrome's sandbox on for local renders where the host supports it (#7625)
* fix(engine): keep Chrome's sandbox on for local renders where the host supports it

Chrome launched with --no-sandbox on every host. Keep the sandbox on
macOS, Windows and non-root Linux outside containers; drop it as root,
in Docker/Podman/Kubernetes, on Lambda and Cloud Run, and where Linux
restricts unprivileged user namespaces. --no-zygote now ships only with
--no-sandbox, since Chrome refuses it while sandboxed. A sandboxed Linux
launch that fails at startup retries once without the sandbox and warns.
HYPERFRAMES_CHROME_SANDBOX=1|0 overrides the choice.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(cli): cover the Linux sandbox retry in managed browser launches

The off-macOS closed-pipe case now passes --no-sandbox, so it still
pins "no seatbelt relaunch" rather than the new Linux sandbox retry,
which gets its own case.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(engine): honor HYPERFRAMES_CHROME_SANDBOX=1 and latch the fallback on clear evidence only

With the override set to 1, a sandboxed launch Chrome refuses now fails
instead of retrying unsandboxed. A bare startup exit (TargetCloseError)
retries that launch without the sandbox but only latches the sandbox off
after a second one, so a single unrelated early kill no longer disables
it for the rest of a long-lived process. Chrome naming the sandbox in its
error still latches at once.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 23:16:45 +00:00
Miguel Ángel 9c3258ccbf fix(engine): fast capture works on Chrome 157+, which wants content=drawable (#7626) 2026-11-12 23:01:15 +00:00
Vance IngallsandClaude Opus 5.5 2df837be9e test(engine): the blur trail mask covers the shutter's sweep, not only whole frames (#7624)
A mover that moves further than its own width between frames leaves gaps in a
trail built from whole-frame blur-off poses; the shutter's smear lands in them and
read as a leak outside the trail (nightly seed 63098). The mask now adds the
shutter's sub-frame poses, captured in time order. Seed 63098 joins the default
seeds as the regression case.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 22:51:07 +00:00
Miguel Ángel f5476851dd chore: release v0.9.40 (#7617) 2026-11-12 21:52:46 +00:00
Miguel Ángel 97df93fb07 fix(cli): check hears a WAV whose header misstates its byte rate, as render plays it (#7618)
* fix(cli): check hears a WAV whose header misstates its byte rate, as render plays it

A PCM WAV whose header byte rate is wrong (some speech generators write 2x) sent the silence decode's input seek past the file's end, so every clip past the middle was reported audio_clip_silent. Render already cuts such a file by decoded time (#7541); the byte-rate rule now lives in parsers and the CLI decoder seeks after decoding starts for those files.

* test(cli): keep the misstated byte-rate case with the other single-clip checks

* style(cli): format the WAV test helper

* style(parsers): keep the byte-rate rule's comment within the line limit
2026-11-12 19:30:02 +00:00
Märten Tropp b4fc4736d7 fix(engine): a frame's pixels no longer depend on the frames drawn before it (#7181) 2026-11-12 17:52:38 +00:00
Miguel Ángel 54bcdc616f fix(producer): a local render extracts each video at about the size it is shown (#7609) 2026-11-12 17:16:59 +00:00
Miguel Ángel 395c845cd3 fix(engine): render work is sized by the CPUs the process may use (#7612)
* fix(engine): render work is sized by the CPUs the process may use

* fix(engine): keep the usable CPU count comment under the line limit
2026-11-12 17:07:45 +00:00
Miguel Ángel cc47f7ea74 fix(engine): a video shown at exactly half its size is extracted at half size (#7607) 2026-11-12 14:00:10 +00:00
Miguel Ángel 256675f92c chore: release v0.9.39 (#7605) 2026-11-12 13:27:37 +00:00
Miguel Ángel 1ec03c4e19 chore: release v0.9.38 (#7594)
* fix(scripts): release:prepare refuses a baseline that skips a release whose tag this clone lacks

* chore: release v0.9.38
2026-11-12 08:29:06 +00:00
terencechoandClaude Opus 5.5 e8e1177ad6 chore: release v0.9.37 (#7578)
* chore: release v0.9.37

* docs(release): add #7576 to v0.9.37 notes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 02:01:41 +00:00
Vance Ingalls f66c673d19 chore: release v0.9.36 (#7575) 2026-11-11 16:06:36 -08:00
terencechoandClaude Opus 5.5 6bd9bb8a44 chore: release v0.9.35 (#7571)
* chore: release v0.9.35

* docs(release): note the render stop and container 403 from #7563 in v0.9.35

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 22:09:19 +00:00
Miguel Ángel 7a4dfb7654 chore: release v0.9.34 (#7555) 2026-11-11 16:46:12 +00:00
James RussoandClaude Opus 5.5 84799bdc59 fix: take helper programs only from install locations, never the project folder (#7524)
* fix(cli,parsers): take helper programs only from install locations, never the project folder

FFmpeg, FFprobe, whisper-cli, parakeet-mlx, Python and system Chrome are now
found through one shared rule: an absolute PATH entry outside the working
directory, or a fixed install dir. A relative PATH entry and any folder
inside the working directory are skipped, on every platform. Windows walks
PATH itself instead of asking `where`, which lists the working directory
first.

FFmpeg discovery no longer falls back to `.hyperframes/bin` or to an
installer package in the project's node_modules; an installer package
installed next to HyperFrames still works. The env overrides are unchanged.
The CLI skill reference stops suggesting the project-local folder.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(cli): give the PATH-lookup tests a fixed PATH on Windows

Windows now walks PATH instead of running `where`, so tests that faked
`where` output found the runner's real python and cmake. Both tests now set
PATH to a temp folder holding only the programs they expect.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: report a missing helper program instead of running it by bare name

When no trusted FFmpeg or FFprobe is found, the engine, the producer's
probes and Studio's waveform, peak and audio-track helpers now report
"not found" with the HYPERFRAMES_FFMPEG_PATH / HYPERFRAMES_FFPROBE_PATH hint
instead of handing the bare name to the OS lookup. Callers that degraded
on a missing binary still do: runFfmpeg returns a spawn_error result, the
GPU and version probes report none, and Studio's audio helpers fail soft.

The Lambda handler names its bundled ffmpeg and ffprobe by path, since
they live under the task root, which is the working directory.

brew, git and cmake for the whisper.cpp install, and the clipboard tool
for `hyperframes add`, run by the absolute path the trusted lookup
approved. The media-use engine gets a PATH holding only trusted folders.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(engine): fail a missing FFmpeg the way a failed spawn always has

Throwing from getFfmpegBinary turned every caller's missing-binary path
into a synchronous throw: the streaming encoder's "failure result, not a
throw" contract broke, and unit lanes that run without FFmpeg crashed at
module load. With no trusted copy the getters now return an absolute path
inside HyperFrames' own install that is never created, named for the
override to set. Spawning it fails with ENOENT exactly as before, and the
OS still never looks the bare name up. The call-site guards and fixture
changes that the throw needed are reverted.

The whisper install tests match git and cmake by name and skip the brew
case on Windows, where the lookup walks the real PATH.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(engine): pin the found FFmpeg before the HDR test looks it up as macOS on Windows

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 09:46:52 +00:00
Miguel Ángel f312fca7e2 feat(producer): fail a render whose variables the page does not declare (#7548)
* feat(producer): fail a render whose variables the page does not declare

* chore(producer): keep the comment share and the dead-code audit clean for the variables check
2026-11-11 08:46:13 +00:00
Miguel Ángel 3ad7611f9f test(engine): the URL-read concurrency test passes on machines with 32 or more cores (#7544)
The test checks that clips read from a URL are not held to the CPU-sized
prepare limit. On 32 or more cores that limit reaches the URL limit of 16,
so the test could not pass there. It now fixes the core count at 8.
2026-11-11 06:35:29 +00:00
Miguel Ángel e596be16c9 chore: release v0.9.33 (#7543) 2026-11-11 06:32:08 +00:00
terencecho 04947d99f7 feat(cli): share rendered videos through unified reviews (#7135)
* feat(cli): share rendered videos through unified reviews (#7135)

* feat(share): attach editable project sources to reviews (#7137)

* feat(share): measure local sharing outcomes (#7138)

* feat(cli): stage the sixty-day publish transition (#7136)

* feat(studio): share review pages from local preview (#7140)

Advertise the CLI sharing bridge before bootstrapping it so standalone Studio does not
request unsupported routes. Preserve origin and session checks.

Budget the intended sharing artifact: clean main packs at 8,060,519 bytes versus
8,162,979 with sharing (8,169,168 in CI). Required policy and Unicode tables, bundled
sharing code, and Studio controls account for the growth. Set the packed-only budget
to 8,577,627, following the 5% headroom convention; retain the unpacked cap and all
package checks.

* fix(share): persist refusals and improve CLI retry feedback

* fix(ci): restore render diagnostics and include sharing workspace

* fix(cli): keep sharing owner error codes stable

* fix(share): clarify update feedback and align audience changes

* fix(share): clarify updates and avoid scratch-file rerenders

* fix(cli): report active shares and preserve update channels

* fix(cli): resolve update channel when checking registry

* fix(ci): refresh sharing package budgets after rebase

* fix(share): require consent before uploading project files
2026-11-11 06:26:24 +00:00
Miguel Ángel 5073100b7d fix(producer): long, mostly still films reach their first frame before the stall check stops them (#7521)
* perf(engine): check still frames once per page and share the result with later sessions

* perf(producer): the probe skips the still-frame check unless its session captures

* chore(engine): keep the comment share of the deferred still-frame check files at their base

* fix(producer): the probe session's deferred still-frame check counts as stall-watcher activity

* docs(engine): the still-frame spot-check range is the task's span, not only its own frames

* fix(engine): a reused fast-capture probe session keeps still-frame reuse
2026-11-11 05:40:33 +00:00
Miguel Ángel 7ae1ae6494 fix(engine): offset clips from a WAV with a wrong byte rate play the right sound to their end (#7541)
* 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
2026-11-11 05:17:46 +00:00
Miguel Ángel eb9092113d chore: release v0.9.32 (#7520) 2026-11-11 02:26:28 +00:00
Vance IngallsandClaude Sonnet 5.5 f78da2d674 fix(engine): cap static-frame dedup verification at 60 s so it cannot outlast the first-frame stall (#7532)
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>
2026-11-11 01:49:42 +00:00
PaprikaChenandClaude Opus 5.5 1a9fb8acb6 feat: opt-in 4:4:4 chroma for SDR MP4 masters (#5820)
* 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>
2026-11-11 00:20:55 +00:00
Miguel Ángel 124591a9d5 fix(lint): flag a script that calls gsap before GSAP loads, and say so when a render fails on it (#7514)
* 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
2026-11-10 21:46:26 +00:00
Michael WangandClaude Opus 5.5 60fb9d2c5e fix(producer,engine): harden render paths, render slots and local listeners (#7508)
* 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>
2026-11-10 20:26:24 +00:00
Miguel Ángel cf90054613 chore: release v0.9.31 (#7506)
* chore: release v0.9.31

* docs(release): keep the release build line neutral in the 0.9.31 notes
2026-11-10 19:56:45 +00:00
Miguel Ángel ad1a5eab29 chore: release v0.9.30 (#7494) 2026-11-10 12:14:01 +00:00
Miguel Ángel b4c7f9cf7c chore: release v0.9.29 (#7483) 2026-11-10 08:45:45 +00:00
Miguel Ángel 1a758fd60f test(engine): split the frame extractor tests so each file stays under the flake gate budget (#7476)
* 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
2026-11-10 03:19:15 +00:00