Every skill now starts the CLI through hyperframes/scripts/plugin-cli.mjs, which starts npm in
the home folder. A standalone install, with no plugin manifest, runs the newest release that
moves into HYPERFRAMES_PLUGIN_CWD. The skills no longer prefer a project's own wrapper over the
CLI.
* ci(publish): publish prebuilt tarballs from a job that runs no release-commit code
Builds, lifecycle scripts and packing move to a pack job with a read-only
token and no secrets. The publish job, which holds the npm token and the
write token, checks each tarball's name and version against the release and
uploads it with lifecycle scripts off. A version already on npm with other
contents fails the first attempt instead of being skipped.
* ci(publish): prerelease tag pushes publish only after a maintainer approves
A prerelease tag can come from any prerelease branch, which no PR review
covers. Tag-push runs now use the npm-prerelease environment, which requires
a maintainer's approval. Merged release PRs keep the npm-publish environment.
* ci(publish): keep every publish in the approval-gated npm-publish environment
npm's trusted publishers are pinned to npm-publish, and that environment now
requires a maintainer's approval with self-review prevented. A second
environment would fail npm auth, so the workflow keeps npm-publish for every
trigger. The docs and test name it as the approval gate.
* fix(parsers): bound canvas scaffold dimension extraction
* chore(parsers): raise packed size budget for linear scaffold scanners
The bounded scanners replace three regexes with a small amount of
procedural code; @hyperframes/parsers packs to 210414 bytes (+1.2%).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): catch-up lists only history lines appended after the hand-off
The seen record now marks the history file (its identity and length) at
the hand-off, and catch-up and the end-of-command notice read only whole
lines appended past that mark. Lines a project already carried are never
shown, whatever dates they claim. After the app trims the history, the
place is found again by the digest of the last line shown; a history the
app set aside and restarted is read from its start; a history replaced or
cut short shows nothing until the next hand-off marks it again. Records
written before the mark keep the dated filter once, then switch to it.
* fix(cli): catch-up notes the history's lines at hand-off instead of a file position
The hand-off now stores short digests of every whole line the history
holds, and catch-up and the notice show lines not among them nor shown
before, in file order. The person's turns keep showing after the app
trims the history or a sync rewrites it, and lines a project came with
never show. A hand-off over an older seen record always notes the
lines; such a record shows dated turns only when all are dated after it.
* fix(cli): catch-up shows nothing for another project now at the same path
The hand-off also notes the project folder's identity (device, inode and
birth time). When a different folder sits at the path, the seen record
counts as no hand-off: catch-up and the notice say nothing, and the next
hand-off notes that project's lines afresh.
Builds, lifecycle scripts and packing move to a pack job with a read-only
token and no secrets. The publish job, which holds the npm token and the
write token, checks each tarball's name and version against the release and
uploads it with lifecycle scripts off. A version already on npm with other
contents fails the first attempt instead of being skipped.
* fix(engine): a cached browser is used only when its files match the pinned build
* ci: install the pinned headless shell for the engine and producer test jobs
* ci: record the producer test job's new setup step for test reachability
* chore: release v0.9.55
* chore: release v0.9.55 notes include #7830
* chore: release v0.9.55 notes include #7859 and #7867
* chore: release v0.9.55 notes name the docs change and cloud render
* chore: release v0.9.55 notes include #7866 and #7801
* chore: release v0.9.55 notes match the style bar
* fix(cli): one trusted PATH rule for the engine and CLI; say why a project copy was skipped
The Windows PATH rules (quoted entries, the %SystemRoot% folders) now live in
the parsers' trustedPathDirs, so engine helper lookups and the CLI's PATH
rewrite apply the same rule.
When sam, aws, gcloud, docker, git or npx is not found but a copy sits in a
project folder the rule skipped, the message names that copy by its path
relative to the project and says why it was not used. cloudrun now reports a
missing gcloud or docker as not found instead of "exited with null".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): join a simulated Windows PATH with the Windows separator
The shared trusted-folder rule now splits PATH on ';' whenever the platform
is win32, as Windows does. Two tests that pretend to be Windows on Linux
built PATH with ':', so the rule saw one folder instead of two.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): name skipped copies above the working folder; pin Windows PATH to the shared rule
The not-found hint now names any copy the trusted PATH rule skipped,
relative to the working folder, including ../node_modules/.bin when an
npm or pnpm script runs from a subfolder. A Windows test pins that quoted
PATH entries still go through the shared rule, so the project root's and
ancestors' node_modules/.bin stay skipped.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli): trim projectCopyHint comments to the package's comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
rootHeadContent and tagRootCompositionFile ran an opener, then [^>]* or a
lazy run, then a required literal, over the project's own HTML. When the
literal never came, each opener rescanned to the end of the page: about
10 s for 250 KB of "<head" or of "<a". Both are now plain scans that give
the same results: only the first <head can match, and each start tag is
checked up to its own > once.
* fix(cli): cloud render sends one zip when it fits and uploads only the largest media
* fix(cli): cloud render leaves unused media out only when the zip is over the limit
* test(cli): eight-at-once upload test waits for eight in flight, never a timer
* test(cli): eight-at-once upload test also fails when more than eight run
* fix(cli): upload archives never include credential or agent-state files
Publish, cloud render and feedback stage the project through one path.
It now always leaves out package-manager and Git credentials (.npmrc,
.yarnrc, .pypirc, pip.conf, .netrc, .git-credentials, .gitconfig), key
files (id_rsa*, id_ed25519*, *.pem, *.key, *.p12, *.pfx), .ssh, .aws,
.gnupg, .docker, .kube, .azure, .config/gcloud and .config/gh, agent and
editor folders (.claude, .codex, .cursor, .agents, .gemini, .vscode,
.idea) and .mcp.json, at any depth and in any letter case. This holds
whatever .hyperframesignore says and whatever the HTML or CSS references.
A reference can bring back a file the ignore rules skipped only when it
is an image, video, audio, font, CSS or JS file, or when it is not in a
hidden folder. Every file left out this way is reported, and a file the
folder walk already reported is not reported again for each reference.
* fix(cli): anchor both alternatives of the key-file pattern
* fix(cli): a page's own scripts in a hidden folder still upload
* fix(cli): the static project server answers only loopback and marks pages another site loads
check, snapshot, validate, layout, compare, grade-compare and motion-shot serve the
project from a loopback server. It now refuses any Host other than loopback or its
in-process name before reading a file. A page or file that another site loads comes
back sandboxed, and its documents carry the another-site mark, so the runtime offers
that site no editing port. The capture browser's own loads are unchanged.
* fix(producer): the render file server answers only loopback and offers no editing port
The render file server now refuses any Host other than loopback before it opens a
file; the capture browser asks for localhost. Every HTML page it serves carries the
another-site mark, so its runtime answers no editing connect. A render never sends
one, so capture is unchanged.
* fix(engine): the exported file server answers only its own host and offers no editing port
createFileServer from @hyperframes/engine now refuses any Host other than loopback or
the hostname it was bound to (on a wildcard bind, this machine's own addresses too)
before it reads a file. Every HTML page it serves carries the another-site mark, so
its runtime answers no editing connect.
* fix(cli): never open another computer's share while staging an upload
publish and cloud render now leave out a reference to another computer's
network share or a Windows device path before any file-system call on it,
and report it as left out with the network_share reason. A page that came
in with an imported project has its outside references left out before the
files they name are checked.
* test(cli): the Windows staging test's lstat mock honours throwIfNoEntry
The received-files lookup above a rendered folder now treats a record path
that exists but is not a readable file (a folder, a dangling link, any
other kind of file) as an unreadable record, the same answer the folder's
own record gives. Only a missing record means nothing was received.
A listed file now counts as inside the rendered subfolder when one of its
parent folders is the same folder on disk, so naming the subfolder in
another letter case on a case-insensitive disk keeps its received files.
* fix(parsers): helper lookups skip the project above the working folder, not only the folder
* fix(parsers): compare a missing PATH folder by its nearest real parent, so Windows short names match
* fix(engine): extraction-time video downloads get the not-media check
A video src that is still remote at frame extraction is downloaded again and
then probed. That copy now gets the checks other media downloads get before
anything reads it as media:
- the not-media sniff, so an HTML, XML or JSON body (including a DASH
manifest) is refused with the existing NotMediaPayloadError, classified as
invalid_media;
- on a render service (PRODUCER_RESTRICT_PAGE_NETWORK), the same
-format_whitelist an https input gets, so a playlist, manifest or concat
list fails to open whatever its bytes say, and no file it names is read.
Real mp4, mov and webm downloads extract the same frames as before.
* fix(engine): the download format check stops when the render is cancelled
* fix(engine): the not-media sniff keeps mp4 files whose box size reads as text
An ISO BMFF file opens with a 4-byte box size and a box type. A size of 60
is the byte `<`, so after the leading NULs were skipped a valid mp4 with a
60-byte ftyp was refused as a text document. The sniff now recognises an
mp4/mov box header (size 0, 1 or at least 8, then ftyp, styp, moov, moof,
mdat, free, skip, wide, sidx or pdin) before it skips NULs. HTML, XML,
JSON and playlist refusals are unchanged.
* fix(engine): the mp4 exception in the not-media sniff needs a box that fits the file
The sniff only skips its document check for an mp4/mov opening when the
first box is ftyp or styp, its declared size (including a 64-bit size) fits
the file length, and the next box header, when the sniff window holds it, is
a known media box that also fits. A document that only spells a box header
falls through to the document and playlist checks as before.
* fix(engine): the not-media sniff keeps mp4 files with leading padding or extension boxes
An mp4 or QuickTime file may open with free, skip, wide, uuid, pdin, moov,
mdat or moof as well as ftyp or styp, and may carry any box type after it.
The sniff now accepts any of those first boxes, then walks every box header
the sniff window holds: each needs a printable four-character type and a
size that fits the file. A document that only spells a box header still
falls through to the document and playlist checks.
The outside-project media check skipped any src starting with data:, blob:,
about: or http(s): in any letter case, while the readers resolve everything
but exact http:// and https:// URLs as a local path. A src such as
data:x/../../outside/clip.mp4 passed the check and the readers opened the
file it named.
The check and the media type preflight now use the readers' remote test,
isHttpUrl, and check every other src with a shared containment helper,
isInsideAssetRoots. Frame extraction, the audio mix, and the HDR and video
sound probes also refuse a local source outside the project, compiled and
download folders on their own when outside files are not allowed.
The CLI static project server and the producer and engine file servers bind
127.0.0.1, but answered any Host header. They now refuse a request whose Host
is not 127.0.0.1, localhost or [::1] at their own port (or the in-process
origin the CLI hands out when listen is refused), and their responses carry
frame-ancestors 'self' and X-Frame-Options: SAMEORIGIN so another site cannot
frame the served page.
The notice a render prints for a received project, and the left-out warnings and
outside-files list that publish, feedback and cloud render print, now show control
characters from references, file names and paths as visible escapes instead of
sending them to the terminal.
While it names the references a received project makes outside itself, the render
check no longer looks at a path on another computer's share or a Windows device
path. It names such a reference in the notice without reading it. A Windows device
prefix such as \\?\ is no longer cut short as if its ? started a query.
A HEYGEN_API_KEY or HYPERFRAMES_API_KEY that a project .env sets now comes
after every credential the person saved or exported. The CLI resolver, the
media environment and the media-use skill use it only when there is no saved
login, no saved API key and no key in the shell. When one is used, a single
stderr line names the .env file.
An expired, foreign-client, unreadable or refused login now raises the login
error instead of switching to a project .env key, whether or not the folder
has a received-files record. A key exported in the shell, or set by the app
that launched the CLI, keeps its current place, and the host gateway path is
unchanged.
* fix(parsers): helper programs never come from the project a subfolder sits in
Run from a subfolder, the trusted PATH check skipped only folders inside the
working directory, so the project's own node_modules/.bin, which npm run puts
on PATH from every ancestor, still supplied helpers. The check now skips every
folder inside the outermost ancestor that marks a project (.git, package.json,
node_modules, hyperframes.json), below the home folder.
A CLI test also runs a real bare-name spawn of an executable planted in the
project folder: it runs under the raw PATH and is not found after the PATH trim.
* fix(parsers): keep the trusted lookup's comment share at main's level
* fix(cli): the audio caches never write or read through links in .hyperframes
The read-audio cache, its stems, mix and descriptions, and the audio-kind cache
now use only real folders under the project's .hyperframes. A link or a file in
place of a cache folder stops the write with a clear message. Every cache file is
written to an exclusive temp file with a random name and renamed into place, so a
link at a temp or final name is replaced, never written through. ffmpeg writes the
voice-free mix into a private staging folder. Stem downloads use the new
downloadToFile replaceLink option. Cached files are read only when they are plain
files, and a stem list may only name files in its own folder.
* fix(cli): the kind cache reads no entry through a linked cache folder
readKindCache now checks that .hyperframes and audio-kind are real folders before
it reads an entry, as writeKindCache already does before it writes one.
* test(cli): read the replaced download before checking its type and mode
The replaceLink test now reads the file's bytes and lstat result once each, so
no read follows a check on the same path.
A download whose response declares a Content-Length re-arms its attempt
timeout on every chunk, so a server that trickles just above the throughput
floor was never cut off by time. Parallel downloads also had no shared limit
on the disk they could fill.
- Each download attempt now has a deadline that incoming data never moves:
30 minutes by default, HYPERFRAMES_MAX_DOWNLOAD_MS to change it. Passing it
fails the download without a local retry.
- The default per-file cap drops from 20 GiB to 8 GiB
(HYPERFRAMES_MAX_DOWNLOAD_BYTES still overrides it).
- Downloads keep 512 MiB free on their volume
(HYPERFRAMES_DOWNLOAD_MIN_FREE_BYTES, 0 turns it off). A declared size is
claimed before the body is read and counted against every parallel
download on the same device, and free space is measured again every 4 MiB
as bytes arrive. Free space that cannot be measured does not block.
- docs/packages/engine.mdx lists the download limits and their variables.
* feat(studio): hosts can seal the preview frames NLEPreview draws
* refactor(studio): Player builds its frame src in a helper, keeping its complexity at main's
* fix(cli): snapshot shows control characters in composition text as escapes
* fix(studio-server): making or serving a still sweeps the transcode cache
Render, capture and the HTML bundler used a narrow private-file rule that
only refused Git data and env files. A composition's script could read the
app's own records under .hyperframes/ (chat history, hand-off, comments,
job log) from the file server, or a data-composition-src could inline one.
Every file server a composition reaches now uses the rule Studio, play and
present already use: Git, env, and .hyperframes/ apart from Studio's own
files and the prepared-assets and requests folders. The rule now matches
Windows spellings too: any case, trailing dots or spaces, backslashes and
stream suffixes.
* feat(studio-server): an opaque preview loads its images, media and fetched files
* refactor(studio-server): the fetch grant's reach is named, not commented
* test(studio-server): the main preview loads under the frame-token path
* refactor(core): Studio's key combo and typing-target rules live in core
* chore(core): raise the packed size budget for the key-combo and typing-target subpaths
* fix(producer): shader transitions blend in Node when the page cannot composite them
* test(producer): the compositor-unavailable fixture uses the usual 30 dB threshold
* fix(engine): restricted downloads use the capture proxy's address rule
With PRODUCER_RESTRICT_PAGE_NETWORK on, remote asset downloads now go
through the same transport and host check as the render page's capture
proxy:
- An IPv6 literal host, or a name the capture proxy refuses, is not
permitted, on the first request and on every redirect hop.
- Names resolve to IPv4 answers only, every answer must be public, and
the download dials the checked address. A name with only IPv6 answers
does not download, as in the capture proxy.
- Proxy variables (HTTPS_PROXY, NO_PROXY) are not used in this mode, so
no host is dialled without the address check. HYPERFRAMES_CAPTURE_PROXY
still routes downloads, as it does for the page.
With the setting off, downloads keep the existing transport.
* fix(engine): restricted downloads keep undici's transport with the capture resolver
The capture transport refuses any compressed response and sends no
User-Agent, and its socket and parse errors were not retried. Restricted
downloads now use the same undici agent as before, with a connect lookup
that calls the capture proxy's resolvePublicAddress: IPv4 answers only,
every answer public, and the checked address is the one dialled.
This keeps the old request headers (User-Agent, Accept: */*), gzip, br
and deflate unpacking for text fetches under the existing byte cap, the
asset path's refusal of compressed bodies, "fetch failed" retry handling,
and connection reuse. Non-public destinations stay non-retryable refusals.
* fix(studio-server): previews with no fetch metadata on a LAN host count as another site
Browsers send no Sec-Fetch-Site header over plain HTTP to a non-loopback
name, such as a LAN address used with HYPERFRAMES_PREVIEW_HOST. The preview
guards now count such a request as the Studio's own page only when its
Referer names the same host. Otherwise the preview is marked and sandboxed,
its validators are dropped, and the thumbnail, waveform, peaks and
frame-token routes refuse it.
* fix(cli): play marks and sandboxes compositions another site loads
The play server's /composition/* route now applies the same another-site
decision as the Studio preview. A load from another site comes back with
the sandbox CSP and without validators, and its HTML carries the
hyperframes-preview-for-another-site mark, so the runtime offers that site
no editing port. The play page's own player is unchanged.
* fix(player): send a same-origin Referer from the composition frame
The player's composition iframe used no-referrer, so on a plain-HTTP LAN
host its own composition load carried neither Sec-Fetch-Site nor Referer
and the Studio and play servers sandboxed it as another site's load.
same-origin sends the host page's URL only to a composition on the same
origin, so another origin still learns nothing about the embedding page.
* fix(cli): benchmark applies the received-files rule for files outside the project
hyperframes benchmark now asks outsideAssetsAllowed() before it creates its
render jobs, the same check hyperframes render and the Studio render route
use. A project whose received-files record lists code files, or whose record
cannot be read, renders without files from outside the project.
* fix(cli): a received .env key never stands in for an expired login
A HeyGen key that a received project's .env set is now used only when no
login or API key is saved. When the saved login has expired, cannot refresh,
belongs to another OAuth client, or HeyGen refused its refresh, the CLI
resolver, afterRefreshFailure and the media-use skill's resolver raise the
login error instead of switching to that key. A person's own .env key and a
shell-exported key keep their current priority.
* fix(cli): a broken credentials file never gives way to a received .env key
A malformed or unreadable ~/.hyperframes/credentials now counts as a saved
credential when deciding whether a received project's .env key may be used.
The CLI resolver raises INVALID_STORE and the media-use skill says the file
can't be read. A person's own .env key keeps its current behaviour. The skill
now tells a person whose saved login belongs to another OAuth client to run
auth login rather than auth refresh.
* fix(cli): cloud render no longer refuses a file only an unused page names
The video's pages are walked from the staged upload, starting at index.html, with the
renderer's resolver; when a page it loads is not staged text, every page stays strict.
* fix(cli): cloud render --composition checks missing files from the page it renders
* fix(core): pages with many CJK characters fetch fonts in several requests
* fix(core): keep text that shapes together in one font request
* fix(core): keep composing characters and their composed forms in one font request
* fix(core): composed forms keep their case variants in the same font request
* fix(cli): uploads leave out outside scripts; .ts counts as video only when it is one
* chore(studio-server): raise unpacked size budget for the upload file-type rule
* fix(studio-server): transport stream check never waits on a pipe and needs binary bytes
* feat(cli): uploads list every file they carry from outside the project
* perf(lint): scan CSS url references in linear time; the test checks growth, not wall time
* test(lint): cap one large malformed stylesheet instead of comparing two small timings
A film clip whose src resolves to a UNC or device path outside the
project's own share is now reported as "network share paths are not
analyzed". The clip is never stat'ed, probed, or decoded. Relative and
local absolute srcs resolve as before.
* fix(cli): uploads leave out outside scripts; .ts counts as video only when it is one
* chore(studio-server): raise unpacked size budget for the upload file-type rule
* fix(studio-server): transport stream check never waits on a pipe and needs binary bytes
* 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>
* fix(cli): play and present answer only local host names and allowed hosts
play and present listen on every interface. Each request now passes the
same Host check preview uses: localhost, loopback addresses and this
machine's own addresses and names are answered, and any other host name
gets a 403 naming HYPERFRAMES_PREVIEW_ALLOWED_HOSTS until it is listed
there. Phones and other machines on the network still open them by LAN
address or .local name.
* fix(cli): a local render of a received composition leaves out files outside the project
When the composition a local render opens is listed in the project's
received-files record, hyperframes render (full and range) no longer
brings in files outside the project. It prints one line naming the
references it leaves out and why. An unreadable record counts as
received. A project whose entry is the person's own, or that has no
record, renders exactly as before.
* fix(cli): received-render scan reads safely and treats an unreadable record as unknown
The scan behind the received-composition notice skips a file it cannot
read, finds url() references with a linear forward scan, and reads at
most 2 MB of each file. An unreadable received-files record no longer
counts as everything received for local render: the render keeps
outside files and names the record it could not read. Publish and cloud
upload still treat it as received. The notice now says the render stops
on a sub-composition outside the project rather than leaving it out.
* fix(cli): the studio render of a received composition leaves out files outside the project
The Studio render route applies the same rule as hyperframes render:
when the composition it renders is listed in the received-files record,
the job does not bring in files outside the project, and the server log
names the references it refuses.
* chore(cli): name the unreadable received-files record helper without a comment
* fix(cli): local render refuses outside files when any composition it plays was received
The received-file rule for local render (CLI and Studio) now checks
every page and stylesheet the render pulls in, not only the entry, so
an own index.html that plays a received scene also reads nothing
outside the project, and the notice names the received file. An
unreadable, truncated or empty received-files record refuses outside
files too, as publish and cloud upload do, and the notice names the
record it could not read.
* fix(cli): decide a received render from the files the compiler reads
Local render (CLI and Studio) now leaves outside-file handling as it is
for a project with no received-files record or an empty one, without
scanning anything. When the record lists files, the compiler's own read
list for the composition decides: the bundler runs out of process with a
deadline and reports every project file it reads, so stylesheet imports
and files past any scan limit count. A received file in that list, a
build that fails or runs past its deadline, or an unreadable record
refuses outside files. The scan that names refused references in the
notice is advisory only: it guards every file system call, tracks visited
files by real path, and caps the files and bytes it reads.
* fix(cli,producer): decide a received render with the render compiler's own composition traversal
The producer exports renderCompositionFiles, which walks
data-composition-src with the same resolution, normalization and private
file rules the render's sub-composition pass uses; that pass now calls
the same helper. The received-render decision adds those files to the
bundler's read list, so leading-slash and percent-encoded references the
render reads count. The advisory scan resolves compositions the same way
and reads template contents.
* fix(cli): refuse outside files in a local render whenever the project has received files
A local render (CLI and Studio) reads nothing outside the project when
the project's received-files record lists any file, or cannot be read.
No static list matches what a render consumes: the page loads its
stylesheets and scripts through the browser at capture time, and
scripts can load more, so the decision no longer depends on one. The
reference scan stays only to name what the notice says is left out. This
drops the out-of-process bundler read list and the producer composition
walk added for that decision.
* fix(cli): refuse outside files only when a received file can load other files
A local render (CLI and Studio) reads nothing outside the project when
the received-files record cannot be read, or lists a received file that
can reference others: an .html, .htm, .css, .js, .mjs, .cjs or .svg
name, or content that reads as HTML, SVG or CSS. A project that only
received images, video, audio or fonts keeps bringing in outside files
as before.
* fix(cli): keep outside files only when every received file is positively media, a font or an image
A local render keeps bringing in outside files only when each file the
received-files record lists has a known media, font or image extension
and starts with that type's signature bytes. Any other received file, a
listed file that is missing or unreadable, or a mismatch between name
and content refuses outside files. An ancestor record's entries now
match a subfolder whose name is spelled in another Unicode form; the
entry keeps its own spelling on disk.
* fix(producer,core): a sub-composition must be an .html file
The render compiler and the runtime load a data-composition-src only
when it names an .html or .htm file. Any other file, such as an image or
video, is refused as a page: render stops naming it, and the runtime
reports the load failure without fetching it.
* fix(producer,cli): the render and static file servers forbid type sniffing
Both servers send X-Content-Type-Options: nosniff with every response,
so the browser loads a file only as the type its extension names: an
image or video cannot run as a script or apply as a stylesheet. .cjs is
served as JavaScript.
* test(cli): a received media file in a composition slot is refused as a page
* test(cli): an empty nested received-files record cannot hide an outer record's received page
* fix(cli): a received media file reached under another name refuses outside files
The received-render decision now compares file identities, not names.
It walks the project once, bounded by entry count and time, and refuses
outside files when a hardlink or a symlink with a name that is not
media reaches a received file, or when the walk cannot finish. A
received file with no identity matches nothing, as in the received
files check.
* fix(cli): compare received files by link target and keep outside files for an empty record
A received media file and every other project name are now compared by the
identity of the file they reach with links followed. A linked folder that
leads outside the project, or a file whose identity cannot be read, counts as
unchecked and refuses outside files. An empty received-files record keeps
outside files without walking the project.
* chore: raise the producer unpacked size budget for the composition file checks
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>