* fix(engine): NAT64 addresses count as non-public; producer exports the address rule
* chore(producer): drop the new section comment
* fix(engine): judge mapped and NAT64 addresses by the IPv4 address they carry
* test(engine): operator ranges hold through mapped and NAT64 addresses
* fix(cli): keep Chrome's sandbox on for website capture where the host supports it
`hyperframes capture` added --no-sandbox on every Linux host. It now uses the
engine's host check, the same one rendering uses: the sandbox stays on unless
the process runs as root, in a container or serverless runtime, or with user
namespaces restricted. HYPERFRAMES_CHROME_SANDBOX=0/1 still overrides, and a
launch Chrome refuses with the sandbox is still retried without it. When the
host check turns the sandbox off, capture prints a one-time warning.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): drop the new comment block from the capture launch args
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): start nvidia-smi, vm_stat, ps and tasklist from trusted folders only
The renderer resolves these helpers through the shared trusted lookup and runs the absolute path, so a program with the same name in a project folder is never started in their place.
* test(engine): memory and import tests follow helpers started by resolved path
* fix(engine): refuse media playlists that name files outside their folder
* refactor(producer): media preflight decides refusals in one helper
* fix(engine): read a playlist once, bounded, instead of sizing it first
* fix(producer): shown-box sampling stays within the validated render duration
Sampling where each oversized video is drawn stepped through the authored
start and end in 0.25 s float steps with no bound, before the render
duration was checked. An enormous start never advanced the step, and an
unbounded end grew the sample set until memory ran out.
The render duration is now validated first, each window is cut at the
composition's end, a window that is not finite is skipped, and the loop
counts integer steps. Building the sample list happens inside the
measurement's try, so any failure falls back to full-size extraction.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: render and capture file servers refuse env files and Git data
The producer render file server, the engine file server and the CLI
static project server served every regular file under the project to the
page, including `.env*` files and anything under `.git`. Compile already
refuses to inline those files, and Studio preview and play refuse to
serve them.
All three now answer 404 for them through the shared isVcsOrSecretPath
rule, checked on the requested name and on a link's target, with the
case and Windows spelling variants it already covers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): inline only public HTTPS scripts, under the download URL policy
The compile step fetched every external `<script src>` with a bare fetch:
any scheme, any host, redirects followed, body size unbounded.
It now fetches through the engine's download policy, the one remote
stylesheets and media already use: HTTPS only, literal and resolved
addresses public, every redirect hop checked again, connect pinned to the
checked address, and at most 16 MiB per script. A new engine helper,
fetchPublicHttpsBytes, returns the raw bytes so integrity metadata is still
checked before decoding; fetchPublicHttpsText now decodes its result.
A script outside the policy keeps its `<script src>` tag, and the capture
browser loads it as before; the log says so at info level instead of
warning that the render may fail. Scripts under the operator's
HYPERFRAMES_GSAP_BASE_URL mirror, which may be loopback HTTP, are still
inlined. An integrity mismatch still fails the render.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): the audio probe skips remote video URLs outside the public HTTPS policy
A video whose remote src compile could not download keeps that URL, and
the probe-only audio pass handed it straight to ffprobe, which fetches any
scheme and host. A src that fails the literal public-HTTPS check (plain
HTTP, loopback, private, link-local or `.internal` hosts) is now skipped,
the same outcome frame extraction already gives it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): the GSAP mirror exception covers only its dist folder
Scripts from the operator's HYPERFRAMES_GSAP_BASE_URL mirror are fetched
outside the public-HTTPS policy, because the mirror may be loopback HTTP.
That exception now covers only plain script file names in the GSAP dist
folder the compiler itself points at, refuses redirects and stops at
16 MiB, like every other inlined script. Any other path on the mirror's
origin follows the public-HTTPS policy and is left for the browser.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): on a render service, https media inputs open only HTTPS
ffmpeg and ffprobe read some https sources in place. An https playlist
or manifest can name segments on any protocol, and the default protocol
list for an https input does not restrict them. With
PRODUCER_RESTRICT_PAGE_NETWORK=true, these inputs now pass
`-protocol_whitelist https,tls,tcp`, so segments and parts they name must
be HTTPS too. Local renders are unchanged.
A new test pins that local project files which are playlists, concat lists
or DASH manifests (with their own extension or named `.mp4`) are probed
and decoded without any request to the URLs they list: ffmpeg limits what
a local file input may open to file, crypto and data, and the concat
demuxer refuses URL entries in safe mode.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): renders reach only public addresses from every part of the browser
* fix(engine): renders reach only public addresses from every part of the browser
* fix(engine): renders reach only public addresses from every part of the browser
* fix(engine): renders reach only public addresses from every part of the browser
* fix(engine): look a host up again after a failed lookup instead of refusing it for the whole page
* fix(engine): name the failed-lookup reset instead of commenting it
* 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
* 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.
* 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
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.
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>
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>
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>
* 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.
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>
* 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>
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>
* 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>
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>
* 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