* 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>
* fix(producer): a render that fails on a missing file says what was gone
* fix(producer): a failed look at what was missing never hides the render's own error
The missing-path probe now returns nothing when it throws, reads through at most four links and only
links that point into the temp root or the cache folder, names a removed folder by its own name, treats
a custom cache folder as the cache, and skips programs that could not start.
* refactor(producer): split the missing-path link walk into its own step
* fix(core): a clip that stops downloading no longer holds the preview in Buffering forever
* fix(core): the stuck-clip bound also holds in a hidden tab
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 tag name went into new RegExp unescaped, so a page could hang or crash
the linter (#8028). This test reads every RegExp the lint package builds
and fails when a template input is not escapeRegExp(...), an escaped*
name or an ALL_CAPS constant. Three inputs that cannot carry page text
are listed with the reason.
#8013 escaped resolve's results, recipes, stats and error lines, and
#8087 the adopt skip line. A few resolve lines still printed their
values raw: argument errors that repeat --type, --provider, --from,
--reuse and the --for path, the measured-grade note and the
similar-asset hint that repeats the intent. cube-validate's error can
quote a value from the LUT file. They now go through the same
terminalText copy, so a control character shows as \xNN. --json output
is unchanged.
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 .media/index.md generators (figma's mediaIndex.ts and media-use's
index-gen.mjs) turned only CR and LF in a record into a space. Vertical
tab, form feed, NEL, U+2028 and U+2029 still ended a row early for
readers that treat them as line breaks, and other control characters
(NUL, ESC, BEL, C1) reached the file as raw bytes.
- Every line-ending character now becomes a space.
- Other control characters are written as visible \xNN escapes through
the existing terminalText helper; tabs stay as they are.
- Both generators and the skill copy change together, so their output
stays byte-identical.
* fix(cli): tests read opencv.js from a CI cache, never a CDN mid-test
* chore(ci): re-pin the cli test job after its opencv cache step
* chore(cli): one-line note on the opencv cache copy
* test(studio): sealed preview crop and scale resize read the frame's values
* fix(studio): crop and scale resize work in a sealed preview
* test(studio): a sealed preview's crop lift and resize box survive lost or bad frame replies
* fix(studio): a sealed preview's crop lift and resize box survive lost or bad frame replies
* refactor(studio): the crop's stylesheet clip under a lift is read in its own step
* test(studio): the frame crop-lift helper answers the lift it just sent
npm, pnpm, yarn and bun run `node-gyp rebuild` on install when a binding.gyp
is present and package.json has no install script, and a .gyp file can include
any .gyp or .gypi. npm, pnpm and yarn run `node server.js` for start when
package.json has no start script. A project from `hyperframes init` has
neither script, so both defaults apply.
toolTrustedFileKind now classifies .gyp/.gypi files and server.js, in every
spelling projectPathSegments folds, so Studio's file routes and the registry
installer refuse to write them. Rename and duplicate refusals now report
why: protected_path when the destination is inside the project, as POST and
PUT already do.
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.
When the 30 s limit stops a guarded ffprobe or ffmpeg run, the line check prints for the
skipped source now ends "stopped after 30 s" instead of a generic read failure. Every
other message is unchanged.
A new test decodes a text-art file through readSamples's guarded path and expects
ffmpeg to refuse it, so dropping the demuxer list from that run fails the suite.
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(studio): slideshow scenes, block stacking, drill-down and shortcuts work in a sealed preview
* fix(studio): sealed preview keys act only with the preview focused; frame replies are validated
* fix(cli): a rename keeps the received-files record listing the moved file
On a disk that tells letter case or Unicode forms apart, a Studio rename to a
name differing only in case or form followed the old spelling, so the record
dropped the file's only line while the file moved to the new name.
- onDiskPath folds a requested name onto an existing entry only when the disk
opens the same file under both spellings, so the record follows the exact
path the rename creates, spelled as the move spells it.
- After a move, an old non-media line goes only when the file left its old
path, sits at the planned path (same identity or content), and another line
lists that path. Otherwise the line stays, as it does for a delete.
- A refused move keeps a new line for a file another move already put there.
* docs(cli): word a rename helper comment as what it checks now
* test(cli): build the rename test folder by its native real path
On Windows the temp folder can carry an 8.3 short name, which onDiskPath
spells in full, as the native real path does.
* 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(studio): error events send a class, a shape and Studio's own frames, not the error's words
Error messages from the browser, a server or the project now leave as an unsalted shape of the cut first line (numbers, quotes and paths removed) plus any HTTP status, beside the error class each sender now passes. Stacks keep only frames in Studio's own scripts as fn@file:line:col; any other frame, its name included, is ?. Component stacks keep component names. A script filename is sent only when it is one of Studio's own. The resolver shadow's mismatch list no longer carries the error's words or the selector-built animation id.
* fix(studio): error shapes match across projects and bare paths are never Studio frames
Only an absolute http(s) frame on Studio's origin is kept; the message shape cuts URLs and selector ids and uses the install salt.
* feat(studio-server): let a host count the requests the API refuses with 403
* fix(studio-server): a refusal names the endpoint asked for, not the middleware that refused it
* style(studio-server): refusal reports carry their meaning in names, not comments
* fix(studio-server): a refusal the API sends through itself again is counted once
* fix(studio-server): a request sent through the API again is known before a middleware swaps it
* test(studio): Add keyframe on a sealed preview seeds from a moved layer's translate
* fix(studio): Add keyframe on a sealed preview keeps a moved layer in place
* fix(studio): a sealed keyframe seed reads the translate the frame renders, a stylesheet's too
The text-over-face pass now treats a page-named source as missing when it
is a private project file, by its name or through a link, or is not a
regular file. Before any ffprobe or ffmpeg run, it refuses a document,
pipe or playlist that names files outside its folder or private in it.
Every probe and decode then uses render's demuxer list and a 30 s limit.
measure reads files named on the command line as before.
* test(studio): a sealed preview moves and saves a layer its animation moves
* fix(studio): a sealed preview moves and saves a layer its animation moves
* test(studio): a sealed drag of a moving layer saves nothing when the preview's tweens can't be read
* fix(studio): a sealed drag of a moving layer saves nothing without the preview's tweens
* refactor(studio): keep the drag stamp's writer beside its reader
* style(studio): keep the drag stamp reader's comment on the reader
* fix(studio): analytics send path and selector facts, not the paths and selectors
Both Studio transports now shape every event's values in one place before they leave the machine: a file path becomes its extension, kind, depth and a per-install salted hash; a selector becomes its kind and the same hash; any other value that reads as a path or selector is dropped and named in dropped_fields. Save failures send the error class, a fixed error key and the server's fixed refusal code instead of the error's words. Session fields can no longer be overwritten by a caller.
* fix(studio): save failures keep their dedupe and no selector leaves in shadow mismatches
The editor's failure dedupe keys on the error's own text again, locally. The resolver shadow's animation_not_found no longer repeats the animation id inside mismatches. Error keys and path kinds read from tables; the server's full refusal list is known.
* fix(studio): a paused save queue reports codes, not the save error's words
save_queue_paused spreads the save failure's fixed codes again; its handler lives outside the persistence hook.
* test(studio): a sealed preview's motion path finds its layer's home
* fix(studio): the motion path draws and creates in a sealed preview
* test(core): a motion path's home counts a wrapper's 2D and 3D translate
* test(studio): a sealed click places a new motion path from the layer's home at the click
* test(studio): a sealed motion path refuses a bad frame reply and reads the blur root via the port
* fix(studio): a sealed click places a new motion path from the layer's home at the click
* refactor(core): a motion path home reads a matrix's translate in one small helper
* test(ci): flag registry listings under HeyGen names that server.json never held
* ci: watch the MCP registry hourly for HeyGen listings server.json never held
* test(ci): the registry watch covers heygen.com's subdomain namespaces
* fix(ci): the registry watch covers heygen.com subdomains and opens an issue when it fails
* fix(figma): write .media and component outputs without following links
The figma importer's writers (index.md, manifest.jsonl, figma-bindings.jsonl,
figma-tokens.json and component files) used writeFileSync, appendFileSync and
recursive mkdirSync, which follow a link at the target or in its folders.
- Folders under the project (.media, .media/images,
compositions/components/<name>) are created one level at a time and refused
when one is a link or resolves outside the project.
- Whole-file rewrites go through replaceFileAtomically (temp file + rename),
so a link at the target is replaced rather than written through.
- Appends open with O_NOFOLLOW and refuse a link at the target.
- index.md cells collapse line breaks, matching media-use's index-gen.mjs
byte for byte, so each record stays on one line.
* chore(figma): trim added comments; check the component folder right before writing
* fix(figma): open appends first, then check the path holds that same file
appendWithoutFollowing checked the path with lstat and then opened it, leaving
a gap between check and use. It now opens with O_NOFOLLOW first and writes
through the descriptor only when lstat finds the same single-link plain file at
the path, the pattern projectRecords' appendRecord already uses.
* fix(cli): Windows process reads and Chrome cleanup no longer pass PowerShell command text
* fix(cli): a forced Chrome close on Windows ends what Chrome started
* test(cli): the forced-close test's child holds no pipe to the browser
* test(cli): the forced-close test's child outlives a dead parent, as Chrome's do
* test(cli): forced-close test waits for the kill; PowerShell starts only via processReadArgs
* fix(cli): Windows cleanup ends only a process the CLI started, never a pid it was handed
* fix(producer): bound the static media selector check by the page it walks
The pre-check matched every script selector against each media element and
bounded the work by selector length alone. A selector such as :has(...),
a positional pseudo-class or a chain of descendant combinators can walk the
whole page on each match, so the check could block the render process.
Only tags, ids, classes and attributes joined by child combinators and at
most one descendant combinator are now matched statically. Each check is
charged for the media element's ancestors and their attribute text, and
everything else is left to the browser probe.
* fix(producer): charge each selector's full text and every simple test
The selector check charged the collapsed selector shape, so a long
attribute value or whitespace run was nearly free even though the matcher
compiles the whole selector on every call. Each media element is now
charged the raw selector length per ancestor. Attribute text is charged per
simple test rather than per compound, and it is measured only once a
non-id selector needs costing.
* style(producer): shorten the selector cost comment
* test(studio): a sealed preview's new page keeps the selection drawn and draggable
* fix(studio): a selected element stays drawn and draggable after a sealed preview reloads
* test(studio): a click after two quick seeks reads GSAP values at the playhead
* fix(studio): a click after two quick seeks waits for the sealed preview's read at the playhead