Commit Graph
494 Commits
Author SHA1 Message Date
Miguel Ángel a1ee40094d fix(studio): a value or keyframe edit shows in place in a sealed preview (#8151)
* 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.
2026-11-18 15:33:50 +00:00
Miguel Ángel a82ee10c68 feat(producer): a failed render says which file was gone again, looking only in its own folders (#8168)
* 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
2026-11-18 13:41:39 +00:00
James RussoandClaude Opus 5.5 c696c0e157 chore(aws-lambda): give the packed size budget its usual 5% headroom (#8176)
#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>
2026-11-18 12:09:00 +00:00
Miguel Ángel 94d06663b1 revert(producer): a render that fails on a missing file stops naming what was gone, for now (#8174)
* 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
2026-11-18 11:34:57 +00:00
James RussoandClaude Opus 5.5 61d65e7177 fix(aws-lambda): match the shell to its own pin, ship only hashed files, refuse the shell ZIP in CDK and SAM (#8173)
* 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>
2026-11-18 11:25:22 +00:00
James RussoandClaude Opus 5.5 ed3f05a05b fix(aws-lambda): pin the shell ZIP route, gate ZIP headroom, match arm64 fonts to x86 (#8170)
- 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>
2026-11-18 10:21:01 +00:00
Miguel Ángel 640cb37929 test(studio): share one sealed preview frame that delivers messages like a browser (#8165)
* 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
2026-11-18 09:57:22 +00:00
Michael Wang 140b701403 fix(skills): the launcher's floor is 0.9.65, the oldest release Desktop ships (#8159)
* 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.
2026-11-18 09:26:49 +00:00
James RussoandClaude Opus 5.5 81d73d2278 fix(aws-lambda): chrome-headless-shell 158 in the arm64 video image, sparticuz 153 in the x86 ZIP (#8155)
* 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>
2026-11-18 09:07:46 +00:00
a9b4745f1f feat(player): add customizable branding to the preview player (#7718)
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>
2026-11-18 04:10:18 +00:00
Miguel Ángel e6cee094b1 fix(cli): tests read opencv.js from a CI cache, never a CDN mid-test (#7968)
* 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
2026-11-18 02:02:15 +00:00
Michael Wang 63c8f8ef66 fix(skills): the launcher never starts a CLI older than its security floor (#8125)
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.
2026-11-18 00:56:38 +00:00
Michael Wang 3f3fa67f9c fix(producer): charge generated mount scripts and scoped styles to the budget (#8094)
* 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
2026-11-17 22:53:11 +00:00
Miguel Ángel 0b0108f2f6 ci: watch the MCP registry hourly for HeyGen listings server.json never held (#8107)
* 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
2026-11-17 21:47:09 +00:00
terencecho 414adffb82 fix(skills): select standalone CLI releases through the launcher (#8102)
* fix(skills): select standalone CLI releases through the launcher

* fix(cli): clarify release commands and share launcher validation
2026-11-17 21:41:22 +00:00
terencecho 1c99314a62 docs(registry): use the installed launcher in block guides (#8101) 2026-11-17 20:01:35 +00:00
Miguel Ángel 88ba1b4d7c fix(release): list the MCP server as com.heygen/hyperframes, signed by heygen.com's key (#8106)
* test(release): the MCP listing publishes with heygen.com's key; io.github retires by hand

* fix(release): list the MCP server as com.heygen/hyperframes, signed by heygen.com's key
2026-11-17 20:00:37 +00:00
Michael Wang bc5259d2d3 fix(media-use): audio scripts judge a received .env by the CLI's rule (#8086)
* fix(cli): a project .env provider key prints a note when it is used

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.

* fix(media-use): the audio scripts read a received .env by the CLI's full rule

The audio scripts judged a project .env as received only from
received-files.json at or above it. They now use a generated copy of the
CLI's rule, which also reads the host's received-state file, nested records
and the received content hashes, and treats an unreadable one as received.
A parity test runs the CLI and the copy over the same projects.

A key the CLI unset from a .env is now passed to the scripts it launches,
so they do not load it again from the same file.

* fix(media-use): match the CLI's folder walk and judge a parent .env by itself

The received-rule copy now skips folders by the CLI's exact private-path rule,
so a hidden Studio folder with an asset-like name is walked as the CLI walks
it. A .env the scripts find in a folder above the working one is judged only
by records and host state at or above that folder, so a received sibling or
a large parent folder cannot flip the person's own key. Keys the CLI unset
are matched by the folder's real path.

* fix(media-use): match the received rule's narrowed private-file check

The CLI's private-file rule now treats a hidden file as private whatever its type,
and framework build-output folders and service-account key names as private.
The media-use copy of the rule follows it, so the parity cases for hidden
asset-named Studio folders agree again.
2026-11-17 19:26:39 +00:00
Miguel Ángel 133965e4f5 fix(studio): GSAP keyframe and value reads work in a sealed preview (#8003)
* test(studio): adding a keyframe at the playhead reads a sealed preview's GSAP values

* fix(studio): GSAP keyframe and value reads work in a sealed preview

* test(studio): run the sealed keyframe test's agent on a marked Studio preview page

* test(studio): a sealed preview's GSAP reply is checked before Studio holds it

* fix(studio): hold a sealed preview's GSAP reply only when it is in shape and within bounds

* style(core): keep the snapshot limits module within the comment share

* refactor(studio): check a GSAP reply's tween in small parts

* build: raise the core packed-size budget for the sealed preview's GSAP reader

* test(core): a sealed preview's GSAP read takes a real keyframes tween

* fix(core): a sealed preview's GSAP read leaves GSAP's live objects out of a tween's vars
2026-11-17 19:11:15 +00:00
Miguel Ángel b22ca1a58e fix(release): count every pusher of a release, need a second maintainer, date approvals (#8076)
* 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
2026-11-17 16:55:33 +00:00
Michael Wang 90de9b6196 fix(cli): a project .env provider key prints a note when it is used (#8056)
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.
2026-11-17 16:52:55 +00:00
Miguel Ángel 9b565c8e02 fix(release): a release merged in one push with other PRs publishes at its own commit (#8077)
* test(release): a release merged in one push with other PRs is found and published at its own commit

* fix(release): a release merged in one push with other PRs publishes at its own commit
2026-11-17 15:22:14 +00:00
Miguel Ángel 93a4d29c03 fix(studio): audio meters and audio groups work in a sealed preview (#8011)
* test(studio): audio meters and group volume in a sealed preview

* fix(studio): audio meters and audio groups work in a sealed preview

* chore(inspector): raise the unpacked size budget for the preview's audio editing kinds

* test(studio): the sealed audio test serves a Studio-marked preview, as the editing port now requires
2026-11-17 13:26:15 +00:00
Miguel Ángel c106793f79 fix(release): publish to npm with the job's OIDC token, not a stored token (#8070)
* 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
2026-11-17 12:20:49 +00:00
Miguel Ángel 4807799c4e fix(publish): a stable release needs a maintainer's approval, not any account's (#8062)
* 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
2026-11-17 09:33:45 +00:00
Michael Wang 909a9b183c build: raise the producer packed-size budget to 936,000 bytes (#8054)
With the sub-composition expansion budget (#8045) on top of the probe
pre-check change (#8044), the producer packs to 930,774 bytes. That is
over its 921,000 budget by more than the 1% tolerance, so the merge
queue's Build step refuses #8045. The growth is the new expansion budget
class and pre-flight walk in the compiler.
2026-11-17 07:55:00 +00:00
Miguel Ángel f91bbf0dac fix(inspector): the inspector's Chrome starts as root or in a container (#8050)
* test(inspector): the inspector's Chrome follows the host sandbox rule, and probes retry without it

* fix(inspector): the inspector's Chrome starts as root or in a container

* test(producer): the page check and the inspector retry Chrome without the sandbox when it refuses

* fix(producer): the page check retries Chrome without the sandbox when it refuses, like the inspector

* chore(inspector): raise the packed size budget for the shared sandbox rule
2026-11-17 07:43:53 +00:00
Michael Wang fe93f9cd47 fix: refuse media paths that ffmpeg's image2 demuxer would read as a pattern (#8047)
* fix: refuse media paths that ffmpeg's image2 demuxer would read as a pattern

ffmpeg's image2 demuxer reads %d, %03d, %% and a % before a wildcard in an
input path as a pattern of other files, folders included. Every project,
private-file and received-file check approves the literal path, so a
composition could name a placeholder whose pattern reaches images outside
the project and get them back as video frames.

Every ffmpeg and ffprobe input built from a project file now goes through
assertLiteralMediaInput, which refuses such a local path before ffmpeg runs.
The engine's urlInputArgs, the parsers' mediaInputFormatArgs and the
studio-server's new mediaInputArgs all take the input path, so the CLI
snapshot and cloud offload, lint, core grade analysis and studio-server
callers are covered too. URLs and other percent signs, such as %20, are
read as before.

* build(parsers): declare the literal-media-input subpath

* build: raise the parsers packed-size budget for the literal-media-input subpath

The new subpath adds its own built entry, type file and export map rows,
about 2.7 KB packed. It is a separate module so test suites that mock
ff-binaries still run the real path check.

* test(parsers): a harmless name shaped like a pattern is refused too
2026-11-17 07:28:09 +00:00
Miguel Ángel d7d416124f fix(studio): colour grading works in a sealed preview (#7999)
* test(studio): colour grading previews and status on a sealed preview

* fix(studio): colour grading reads a sealed preview through the editing port
2026-11-17 07:00:14 +00:00
Michael Wang 6115945cf4 fix(skills): run bundled TTS helpers from the skill folder, not the working directory (#8035)
The media-use TTS and captions references ran heygen-tts.mjs and
heygen-voice.mjs as skills/media-use/... paths relative to the working
directory. Agents run these commands from the user's project, so a project
that ships a file at that path would run instead of the bundled helper.

Name the helpers through <SKILL_DIR>, as the rest of media-use does, and add
a skill lint rule that fails when a code block or inline command runs node,
python, bash, sh, tsx or bun on a relative script path. Docs whose commands
run inside a HyperFrames checkout, or only on a checked template kit, opt out
with a marker that states the reason.
2026-11-17 05:52:10 +00:00
Miguel Ángel 5f6007ffc4 ci: publish a stable release from the push that merges its release PR (#8020)
* 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
2026-11-17 05:20:53 +00:00
Andy CheighandClaude Opus 5.5 19743ea094 fix(studio): the copied render command carries no composition text a shell can run (#8012)
* 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>
2026-11-17 05:05:28 +00:00
Michael Wang 9fae4ffd81 ci(publish): a prerelease tag publishes only to an allow-listed dist-tag (#7963)
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.
2026-11-17 04:35:57 +00:00
James RussoandClaude Opus 5.5 5f6995fe77 fix(studio-server): audio decodes are bounded, stop when nobody waits, and their cache is capped (#7991)
* fix(studio-server): audio decodes are bounded, stop when nobody waits, and their cache is capped

The waveform and peaks routes each started a full-file ffmpeg decode per request, with no limit on how many ran
at once, no sharing on the waveform route, and no way to stop one after its request went away. Their cache
folder also grew without end.

- Both routes now decode through one shared queue of 4 slots, one decode per cache entry, shared by every
  request that wants it. When the last request waiting on a decode leaves, its ffmpeg is killed (or it leaves
  the queue).
- `.waveform-cache` keeps at most 500 entries; a write past that drops the oldest.

— Rames

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(studio-server): trim comments to the package's comment share

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(studio-server): raise the packed size budget for the audio decode limits

The bounded decode queue, the abort when nobody waits and the capped cache
add about 485 bytes to the packed tarball. Main had already reached 178,489
bytes against a 178,000 budget, so together they pass the 1% tolerance
(179,877 bytes). The new budget is the measured size plus the script's 5%
headroom.

— Rames

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(studio-server): waveform decodes keep a fixed-size peak buffer, time out, and the cache is byte-capped LRU

- decodeAudioPeaks streams samples into a 65536-entry max-abs buffer that merges
  neighbouring runs when full, instead of buffering and concatenating the whole decode.
- A shared decode is stopped after 10 minutes and its slot freed.
- .waveform-cache is capped at 256 MB as well as 500 entries; a cache hit marks its
  entry used, so eviction drops the least recently used.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(studio-server): raise the unpacked size budget after rebasing onto main

Measured with pnpm pack after the rebase: 697160 unpacked bytes, over the
690000 budget by more than 1%. The new budget is the measured size plus 5%.

— Rames

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 04:34:40 +00:00
Miguel Ángel fee03bfbe1 fix(studio): an undo on a sealed preview shows in place, not after a reload (#8009)
* fix(studio): an undo on a sealed preview shows in place, not after a reload

* fix(studio): split the sealed restore checks, and the inspector budget takes the new kind
2026-11-17 03:55:09 +00:00
James RussoandClaude Opus 5.5 bffe8d5985 fix(studio-server): bound preview stills and keep proxy work to the Studio's own pages (#8007)
* fix(studio-server): bound preview stills and keep proxy work to the Studio's own pages

- Queue at most 16 stills behind the 4 being made; past that, answer 503 with Retry-After.
- Refuse a still past the end of the source before starting ffmpeg (404).
- Refuse a ?hf-proxy request on a plain preview path when another site asks for it. The
  Studio's own opaque frames already load through the frame-token path, and sandboxed
  thumbnail captures now do too.

— Rames

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(studio-server): raise packed size budget for the still-queue and cross-site checks

The bounded still queue, the past-end refusal and the cross-site proxy
check add about 2.2 KB to the packed studio-server (180252 bytes in CI).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 03:09:21 +00:00
Xuanru Li 45ff3526c0 ci(mcp): run the MCP registry publish in the mcp-registry environment (#7966) 2026-11-16 21:54:12 +00:00
Miguel Ángel a707e47379 docs(publish): say publishing waits for no approval and only admins push prerelease tags (#7960) 2026-11-16 18:37:38 +00:00
wonjangandClaude Fable 5.2 77e675574f fix(ci): a catalog publish run that main overtook ends clean instead of failing (#7816)
Every push to main starts its own Publish catalog run, so a run that finds
main ahead of its checkout has nothing left to do. It used to throw, which
marked 6 of the last 100 main runs red with nothing to fix.

Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-16 18:16:05 +00:00
Robin Ebers 5be6c1580f feat(player): add a fullscreen button to the preview player (#7726)
The button puts the whole player, controls included, in fullscreen and follows every
fullscreen change. Set disable-fullscreen to hide it.

It raises the player's package size budget. With pnpm 10.17.1, main packs to 158,705 bytes
(544,891 unpacked) and this branch to 160,137 (549,402).
2026-11-16 18:15:38 +00:00
Miguel Ángel 5f46379775 fix(publish): upload only what npm reads as checked; tags publish only main, next or alpha commits (#7959)
* fix(publish): upload only what npm reads as checked, and tag-publish only main commits

npm reads tarballs with node-tar, which can resolve a header differently from the GNU tar
check. A dry run of the same npm now has to agree on name, version and files before anything
is written. A v*-* tag now builds only a commit already on main.

* fix(publish): a v*-* tag publishes a commit on main, next or alpha

Alphas stay cut from next or alpha as release-channels.mdx says; a commit on none of them is
refused before any job builds it, and the error names it as not an ancestor of those branches.

* style(publish): wrap the npm check comment under the 120-column limit
2026-11-16 17:13:42 +00:00
WaterrrForeverandClaude Opus 5.5 071a2da0b5 fix(cli): own render-slot lock dir; refuse cache files other accounts can write (#7951)
* fix(cli): own render-slot lock dir; refuse cache files other accounts can write

Sharing one render slot across accounts no longer means sharing HYPERFRAMES_CACHE_DIR,
which holds the browser, packages and helpers each account runs.
HYPERFRAMES_RENDER_LOCK_DIR names a folder of lock records only, created sticky and
writable by all (1777); the per-user lock folder is created 0700. Help text, errors and
docs no longer suggest sharing the cache or chmod 777.

foreignWritablePath (core/cache-dir) refuses a cached file whose path up to the cache
root is owned by another account or is group/world-writable. Chrome (CLI, engine,
inspector), optional packages (incl. the Sherpa runtime), the whisper.cpp build, the TTS
script, the Apple audio helpers, opencv.js and the Lambda handler reinstall or rebuild
instead of running such a file, and trustedCacheRoot moves their installs to
~/.cache/hyperframes when another account can write HYPERFRAMES_CACHE_DIR.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cli): seal own cache installs against umask 002 and repair old lock folder modes

sealCacheInstall (core/cache-dir) takes group and world write off what this account just
installed and the folders above it up to the cache root, so an install made under umask
002 passes foreignWritablePath on the next run instead of being refused and fetched again.
Chrome, optional packages, the whisper.cpp build, opencv.js, the TTS script, the Apple
audio helpers and the Lambda handler call it after installing.

ensureLockDir makes an existing per-user lock folder 0700 again when an older release left
it open, and adds the sticky bit to an existing HYPERFRAMES_RENDER_LOCK_DIR folder, warning
once with the folder's name when it cannot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* refactor(cli): drop added comments to pass the comment ratchet

The explanations move into names: the mode bits in core/cache-dir are GROUP_OR_WORLD_WRITE
and WITHOUT_GROUP_OR_WORLD_WRITE, and the owner check is anotherAccountCanWrite. No change
in behaviour.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cli): verify the lock folder through a no-follow handle and stage installs owner-only

The render lock folder is opened with O_NOFOLLOW | O_DIRECTORY and checked and chmod-ed
through that descriptor: a link, or a folder another account owns (root may own a shared
one), is refused with RenderLockFolderRefused instead of being made world-writable or
used as is.

Chrome staging, the optional-package staging folder, the whisper.cpp build folder and the
opencv, TTS, Apple helper and Lambda handler folders are created 0700, and Chrome's staged
tree is sealed before it leaves staging, so nothing is group-writable while it installs.

foreignWritablePath accepts a sticky folder owned by this account or root, as /tmp is, and
tolerates a statSync without options; tests whose cache sat directly in /tmp, and tests
that mock statSync, failed on both. Docs note that a record naming a live process of
another account holds the shared slot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(cli): skip the uid-based Chrome cache refusal cases where there is no uid

Windows has no process.getuid, so the ownership check never runs there and the two cases
that expect a refusal cannot hold.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(core): raise the unpacked size budget for the cache ownership checks

core grew to 4418013 bytes unpacked with foreignWritablePath, sealCacheInstall
and trustedCacheRoot; the budget follows the usual 5% headroom over that size.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 15:21:35 +00:00
Miguel Ángel 5d5e2c062a ci(skills): read the ClawHub token from the main-only clawhub environment (#7923) 2026-11-16 11:40:45 +00:00
Vance IngallsandClaude Opus 5.5 ead110aab9 fix(engine,producer,cli): media inputs refuse formats that open other files (#7931)
* fix(engine,producer): media inputs refuse formats that open other files

Composition media read by ffprobe/ffmpeg now passes a format allowlist on every
input: the demuxers the installed ffmpeg reports, minus the ones that open other
files or URLs on their own (DASH, IMF and similar). hls and concat stay allowed,
since ffmpeg carries the list into every file they open. The HDR window,
alpha-plane, GIF, HEIC, audio-sidecar and snapshot reads that skipped it now use it.

The not-media check skips ID3v2 tags before it looks at the first byte, refuses a
playlist entry that is a document, and refuses JSON or non-SVG markup as an <img> src.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(engine,parsers,core,lint,cli): format allowlist reads old listings and covers every media probe

The demuxer listing is read from the binary that enforces the flag, accepts ffmpeg 4's
two-column output, and a failed listing is asked again next time. The lint HEVC probe,
the grade analyzer and the snapshot probes use it too. A nested playlist entry is refused
only for a real document signature, so encrypted segments and keys are kept; an image whose
prolog outruns the sniff window, or that is UTF-16, is no longer refused.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(parsers,producer): trim comments added with the media format list

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(engine): keep the format-limit probe's argv in the shape the ffprobe contract reads

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(engine): the image markup check reads a doctype without regex backtracking

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(parsers): raise the parsers size budget for the media format list

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 00:35:56 -08:00
Miguel Ángel b741ecf132 feat(studio): a sealed preview frame forwards Studio's playback keys (#7844)
* feat(studio): a sealed preview frame forwards Studio's playback keys

* fix(core): a key held while Studio re-sends its watch list still forwards its keyup

* fix(core): the key watch adds and removes its listeners by name, as the runtime typecheck needs

* chore(producer): raise the unpacked size budget for the runtime's key forwarding
2026-11-16 08:09:03 +00:00
Miguel Ángel 9f85cf0a25 fix(publish): a first release attempt no longer fails looking for an artifact a retry would reuse (#7929) 2026-11-16 07:08:10 +00:00
andybpanandClaude Opus 5.5 94e499d8cf fix(media-use): the carve bundle exports analyseCarveDynamics, so carve runs again (#7893)
carve.mjs calls analyseCarveDynamics for the bed's carve lanes, but the
generated lib/audio-carve.mjs did not export it, so every real run failed
with "carveApi.analyseCarveDynamics is not a function" after detecting the
tracks. The generator now bundles it, and a test fails when carve.mjs calls
any function the bundle does not export.

Reproduce on main: node skills/media-use/audio/scripts/carve.mjs --comp index.html
in a composition with a music bed and a voice.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 06:42:11 +00:00
Michael Wang 7aaeb93716 fix(producer): the plan copy checks every project entry, whatever its name (#7906)
* fix(producer): the plan copy checks every project entry, whatever its name

A top-level name that starts with two dots, such as ..assets, is an ordinary
project entry. The plan copy treated it as outside the project and skipped the
link-resolving containment check, so a link with such a name had its target
copied into compiled/. Only the project folder itself now skips the check, and
the outside test compares whole path segments.

* fix(aws-lambda,gcp-cloud-run): untar leaves out symbolic links and special files

A project archive can come from another person. A symbolic link in it could
point anywhere on the render host, and the planner would copy its target. Untar
now unpacks only files, folders and hard links. node-tar already keeps a hard
link's target inside the destination folder. The CLI's site upload follows
symbolic links when it packs, so its archives hold none.

* fix(aws-lambda,gcp-cloud-run): untar turns hard links into separate plain files

The site upload packs two hard-linked project files as one file and a hard
link. Untar still unpacks both, then gives each hard-linked file its own copy,
so the extracted project holds no links of any kind and loses no file.

* fix(aws-lambda,gcp-cloud-run): copy hard-linked files without mkdtemp; untar test in its own file

* fix(cloud): keep the hard-link copy name short so long file names still unpack
2026-11-16 06:38:08 +00:00
Miguel Ángel dac0468f70 ci(publish): publish only tarballs npm reads the way the check does (#7922)
The publish job now refuses a packed tarball that holds anything but plain files
under package/ with one package/package.json, or whose publishConfig sets more
than access, registry, exports, main and types. npm publish pins the registry,
and a prerelease tag can no longer publish to the latest dist-tag.
2026-11-16 06:27:35 +00:00
Miguel Ángel 25c6035212 fix(media-use): carve runs its own copy of core's analysis, never the project's (#7926)
* fix(media-use): carve runs its own copy of core's analysis, never the project's

carve.mjs loaded @hyperframes/core from the composition's own node_modules, so carving
a project ran whatever that project shipped under that name. It now imports a bundle
of core's carve and audio-fx functions generated beside it, with a test that fails
when the bundle drifts from core's source.

* fix(media-use): lint and format skip the carve bundle on the CLI path too
2026-11-16 05:52:09 +00:00