* test(engine): a capture page whose tab Chrome closed while opening it is replaced once or named
* fix(engine): reopen a render page whose tab Chrome closed while opening, or say why it can't
* style(engine): keep openPage's comment to two lines
* fix(studio): a sealed resize saves its anchor on the route GSAP moves it by
* style(studio): format the sealed resize test and drop the new comment lines
* fix(skills): the launcher's floor is 0.9.67
The skill launcher now refuses any HyperFrames release older than 0.9.67, the latest
release and the oldest one the HyperFrames Desktop app will accept. 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.67. Every
plugin manifest in this repo already pins 0.9.67.
The skills guide and the plugin installation reference name the new floor.
* docs(skills): the launcher floor stays at or above Desktop's oldest accepted release
Desktop currently accepts 0.9.66 and later, and a pending Desktop change raises that to
0.9.67. The launcher's comment now says its floor stays at or above the oldest release
Desktop accepts, without naming a Desktop version, so it stays true when Desktop moves.
* fix(studio-server): proxy piece list names only the pieces, not their folder
The chunked proxy join wrote each piece as an absolute path into a concat
list in the system temp folder. A line break in a folder name above the
project ended an entry early, so the rest of the path could be read as
further list lines naming other local files.
The list now sits in the cache folder beside the pieces and names each
piece by its own generated file name, and ffmpeg runs the join from that
folder. No project or folder name is written to the list, so folder names
with line breaks, quotes, '#' or '?' all join only the copy's own pieces.
The CLI publish bake uses the same join and is covered too.
* fix(studio-server): a proxy copy lock dated ahead of the clock no longer holds waiters
A copy waits for another process's lock while that owner's lock, temp and
piece files keep changing. The newest modified time was taken as is, so a
lock or temp file dated in the future looked like fresh progress forever,
and the waiter held its transcode slot without end. Preview and the
publish bake could then wait with nothing running.
Each file's modified time now counts as no later than the moment the
waiter first saw that time. A file dated ahead of the clock ages from
then, so the waiter gives up within the stall window and frees its slot.
An owner that keeps writing still sets a fresh time on each change and is
waited for exactly as before, even beside a future-dated file.
* fix(studio-server): keep the absolute piece list and default folder on Windows
On Windows the working folder is part of the DLL search, and a long cache
folder path may fail to start a process from it. Windows paths cannot hold
a line break, so the piece join there lists absolute piece paths again and
starts ffmpeg from the default folder. Elsewhere it still runs from the
cache folder with bare piece names.
The line-break test now injects an unquoted list line, so the old join
really pulls in another file, and it checks that the copy holds none of that
file's frames. A spawn test checks the join's folder and bare list name.
* fix(studio): the property panel shows a sealed preview's animated values
* fix(studio): a sealed preview's panel shows rotation and scale from tweens that only turn or grow
* feat(engine): renders send page traffic through the egress proxy in HYPERFRAMES_CAPTURE_PROXY
* feat(engine): render media downloads go through the egress proxy in HYPERFRAMES_CAPTURE_PROXY
* fix(engine): downloads through the egress proxy keep undici's fetch, so gzip text and headers work
* fix(cli): batch render, cloud render and publish print project text as visible escapes
A batch render printed each failed row's error straight to the terminal. The
error can quote file names and attribute values from the project, so control
characters in them could move the cursor, rewrite earlier lines, set the
window title or write the clipboard. That line, and the manifest path in the
batch header, now go through terminalLines() and terminalText(), which keep
real line breaks and show every other control character as an escape.
cloud render does the same for the media lines it offloads, the "also stays in
the zip" line, the largest-files list, the aspect-ratio detection line and the
names of fonts that are not on this computer. publish does the same for the
composition path in the blank-entry hint and for the publish failure message.
The manifest file and --json output are unchanged.
* fix(cli): sign-in callback ignores requests without the login's state
The browser sign-in listens on a local port for the redirect back from the
sign-in page. It acted on an error in that redirect before checking the
state value, so any page or local process that reached the port could end a
pending sign-in and put its own text in the terminal. A request with a
missing or wrong state also ended the sign-in.
Now only a request carrying the login's state can end it. Any other request
gets the same 400 page as before and the listener keeps waiting for the real
redirect or the timeout. A sign-in that is cancelled or fails on the sign-in
page still carries the state, so it reports the failure as it does today.
The error text from the redirect, and the "Sign-in failed" line, now show
control characters as visible escapes.
* fix(cli): variable issues and oversize file list print control characters as escapes
Variable issue lines from render and render --batch printed the variable ids
and allowed options from the project's data-composition-variables as they
were. Each line now goes through terminalText(), so control characters,
line feeds included, show as visible escapes. The issue objects and their
messages are unchanged for other callers.
When a cloud render project is over the upload limit, the list of its largest
files now escapes each path, line feeds included, so a file name cannot add a
line of its own.
Font names in the cloud render notice are looked up as written and escaped
only when printed, so a name with a trailing control character keeps its
look-alike suggestion.
* fix(cli): a callback from another sign-in says the terminal is still waiting
The 400 page for a callback without the login's state now tells the person to finish signing in
from the newest tab, since the terminal keeps waiting instead of ending the login.
* fix(studio): copy, duplicate and audio lane updates work in a sealed preview
* fix(studio): a sealed copy keeps its starting selection, and a stale lane read is dropped
* fix(studio): a saved lane value outlasts an older sealed read, and cut deletes in its own project
* fix(studio): a sealed preview pauses on press and reopens a link's selection
* fix(studio): a linked selection retries on a timer, whatever the playhead
* refactor(studio): one lookup-state hook keeps the URL-state hook's size where main had it
* fix(studio): a linked group member keeps the lookup waiting until the preview can answer for it
* fix(cli): reject bad billing --timeout and --needed values as usage errors
Closes#7909
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(cli): share one positive-integer flag parser across billing, compare and share
Refs #7909
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): resume checks the segment file the join reads, not the manifest's path
A resumed segmented render now validates each reusable segment at its own
computed path in the segment folder. It must be a plain file, not a link, and
match a slice of this render's plan. The path a manifest records is never
opened or probed.
* fix(engine,producer): concat joins open only the list and encoder containers
Both concat-demuxer joins (the engine's chunk and segment concat and the
distributed assemble join) now pass a format whitelist of concat, mov and
matroska. ffmpeg applies it to every file the list opens, so a listed file
that is a playlist or manifest cannot pull in other files, while mp4, mov and
webm joins work as before.
* fix(producer): resume reuses only segments this install recorded
Segment manifests are now signed with an HMAC keyed by a per-install secret
kept in the HyperFrames config folder, outside every project. Resume trusts a
manifest only when its signature checks out, so a segment folder copied from
another machine or shipped inside a project is captured again, while a
render's own interrupted run resumes as before.
* docs(producer): restore the segment path ordering comment and rewrap resume docs
* fix(producer): replace an empty or short resume key file
A key file too short to use is now replaced by a fresh key instead of
disabling resume for good. A missing key is still linked into place, so
renders that create it at the same time share one key; a test runs eight
processes against one path to check that.
* fix(producer): warn under --resume when no resume key is available
When the resume key can be neither read nor created, for example on a
read-only home folder, a file system without hard links or a serverless
runtime, --resume now logs one warning that every segment will be captured
again instead of only reporting zero complete segments.
* fix(engine): fail a concat join at a list entry ffmpeg refuses
The concat demuxer ends the stream at a listed file it cannot open and ffmpeg
still exits 0, which cut the output short without an error. -xerror on the
concat input makes the join fail instead. mp4, mov and webm joins still exit
0.
* fix(producer): resume checks each reused segment's SHA-256
Each finished segment's SHA-256 is now recorded in the signed manifest. The
hash is taken once when the segment closes, and on resume only the files
about to be reused are hashed again, so a file swapped for another of the
same size is captured again.
* docs(cli): note that resume re-checks segment hashes and recaptures older segments once
* fix(studio-server): proxy joins only its own pieces, through the shared concat input
Studio's chunked proxy copy now names its pieces with a tag keyed by the
user's preview token, so pieces that arrive inside a project folder sit at
names it never looks up and every piece is encoded fresh. A stopped copy of
the user's own still continues from its finished pieces.
The piece join uses concatListInputArgs, now in @hyperframes/parsers so the
engine, producer and Studio share it. It allows only local files in the
concat, mov or matroska formats and fails at a refused entry. The cache sweep
recognizes both tagged and older piece names.
* test(parsers): prove the concat protocol whitelist with a data: entry
ffmpeg already refuses http:// in a concat list opened from a file, so the
test passed without the whitelist. A data: entry opens by default; the test
now asserts it is refused as not on the 'file' whitelist.
* fix(studio-server): only the copy's own tagged pieces count as lock progress
The copy lock counted any .part-<key>- file as the owner's progress, so a
piece shipped with a future modified time kept a stalled lock looking active.
It now counts only names under the copy's own tagged piece prefix. The cache
sweep removes untagged pieces past the usual age even while that copy runs,
and measures age in both directions so a future-dated piece is swept too.
* fix(studio-server): say once when proxy pieces cannot be keyed to the user
Without a preview token, piece names use a per-process secret, so pieces are
reused only within that Studio process. Studio now logs that once, so a copy
restarting from its first piece after a restart has a visible cause.
* test(studio-server): name the proxy join test for what it checks
* fix(producer): derive the segment manifest key from the preview token
Sign segment manifests with an HMAC key derived from the per-user preview
token instead of a separate key file. The token is created with an exclusive
open, so concurrent renders never end up with different keys, and it is only
used when the file is private to this user.
Resume now checks a segment's SHA-256 before probing it, and a real-ffmpeg
test documents how the concat join treats an entry that is itself an ffconcat
list.
* docs(producer): describe the manifest key per user and the no-token case
The generic "Try --docker for containerized rendering" hint was printed
under every failed render. When the failure is a video source FFmpeg could
not read, a missing file or a 404 URL, a container reads the same source
and fails the same way. Those three now get a hint about the file.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
"1,080" and "3.5%" were split at the separator and counted as two words,
so a two-word line such as "1,080억 달러" was timed as three and its
shortest allowed hold went from 0.4 s to 1.05 s.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* fix(studio): a value or keyframe edit shows in place in a sealed preview
* fix(studio): a sealed group edit reloads once at its end, and a batch renders its last tween
* refactor(studio): the sealed tween patch path lives in its own module
Keeps useGsapScriptCommits under Studio's 600-line limit, and records the authoredOpacity helpers' move into core as an intended deletion.
* refactor(studio): the sealed tween patch code passes the quality audit without suppressions
Splits the frame-side change parser per kind, the tween lookup and keyframe rebuild into small checks, and the reachable-preview patch out of applyPreviewSync; drops an unused type re-export.
* 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>
* feat(producer): a render that fails on a missing file says what was gone again
Restores the diagnostic the previous commit on main took out, as it was; the commits after it confine what it looks at.
* test(producer): render failure diagnostics never probe a path from error text or outside the render
* fix(producer): probe a missing path only from a real error, inside the render's folders
describeMissingPath now reads only the path Node set on an ENOENT error, never
one quoted in a message the page can write, and looks on disk only under the
render's temp root, extract cache or work folder. Any other path is named from
its text, so a network share is never contacted and the facts cannot tell an
existing path from a missing one.
* test(producer): a missing-path probe never passes an outside link or climbs above its folder
* fix(producer): walk down from the render's own folder and check each link before following it
* build(producer): give the packed size budget its 5% headroom with the missing-file diagnostic back
* test(studio): a sealed scene's children and clip parents fill as an open preview's do
* fix(studio): a sealed preview's scene children and clip parents come from the editing port
* test(studio): a sealed preview's first-frame event carries its clips and length
* fix(studio): a sealed preview's first-frame event counts its clips from the document copy
* refactor(studio): drop two comments the names already carry
* test(core): reading an svg id scope's size never walks its ids
* perf(core): count an svg id scope's renames once, not on every stylesheet it rewrites
* test(cli): time where the very-many-files case spends its time on each runner
* fix(cli): the received-render size tests cap the walk instead of writing 20,000 entries
* fix(studio-server): an inserted scene names its file from the project root, as the renderer reads it
* test(studio-server): keep a test comment under the line limit
* fix(studio): refused group, freeze frame and animation saves keep the server's status
* refactor(studio): withStatus says what it does without a comment
* test(producer): remote scripts and stylesheets inlined at compile time stay within the size limit
* fix(producer): fetch each remote script and stylesheet once, a few at a time, within the size limit
Every inlined copy is charged to the render's expansion budget as it arrives;
going over fails the compile with COMPOSITION_TOO_LARGE and stops the
downloads still queued. Remote CSS is spliced in literally, so `$` sequences
in it are no longer expanded.
* fix(producer): drop the budget label comment the comment gate counts
* fix(producer): count a remote script when it arrives and stop the queue on an integrity mismatch
* test(producer): font normalization tests answer Google Fonts from a stub, not the network
* style(producer): wrap the stubbed font response
#8173 set the budget to 82,000 against 81,378 bytes measured, about 0.8%
over. The budget file's own rule is 5% above measured, so the next small
change would trip it again: ceil(81,378 × 1.05) = 85,447.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The bench's openStudio now waits in the page for Studio's own word that the
composition loaded (studio_look reports a duration) under the one 90 s boot
budget, instead of a separate 30 s poll that failed a case Studio was still
loading after a reload under load. A boot that never loads names Studio's last
report, and seekBound names the condition it was still waiting on.
hiddenTarget no longer throws on a preview frame detached mid-scan: puppeteer
throws that synchronously, so the per-frame .catch never ran.
* revert(producer): a render that fails on a missing file stops naming what was gone, for now
This reverts commit cfea8cfff5 (#7955). The detail comes back in a follow-up that only looks inside the folders the render owns.
* revert(producer): name the files the #7955 revert removes in the deletion guard
* fix(aws-lambda): match the shell to its own pin, ship only hashed files, refuse the shell ZIP in CDK and SAM
Review follow-ups to the pinned shell route:
- build-zip --source=chrome-headless-shell accepts the folder only when its
digest is pinned for this version, not for any pinned build.
- It leaves out the files the digest skips (debug.log and chrome_debug.log,
which Chrome writes as it runs), so nothing unhashed ships.
- The CDK construct throws on chromeSource "chrome-headless-shell" and the
SAM template allows only sparticuz, as lambda deploy already refused it:
a shell ZIP cannot fit a function. The CHROME_PATH wiring for that ZIP is
gone with it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(aws-lambda): raise the packed size budget to 82,000 bytes
The shipped build-zip script now checks the shell against its own
version's pin and skips the files the digest leaves out. That takes the
tarball to 81,378 bytes in CI, over the 80,500 budget's 1% tolerance;
main was already within about 200 bytes of it.
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>
* test(studio): property panel edits in a sealed preview reach the frame's element
* fix(studio): property panel style and attribute edits show in a sealed preview
* fix(studio): keep live property saves synchronous and use the runtime's realm-safe element check
* fix(studio): a sealed edit's put-back never replaces a newer edit
* refactor(studio): keep the sealed save wait private
* fix(studio): check a sealed edit's put-back reply without the helper main removed
* test(studio): share one sealed preview frame that delivers messages like a browser
* test(studio): name the sealed frame's port wrapper instead of commenting it
* fix(ci): the capture check treats .test-helpers files as tests, like the rest of the repo
* test(studio): keep the sealed frame's delivery helper private
* fix(studio): keep test helpers out of Studio's typecheck, like core does
* test(producer): a deep or query-stretched composition folder stays within the size limit
* fix(compiler): rebase composition asset paths from the file read and charge what they add
A mount's references now rebase from the project file the render read for
it, so a query or fragment in data-composition-src no longer lengthens every
rebased path. Every byte a rebased reference adds, including the entry file's
own rebase, is charged to the render's expansion budget as it is produced.
* test(producer): close the font embedding block after the rebase
* fix(cli): figma commands print manifest and folder text with visible escapes
figma asset prints a manifest row's id, path and description, and the <img> snippet built
from them. These lines, the index.md regeneration warning and the tokens 'wrote' line now go
through terminalText, so control characters show as visible escapes. The manifest file and the
returned records are unchanged.
* test(cli): run the figma escape fixtures where file names may hold control characters
* fix(cli): project folder names print control characters as visible escapes
check, info, compositions, benchmark, play, present and preview printed the
project folder name, and in places the project path, straight to the
terminal. A folder name can hold escape bytes on Linux and macOS, so a
received project could move the cursor, rewrite earlier lines, set the
window title or write the clipboard. Those lines now go through
terminalText(), as validate, snapshot, layout and lint already do. This
covers the preview summary, --status, --stop, --list and --kill-all lines,
and the check report path. The CLI's own colours stay, and --json output is
unchanged.
The play page also HTML-escapes the name in its title and footer, as the
present page does.
* fix(cli): preview --selection and --context print Studio text as visible escapes
The human output of preview --selection and --context printed the selected
element's label, source file, target and thumbnail URL, and the preview
server's project name, straight to the terminal. These come from the
composition or from whichever preview server answers, so control characters
in them could move the cursor, rewrite earlier lines, set the window title
or write the clipboard. They now go through terminalText(), as do the
failure messages these commands print. The CLI's own colours stay, and
--json output is unchanged.
* fix(cli): cloud get, list and delete print server fields as visible escapes
The human output of cloud get printed render fields from the server, such
as the failure message, title, composition and URLs, straight to the
terminal. A failure message can quote text from the rendered project, so
control characters in it could move the cursor, rewrite earlier lines, set
the window title or write the clipboard. cloud get, cloud list (rows and
the next-page token) and cloud delete now pass those fields through
terminalText(). The CLI's own colours stay, and --json output is unchanged.
* fix(inspector): the live inspection stamp gives the page only the generation id
prepareLiveInspection wrote the project's absolute path into the preview
page as window.__hfLiveInspection.project. Nothing in the page reads it, but
any composition script on that page could, which told it the account name
and folder layout. The page now gets only the generation id; the project
path stays with the host that prepared the page.
* fix(skills): locate.mjs keeps its grid font in a private per-run folder
locate.mjs drew its grid labels with a font at the fixed shared path
/tmp/locate-font.ttf. It used whatever file was already there and copied a
system font onto that path otherwise, following any link in its place. On a
machine shared with other accounts, someone else could plant that file
first, so the grid showed wrong numbers, a file appeared where they chose,
or every run failed.
The font is now copied into a folder made with mkdtemp (mode 0700) for each
run and removed when the run ends, so no file another account can create is
read or written. The skills manifest hash is regenerated.
* fix: escape the check report path and lint warnings, and harden locate.mjs font cleanup
check's report path notice and its not-recorded warning, and preview's
"Lint did not finish" warning, now print control characters as visible
escapes, like the other lines that carry the project path.
locate.mjs escapes the font path for ffmpeg's filter syntax, so a temp
folder with ':', ',', quotes or brackets in its name still works, and it
removes its font folder when the run is stopped by SIGINT or SIGTERM before
re-raising the signal.
play and present share one HTML escape helper.
* refactor(cli): keep the shared HTML escape helper within the comment budget
* fix: one HTML escape helper for the CLI, and locate.mjs escapes its font path in one pass
The sign-in callback page uses the shared escapeHtml helper, which now also
escapes single quotes.
locate.mjs escapes the font path for ffmpeg's option list and filtergraph
in a single replacement with the same result as before, and removes its
font folder on SIGHUP as well as SIGINT and SIGTERM.
* fix(cli): escape render output paths and cloud upload names
A finished render printed its output path and the desktop app hint raw.
The default output path sits under the project folder and is named after
it, so the folder name reached the terminal on every render. Batch renders
printed row output paths and the manifest path raw, and cloud render
printed the archive name in its upload progress lines and walked file
names in its left-out warnings raw. These lines now go through
terminalText() or terminalLines(). --json output is unchanged.
* 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>
* test(producer): a font many rules name stays within the page's size limit
* fix(producer): inline a local font only while the page stays within its size limit
Only url() sources inside @font-face rules are replaced, and every inlined
copy is charged to the render's expansion budget. Once the budget is spent,
the remaining references keep loading the font from its file.
* fix(producer): keep the font anchoring test and name the fit-or-skip charge
* fix(studio): a sealed preview's element reads are bounded, and a frame with no agent answers at once
* fix(studio): a sealed preview's sources and style names are bounded too, never cut
* test(core): two editing clients of one preview frame each get their replies
* fix(core): each editing client takes its own port, so a sealed preview answers Studio again
* test(core): SVG id renaming shares its table, looks up only named ids, caps and charges what it adds
* fix(core): SVG id renaming shares one table, caps id prefixes and charges the bytes it adds
* test(core): a long namespace is hashed once per mount
* fix(core): sanitize and hash each mount's namespace once, before minting its ids
* test(core): page goldens carry the regenerated selector alias bundle
A folder move or delete in Studio checked each file inside only by its
name. A script that package.json runs from a subfolder could be moved
aside or deleted with its folder. A move could also land a file on a
path a direct write refuses, such as a script package.json runs or
mise/config.toml, by moving a folder onto the right name.
Now each entry in the folder is checked at its current path with the
same rules a direct delete or rename uses, including the package.json
scripts. For a move, it is also checked at the path where it would
arrive. Ordinary folder moves still work.
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>
* fix(studio): a sealed preview takes its film's size from the player
A sealed preview frame refuses Studio's reads, so the size reader found no
document and Studio kept a 16:9 stage and no size for anything placed on
the picture. For a sealed frame it now reads the size its player got from
the runtime, once the player is ready, and the preview reads it again when
the player reports it.
* fix(studio): a sealed preview's size reader keeps its files' comment share
* refactor(studio): the player's size callback reaches its newest owner through one stable call
* fix(studio): a sealed preview reads its size once its film is ready to show, with no new player prop
* test(studio): the preview's mock player loads once, as a frame does
* test(core): a composition id with $ patterns scopes as text, not as a replace pattern
* fix(core): scoping writes a composition id's $ as text, at compile time and in the runtime script
* fix(compiler): bound composition variable styles and variable media sources
Charge every compile-time composition-variable rule against a size budget
and stop emitting once it is exceeded. The render compiler shares one
CompositionExpansionBudget between mounts, variable styles and variable
media sources; other callers get a 32 MiB core default. Host
data-variable-values are now parsed once per host instead of once per
declarer. Bound media sources over 8 KiB or holding control characters are
refused, and every src written is charged.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(producer): trim bound media sources and name the variable budgets in errors
Bind the trimmed value, as a browser does, so a trailing newline no longer
makes compile-time probing disagree with the runtime; refuse only interior
control characters or values over 8 KiB, and log the refusal as a warning.
The generated-bytes error now says which of variable styles or variable
media sources overran. Adds a with-mount test for the after-inline budget.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(producer): trim comments added to htmlCompiler to keep its comment share down
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>