* fix(studio): recovery drafts are kept by each project's own server, never the browser
* fix(studio): a restored draft stays offered when Studio settles which composition is open
* fix(studio): a draft read never waits on a pipe or loads an oversized record
* test(studio): the draft read's child fixture is an entry point, and its note sits in the test
* chore(studio-server): size budget covers the recovery-draft route
* chore(cli): unpacked size budget covers the recovery-draft route
* fix(media-use): audio engine reads and writes only inside the project folder
A voice line id must be a plain file name and a recording path must stay
inside the project. The engine never writes through a link or into a folder
that leads outside the project. wait-bgm reads only the renderer's own log in
assets/bgm, and a carried-over BGM job keeps its pid and log only when that
log is the engine's own.
* fix(media-use): engine outputs and recordings stay inside the project
A recording that is a playlist or list naming other files is refused,
and ffmpeg is pinned to the probed format with file-only input. The
media manifest, its index, bgm_status.json and an in-project
audio_meta.json are never written through a link, and a .media folder
that leads outside the project is refused. Index cells keep each record
on one line. wait-bgm ignores a track path outside the project and
drops a pid whose log is not the engine's own.
* fix(cli): the published skills leave their test files out of the package
The pack job no longer downloads Lambda assets already attached to the
release; it always pins the handler zip and video image this run built.
The publish job decides what the release keeps. Once
@hyperframes/aws-lambda is on npm for the version, the release must hold
exactly the assets that package pins. Before then, an asset this run did
not produce fails a first attempt, and a re-run of the same workflow run
replaces it. An asset identical to the bundle's is left alone, so a
re-run of only the publish job also works.
* fix(cli): batch outputs from a template that starts with a placeholder stay in the working folder
* fix(cli): the bare {path} template is named, not commented
* fix(hdr): bound HDR image decode and resample sizes
The native HDR image path sized its host buffers from the PNG header and
the element's page-measured layout box, with no ceiling.
- PNG decode checks IHDR dimensions and bit depth before allocating,
inflates with maxOutputLength = height * (stride + 1), and rejects image
data whose inflated length does not match the header.
- HDR images are limited to 8192x8192 pixels; resampleRgb48leObjectFit
refuses targets above that.
- A layout box larger than the output frame is shrunk uniformly to fit it.
- Decoded and resampled HDR image buffers count against the HDR extraction
budget (HDR_EXTRACTION_MAX_BYTES / cgroup limit) for the render's lifetime.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* build(engine): raise the packed size budget to 510000 bytes
The PNG header checks and bounded inflate add about 500 bytes to the
packed engine, which was already within a few hundred bytes of its
1% tolerance over the 500000-byte budget.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): the CLI trusts a preview only once it proves this user started it
* test(cli): a listener that cannot prove it is the user's preview is never trusted
* test(cli): stand-in previews answer the challenge as the user's own do
* style(cli): format the preview proof changes
* fix(cli): a preview's proof names its own endpoint and config, and the token file must be private
* style(cli): format the proof changes
* test(studio): the fake request in the host check has a socket, as every real one does
* fix(studio): a Studio started by hand proves it is the user's, so the CLI still finds it
* fix(cli): the challenge travels in a header, so Studio's routes keep their exact paths
* style(studio): keep the config producer compact
* fix(cli): fixed-name outputs and history turn records replace a link, never write through it
transcript.json, hyperframes.json patches, the grade-compare sheet, the batch manifest, diff and
measure outputs, lambda stack state and the history turn records are written through a temp file
renamed into place. A linked hyperframes.json is left alone, and the default .hyperframes/<tool>
output folder is used only when every folder on the way is real.
* fix(cli): measure and diff pictures and sbs.mp4 replace a link, never write through it
writeImage and the diff side-by-side now have ffmpeg write into a new private folder beside the
output, then rename the file over its name. measure frames already staged and renamed its PNGs.
* wip: paused before review
* test: cover credential files on the preview routes and the deploy notice
* refactor: name the inspector's file lookup for what it serves
* fix(cli): a link to a private file outside the project keeps its own left-out reason
* fix: escape the upload notice and skip private files from old manifests
* fix(inspector): the inspection page reaches only its own server and public hosts
* fix(inspector): release the page server when the proxy fails to start
* fix(inspector): open each source session in its own browser context
Image prep (HEIF and GIF, in renders and the Studio preview) now applies the
other-network-root test to every candidate path, whatever its leading
character, and decides whether a candidate is allowed before checking that it
exists. Outside-project asset collection leaves out paths on another network
root with the existing network_share reason before any file lookup.
Tests run both under Windows path rules and record every path the disk is
asked about.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
On Windows even a stat or realpath of a \\host\share path connects to that
host and signs in as the current user. Three readers looked such paths up
before refusing them:
- `hyperframes compositions` resolved a data-composition-src with
path.resolve, so an absolute or share src reached readProjectFile. It now
uses resolveCompositionSrc, the resolver preview and render use.
- The timeline reader (`timeline`, `audio`, measure) realpath'd a
sub-composition before its containment check. It now refuses a path on
another network root first.
- Artifact bookkeeping for render, check and snapshot looked up the paths
recorded in .hyperframes/video-state.json. A recorded path must now be
spelled inside a .hyperframes/artifacts/<kind> folder on the project's own
root before cleanup looks at it, and a record naming another share counts
as gone without a lookup.
* wip: partial security fix, paused before tests finished
* fix(cli): templates pull checks every file of a kit and moves a changed one aside
A template folder counts as pulled only when every path under it matches the
file list a verified download unpacked to: the same paths, sizes and SHA-256,
no extra files, links or hard-linked files. That list lives in the user's
cache, never in the project. A folder that differs is moved to a dated
templates/<slug>.changed-<time> sibling and a verified copy takes its place.
* test(cli): drop a test comment the helper's name already says
* wip: partial security fix, paused before tests finished
* fix(cli): a received-files record in a folder under the project counts for a render
The received-files lookup now also walks the project's folders for records,
skipping tool and output folders and never following links. A nested
record's entries are received files named from the project folder, so a
received scene copied in with its own record makes the render leave out
outside files, as a record at or above the project does. A walk that cannot
list every folder fails closed.
* fix(engine): give each superset extraction a folder of its own
A superset group extracted into a folder named from the group index and the
process id, and deleted and recreated it by that name in the cache root that
every render shares. Two renders in one process could share the folder and
remove each other's frames.
Partial folders are now created with mkdtemp, so each extraction writes only
into a folder it made. A cache entry is published only when its frame count
is the one the extraction wrote.
* fix(engine): make the partial folders with createStagingDir; raise the engine size budget
* fix(producer): compile and render-telemetry tag scans run in linear time
The compiler's gsap script rewrite, crossorigin and preload strips, remote
media and image src scans and inline-script scan, and the render telemetry's
tag counts, now use forward scans that return exactly what the regexes they
replace returned. Those regexes rescanned to the end of the page from every
tag opener that never closed, or from every character of a long whitespace
run in one tag. The telemetry's script and style strip stops after 8 passes.
* test(producer): give the scan fuzz tests room on CI and raise the producer size budget
* fix(studio-server): history restores stay inside the project and use only intact copies
* fix(studio-server): a history path's trailing dots and spaces are trimmed by a scan, not a regex
* test(lint): density warning ignores lanes
* fix(lint): count dense timelines per file so agents keep scenes on one lane
* chore(skills): make room for the lane pointer in the entry skill
* fix(lint): plain comment on the per-file density count
* chore(skills): say why the entry skill budget grew
* test(skills): pin the one-lane wording agents follow
* style(skills): format the lane wording test
* chore(skills): regenerate skills manifest
* docs(skills): overlapping sound effects take a second lane
* wip: paused before review
* test: cover credential files on the preview routes and the deploy notice
* refactor: name the inspector's file lookup for what it serves
* fix(cli): a link to a private file outside the project keeps its own left-out reason
* fix: escape the upload notice and skip private files from old manifests
* wip: paused before review
* fix(core): keep the flash fade, with a checked duration set per element
* fix(core): find stylable flash targets with the realm-safe predicate
* fix(media-use): local models start outside the project, so a model id never names a project folder
MusicGen, parakeet-mlx and the LTX video runner take Hugging Face ids that their loaders read as
a folder when one exists in the working directory. Each now starts in the home folder; transcribe
still resolves a ./ or ../ --model path against the caller's folder.
* fix(media-use): a relative runner override still names the caller's folder
HYPERFRAMES_PARAKEET and HYPERFRAMES_PYTHON values with a folder in them are made absolute
against the caller's folder before the runner starts in the home folder. Bare names keep their
PATH lookup.
A preview made opaque by its server (Content-Security-Policy: sandbox) under a
frame with no sandbox attribute posts as null. frameOrigins now accepts null
for such a frame, only from that frame's own window and only while its window
refuses reads.
* fix(cli): history turn ids from the project folder are checked and sent encoded
* test(cli): history turn fixtures use the id shape the CLI mints
* fix(cli): a turn's label and agent name are kept as written; only ids are checked
* style(cli): format the turn reader
* refactor(cli): the turn reader checks a marker through small predicates
The static-dedup and at-risk predictors turn each GSAP tween into a frame
range and wrote every frame of every range into a Set. The page decides how
many tweens there are and how long they claim to run, so stacked tweens
multiplied the loop and the at-risk predictor never clamped a range's end at
all: one tween ending at 1e9 s walked billions of frames.
Ranges are now clamped to the frames the render captures, merged before any
frame is written, and the interval list is capped. Past the cap, static dedup
is skipped and every frame is treated as at risk (screenshot capture), so
output never changes for the worse.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): the preview reads hf-preview messages only from its own frame
The preview message router acted on a message with no sender window, and on
any message that arrived before the preview frame existed. It now takes an
hf-preview message only when the preview frame exists, the message comes from
that frame's window, and its origin is one the frame can have: the page's own
origin, or "null" for a sealed frame. The element picker checks the same.
* fix(cli): present sandboxes deck pages another site loads and refuses framing by other sites
present now applies the same another-site decision as play to its
/composition/* route: a load by another site gets a sandbox CSP, its
validators are dropped, and the document is marked so its runtime offers
that site no editing port. Every present response also sends
frame-ancestors 'self' and X-Frame-Options SAMEORIGIN, so only the
presenter page itself can frame the deck. The route setup moves into
buildPresentApp so tests exercise the server as run() builds it.
* 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.
* 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