Commit Graph
2375 Commits
Author SHA1 Message Date
wonjangandClaude Fable 5.2 8dbbc1d371 fix(registry): caption keywords, emoji and aftershock work for words outside a-z (#7804)
caption-emoji-pop and caption-neon-accent look a word up in KEYWORDS and
WORD_EMOJI after stripping everything outside a-z, and caption-glitch-rgb
counts a word's \w characters to decide on the aftershock. A Korean, Cyrillic
or accented word comes out empty or cut, so a keyword written in that script
never matches and a long word never pulses.

The three components now strip by Unicode letter (\p{L}) instead, which is
the same set for a lowercased English transcript.

Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-15 05:44:00 +00:00
James RussoandClaude Opus 5.5 477a3aea13 fix(cli): upload archives always leave out env files and private records (#7796)
publish, cloud render and feedback --file-issue build their archive from a
walk of the project folder that only consulted .hyperframesignore, so a rule
re-including dotfiles also uploaded .env files. The walk now leaves out env
files, Git data and Studio's private records whatever the ignore rules say,
and reports each one as left out with the reason "private".

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 02:39:36 +00:00
James RussoandClaude Opus 5.5 83eae240fb fix(cli): start helper programs only from trusted PATH folders on every platform (#7787)
* fix(cli): start helper programs only from trusted PATH folders on every platform

At startup the CLI and its worker entry points rewrite their own PATH to
absolute folders outside the working directory, on every platform, so a
program planted in the project (a relative or empty PATH entry,
node_modules/.bin, or any folder inside the cwd) is never run by name.
Child processes inherit the trimmed PATH. media-use reuses the same helper
instead of its private copy.

doctor resolves docker with findTrustedExecutable and runs it by absolute
path with execFileSync, no shell. A docker found only in the project's
node_modules/.bin is reported as not found, with a hint that it was skipped.

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

* fix(cli): keep stale-install detection and Windows system folders after PATH trim

The stale hyperframes check for reverse start reads the PATH the process
started with, so an older copy in the project's node_modules/.bin is still
reported. It only reads the filesystem and never runs that copy.

On Windows the trim now keeps %SystemRoot%, System32, System32\Wbem and
the WindowsPowerShell folder even when the CLI starts inside them, so an
elevated prompt in C:\Windows\System32 can still run cmd, taskkill,
tasklist, powershell and tar. PATH entries wrapped in double quotes are
unquoted before the check instead of being dropped. PATH order is kept.

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

* fix(cli): resolve the empty-PATH placeholder only when it is needed

Computing it at import threw in test environments where import.meta.url is not a file URL.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 01:24:20 +00:00
Miguel Ángel ad3a2389ee chore: release v0.9.52 (#7800) 2026-11-14 21:38:34 -05:00
Miguel Ángel cb15cb0e54 chore: release v0.9.51 (#7799) 2026-11-14 21:09:12 -05:00
Michael WangandClaude Opus 5.5 870b1fa4dc fix(cli,studio-server): received-file guard covers subfolders and spellings; playlists named as media never reach ffmpeg (#7771)
* fix(cli): a subfolder of an imported project keeps its received-files record

Publish, cloud render and feedback now read the received-files record at
the nearest folder at or above the one they stage, so staging a subfolder
of an imported project still leaves out the outside files its received
files reference.

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

* fix(cli): a received file counts under any spelling of the same file on disk

The received-files lookup now also matches a project file that is the
same file on disk as a listed path, so a name respelled in letter case on
a case-insensitive disk keeps its received status.

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

* fix(cli): cloud render prepares only the GIFs staging kept

The entry GIF prep before a cloud render upload now reads only the staged
copies it is handed. An image whose source staging left out keeps its
reference as written and is never read from disk.

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

* fix(cli,studio-server): never hand a playlist named as media to ffmpeg

A media file whose first bytes are an HLS playlist, an XML manifest or a
concat script now stays out of ffprobe and ffmpeg: cloud render leaves it
in the zip as authored, the media probe reports it as not media, and the
proxy copy refuses it. Real media never starts with these bytes, so it
probes and transcodes as before.

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

* fix(studio-server): catch playlists with control bytes, and keep them from stills and audio probes

A text playlist or concat script is detected whatever bytes follow its
first line; only markup must be all text. A still frame and the audio
probe behind waveforms, peaks and loudness now refuse a file the probe
reads as not media, as the proxy copy already does.

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

* fix(cli): a parent folder's state the CLI cannot read never marks a project received

The walk up for a received-files record now skips a parent whose record
cannot be reached. Only a record file that is there but cannot be read
or parsed counts every file as received.

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

* fix(cli): a drive that reports no file ids matches no received file by identity

Some network and virtual drives report a file id of 0 for every file, so
the same-file match now gives such a file no identity instead of
matching it to every listed file.

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

* refactor(studio-server): read a media file's first bytes with a read stream

The playlist check reads the first 64 bytes through a bounded read
stream instead of a raw file descriptor, and the audio-track probe's doc
comment sits on its function again.

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

* chore(studio-server): raise the packed size budget for the media playlist check

Main packs @hyperframes/studio-server close to the 1% tolerance on the
168500 budget, and the playlist check adds about 320 bytes, which put
the Build over. Set the budget to 172000.

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

* fix(cli,studio-server): open media only through self-contained media demuxers

Every ffprobe and ffmpeg input that cloud render offload, the publish
proxy bake and Studio's media helpers open now carries a demuxer
whitelist built from the supported media extensions: MP4/MOV/M4A/AVIF,
Matroska/WebM, MXF, AVI, MPEG-PS/TS, FLV, ASF, Ogg, WAV, MP3, AAC, FLAC,
AIFF and the still-image formats. Playlist, manifest and concat demuxers
can no longer open, whatever a file's bytes say. The proxy's own concat
step is left as it is.

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

* fix(cli,studio-server): keep media probe argv flat, and expect the demuxer list in loudness args

Two probe argv literals built from nested spreads are flat again, so
"--" stays the visible second-to-last entry the argv contract checks.
The normalize-audio test expects the demuxer list before the input.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 00:33:29 +00:00
James RussoandClaude Opus 5.5 27b195febc fix(cli): keep Chrome's sandbox on for website capture where the host supports it (#7774)
* 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>
2026-11-15 00:20:52 +00:00
James RussoandClaude Opus 5.5 e4e93d6ed9 fix(cli): keep captured page text out of generated agent instruction files (#7772)
* fix(cli): keep captured page text out of generated agent instruction files

The AGENTS.md / CLAUDE.md / .cursorrules files that `hyperframes capture`
writes are loaded by coding agents as instructions. The heading now uses the
captured site's hostname instead of the page title, font names are kept only
when they read as plain names, and the file states that everything the capture
saved from the website is data, not instructions.

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

* fix(cli): trim the font-name comment

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 00:20:48 +00:00
Miguel Ángel 5e0577f124 chore: release v0.9.50 2026-11-14 19:39:50 -05:00
Michael WangandClaude Opus 5.5 603395c89a fix: render file servers refuse env and Git files; shown-box sampling stays within the render (#7765)
* 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>
2026-11-14 23:36:46 +00:00
Miguel Ángel fd7217c8af chore: release v0.9.49 (#7767) 2026-11-14 18:15:46 -05:00
Miguel Ángel f33f137b2d chore: release v0.9.48 (#7761) 2026-11-14 17:04:22 -05:00
Miguel Ángel a6ff3922b4 fix(engine): renders reach only public addresses from every part of the browser (#7758)
* 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
2026-11-14 16:38:35 -05:00
Miguel Angel Simon Sierra 2f46a88dea chore: release v0.9.47 2026-11-14 12:13:11 -05:00
Miguel Ángel cb52dcf646 fix(cli): an unknown flag's error leaves out hidden rename shims (#7746)
* fix(cli): an unknown flag's list leaves out hidden rename shims

The list pointed agents at init's --template, --video-legacy and --agent,
which only print an error. It now shows the flags --help shows.

* fix(cli): an unknown flag never suggests a hidden rename shim

The did-you-mean search still used every spelling, so '--templat' on init
was pointed at the hidden --template. It now uses the same visible flags
the list shows.
2026-11-14 16:06:47 +00:00
Miguel Ángel d26ec25385 fix(cli): check still reports a film's other GL driver notes (#7745)
The filter for check's own readback stalls matched every GL driver
Performance note. It now matches only the ReadPixels stall.
2026-11-14 15:28:36 +00:00
Miguel Ángel 88beb282f2 fix(cli): an unknown flag lists the command's real flags (#7740)
The error only said to run --help, so an agent guessed another flag. It now
names every long flag the command declares, and --search points to --query.
2026-11-14 14:46:32 +00:00
Miguel Ángel e21e64f6ab fix(registry): caption-highlight clears a short word's highlight when the word ends (#7735)
* fix(registry): caption-highlight clears a short word's highlight when the word ends

On a word shorter than 0.05 s the 0.15 s fade-in outlived the fade-out, so
a frame inside that tail lit the highlight again until the phrase ended.

* fix(registry): leave the generated caption-highlight catalog files to the generator
2026-11-14 14:39:00 +00:00
Miguel Ángel 35d145157b fix(cli): check no longer reports GPU stalls from its own pixel reads as the film's warnings (#7736)
check copies each canvas into a 2D context to see whether it moved. On WebGL
that readback makes Chrome log a GL driver Performance note, which check then
listed as a console warning from the composition.
2026-11-14 14:33:10 +00:00
Miguel Ángel c31e7dd08c fix(cli): check times a line held across a split clip as one hold (#7733)
* fix(cli): check times a line held across a split clip as one hold

A clip split in two hands its line to a second element at the same place.
line_unread timed each element alone, so the first half warned while the
same text stayed on screen.

* refactor(cli): name the split-clip line hand-off instead of commenting it
2026-11-14 13:45:08 +00:00
Miguel Ángel 43132411c8 chore: release v0.9.46 (#7732) 2026-11-14 13:40:20 +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
Stephanie 50c21c355a fix(cli): parse capture and grade-compare --timeout as a duration (#7715)
capture read --timeout with parseInt, so `--timeout 1s` became a 1 ms
page-load timeout. grade-compare dropped an invalid value without a
warning. Both now use the shared parseTimeoutMs helper that check and
snapshot already use, keeping their defaults of 120000 ms and 5000 ms.

Fixes #7671
2026-11-14 04:30:52 +00:00
Stephanie 3e69d0dff0 docs(cli): list --format and the 24-worker cap in docs rendering (#7716)
`hyperframes docs rendering` said workers run 1-8, but the engine
clamps an explicit value to 24, and it never mentioned --format or
--gif-loop. The options now match render.ts and the engine limit.

Fixes #7668
2026-11-14 04:16:14 +00:00
wonjangandClaude Opus 5.5 213f7c5383 fix(cli): quote the project name in init's printed cd commands (#7608)
`hyperframes init --non-interactive` closes with `cd <name> && npm run …`
lines for the person or agent to paste. The name went in as typed, so a
name with a space or a quote printed a command that fails as written:
`cd my first video` (bash: "cd: my: No such file or directory", zsh: "too
many arguments") and `cd it's mine` (an unterminated quote).

A new `shellArg` quotes a word only when a shell would split or expand
it: double quotes, or single quotes when the text holds `$`, a backtick,
`\`, `"` or `!`; on Windows, double quotes, with `\` paths left bare.
`hyperframes open` / `preview --stop` hints (desktopApp's `shownDir`)
already quoted whitespace with JSON.stringify and now use it too, so a
name like `it's` or `a&b` is covered there as well.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 03:47:58 +00:00
wonjangandClaude Opus 5.5 2f31cc14b1 fix(cli): the render header names the quality preset and CRF it encodes with (#7697)
The settings line printed the encoder tier, so the default render said
"30fps · standard · …" while it encoded the looks preset at CRF 16, and
-q delivery said "high". A long-form render that came out at ~40 Mbps
read as "standard quality" in its own log.

The line now prints the --quality name as asked for and the CRF or
bitrate in effect: "looks (CRF 16)" by default, "looks (CRF 20)" with
--crf 20, "looks (10M)" with --video-bitrate 10M, "draft", "delivery".

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 03:47:55 +00:00
wonjangandClaude Opus 5.5 08e11cb563 fix(check): name a color-graded video by its own selector in layout findings (#7699)
A color-graded <video> is painted into a canvas the runtime inserts after it,
with a runtime-generated id (__hf_color_grading_<video id>). Layout findings on
that canvas (e.g. container_overflow for a punch-in inside an overflow:hidden
box) named the canvas, so the fix hint "mark intentional overflow with
data-layout-allow-overflow" pointed at an element the author never wrote.
The audit already reads flags from the authored video (authoredElement);
uniqueSelectorFor now names that element too, so the finding's selector,
data attributes and source file are the video's.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 03:47:53 +00:00
wonjangandClaude Opus 5.5 c66a430967 fix(cli): stop the CLI build looking for the removed gsap skill (#7689)
skills/gsap was folded into the animation skill in #1349, but build-copy
still listed it, so every CLI build printed "[build-copy] skill not found,
skipping: skills/gsap". Drop the entry, and add a test that every bundled
skill name has a SKILL.md so the next rename fails CI instead of warning.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 03:47:50 +00:00
Miguel Ángel 0f008f9412 refactor(cli): keep the warm check idle timeout private to its module (#7702) 2026-11-14 03:42:12 +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 45882027bd feat(cli): check warns when text leaves the 9:16 social safe areas (#7680)
* feat(cli): check warns when text leaves the 9:16 social safe areas

* feat(core): safe areas owned by core; check adds --safe-zone standard

* style(cli): format

* refactor(core): name the safe-area band fields

* fix(cli): defects outrank safe-zone warnings at the issue cap

* style(cli): format

* test: read the safe-box constants from core
2026-11-14 02:00:15 +00:00
Miguel Ángel f7b49f1207 fix(core): free a preview clip's decoder when the playhead leaves it (#7679)
* fix(core): free a preview clip's decoder when the playhead leaves it

* fix(core): keep audio buffered when the playhead leaves it, free only video decoders

* fix(core): leave Safari's loaded video alone when the playhead leaves it
2026-11-14 01:54:54 +00:00
James VarahandClaude affa03b60f fix(cli): report an invalid catalog --type as a usage error (#7678)
`catalog --type widget` exited 1 with a runtime_error. A bad flag value
is a usage mistake, so it now throws CliUsageError: exit 2, and under
--json a usage_error envelope with the same message.

Closes #7669


Claude-Session: https://claude.ai/code/session_01M3Xbw44WYGyVqg4AjkzFxj

Co-authored-by: Claude <noreply@anthropic.com>
2026-11-14 00:09:26 +00:00
Miguel Ángel c727e890f2 chore: release v0.9.43 (#7664) 2026-11-13 22:42:53 +00:00
bardrop 564a597be2 fix(cli): reject invalid check numeric flags as usage errors (#7673)
* fix(cli): reject invalid check numeric flags as usage errors (#7672)

--samples, --max-issues, --max-transition-samples and --tolerance fell
back to their defaults on any value they could not parse, and parseInt
read 5abc as 5. A bad value now exits 2 with a usage_error that names the
flag and the value. Absent flags keep their defaults.

* fix(cli): drop added comment to satisfy the comment ratchet
2026-11-13 22:00:57 +00:00
yuxuanx-rainandYuxuan Xia 0ca4bb8aec fix(cli): validate compare --timeout (#7545)
Co-authored-by: Yuxuan Xia <333204300+yuxuanx-rain@users.noreply.github.com>
2026-11-13 21:19:19 +00:00
jf-hgeng 85503a352b test(cli): remove committed TLS private key and generate test certificates (#7644)
* test(cli): generate TLS fixtures instead of committing private keys

* test(ci): allow the intentional removal of plaintext TLS fixtures
2026-11-13 19:37:56 +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 d77731aab5 chore(deps): update happy-dom to ^21.0.4 (#7641)
* chore(deps): update happy-dom to ^21.0.4

happy-dom 21 turns off iframe page loading by default. The player and
sdk test environments load same-origin iframe documents, so they opt
back in through their vitest happyDOM settings.

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

* test: adapt studio and cli tests to happy-dom 21

Studio tests load same-origin iframe documents, so they opt back in to
iframe page loading. happy-dom 21 adds Element.checkVisibility, which
reads the real styles rather than the mocked getComputedStyle, so the
motion-signature decoys are hidden in the DOM as well as in the mock.

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

* test(studio): fix remaining studio tests on happy-dom 21

- happy-dom now implements getAnimations, so Base UI deferred popup
  unmounts to animation frames; test setup sets Base UI's
  BASE_UI_ANIMATIONS_DISABLED, matching the old synchronous behaviour.
- happy-dom 21 drops vendor-prefixed properties it does not list, so the
  -webkit-text-fill-color tests move to a jsdom file with shared helpers.
- The scaled-iframe drag test builds its own Window, which now needs
  enableIframePageLoading.
- NLEPreview.slowBoot's per-file environment options never applied the
  disable setting and now wiped the config's iframe opt-in; drop them.

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

* test(studio): inline fill-test helpers instead of a shared module

Keeps the moved -webkit-text-fill-color tests self-contained and leaves
the original test file's helpers untouched.

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

* test(studio): drop the Base UI flag comment for the comment ratchet

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 16:56:15 +00:00
James RussoandClaude Opus 5.5 2c2b399bfa fix(producer): local renders bring in only media, font, CSS and JS from outside the project (#7647)
* 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>
2026-11-13 16:26:19 +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
James RussoandClaude Opus 5.5 89a7aa3004 fix(cli): copy only media, font, CSS and JS files from outside the project (#7636)
* 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>
2026-11-13 03:24:23 +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 2591abfbf0 feat(cli): cloud render --json lists the files an upload leaves out (#7631)
* feat(cli): cloud render --json lists the files an upload leaves out

`cloud render --dry-run --json` now reports `left_out`: each file outside the
project that the upload leaves out, with the file that points at it, the
reference as written, its path from the project, the reason (blocklisted or
received) and how many folders above the project it is. A wrapper can ask
before uploading. A full `--json` run carries the same list in its result and
prints a `{"event":"left_out"}` line on stderr for each, beside the warning a
person reads.

Publish, cloud render and feedback's repro send `cli_upload_left_out` when an
upload leaves something out: counts and folder depths only, never a name or
a path.

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

* refactor(cli): keep the left-out report's comment share at its package's

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 01:34: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