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>
* fix(producer): local renders bring in only media, font, CSS and JS from outside the project
Local renders (`render`, range render, `benchmark`, the Studio server and the
Vite Studio adapter) run with allowOutsideProjectAssets, which copied every
existing file that markup named outside the project into compiled/hf-ext, of
any type and from any folder, and served project links that lead outside
without looking at where they lead. Publish already applies a policy here:
outside references are kept, private locations are left out, and only image,
video, audio, font, CSS and JS files are copied. Local renders now follow the
same policy.
The publish predicates (private location, copied file type, left-out wording)
move from the CLI to a new `@hyperframes/studio-server/outside-file` subpath,
since the producer cannot import the CLI and already depends on studio-server.
The CLI re-exports them, so publish behaves as before. The media extension
sets move with them because the copied-type list includes them.
The producer decides with one predicate, `outsideAssetRefusal` in
utils/paths.ts, and applies it wherever allowOutsideProjectAssets lets an
outside file in, so no entry point can skip it:
- collectExternalAssets: src/href/url() references, which covers <a href> and
<link href>
- dropMediaOutsideProject: video/audio/image sources in any spelling the media
resolver accepts (file: URLs, percent-encoding), so nothing probes or
extracts them
- the render file server: project links that lead outside
- the distributed plan's project copy: the same links (range render)
- GIF/HEIC prep and sub-composition links: private locations only, since
those inputs are converted or compiled rather than copied as they are
Each left-out file logs the publish wording with "left out of the render".
To reproduce on main: a project whose index.html references
../../.ssh/id_key through <link href>, <a href> and url(), with a project
link to a file in .ssh, rendered locally, gets those files copied into
compiled/hf-ext and served.
Comment lines: the four in studio-server's outsideFile.ts moved verbatim from
the CLI files they replace. Two are new, in utils/paths.ts. The one on
outsideAssetRefusal states the policy once, so its six call sites carry no
comment. The one on refusesOutsideLink says its boolean means "refused, and
already warned", which the name alone does not say. Comment ratchet is clean.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep outsideFileType as a re-export of the shared module
The base repository's deletion guard rejects removing a file that exists on
main unless git pairs it as a rename. outsideFileType.ts moved into
studio-server/outside-file with enough added around it that git no longer
pairs the two, so CI's "Reject accidental file deletions" step failed.
The file stays as a two-name re-export and publish keeps importing from it,
so publishProject.ts and its file-type test are back to main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): raise the unpacked size budgets for the outside-file policy
CI's packed-manifest check measured @hyperframes/producer at 3,244,665 bytes
unpacked (budget 3,210,000) and @hyperframes/studio-server at 653,506
(budget 646,000), both just past the 1% tolerance.
Both packages were already at the edge on main. Measured locally with
npm pack --dry-run, main is 3,237,162 for producer and 652,502 for
studio-server, so studio-server on main is already at its ceiling. This
branch adds about 7.9 KB unpacked to producer, because the new checks sit in
the compiler, render stages and file server, which each producer entry
bundles. It adds about 5.5 KB to studio-server for the new outside-file
entry and its declarations. No source maps, tests or assets were added to
either tarball.
The budgets go to 3,245,000 and 654,000, just above CI's measurements, the
same way #7579 raised producer's budget for the project-folder checks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): apply the outside-file policy to embedded local fonts
A project font file that links outside the project is now left out of
font embedding with the same warning the file server gives, instead of
being inlined into the compiled HTML.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): a file held open or read-only answers 423 or 403 with a reason, not 404 or 500
* fix(studio): valid workflow name for the Windows held-file test
* test(studio): release the held file before the held-file test removes its folder
* fix(studio): the code editor's save toast names a held or read-only file
* fix(cli): copy only media, font, CSS and JS files from outside the project
Publish, cloud render and feedback now copy an outside reference into _ext/
only when its extension is an image, video, audio, font, CSS or JS type,
taken from studio-server's MIME map (new ./mime subpath; .avif added).
Anything else outside the project is left out with a warning and a
left_out entry whose reason is file_type; telemetry counts it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep the new outside-type file under its package's comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): copy the outside media cloud render re-encodes or converts
The outside allowlist now also takes the video, audio and still-image
extensions cloud render re-encodes or converts (.avi, .ogv, .aiff, .tif,
.bmp and the rest), from one shared list offload imports too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(studio): record the layer name on each history entry's target
* feat(studio): record the clip's name on timeline move and resize entries
* chore(studio): drop doc comments the names already carry
* 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>
* 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>
* fix: track local Studio sharing CTA intent
* fix: tag local Studio and CLI share upgrade links with where they came from
The local Studio share modal's Upgrade to Pro link opens
/pricing?from=cli&entry=local_studio_share, and hyperframes share's source-files
notice links /pricing?from=cli&entry=cli_share, so the pricing page can tell
which link a visit came from and return the visitor to their terminal. The
modal accepts its own pricing page with any query, still only on
hyperframes.dev's two origins. share_upgrade_clicked carries
cta=share_modal_upgrade.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: name the local Studio upgrade CTA and drop the explaining comments
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep the local Studio upgrade link's return page unchanged
Only entry=local_studio_share is added to the local Studio share window's
Upgrade to Pro link. from=cli would have told these buyers to go back to their
terminal after checkout, but they return to a browser tab. hyperframes share's
link keeps from=cli, as the CLI's other upgrade links do.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): keep git metadata and env files out of bundled HTML
The bundler now checks every file it reads against the project's private
paths (git metadata and env files, spelled directly or through a link)
and leaves a refused reference as authored instead of inlining it.
Bundle options gain a canRead predicate; Studio's preview passes its own
private-file rule so the preview document matches what the file routes
serve.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): check capture read grants against the decoded path
A capture page's read grant now looks at the path the way the static
preview route decodes it, including encoded separators, so a URL that
resolves to a dotfile or into a dot-folder gets no CORS grant. Ordinary
project files keep loading in thumbnails.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): accept local share requests only from loopback connections
The local share routes already require loopback Host and same-origin
headers. They now also require the connection itself to come from this
machine, so a Studio bound to a network address still keeps sharing
local to the person running it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): ask the bundler for Studio's private-file rule as plain data
The preview route passed a fresh `canRead` callback on every build. A host that builds on a
worker thread cannot send a function across, so it built on its own thread, and it could no
longer share one build between two same-content requests.
The bundler now takes `privateFiles: "studio"`, a plain string, and applies Studio's
private-file rule itself. That rule (git metadata, env files, and the app's records under
`.hyperframes/`) now lives in `@hyperframes/core/safe-path`, and studio-server reuses it.
The `canRead` option is removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): do not serve a preview main file linked to a private file
When index.html (or <id>.html) is a link to an env file or into git metadata, the
bundler refuses it and the route falls back to reading the main file from disk. That
fallback now skips a candidate that is a private project file, by the same rule the
file routes use. A main file linked from outside the project is still served.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): never inline git or env files as render sub-compositions
The render compiler resolved data-composition-src and inlined the file it named, so
`data-composition-src=".env"` put the env file's text into the render page. It now
refuses git metadata and env files with the same shared rule the bundler uses. The
pre-render check names the refused reference and stops the render.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: raise the inspector unpacked size budget to 3,722,000 bytes
The inspector already sat about 36.8 KB over its 3,684,092 budget, just inside the 1%
tolerance. Moving Studio's private-file rule into core added a few hundred bytes to the
bundles it ships, which pushed it to 3,721,419 bytes and over the tolerance.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): let opaque preview frames load project fonts and module scripts
A preview framed with an opaque origin, such as the Compositions hover
preview, makes its font and module-script loads in CORS mode with
`Origin: null`. Without a CORS grant they failed: the frame fell back to a
system font and module scripts never ran.
The preview asset route now answers those two loads with
`Access-Control-Allow-Origin: null`, `Vary: Origin` and
`X-Content-Type-Options: nosniff`. The grant is chosen by `Sec-Fetch-Dest`,
which the browser sets and page script cannot: `font` for a font file and
`script` for a .js/.mjs file, served with the matching content type. A
page's own `fetch()` is always `empty`, so it still gets no grant and
composition script still cannot read project files.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(studio-server): keep opaque-frame grant comments within the package share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): let opaque preview frames load project fonts
Narrow the opaque-frame grant to fonts. Every sandboxed frame sends the
same `Origin: null` and fetch metadata, so a CORS grant for module
scripts could not be limited to frames the Studio itself serves. Module
scripts stay unloaded in the hover preview for now; fonts keep their
grant, and `Sec-Fetch-Dest: script` loads of .js/.mjs get none.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): load fonts and modules only in the Studio's own preview frames
A CORS grant to `Origin: null` reaches every sandboxed frame, whichever
page it sits in. The grant now lives on a per-project path instead:
`/projects/:id/preview/~<token>/...` serves exactly what `/preview/...`
serves, and only there do font loads (`Sec-Fetch-Dest: font`, a font file
served as `font/*`) and module-script loads (`script`, a .js/.mjs file
served as `text/javascript`) from an opaque frame get
`Access-Control-Allow-Origin: null`. The plain path gets no grant.
The token is an HMAC-SHA256 of the project id under a random per-server
secret, compared in constant time. The Studio reads it from
`/projects/:id/frame-token`, which refuses cross-site and same-site
requests, and the Compositions hover preview frames its composition at
the token path. Documents served there are re-based under the token and
carry `Referrer-Policy: no-referrer`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(studio-server): raise the packed size budget for the preview frame tokens
The per-project frame-token path adds server code to the package, and the
packed tarball measured 166941 bytes in CI against a 164800 budget. Set the
budget to the measured size plus about 1% headroom.
— Rames Jusso
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* 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>
* fix(core): fall back to a direct write when link() is denied with EACCES
On Android app data (Termux, SELinux enforcing), link(2) fails with
EACCES in a folder the temp file was just written to. createFileAtomically()
and the studio history owner lock treated that as fatal, so
`hyperframes init` left a half-scaffolded project and every render logged
a recordRenderSuccess failure. Both now take their existing exclusive
direct-write path, as they already do for EPERM.
Fixes#7473
* fix(share): treat EACCES as no hard links in the project share lock
Same Termux/SELinux link() denial as core and the studio history lock:
the share lock's link-then-exclusive-create fallback now covers it too.
Folds the Android note into the existing comment so no file's comment
share rises.
* fix(cli,studio-server): limit registry installs and Studio file writes to project content folders
Registry blocks and components now install only into the project's
compositions, components and assets folders (plus models/ and lib/, which
the catalog uses, and notes at the root). node_modules, agent instruction
files and programs or scripts are refused at any depth, matched
case-insensitively with either separator, and checked again on the path
the project's own links lead to.
Studio's file routes never read or write git metadata or env files, and
every route that writes, renames, deletes, copies or uploads a
request-named path refuses the project folder itself, node_modules and
hidden files or folders other than .hyperframes/ and .media/, on both the
spelled and the link-resolved path.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli,studio-server): trim comments added by the write allowlist
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli,studio-server): trim path segments in linear time
The trailing dot/space and :stream trims used anchored regexes that
backtrack quadratically on long runs of spaces, dots or colons in a
request path. Trim with a plain scan instead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): refuse example dependencies in add and allow only TEMPLATE.md at the root
- addToProject now refuses a block or component that depends on an example,
not only an example asked for by name. The installer lets an example write
at the project root, so a dependency must not carry that through.
- The only file a block may write at the project root is TEMPLATE.md, the
catalog's usage note. Any other .md or .txt name could be one a tool loads.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): run thumbnail captures in an opaque origin
The thumbnail renderer loads each composition as a top-level page, so its
scripts ran on the Studio's origin. The capture document (`?hf-capture`) now
carries `Content-Security-Policy: sandbox allow-scripts`, so those scripts get
an opaque origin.
An opaque page's CORS-mode loads fail without a CORS header. The renderer that
opened the page is trusted, so it adds `Access-Control-Allow-Origin: null`
itself, over that page's own DevTools session, to the loads a frame needs:
- fonts, module scripts and images;
- the `.html` scenes, `.json` and `.cube` files the runtime fetches.
Only GETs of the project's preview files qualify, matched by file type. Both
thumbnail renderers do this: the CLI's and the Vite dev server's.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): let an opaque capture wait for a video's preview copy
A video the browser cannot decode is drawn from its `?hf-proxy=` copy. The
runtime waits for that copy with a ranged fetch, preflighted when it carries
the priority header. In the opaque capture page both failed, so each such
thumbnail fell back to a still after about five seconds of retries.
The renderer now answers that preflight itself. It also exposes the copy's
status headers to the wait, for video files under the preview path only.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(studio-server): keep capture-load comments within the package share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): keep video pixels and project fetches in opaque thumbnail captures
- Media loads: the renderer now grants them, and a capture document loads the
project's own videos with `crossorigin="anonymous"`. Color grading and shader
textures can then read their pixels.
- Fetches: every GET of the project's preview files is granted, except a dotfile
or dot-folder path such as `.env` or `.git/`. This covers the models and fonts
that registry blocks fetch at runtime.
- Opt-in: the capture sandbox is now a `createStudioApi` option,
`sandboxThumbnailCaptures`, off by default. The CLI Studio server and the Vite
dev server turn it on, because their thumbnail renderers install the grant.
Another app keeps its current capture documents until its renderer does the
same.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(shader-transitions): prepare transitions when IndexedDB is denied
An opaque-origin document, such as a sandboxed preview or thumbnail capture,
has no IndexedDB, and opening it throws. The snapshot cache now treats that
as no cache, so the transitions still prepare and draw.
Thumbnail captures also grant a CORS read of a missing preview file, so a
fetch() sees its status as a same-origin page would.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): leave a video with another host's <source> out of capture CORS
A video whose <source> child points to another host now keeps its plain
load in a thumbnail capture. Adding crossorigin to it would make a CDN
that sends no CORS headers refuse the video, leaving the clip blank.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* 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
* 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(studio-server): keep cache writes inside the project and canonicalize preview paths
- The tool's own folders (.hyperframes records, backups, preview documents,
.thumbnails, .transcode-cache) are no longer written, pruned or emptied
through a link that points outside the project. Thumbnails are still
served when their cache folder is a link; they are just not cached.
- The hf-id stamp record and the history id are replaced atomically instead
of written through an existing link.
- Sub-composition previews and thumbnails use the composition's canonical
project-relative path, and the path is attribute-encoded in the document.
- Thumbnail requests from another site are refused before any capture.
- Saved GSAP scripts escape a `</script` sequence so the script element
keeps its contents.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): refuse a UNC or device path on another root before any disk access
isSafePath now rejects a target whose root is a UNC or device root other than
the project's own before it calls realpath or lstat. Projects on a share keep working.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): answer WebMCP clients only from Studio's own page
The polyfill now starts with its tab transport limited to Studio's origin and
its frame transport off, so a page that frames Studio cannot list or call its tools.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(inspector): check Host on the per-session preview server
The preview page server applies the inspector API's loopback Host rule, so a
rebound DNS name cannot read the bundled composition or project files.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* revert(studio-server): keep writing media proxies through a linked .transcode-cache
Refusing the folder made every proxied video in such a project answer 502.
A linked cache folder now receives copies again; it is still never swept,
so nothing already in the folder it points at is removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(studio-server): drop a comment the comment ratchet refuses
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): skip HEIF and GIF preview prep when .hyperframes/prepared-assets is a link
The preview transform wrote converted images into .hyperframes/prepared-assets
through a link, so a project shipping .hyperframes as a link to another folder
had files written there. Such a project now gets its preview with the images
as written in the composition, unconverted, and nothing is written.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): never sweep a linked .transcode-cache, from Studio or hyperframes clean
The link check moves into cleanupProxyCache, which both Studio's cache
maintenance and `hyperframes clean` call, so neither removes files from the
folder a linked .transcode-cache points at.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): thumbnail origin from the server, sandbox previews from other sites
The thumbnail route builds the headless browser's URL from the server's own
listening origin (a new optional `serverOrigin` on the adapter, wired in the CLI
preview server and the Vite dev host) instead of the request's Host header.
Hosts that report no origin fall back to a loopback Host only.
Preview responses (bundled, sub-composition and project files) opened from
another site carry `Content-Security-Policy: sandbox allow-scripts` and
`Vary: Sec-Fetch-Site`. Studio's same-origin iframe, browser automation and
non-browser clients are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): build the thumbnail origin from a hostname bind name
With HYPERFRAMES_PREVIEW_HOST set to a hostname, the listening address is
the IP it resolved to, and the Host check accepts the bind name, not that
IP. The thumbnail browser then loaded a 403 page. Use the bind name when it
is a hostname; IP and wildcard binds keep the listening address.
— Rames Jusso
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* style(studio): drop the serverOrigin comment that put it over the package's comment share
The hostname-bind rule is stated by its test name in serverOrigin.test.ts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): project history lists files without holding the host's event loop
* test(studio-server): the history walk test counts the hold up to the sweep's end
* fix(studio-server): history rewrites video-state.json only when it changed
* refactor(studio-server): names carry what the history walk comments said
* fix(studio-server): reject cross-origin state-changing requests
Non-GET routes in createStudioApi answer 403 unless the shared
sameOriginPost predicate (lifted into studio-server's ./request-identity
subpath) accepts the request: the Host must be a server identity, a
present Sec-Fetch-Site must be same-origin, and a present Origin must
match the effective host and scheme. Hosts behind Codespaces or tunnels
allow their public name with HYPERFRAMES_PREVIEW_ALLOWED_HOSTS, read by
`hyperframes preview` and the Studio dev server.
Squashed from #6128 (42574a7, 110a300, 89011e1, 41c6626, 27193bb) onto
current main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): the preview server answers only the hosts it is reached by
Every route of `hyperframes preview` (the forwarded studio API, the SSE
stream, /__hyperframes_config and the Studio page) now answers only
loopback names, the HYPERFRAMES_PREVIEW_HOST bind, or a host listed in
HYPERFRAMES_PREVIEW_ALLOWED_HOSTS, the same list the write guard uses.
Only the Host header counts here, since a page can set X-Forwarded-Host
on its own requests and a read carries no Origin to compare it with.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Dextheking1 <Dextheking1@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): buildSubCompositionHtml reads only compositions inside the project
The helper joined projectDir with compPath and read the result, trusting
every caller to have confined the path first. Studio's own preview route
does; an embedder that forgets would serve any readable file. The helper
now resolves compPath with core's resolveWithinProject and returns null
for a path outside the project, the same answer as a missing file.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): keep subComposition.ts's comment share flat
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): the sub-composition head reads only an index.html inside the project
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): history waits out a file a save has emptied, and rereads one written mid-copy
* style(studio-server): state the history copy's null result in the present tense
* style(studio-server): wrap the put doc comment
* style(studio-server): shorten the put doc comment to one line
* fix(studio-server): a file still changing as history opens starts at its first whole copy
* 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
* perf(studio-server): a large project's first history copy takes a fraction of the time
* perf(studio-server): read a small file through one handle, with fewer comments
* fix(studio-server): small files keep their exact permissions in history under a strict umask
* fix(studio-server): a video with a codec nobody listed gets a playable preview copy
* refactor(studio-server): drop a comment the codec names already carry
* fix(studio-server): proxy MPEG-4 Part 2 and MJPEG video the browser cannot decode
* fix(studio-server): drop the codec comment the comment gate counts