* 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
* fix(cli): normalize-audio --reference stops short of the peak ceiling instead of refusing
* docs(cli): the README says normalize-audio stops short of the ceilings instead of refusing
* 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(studio-server): the cancel route replies once the adapter's stop has settled
* fix(studio-server): shorten the cancel route comments
* fix(studio-server): drop the added cancel comments so the comment share stays down
* fix(studio-server): the cancel route clears its timer when the stop throws
* fix(cli): check stops after 2 minutes of video copies and says how to finish
* fix(cli): check copies only the stretch of a video the composition plays
* docs(cli): check copies only the played stretch of a long video
* docs(cli): shorten two comments on the copy window
* fix(cli): finding crops and frames get the same copy windows as the check
* fix(cli): drop a comment the ratchet counts
* refactor(studio-server): keep runFfmpeg under the complexity gate
* fix(studio-server): a render that ran over 5 minutes can still be read after it finishes
* fix(studio-server): keep the finished-jobs helper's reasoning in its names
* fix(studio-server): a project's signature no longer freezes the host while it walks the files
* style(studio-server): format the signature changes
* fix(studio-server): keep the adapter for the preview's early-error script
* feat(studio-server): the preview records the kind and origin of each early error
* fix(studio-server): write preview script values with U+2028/2029 and < escaped
* fix(studio-server): two exports in the same second get separate jobs
* fix(studio-server): name the same-second job id helper instead of commenting it
* feat(preview): an unplayable video shows its own frame while its copy is made
* fix(preview): drop the comment on the copy's light flag
* fix(preview): shorten the still helper's doc comment
* test(preview): each proxy-wait test starts with no copy report left over
* fix(preview): cached still frames are swept with the proxy copies
* fix(studio-server): more than six clips on one media file no longer starve check and preview of connections
Every file server answered `Range: bytes=N-` with the rest of the file. A
media element reads that until its buffer is full, then stops reading but
keeps the response open, so each <video> held one of Chrome's six HTTP/1.1
connections to the host. With seven or more <video> clips on the server's
host, every other request queued behind them and `hyperframes check`
stalled at 0% CPU. A long recording cut into trimmed segments, each its own
<video> on the same file, is enough.
An open-ended range of audio or video now gets at most 4 MiB
(OPEN_MEDIA_RANGE_BYTES), as a normal 206 with an exact Content-Range. The
element asks for the next range as it plays or seeks. Bounded and suffix
ranges, and files that aren't media, are served as before. The helper lives
in studio-server; its preview route and the CLI's static project server and
composition server use it.
Fixes#6029
Claude-Session: https://claude.ai/code/session_014aw1z3VrTNenka3LGDBBLa
* fix(studio-server): carry the range cap's reason in names and tests, not comments
The comment ratchet doesn't let a file's comment share rise: mediaRange.ts
was 48% comments against the package's 7%, and staticProjectServer.ts gained
a line. The cap is now MAX_OPEN_MEDIA_RANGE_BYTES, and the why and the
repro stay in the three tests and #6029.
Claude-Session: https://claude.ai/code/session_014aw1z3VrTNenka3LGDBBLa
* fix(producer): the render file server bounds open-ended media ranges too
parseRangeHeader takes the response's content type and caps an open-ended
`bytes=N-` on audio or video with openRangeEnd, like the CLI and Studio
servers. The producer imports it from a new `media-range` subpath of
@hyperframes/studio-server, as it does `encoder-options`, so a render
doesn't load the rest of the package.
Claude-Session: https://claude.ai/code/session_01DW4V8HZZx5JUgMffb3juVV
* test(cli): eight clips on one file no longer leave the host unanswered
A real Chromium page buffers eight long video clips of one file from the project server and then asks the same host for another file; with open-ended ranges unbounded the request stays unanswered, with the bounded piece it is answered at once.
* docs(producer): range comments name the open-ended form in lowercase
* docs(cli): the range test's comment says what holds now
---------
Co-authored-by: HuntsDesk <hunter@talloak.com>
* feat(core): make a heavy clip's lighter copy ahead of time when the host asks
* feat(core): keep the comment share of the proxy transcoder where it was
* feat(core): split the copy-ahead choice so each part stays simple
* feat(core): the preview route passes the copy's urgency as the proxy options expect
* fix: cache paths follow HYPERFRAMES_CACHE_DIR
Every place HyperFrames keeps downloaded or built files now takes its
folder from one helper, hyperframesCacheDir() in @hyperframes/core. The
default stays ~/.cache/hyperframes; HYPERFRAMES_CACHE_DIR moves it.
* fix: register the cache-dir subpath for bun and node, and build inspector from core source
* test: the cache-dir override test uses a folder that is absolute on every platform
* fix: the opencv cache follows HYPERFRAMES_CACHE_DIR
* fix(cli): npm installs run in their staging dir, so no cache path reaches a command line
* fix(cli): whisper.cpp is cloned inside its build dir, so no cache path is a git argument
* test(cli): the whisper clone test finds no system whisper on Windows either
* fix(studio-server): a copy another process holds without progress ends in a named error
* fix(studio-server): a long source's in-progress piece counts as the owner's progress
* test(history): the write-timing test no longer depends on how late its timers fire
* test(history): the write-timing test gives its turn a wide idle limit
* fix(cli): history show --diff names a changed video or audio file instead of refusing
* fix(cli): history show --diff names a changed video or audio file instead of refusing
* fix(studio): a split at a clip's edge leaves the file unchanged
* fix(studio): keep the split margin's doc within the comment width
* chore(studio-server): keep the split margin's comments within the file's share
* fix(cli): normalize-audio never cuts a clip that is quieter than the target
* fix(cli): carry the boost-hold rule in a name, not a comment
* fix(cli): normalize-audio no longer says a clip is matched when a limit holds it short of the target
* fix(cli): format normalize-audio, drop the extra comment, and say a held clip is held
* fix(studio-server): the render route passes a MOV ProRes profile to the render
* fix(studio-server): drop the added comment line so the comment share does not rise
* fix(studio-server): undo and redo on Windows restore a file something holds open
* fix(studio-server): a restore waits for the preview's reads to close before replacing the file
* fix(studio-server): a restore checks the project folder after the preview's reads close
* fix(preview): the proxy copy for the video at the playhead is made ahead of the rest
* test(preview): the resolveProxy assertions carry the priority option
* fix(preview): the proxy copy asked for last goes first, and a repeat ask moves it to the front
* refactor(preview): the proxy wait loop moves its header and progress handling into helpers
* fix(studio-server): a history lock whose start cannot be recorded is given back
claim() took owner.pid and then wrote the start record; if that write threw, the error left owner.pid held by this process, so later opens waited on and then named their own pid as the busy owner. Creation and recording now release the file together.
* refactor(studio-server): drop the comment the ratchet counts against ownerLock.ts
* fix: phone videos with an undecodable first audio track check, preview and render
* fix(engine): a rate-lane clip bakes its ramp from the decodable audio track
* test: phone-clip tests end ffprobe options before the input
* fix(studio-server): an HDR clip previews and snapshots the way the SDR export renders it
Footage tagged HLG or PQ played raw in the preview, where the browser tone-maps it its
own way, while the SDR export tone-maps it with zscale and hable: the same clip came
out lighter and with different reds and blues. HDR video now takes the tone-mapped
preview copy (the filter the export uses), and a snapshot still of HDR footage runs
the same tone map. Without an ffmpeg that has zscale and tonemap the clip plays
natively, with a warning that names the missing library.
* fix(studio-server): an HDR clip is never playable for preview, whatever its codec
Only HDR H.264 and ProRes took the tone-mapped copy: an HDR HEVC, VP9 or AV1 clip kept
its codec's test type, so a browser that can decode it was judged able to play it and
the original played with the browser's own mapping. An HDR clip now has no test type, so
the swap always fires. The missing-library warning no longer names the file.
* test(cli): the HDR still test ends ffprobe's options before its input
The repo's ffprobe argv contract requires "--" immediately before the input path; the new
test passed the still's path without it.
* fix(studio-server): preview loads root-path media, images and CSS from the project, as render does
* fix(studio-server): preview writes root paths project-relative, the form Studio reads back
* fix(studio-server): preview resolves root-path module imports to the project
* test(studio-server): preview's own scripts make no module import; lint flags a broken import map