* fix(cli): play and present answer unknown paths with an inert refusal (SECOPS-2642 part 3)
An OAuth return that lands on the play or present port was a 404 document on
the same origin as the composition frame, so project script could read its
?code=&state= through a frame, a popup or the authorize redirect. Unknown
paths, missing composition files and any request carrying code or state now
get a fixed text/plain 404 on an opaque origin (CSP sandbox) that cannot be
framed and drops its opener (COOP same-origin).
play's app setup moves into an exported buildPlayApp so tests can serve it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): trim the inert refusal's comments to the package share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
- build-zip --source=chrome-headless-shell stages only the repo's pinned
build (managedChromeVersion) and only when its folder matches the pinned
digest (isPinnedHeadlessShell), instead of the newest folder in the cache.
The folder cannot fit a ZIP function, so lambda deploy refuses
--chrome-source chrome-headless-shell up front on either arch, and the
docs say the arm64 video image is where the shell runs.
- build-zip prints the headroom under the unzipped gate, and a new
"Lambda handler ZIP" workflow builds the ZIP on PRs that touch the code
it bundles, so growth fails before merge rather than in the release job.
- The arm64 image keeps @sparticuz/chromium's fonts and fonts.conf from the
handler ZIP (FONTCONFIG_PATH=/var/task/fonts) instead of liberation-fonts,
so text falls back to the same fonts as on x86. The image workflow renders
a mixed-script page on both arches and fails when any line resolves to
different platform fonts.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(skills): the launcher's floor is 0.9.65, the oldest release Desktop ships
The skill launcher now refuses any HyperFrames release older than 0.9.65, the oldest release
the HyperFrames Desktop app ships. This applies to --cli-version, to
HYPERFRAMES_STANDALONE_CLI_VERSION, to a helper started with --script and to a plugin manifest
pin. A standalone install's default npx range starts at 0.9.65. Every plugin manifest in this
repo already pins 0.9.65.
The skills guide and the plugin installation reference name the current floor, and a test
keeps them in step with the launcher. Desktop's release checks read the floor from the
published launcher, so a comment asks that it stay a string literal.
* test(skills): a helper started with --script forwards a release at the launcher's floor
The accept loop now also starts a --script helper, so all four paths are shown accepting 0.9.65.
* fix(aws-lambda): run chrome-headless-shell 158 in the arm64 video image
The arm64 video image now installs Chrome for Testing's linux-arm64 chrome-headless-shell
158.0.8127.36, pinned by sha256 and fetched with curl -f, as the whole shell folder. The Lambda
Node 22 base has none of the shared libraries the shell links and no fonts, so the image installs
them from the base's repository at the same pinned release. The image sets
HYPERFRAMES_LAMBDA_CHROME_SOURCE and HYPERFRAMES_LAMBDA_CHROME_PATH itself, and the nested video
function no longer passes ChromeSource, which would override them. stage-arm64-image.ts stops
fetching the sparticuz arm64 pack and drops the ZIP's x86 sparticuz Chrome instead.
The x86 handler ZIP stays on @sparticuz/chromium, bumped from 148.0.0 to 153.0.0. It builds at
258,502,222 bytes unzipped, under Lambda's 262,144,000-byte limit and the 248 MiB in-house gate.
Two fixes for --source=chrome-headless-shell:
- build-zip.ts staged only the executable, which exits at launch without its ICU data and .pak
files. It now stages the whole shell folder at chrome-headless-shell-linux64/.
- Nothing set HYPERFRAMES_LAMBDA_CHROME_PATH, which src/chromium.ts requires for that source.
The SAM template and the CDK stack now set it to the bundled shell when ChromeSource asks for it.
Drops the unused @types/aws-lambda devDependency, which the dead-code audit reports whenever this
package's manifest changes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* ci(publish): build the Lambda arm64 video image on an ARM runner
The video stage now installs Chrome's system libraries with microdnf, so it runs code for arm64.
The pack job built that image on ubuntu-latest with no emulation, which it could do only while the
stage copied files. A new lambda-video-image job builds it natively on ubuntu-24.04-arm, from the
handler zip whose sha256 the zip job reported, and reports the OCI tarball's sha256. Pack downloads
that tarball, checks the sha256 against the job's, and pins it as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(aws-lambda): fit the comment ratchet and the package size budget
chromium.ts loses the two doc lines on BUNDLED_SHELL_DIR and BUNDLED_SHELL_PATH; the names and the
SAM template's comment already say what they are.
@hyperframes/aws-lambda's unpacked budget goes from 290,508 to 298,000 bytes. The package unpacks to
295,324 bytes, up from the shared chrome-headless-shell staging module the ZIP and image scripts now
import and from the README and docs that describe the two Chrome sources.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The engine ceiling moves from Beta 152.0.7977.30 to stable 158.0.8127.36, with its Chrome for
Testing digests. The places that installed `@stable` or an older pin follow it: the CI test
workspace, the regression test image, the k8s and Cloud Run examples, the CLI render image
(amd64) and the Lambda build hint. The motion-blur nightly keeps its pinned-versus-stable
comparison: the pin leg now uses the workspace's pinned shell, and a stable leg fetches stable.
The chat regression golden is regenerated on 158. Chrome 157 renders it pixel-identically to
158, so the previous golden recorded Chrome 152's paint of a background-clip:text phrase whose
word spans start at opacity 0.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Clicking or dragging the scrubber while a film played left it paused at
the new spot, and `paused` turned true without a `pause` event. The
controls now hold a playing film during the press and play on from where
it is released, like a <video>'s own controls; a paused film stays
paused. A touch scrub no longer replays as mouse events.
seek() gains an opt-in { keepPlaying: true } for hosts (keyboard seeks,
chapter jumps). A plain seek(t), and setting currentTime, still land
paused, so existing callers keep their behavior.
The packed player tarball grows 339 bytes (158705 to 159044, packed with
pnpm 10.17.1 as CI does). main sat 11 bytes under the 1% gate, so the
packed budget moves to 159100; the unpacked size stays within budget.
Co-authored-by: robinebers <16515780+robinebers@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
A page that embeds <hyperframes-player> can now give it its own play,
pause and volume icons and its own loading logo, by putting elements with
a slot attribute inside the player. Anything the page leaves out keeps
today's HyperFrames look.
Co-authored-by: robinebers <16515780+robinebers@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
The skill launcher raises its floor to 0.9.64, the oldest release with every
protection for projects received from someone else. The floor applies to a
plugin pin, to --cli-version and to HYPERFRAMES_STANDALONE_CLI_VERSION. A
release below it is refused with a message that names the floor.
The skill lifecycle reference no longer sends the agent back to the project's
pinned release after a failed check. The agent stops and reports, and runs
the old release only when the person asks for it. The CLI notice for a
project that pins a newer release now says the pin is the person's choice.
The media-use copy of the received-files rule now reads the host app's kept
copy of an expected project's record, as the CLI does. It adds back each kept
entry whose path still holds something, checks the folder identity for a
project found only by dev and ino, and counts every file as received when the
copy has no list, is doubted, a link, oversized, unparsable or another
project's.
In both the CLI and the copy:
- a kept copy whose identity names another folder counts every file as
received instead of being ignored;
- a kept copy that fails its first read, for example because the app replaced
it mid-read, is read once more before every file counts as received;
- a kept copy named both by path and by dev and ino is read once.
The docs no longer suggest that the app's next read restores a kept entry
whose file is gone.
* fix(producer): charge generated mount scripts and scoped styles to the expansion budget
The expansion budget charged only the source bytes of each mounted file.
The inliner wraps every inline script in kilobytes of scoping code and
prefixes every style rule with the host's scope, so tiny scripts or a long
composition id over many rules assembled a page hundreds of times larger
than its source.
The inliner now reports what it generates through a chargeEmitted option.
Each wrapped script is charged once built. Each style rule reserves an upper
bound before it is scoped and settles to its real size after, so no rule is
built past the limit. Generated output has its own 32 MB allowance.
* fix(core): reserve the separator postcss re-joins scoped selectors with
The per-rule reservation summed a bound per selector but left out the
separator. postcss's selectors setter re-joins the list with the first
separator in the authored selector, so a wide first separator over many
selectors grew the rule past its reservation before it was charged.
* test(core): give the scoper bound test the same time limit as its neighbour
* fix(cli): keep files received that a host's kept record still lists
When the received-state file names a project as expected and the host
keeps its own copy of that project's record beside the state file, the
received-file checks read the record together with each entry that copy
lists whose path still holds something. A record shortened or emptied
outside the host no longer makes those files read as the person's own.
A kept copy with no list, a doubted one, a link or one that cannot be
read counts every file as received; with no kept copy, nothing changes.
* fix(cli): keep a record's own lines when the host's kept copy cannot be read
A kept copy with no list, or one that cannot be read, now counts every
file as received through its own entry, named by the kept copy's path,
instead of hiding the record's lines from Studio's rename and move
tracking. A copy found only by folder identity counts only when its
identity matches the folder, and a copy that disappears mid-read counts
as no copy.
* docs(cli): say a kept entry whose file is gone is not added back
* fix(cli): say a listed received file is gone, and drop a media file's line on rename
Follow-up to the change that keeps a deleted received page listed.
- The render warning for a listed file that no longer exists now says it
is gone and how to clear it.
- A listed file whose name was already a media name drops its old line
when renamed to another media name, so repeated renames leave no
dead lines.
- The docs say that any listed file that is not media by its first bytes
stays listed after a delete, and that the line can sit in a record
above or inside the project.
- A test restores content after a plain Studio delete and checks that
outside files stay refused.
* test(cli): match the gone-file warning without a POSIX path, for Windows
A Studio delete took a received page's line off the record, and files
created afterwards were not followed. A script in the preview could
delete every received page and create it again with new bytes, so the
project no longer counted as received and outside files were read.
A deleted page, stylesheet or script now stays listed, so whatever is
written in its place counts as received. A received page renamed to a
media name keeps its old line too. Deleted or renamed media, fonts and
images still drop off, so a media-only project keeps working.
Free's 5 cloud exports a month read as a cap on every export. One sentence in the FAQ's cost answer and on the Export page says local exports are unlimited.
* feat(cli): check reports text drawn over a face in a video
The layout audit reports text painted in front of an opaque video with its
word boxes and where the video's frame lands; Node finds the faces in the
video file with the detector `measure face` uses and adds a `text_over_face`
finding (info from 5% of the face covered, warning from 30%) with
`coveredFraction` and `faceRect`. `layout.faceCheck` in the report says
whether the pass looked. `data-layout-allow-on-face` waives it.
Also reads a two-token `object-position` whose first token is "50%" as the
horizontal one.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(cli): measure cuts names the shot a take resumes
A shot that returns to an earlier camera setup after at least one other
shot (a wide take, a close-up cut into it, the wide take again) carries
`continues`: the index in `shots` of the shot it resumes. It is read from
the signatures `cuts` already decodes, by the scene's edges, so a person
who has moved or an exposure that drifted does not hide the match.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(cli): measure hands follows a hand through a clip
`measure hands <video>` reports where a hand's palm (with the hand's
size), index fingertip or pinch is in each sampled frame of a stretch of
up to 15 s, from MediaPipe's hand landmarker. A frame with no such hand
is null, never filled in. The landmarker runs in the CLI's headless
Chrome on a page answered from disk; its code and model are not shipped
and are downloaded on first use, pinned by size and sha256, into the
trusted cache.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(cli): text_over_face is info only, and a stalled OpenCV download no longer stalls check
The face detector can take texture for a face, so text_over_face is
reported as info however much of the face is covered and never fails
--strict.
check passes its deadline and a 30 s limit into the detector's first-use
OpenCV download. A download that does not answer costs the face pass
only: faceCheck is { ran: false, reason }, the other findings are kept
and the process exits.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* test(release): a release's approver must not have pushed it, and a second maintainer must have
* fix(release): count every pusher of a release, need a second maintainer, date approvals
* docs(release): who may approve a stable release, and the second maintainer it needs
* test(release): a push the activity log records with no account stops the release
* fix(release): a push recorded with no account stops the release
A provider key from a project .env is still used when no own credential
competes. Capture vision (OpenRouter, Gemini, Google and both Vertex parts),
snapshot --describe, Gemini speech and Lyria music now print one note per key
before it is first used, naming the variable and the escaped .env path, as
the ElevenLabs note does. The ignoring notes escape the path too, and the
media-use skill gets a generated copy of the CLI's terminal-text helper.
* test(release): npm publishes with the job's OIDC token, no stored token named
* fix(release): publish to npm with the job's OIDC token, not a stored token
* test(release): catch a secret named by index or inherited, not only secrets.X
* test(publish): a stable release counts only maintainers' reviews, never the approver's own push
* fix(publish): a stable release needs a maintainer's approval, not any account's
* fix(publish): only approvers and change requesters are looked up, and a failed lookup always refuses
* style(publish): the release gate's comments and lines fit the 120-character limit
* fix(cli): leave files from outside the project out of Lambda and Cloud Run site uploads
A site upload for `lambda` or `cloudrun` followed every symlink in the project and
shipped what it pointed at, wherever that was on the machine. `publish` and `cloud
render` already ask first. Site uploads now leave a file or folder linked in from
outside the project out and name each one; `--include-outside-files` (or
`includeOutsideFiles` in the SDK's deploySite, renderToLambda and renderToCloudRun)
uploads them. publishProjectArchive called without a prepared archive now leaves
outside files out too, since nothing approved them.
— Rames
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): drop the new option comments the comment ratchet refuses
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): a host can name projects whose received files are expected or all received
HYPERFRAMES_RECEIVED_STATE_FILE points at a JSON file a host app keeps,
listing project folders (by path, and optionally by device and inode) as
"expected" or "all". For an expected project, a missing received-files
record counts every file as received and is not started afresh; for an
all project, every file counts as received whatever the record lists. A
state file that is named but cannot be read counts every file as received.
A record lock dated in the future is taken over like a stale one.
* fix(cli): read host provenance state through one file handle
* fix(cli): canonicalize host state paths like record writes
* test(cli): expect canonical received warning paths
* fix(producer): cap a render's total sub-composition expansion
The 16 MB limit checked each composition file alone, so a few small files
that mount each other many times assembled a page far larger, and the
pre-flight walk and sub-composition compile redid their work for every mount.
The pre-flight walk now reads each file once and charges every mount to one
budget: 32 MB of composition HTML across at most 10,000 mounts. Past either
limit the render fails with the existing non-retryable COMPOSITION_TOO_LARGE
error, before compiling. Sub-composition compilation handles each path once,
and the inliner charges each mount to the same budget as it builds the page.
* docs: describe the total sub-composition expansion limit
* fix(producer): check each mount path and read each fallback file once
The pre-flight walk resolved and checked a mount's path on disk for every
mount, and the inliner's disk fallback did the same for every mount it
inlined. Both now do it once per path, so a refused fan-out costs about
half a second instead of several. The test now covers both a fan-out the
pre-flight refuses and one inside templates, which only the inliner sees.
* fix(producer): the pre-flight charges mounts inside templates to the budget
The pre-flight walk could not see mounts inside a <template>, so a
template-wrapped fan-out was only refused by the inliner, after seconds of
work. The walk now charges those mounts to the same budget without
reporting them, since the inliner still only warns about a broken one.
The refusal now names which limit it passed, and the tests assert the
mount count instead of a time.
* fix(cli): a project .env provider key gives way to the person's own credential
A project .env could set OPENROUTER_API_KEY, GEMINI_API_KEY, GOOGLE_API_KEY,
the Vertex settings or ELEVENLABS_API_KEY and outrank a credential the person
set in their shell or saved settings. The earlier rule covered only received
projects; a cloned or downloaded project still won.
Now every project .env provider key is unset, with a note naming the file,
when a competing provider has a credential from a surer source: the shell or
saved settings first, then the person's own project .env, then a received
one. A project key with no competing credential is still used, model and
timeout settings still apply, and the media-use scripts note an ElevenLabs
key from any project .env before speech starts.
In the CLI process an own-project key yields only within the vision choice;
the media-use scripts remake the Gemini audio choice from the passed key
origins.
* fix(cli): weigh an own project's provider key only against credentials its feature can use
Review found that the global yield removed a person's own project keys where
the shell credential could not do the job: snapshot's Gemini key next to a
shell OpenRouter key, and a Gemini key that music needs next to a shell
service account.
- Startup keeps the received-project rule only.
- Capture drops a project .env vision key only when the shell or settings
hold another complete vision credential; the two Vertex parts are one
credential and are not weighed against each other.
- A key dropped once is not brought back when capture re-reads the same .env,
so its note prints once.
- In the audio scripts, an own project's Gemini key gives way only to the
other Gemini API key, which speech and music both accept, and an own
ElevenLabs key stays for an explicit provider choice.
* ci: publish a stable release from the push that merges its release PR
* test(ci): read the publish job's own concurrency, where a publish in flight now waits
* ci: a stable release needs another person's approval of its final commit
* ci: only a person's approval counts for a stable release
* fix(studio): the copied render command carries no composition text a shell can run
The Variables panel's "Copy render command" put every variable value inline,
quoted for POSIX shells only. A shared project's author chooses those values,
so in PowerShell, cmd.exe (including npx.cmd's re-parse) or fish a default
such as `x'; calc.exe; '` ran as commands when the command was pasted.
The command is now fixed text: `npx hyperframes render -c <composition>
--variables-file .hyperframes/render-variables.json`. Copying it saves the
previewed values to that file through a new PUT /projects/:id/render-variables
route, which refuses a link standing in for .hyperframes and replaces, rather
than writes through, a link at the file itself. A composition path that is not
one plain word in every shell (letters, digits, `_ . / -`) gets no command.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(scripts): the comment checker skips a template nested in a substitution
stripLiterals ended a template literal at the first backtick, including one
that opens a nested template inside `${...}`. On a line such as
`'${value.replace(/'/g, `'\\''`)}'` that left a backtick unmatched, so
scanCLike read the rest of the file as one template and counted none of its
comments. The ratchet then measured VariablesPanel.tsx on main at 1 comment
line instead of 31 and failed any change that removed that line.
A `${...}` is now scanned as code: strings, regexes and templates inside it
are skipped, and its closing brace returns to the outer template.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(studio-server): read the replaced render-variables record through one no-follow descriptor
The link test checked the record with lstat and then read it by path, two
lookups CodeQL reports as a file-system race. Opening it once with O_NOFOLLOW
fails if a link is still there and reads the file that open checked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): dev Studio renders apply the received-project rule for outside files
The Vite Studio adapter started every render with files from outside the
project allowed. It now asks the CLI's outsideAssetsAllowed, the same check
the CLI's embedded Studio, hyperframes render and benchmark use. A project
whose received-files record lists code files, or cannot be read, renders
without files from outside the project, and the reason prints with a
[studio] prefix.
The adapter loads the rule from the CLI source through the dev server, as it
already does for background removal. It runs only from a source checkout, so
studio takes no package dependency on the CLI.
* fix(cli): a received project's .env provider key never replaces your own credential
A received project's .env could set OPENROUTER_API_KEY, GEMINI_API_KEY,
GOOGLE_API_KEY or Vertex settings that outranked a vision or Gemini
credential the person set in the shell, so capture, snapshot describe and
media-use speech and music could send content to another account.
After the CLI and capture load a project .env, each provider key it set is
unset when that .env came with a received project (a received-files record
lists it, or a record cannot be read) and the person has their own
credential for a competing provider. One stderr line names the key, the
.env file and the credential used instead.
A person's own project .env keeps its keys and its current precedence, so
an OPENROUTER_API_KEY in a project .env still wins over a Gemini key in the
shell, as the docs describe. Voice needs no change: the person's HeyGen
credential already ranks above ElevenLabs.
* fix(cli,media-use): media-use scripts apply the received .env rule, ElevenLabs included
The media-use audio scripts read the project .env again, so a Gemini key the
CLI had left out came back. They now apply the same rule after loading: a
key from a received project's .env gives way to the person's own credential
for a competing provider. GEMINI_API_KEY and GOOGLE_API_KEY give way to the
person's Gemini key or service account. ELEVENLABS_API_KEY gives way to the
person's HeyGen sign-in, saved key or shell key. A dropped key gets one
stderr line that names the file and the credential used instead.
A received ElevenLabs key that is still used, because the person has no
competing credential, gets one stderr line naming the .env before speech
starts. hyperframes media-use tells the engine which keys it took from a
project .env (HYPERFRAMES_PROJECT_ENV_ORIGINS), so a key the CLI loaded is
not mistaken for the shell's.
When the project's folders are too many to scan for received-files
records, the CLI's note now says the project's origin could not be
checked, instead of calling it a received project.
* refactor(studio): check the shape of the CLI's outside-files rule before calling it
The Vite adapter loads outsideAssetsAllowed from the CLI source at run time.
It now checks that the export is a function and treats only a true result
as allowed, instead of casting the module's export.
* docs(auth): a received project's ElevenLabs key gives way to your HeyGen credential
* test(studio): load the received-project rule before render waits start
The publish job took the npm dist-tag from the pushed tag's suffix and refused
only an exact "latest". A tag such as v1.2.3-LATEST.1, or one with a new suffix,
still named its own dist-tag. The job's channel check now accepts only alpha,
beta, rc, next, canary, hdr, native and desktop, matched exactly.
* fix(cli): render --docker applies the received-files rule decided on the host
The container mounts only the project, so it cannot see a received-files record
in a folder above it. The host now makes that check for single and batch Docker
renders and passes --refuse-outside-files into the container when it refuses
outside files.
* fix(cli): a Docker batch decides the received-files rule once
A batch render now applies the received-files rule once and hands the result to
every row, so it warns once instead of once per row. A test now drives renderDocker
itself and checks the docker run arguments it starts.
* fix(cli): files from outside the project are uploaded only once approved
publish, cloud render and feedback --file-issue copied every image, video, audio,
font and CSS file a composition named from outside the project folder, and every
project file that links outside it, and only listed them. A project that came from
someone else could pull a file from anywhere on the uploader's disk into an upload.
Now each such file needs approval. In a terminal the command lists them and asks,
defaulting to no; a yes is remembered per project in the CLI's config folder
(~/.hyperframes/outside-files.json), never in the project. --yes, --json, --dry-run
and unattended runs leave them out with a warning naming each file and saying how
to include it. --include-outside-files uploads them without asking.
— Rames
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): check the approvals file mode only where files have POSIX modes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): compare and keyframes --shot serve only the files a bare HTML file names
A bare .html file given to compare or keyframes --shot is staged with
only the files its markup, stylesheets and sub-compositions name inside
its own folder, and only types a composition loads. Private files stay
out. A scene its project's index.html mounts is staged from the
project, so it keeps its shell.
* fix(cli): stage root-relative names, string imports, SVG links and grading tables
A bare HTML file's staging now also copies the files named by a
leading-slash URL (resolved against the staged folder), a string-form
CSS @import, an SVG xlink:href and the LUT of data-color-grading.
compare and keyframes --shot print one line naming any file they left
out. The CLI docs describe the single-file rule.
A local render brought in .js and .mjs files that markup or a project link
reached outside the project, so an imported composition could copy a script
from elsewhere on disk into the page it runs and read it. Images, video,
audio, fonts and CSS still come in. Scripts are left out with a warning that
names each one and how to include it: move it into the project, or pass the
new --include-outside-files to hyperframes render.
The policy covers the compiler's outside-asset copy, the file server's
linked files and the distributed plan's project copy.
— Rames
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): linear probe media check, and renders refuse composition HTML over 8 MB
The probe stage tested every inline script body with /<(?:video|audio)\b[^>]*>/i.
A body full of unclosed <video openers made that test take quadratic time on the
render server's main thread. hasClosedMediaTag finds the first opener and then
looks for one '>' after it, which gives the same answer in linear time.
Compile and probe work on a page also runs on the main thread, and its cost grows
with the page's size. Entry and sub-composition HTML files over 8 MB are now
refused before they are read, with the COMPOSITION_TOO_LARGE error code.
* fix(producer): raise the composition HTML limit to 16 MB
The largest real render pages are about 7 MB of HTML, so 8 MB left too little room.
16 MB is more than twice that, and still bounds one file's compile to about 12 s
on dense markup.
History undo, restore and Cmd+Z now leave alone every file that Studio's
file routes refuse to write. This covers tool-trusted, private, hidden and
node_modules paths, and scripts the project's package.json runs. Cmd+Z
passes over an edit that only changed such files. A claim no longer takes
such a file's pending change.
A claim's `overwrote` version now counts only when the server itself saw
that version at that path. A version stored for another file can no longer
become a file's earlier state.
The write rule also refuses more files that tools and agents load on
their own: opencode and crush settings, compose override files,
Dockerfile.* and Containerfile, every lefthook spelling, mise, nodemon,
devbox, wrangler, vercel and netlify settings, *.config.jsonc,
tsconfig.*.json, Taskfile.dist, simple-git-hooks, Ruby build files, and
.nix and .fish scripts.
* fix(cli): cache installs only use folders the current user owns
Code the CLI downloads or builds into its cache (Chrome, the TTS script,
audio helpers, whisper.cpp, OpenCV, the Lambda handler, optional packages)
now goes into folders created by the current user with owner-only write,
and each installed file is checked again before it is returned.
- A cache root that other accounts can add entries to, sticky or not, is
no longer used for code; the per-user cache is used instead.
- The ownership check reads links rather than following them, and a link
that leads out of the cache root is not trusted.
* fix(cli): validate cache ancestry before filesystem side effects
* fix(core): check links before parent path segments
* fix(cli): validate cached libraries and clarify private parent requirements
* fix(cli): use the shared staging directory helper for Apple builds
The lambda commands read the bucket and state machine from
.hyperframes/lambda-stack-<name>.json, which arrives with any project
someone sends. A file naming another account's bucket made render,
render-batch and sites create upload the project there.
- renderToLambda pins ExpectedBucketOwner to the state machine ARN's
account on every S3 request; deploySite takes expectedBucketOwner,
which sites create and render-batch pass.
- The state file is read only as a plain file in a real .hyperframes
folder, and its bucket, ARN, region and other fields are checked.
* feat(cli): diff --hide scores a project's layer by what it adds
A project folder is captured a second time with the layer hidden (a clone, so its
fonts and sub-compositions stay). Where the captures differ is the layer's footprint;
over it, benefit = 1 - MAE(original, with) / MAE(original, without), and the
original's copy of the layer is fitted by position (+-40 px) and size (80-120%)
into an instruction such as "move down 12 px". Moments where leaving the layer out
already matches the original are not scored. Reported in the result's `layer`;
`pass` is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): diff --hide scores a layer over most of the frame without running out of stack
The footprint's box came from Math.min(...pixels), which throws RangeError past about
150k pixels (a 500x300 card at 1080p), aborting the whole diff. The box is now one loop,
and the position/size fit reads an evenly strided sample of at most 20k footprint
pixels; benefit still reads all of them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* docs(changelog): weekly digest 2026-11-09-2026-11-16
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(changelog): embed weekly video for 2026-11-09-2026-11-16
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>