Long caption overlays plan thousands of verification screenshots, so the
verification budget clamped at its 300 s ceiling in every render worker. That
equals the producer's 300 s first-frame and session-init stall floor, so the
stall always won and the render failed before its first frame. Verification
fails closed on exhaustion (dedup is disabled for unverified runs and normal
capture proceeds), so a lower ceiling costs only some frame reuse.
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* feat(engine): decouple transparent background from png capture format
PNG capture used to imply a cleared page background. A new
CaptureOptions.transparentBackground lets lossless opaque PNG capture
(4:4:4 MP4 output) keep the page background. Absent, it still follows
format === "png", so alpha output and motion blur are unchanged.
Opaque PNG skips drawElement, whose verification and worker-encode
paths are JPEG-only.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(engine): add 4:4:4 chroma option to getEncoderPreset
getEncoderPreset takes an optional chromaSubsampling ("420" by
default). "444" returns yuv444p for SDR MP4, so libx264 encodes the
High 4:4:4 Predictive profile and odd sizes need no even padding.
WebM, MOV and HDR presets ignore it. The ChromaSubsampling type is
exported for the producer.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(producer): chromaSubsampling render option with lossless png capture
RenderConfig.chromaSubsampling ("420" by default) opts an SDR MP4
render into 4:4:4. "444" encodes libx264 yuv444p and captures every
frame as opaque PNG: Chrome's quality-100 JPEG is already 4:2:0 on
beginFrame and screenshot capture, and drawElement can fall back to
screenshot mid-render, so PNG is the only capture that keeps the
colour. drawElement is turned off for these renders.
The probe and main capture options share resolveCaptureSurface, so
they cannot disagree on format, quality or background.
Formats other than mp4, GPU encoding and HDR output are rejected
before any work starts, auto-detected HDR sources fail before capture,
and distributed requests refuse 444. The default render is unchanged.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(producer,studio-server): accept chromaSubsampling on render routes
The shared parseEncoderOptions validates chromaSubsampling and answers
400 for "444" with a non-mp4 format, gpu, or force-hdr, so a request
that would come back 4:2:0 never starts a render. The Studio render
route, both Studio adapters and the producer HTTP server forward it.
The producer server also refuses "444" with outputDynamicRange "hdr",
which parseEncoderOptions cannot see.
No Studio UI control; the option is route-level like crf and hdrMode.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): add --chroma-subsampling flag
`hyperframes render --chroma-subsampling 444` opts an SDR MP4 render
into full-resolution chroma (yuv444p with lossless PNG capture). The
default stays 420. The plan rejects 444 with a non-mp4 format, --gpu
or --hdr before anything renders, with a usage error that names the
conflicting flag.
The value reaches the local render request and, only when it is 444,
the Docker argv, so default Docker invocations are unchanged.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: document 4:4:4 chroma subsampling
Add a "4:4:4 masters" section to the rendering guide: when to use
--chroma-subsampling 444, why it captures PNG, the measured chroma gain
(large for text and UI, none for footage and gradients), its limits,
and a player compatibility table to be filled in from testing.
Document the flag in the CLI reference, the built-in rendering docs and
the hyperframes-cli skill reference (with the regenerated skills
manifest), and the chromaSubsampling option in the producer docs.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: add 4:4:4 player compatibility results
Fill the 4:4:4 compatibility table from testing H.264 High 4:4:4
Predictive output. Chrome 155, Edge 155, VLC 3.0, Safari on iOS 26.6
and Safari 26.6 on macOS play it, and so does AVFoundation on macOS
26.6, the framework QuickTime Player plays through. Firefox 157 on
Windows and both Windows media players do not.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: note the measured render cost of 4:4:4 output
Replace the vague "slower capture" note with measured numbers: a text
and UI composition rendered in about twice the default time, full-frame
footage in about three and a half times, because PNG encoding cost grows
with image detail.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): reject chromaSubsampling 444 in distributed render config
Distributed configs have no chroma field and validateDistributedRenderConfig
ignored unknown keys, so a JS caller passing chromaSubsampling: "444" to the
Lambda or Cloud Run SDK got a 4:2:0 file with no error. Reject it, and make
the rendering guide say so precisely.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): check a 444 render reaches the encoder as yuv444p
Every helper had tests, but nothing checked the orchestrator passes
chromaSubsampling through, so dropping it from the encoder preset or capture
surface would turn 444 renders back into 4:2:0 with all tests green. Render a
small fixture with "444" and with the default and check pix_fmt with ffprobe.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(producer): move the 444 drawElement gate into a helper
Keeps runCompileStage under the fallow complexity threshold.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: keep comment share at or below the merge-base
comment-ratchet failed on 11 files this PR touched. Keep the 4:4:4
rationale once in chromaSubsampling.ts, move the distributed-render
reason into its error message, and cut the rest.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): check a 444 render captures full-resolution chroma
The encoder check alone passes when chromaSubsampling is dropped from the
capture surface: frames are captured as JPEG and encoded yuv444p with
4:2:0 colour. Put a red/blue edge at an odd x, inside a 4:2:0 chroma
pair, and require the two pixels to differ in Cb.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): trim the chromaSubsampling.ts header to the package comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: finish switching to capturesAlpha from #6262
The merge that adopted main's transparent / capturesAlpha left these files
uncommitted, so resolveCaptureSurface still returned transparentBackground.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(engine): use transparent / capturesAlpha from #6262
main added CaptureOptions.transparent and capturesAlpha (#6262), which do
what this PR's transparentBackground did. Use them, keep the PNG check in
drawElementWorkerEncodeEligible, and re-pin test-classification.mjs and
the skills manifest against current main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): cut the 4:4:4 comment blocks to one to three lines
The reasoning lives in the PR description with the measurements.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: reconcile 4:4:4 chroma with latest main
Keep main's video-layer capture overrides, template entry resolution,
ProRes profile parsing and blur-differential tests alongside the chroma
option, and fold the encoder sub-parsers into one loop.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: keep main's compile-stage tests and regenerate the skills manifest
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): run the composition hover preview in an opaque origin
The Compositions panel hover preview framed the composition with
allow-scripts and allow-same-origin, so the composition's scripts ran in
the Studio's own origin. The frame now gets only allow-scripts. The card
no longer reads the frame: it plays the preview muted when the runtime
posts "ready", and sizes the stage from the runtime's "timeline" message.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): name the hover preview's sandbox and bridge steps instead of commenting them
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* docs(readme): show the GitHub rank and skills downloads badges
* docs(readme): size the rank badge so its text reads
* docs(readme): lead the badge row with skills downloads and rank
* docs(readme): keep the rank badge link free of stray whitespace
* fix(producer): size the first-frame stall window from the probe's browser start-up
* fix(producer): keep the chunk's fixed first-frame window without a comment
* fix(lint): flag a script that calls gsap before GSAP loads, and say so when a render fails on it
* fix(lint): judge the first gsap call by when it runs, so a listener after a deferred GSAP passes
* fix(lint): keep the gsap timing helper's comment to two lines
* fix(producer): build the render job before taking a render slot
A request whose options fail the strict render-request validator now gets
a 400 on both the blocking and streaming routes, and its inline project
directory is removed. Validate workers up front like the other overrides.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): write compiled sub-compositions only inside the compiled directory
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): keep media work files inside their directory for any element id
Map a media element id to one plain path segment before it names a frame
directory or an intermediate audio file. Ids that already are one plain
segment map to themselves, so existing paths stay the same; the producer
and the distributed plan derive the same segment.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): listen on loopback by default in the engine file server
The file server feeds the co-located capture browser, which loads it from
localhost. A caller that wants another interface passes hostname.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): refuse cross-origin browser posts to the standalone render server
A web page on another origin can no longer start a render or lint through
the server's POST routes. Requests without an Origin header (CLI tools,
server-to-server callers) and same-origin pages are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(engine): trim comments on the media path segment and file server host
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): trust the browser's Sec-Fetch-Site verdict for render server posts
A same-origin page behind a reverse proxy that rewrites the Host header sent an
Origin that no longer matched Host, so the cross-origin guard refused it. The
guard now uses Sec-Fetch-Site when the browser sends it and falls back to the
Origin and Host comparison only for browsers that do not.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): keep generated media path names apart from plain ids and within filename limits
A plain media id that already ends like a generated name now takes the hashed
branch too, so it can no longer share frame folders or audio work files with
the unsafe id that produced that name. The readable part of a generated name
is capped at 64 UTF-8 bytes before the digest, so long or multibyte ids that
contain separators stay within the 255-byte filename limit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): keep cache writes inside the project and canonicalize preview paths
- The tool's own folders (.hyperframes records, backups, preview documents,
.thumbnails, .transcode-cache) are no longer written, pruned or emptied
through a link that points outside the project. Thumbnails are still
served when their cache folder is a link; they are just not cached.
- The hf-id stamp record and the history id are replaced atomically instead
of written through an existing link.
- Sub-composition previews and thumbnails use the composition's canonical
project-relative path, and the path is attribute-encoded in the document.
- Thumbnail requests from another site are refused before any capture.
- Saved GSAP scripts escape a `</script` sequence so the script element
keeps its contents.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): refuse a UNC or device path on another root before any disk access
isSafePath now rejects a target whose root is a UNC or device root other than
the project's own before it calls realpath or lstat. Projects on a share keep working.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): answer WebMCP clients only from Studio's own page
The polyfill now starts with its tab transport limited to Studio's origin and
its frame transport off, so a page that frames Studio cannot list or call its tools.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(inspector): check Host on the per-session preview server
The preview page server applies the inspector API's loopback Host rule, so a
rebound DNS name cannot read the bundled composition or project files.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* revert(studio-server): keep writing media proxies through a linked .transcode-cache
Refusing the folder made every proxied video in such a project answer 502.
A linked cache folder now receives copies again; it is still never swept,
so nothing already in the folder it points at is removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(studio-server): drop a comment the comment ratchet refuses
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): skip HEIF and GIF preview prep when .hyperframes/prepared-assets is a link
The preview transform wrote converted images into .hyperframes/prepared-assets
through a link, so a project shipping .hyperframes as a link to another folder
had files written there. Such a project now gets its preview with the images
as written in the composition, unconverted, and nothing is written.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): never sweep a linked .transcode-cache, from Studio or hyperframes clean
The link check moves into cleanupProxyCache, which both Studio's cache
maintenance and `hyperframes clean` call, so neither removes files from the
folder a linked .transcode-cache points at.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(docs): escape catalog preview values and the install command's --vars argument
The catalog preview embeds variable values as JSON that cannot close a
script element or attribute, accepts value messages only from the page
that embeds it, and reads only declared ids with primitive values from
the link. The install command shell-quotes its --vars JSON and keeps
only variable-id keys with primitive values.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): fold CSS line endings before decoding escapes in the SVG sanitizer
A browser folds CR LF, CR and form feed into one newline before it reads
CSS escapes, so the whitespace after a hex escape can be a CR LF pair.
The sanitizer now does the same, so an escaped function name split by a
line ending is checked under its real name. The media-use bundle is
regenerated from the source.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(lint): match template ids and CSS rules in linear time
A getElementById template literal is matched against document ids with
an in-order indexOf scan instead of a regex of joined wildcards, so the
time no longer grows with the number of placeholders. The CSS rule
scanners only start a match at the beginning of a brace-free run, which
finds the same rules without rescanning long brace-less text. Lint
results on every HTML file in the repository are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(parsers): keep GSAP writer output inside its script element
String literals and quoted keys the GSAP writers emit now encode a
script closer or comment opener as \u003c, so a value can no longer end
the inline script that holds the timeline. Strings without those
sequences are written exactly as before. The writers also refuse a tween
method outside set, to, from and fromTo, and a motion path whose
coordinates or curviness are not numbers, since both are emitted as code.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(scripts): confine registry asset hosting to files inside the item
The asset hosting script now refuses a manifest path that leaves the
item directory or reaches its file through a symlink, before anything is
read, staged, uploaded or removed. A repository test fails when the
registry tracks a symlink or a manifest path that leaves its item.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(registry): pin the map blocks' d3 and atlas files to exact versions
The five map blocks load d3 7.9.2, the build the d3@7 range serves today,
with a subresource integrity hash, and fetch us-atlas 3.0.1 and
world-atlas 2.0.2, the files their ranges serve today. The bytes are
unchanged, so the blocks render the same. A repository test fails when a
registry item names an npm CDN package by range, tag or no version.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(registry): pin map blocks to d3 7.9.0
7.9.0 has been the stable release since 2024; 7.9.1 and 7.9.2 were published days ago. Pin the
long-standing version, with its subresource integrity hash.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(registry): keep the map block PR source-only and formatted
Restore the generated catalog pages and payloads, which the catalog
publish job regenerates from the item sources. Name the us-atlas URL
in us-map-flow so the call fits on one line and formatting is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(scripts): check registry asset containment with one prefix test
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(lint): scan simple CSS rules in linear time
The two CSS-rule scans in the gsap rules took a body that could cross
'{', so a closed style of many '{' with no '}' rescanned to its end from
every brace. A scanner now returns the same selector and body pairs and
remembers the next '}', so each scan is linear. Findings are identical
on every tracked HTML file.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(core): label the form-feed sanitizer case as a guard
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): resolve helper programs from PATH, never the working directory
On Windows a bare command name is looked up in the working directory before
PATH. The CLI now sets NoDefaultCurrentDirectoryInExePath at startup, which
Node's spawn and cmd.exe both honor and child processes inherit, so tools
such as powershell.exe, taskkill and npx.cmd always come from PATH.
The shared ffmpeg/ffprobe resolver no longer scans the working directory on
Windows and skips relative PATH entries.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep Python helpers from importing files in the working directory
`python -c` and `python -m` put the working directory first on sys.path, so
a file in the project named like a probed module ran instead of the
installed package. Inline helper code now drops that entry before any
import, and `-m` helpers (pip) run through runpy after the same step. Paths
and arguments are unchanged.
On Windows, findPython also skips a `where` match in the working directory.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): run the skills installer and nested CLI calls independent of the project
The global skills install ran `npx skills@<pin>` in the current folder, so
npm could take the package or registry from that project's node_modules or
.npmrc. It now runs from the home folder; the install is global either way.
When the CLI starts the media-use engine it hands over its own entry file.
The local voice fallback and the audio helpers then run that same CLI with
the same Node instead of resolving `npx hyperframes` from the project.
Without a handed-over entry they behave as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(media-use): load only provider keys from a project .env
The audio scripts copied every key of a project .env into their environment
except two. They now take the same kind of short allowlist the CLI uses:
HeyGen, ElevenLabs and Gemini API keys plus a few harmless settings. Program
overrides, runtime options, credential files and the credential store path
come only from the person's own environment.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): build whisper.cpp only from a pinned, verified release
The source-build fallback cloned the upstream default branch. It now clones
the v1.9.5 release tag and refuses to build unless the checkout is the
reviewed commit for that tag.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep registry caches apart and refuse config install targets
Registry cache file names now include a digest of the exact registry URL,
and each entry records the URL it came from, so one registry's cached
manifest is never read for another. Entries from older versions are
refetched once.
Registry installs refuse targets inside .git or any hidden directory, hidden
configuration files, and package.json, hyperframes.json and
hyperframes.lock.json. An example installed by `init` may still bring its
own package.json and .gitignore.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(capture): keep page text to one line in agent files and validate Vertex keys
Capture writes AGENTS.md, CLAUDE.md and .cursorrules from the page's title,
font names and colours. Page text is now flattened to one short line and
colours must be hex values. Existing agent files that capture did not write
are kept, with a warning.
HYPERFRAMES_VERTEX_SERVICE_ACCOUNT must now be a plain service-account key
with a Google token endpoint; other credential types skip captioning with a
warning.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): find the digest-named registry cache and trim a new file's comment
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): match registry targets as Windows names them; skills install without HOME
Windows drops trailing dots and spaces from a path segment and reads name:stream as
name, so package.json. or .git./hooks reached the files the target rules refuse.
The global skills install now falls back to the temp folder when HOME does not exist.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): turn off the Windows working-directory lookup in every program entry
The warm-check server and client are their own tsup entries and copied the
environment before cli.js set NoDefaultCurrentDirectoryInExePath, so the server
spawned a bare powershell.exe that Windows could take from the project folder.
Every entry that hides child consoles now also loads windowsExeSearch first.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): refuse Windows short-name registry targets
A segment like CLAUDE~1 or PACKAG~1.JSO opens the long name on NTFS, so it
reached the files the target rules refuse. The trailing-dot and stream-name
normalization is removed: publication already rejects those segments.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): lambda destroy runs SAM in a private folder and acts only on the selected stack
- sam delete outside a checkout runs in a fresh private temp folder,
removed afterwards, instead of the shared temp directory.
- A stack state file must name the stack it is selected by.
- destroy and deploy derive the video repository name from the stack
name instead of trusting the recorded value.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): snapshot keeps remote clips in a private folder and reads only allowed URLs
- A video URL the download policy refuses (plain http, or a private,
loopback or link-local host) is no longer handed to FFmpeg; the clip
is skipped instead, as render does.
- Remote clips are cached in a per-user, owner-only temp folder; a
folder open to other users is never reused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): upgrade --project writes package.json through an exclusive temp file
The rewrite now uses the shared atomic replace, which creates a fresh,
unpredictable sibling with exclusive creation, so an existing
package.json.tmp entry is never written through.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep env files, Git data and tool records out of served and uploaded projects
- play and present answer 404 for .env files, .git and the tools'
private .hyperframes records, as Studio's preview does for the records.
- publish and cloud render never stage an env file or tool record, even
when markup references it, and never pull in an env file from outside
the project.
- Cloud site uploads (Lambda and Cloud Run deploySite) leave env files out.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): lambda commands accept a state file whose stack name differs only in case
On a case-insensitive disk, deploy --stack-name=Demo and --stack-name=demo share one
state file, so a name that matches apart from case is the same stack the user deployed
and keeps working as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): snapshot's fallback media folder uses createStagingDir
The repository check forbids bare mkdtemp beside a caller-supplied path, because it
fails past 260 characters on Windows. Also trims a comment so the new helper file stays
within its package's comment share.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): snapshot never hands FFmpeg a remote URL
FFmpeg follows redirects and resolves hosts on its own, so a clip the downloader could
not fetch must not reach it as a URL. Snapshot now leaves such a clip out and warns,
as render does. A fallback media folder is removed when the process exits.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): cover .envrc, .env-local and .env_prod, and test present's private-file 404
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The publish job's checkout persisted its contents:write token in
.git/config, where every later step, including the package install and
build, could read it. Check out without persisting credentials and give
the token only to "Create release tag", the one step that pushes. It
authenticates its own git calls through step-scoped GIT_CONFIG_* env and
masks the encoded value. The gh steps keep their own GH_TOKEN.
The workflow test now covers the checkout flag, which steps may receive
the token and under what name, the auth header the tag push actually
carries, and that nothing is written to .git/config.
— Rames Jusso
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): Safari keeps a small file's authored preload and never holds a clip already playing
* fix(core): Safari still holds a long file's later clips that were parsed before the runtime
The sweep sets preload none on them again and gives a clip its authored preload back once its file turns out not to be long.
* fix(core): Safari leaves the src of a long file's clip that is already playing or seeking
Its file's size can arrive after the clip started; writing an in-point src then restarted its load and sent it back to the in-point.
* fix(studio): check Host on the dev server's API routes and honor preview allowed hosts
The Studio Vite dev server now applies the same Host rule as the CLI
preview server to the routes its plugin serves (/api/*,
/__hyperframes_config), registered ahead of the plugin's other
middleware, and also accepts the IP-literal and configured hosts Vite
allows by default. HYPERFRAMES_PREVIEW_ALLOWED_HOSTS is now fed into
Vite's server.allowedHosts, so a host listed there loads the Studio page
as well as passing the API's checks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): accept the *.localhost and leading-dot hosts Vite serves on the API routes too
The dev server's API Host check was stricter than Vite's own rule, so a page
Vite served on studio.localhost or under a leading-dot allowed host got a 403
from every /api call. The check now applies Vite's rule alongside the CLI's.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* ci(publish): build the Lambda handler zip in a read-only job and verify its hash before release
The handler zip build runs dependency install and bundling code. It moves out of the
publish job into its own job with `contents: read`, no secrets and no persisted git
credentials. The publish job downloads the artifact, checks its sha256 against the
build job's output, then pins and attaches it as before. A retried run still reuses
the zip already on the release.
Refs #7485
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(ci): cover the read-only Lambda zip build job and the pin step's hash check
The publish workflow test still looked for the old "Build Lambda handler zip"
step. It now checks the build job's read-only permissions and the publish job's
dependency on it, and runs the pin step for the retry, matching-hash,
mismatched-hash and empty-hash cases.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): thumbnail origin from the server, sandbox previews from other sites
The thumbnail route builds the headless browser's URL from the server's own
listening origin (a new optional `serverOrigin` on the adapter, wired in the CLI
preview server and the Vite dev host) instead of the request's Host header.
Hosts that report no origin fall back to a loopback Host only.
Preview responses (bundled, sub-composition and project files) opened from
another site carry `Content-Security-Policy: sandbox allow-scripts` and
`Vary: Sec-Fetch-Site`. Studio's same-origin iframe, browser automation and
non-browser clients are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): build the thumbnail origin from a hostname bind name
With HYPERFRAMES_PREVIEW_HOST set to a hostname, the listening address is
the IP it resolved to, and the Host check accepts the bind name, not that
IP. The thumbnail browser then loaded a 403 page. Use the bind name when it
is a hostname; IP and wildcard binds keep the listening address.
— Rames Jusso
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* style(studio): drop the serverOrigin comment that put it over the package's comment share
The hostname-bind rule is stated by its test name in serverOrigin.test.ts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): a render uses the CLI's own GSAP, so the default CDN's file needs no network
* fix(cli): the GSAP vendor lookup runs as ESM from source, so render starts again
* chore(producer): raise the unpacked size budget by the bundled-script module's 3 KB
A project-local node_modules/.bin/hyperframes can shadow plain npx hyperframes,
but npm install -g never updates it. Classify the shadowing copy like the
running one: global installs keep their manager's command, project-local
installs get the project's own manager (from its lockfile), and unknown
layouts stay quiet. The command pins the release the npx copy is running.
* perf(core): Safari clips open at their in-point and are fetched ahead
* perf(core): Safari opens a long file's clips at their in-point and leaves short files as they were
* perf(core): Safari holds a long file's later clips with no source until each one is due
* perf(core): Safari plays a long file's sound from its element instead of fetching the whole file
* perf(core): Safari holds a later clip of a long file even when WebKit began reading it at parse
* style(core): fit the long-file comments to the comment budget and the formatter
* refactor(core): one proxy trigger path, and the producer budget at its measured size
* perf(core): Safari opens a later clip WebKit read at parse at its in-point rather than holding it
* build: the producer size budget at its measured 3162274 bytes
* refactor(core): name the condition that holds a long file's later clip
* fix(reverse): give agents the sign-in reason to say, and catch stale CLIs that know reverse
- `reverse start`'s signed-out `next` now carries a sentence the agent can say as is
(why HeyGen, and that the HyperFrames account is the HeyGen account), asks for it at
the start of the sign-in message, and on remote terminals has the agent send the
device link and code before it waits.
- references/start.md: same ordering, an example that fits both login routes, and no
links to or quotes from the instructions themselves.
- An old global install that knows `reverse start` but predates `next` was never caught:
agent runs get no update notice and no auto-install, so it stays frozen. The skill now
also treats `_meta.updateAvailable: true` from `reverse start` as an old install and
runs the rest with `npx -y hyperframes@latest`; every CLI that knows `reverse start`
already reports that field.
* fix(reverse): send remote terminals straight to device sign-in, reason in every link message
- `reverse start` now knows when no browser can open (the check `auth login` uses, moved
to attendedTerminal): `login_command` is `auth login --device` and `next` asks for one
message with the reason, the link and the code. The two-step route (a refused browser
login, then a bare follow-up with the code) is where the reason got lost.
- Every message that gives the sign-in link starts with the reason; agents say they are
waiting rather than quoting the skill, and give no file paths.
- The out-of-date line for an old global install goes in the next message to the person.
* fix(reverse): flag an older global install that shadows npx, and pin the run's release
- installerDetection: `shadowingInstall` finds the older global `hyperframes` that a plain
`npx hyperframes` runs instead of this npx copy (first on PATH outside the npx cache), with
the command that moves it. `detectInstaller` takes the entry to classify.
- `reverse start` run through npx opens `next` with that line as words to say, signed in or
not. Skill prose alone did not get agents to tell the person.
- Skill: a signed-out `reverse start` with no `reverse.next` is also an old install, which
covers a cold update cache; the run pins the release `@latest` resolved to.
* fix(aws-lambda): the handler ZIP installs its runtime from a committed lockfile with scripts off
build-zip.ts ran `npm install --no-package-lock` in the publish job, so
transitive versions floated at release time and any dependency's install
script ran beside the release credentials. The ZIP now runs `npm ci
--ignore-scripts` from runtime-lock/<source>/package-lock.json (versions
and integrity for every package), and the build fails if that lock
disagrees with bun.lock instead of falling back to a range or "latest".
`bun packages/aws-lambda/scripts/lock-runtime.ts` regenerates it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(aws-lambda): check only direct runtime versions against bun.lock; Renovate refreshes the rest
The runtime lock's transitive tree is npm's own resolution, not bun.lock's (modern-tar
0.8.6 there vs 0.8.4 in bun.lock), so the parity claim now covers puppeteer-core and
@sparticuz/chromium only. Renovate's weekly lockFileMaintenance refreshes the transitive
tree; its direct-version bumps are off for these dirs because those follow bun.lock.
— Rames Jusso
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(aws-lambda): keep the maintainer-only lock-runtime script out of the package
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): project history lists files without holding the host's event loop
* test(studio-server): the history walk test counts the hold up to the sweep's end
* fix(studio-server): history rewrites video-state.json only when it changed
* refactor(studio-server): names carry what the history walk comments said
The Cloud Run render image ran bun's remote install script, fetched
chrome-headless-shell through an unpinned npx package, and built FROM a mutable
tag. The base image is now pinned by digest; chrome-headless-shell and bun are
downloaded directly and checked against pinned sha256s before use.
— Rames Jusso
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): reject cross-origin state-changing requests
Non-GET routes in createStudioApi answer 403 unless the shared
sameOriginPost predicate (lifted into studio-server's ./request-identity
subpath) accepts the request: the Host must be a server identity, a
present Sec-Fetch-Site must be same-origin, and a present Origin must
match the effective host and scheme. Hosts behind Codespaces or tunnels
allow their public name with HYPERFRAMES_PREVIEW_ALLOWED_HOSTS, read by
`hyperframes preview` and the Studio dev server.
Squashed from #6128 (42574a7, 110a300, 89011e1, 41c6626, 27193bb) onto
current main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): the preview server answers only the hosts it is reached by
Every route of `hyperframes preview` (the forwarded studio API, the SSE
stream, /__hyperframes_config and the Studio page) now answers only
loopback names, the HYPERFRAMES_PREVIEW_HOST bind, or a host listed in
HYPERFRAMES_PREVIEW_ALLOWED_HOSTS, the same list the write guard uses.
Only the Host header counts here, since a page can set X-Forwarded-Host
on its own requests and a read carries no Origin to compare it with.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Dextheking1 <Dextheking1@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): buildSubCompositionHtml reads only compositions inside the project
The helper joined projectDir with compPath and read the result, trusting
every caller to have confined the path first. Studio's own preview route
does; an embedder that forgets would serve any readable file. The helper
now resolves compPath with core's resolveWithinProject and returns null
for a path outside the project, the same answer as a missing file.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): keep subComposition.ts's comment share flat
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): the sub-composition head reads only an index.html inside the project
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): label GPT image prices as estimates and show the charged credits
GPT Image generations on a HyperFrames plan are moving to fal's reported
vendor cost, so the pre-run figure is an estimate. The --plan basis for
gpt-image-2.5, 2.6 and 2.6-flare now reads "about N credits (charged at
vendor cost)". Nano Banana is unchanged.
When the /v3/images job carries charged.amount, generate reports it as
charged_credits and records it in the media ledger's provenance. Without
it, nothing new is printed. --max-credits is unchanged.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat(cli): keep 10% headroom under --max-credits for vendor-priced images
gpt-image-2.5, 2.6 and 2.6-flare are charged at the vendor's cost, so
--max-credits now refuses one when its estimate plus 10%, rounded up to a
whole credit, is over the limit. A 16:9 gpt-image-2.5 image (about 40
credits) is refused at --max-credits 40 and passes at 44. Other models keep
the plain estimate check. The refusal and the --max-credits help say so, and
the help notes this is not a hard ceiling.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(cli): count only HyperFrames-credit charges, and keep headroom under the run's limit
Review fixes for the vendor-cost image work:
- charged_credits is reported only when the job's charged.pool is
hyperframes_credits. A charge to api_credits or any other pool is in
that pool's own unit, so an API-key caller no longer sees it as HF
credits.
- runJob logs that charged amount, not the estimate, on a job's completion
row in heygen-jobs.jsonl, so later credit-limit checks see the real total.
Without a HyperFrames-credit charge the estimate is kept.
- The run's credit limit (.hyperframes/credit-limit.json) uses the same 10%
headroom rule as --max-credits for gpt-image-2.5, 2.6 and 2.6-flare,
through one shared limitCheck helper, with the same refusal wording.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* docs(media-use): say the credit limit is not a hard ceiling for GPT Image
A GPT Image call is admitted at its estimate plus 10% but charged the
vendor's cost, so it can still go past a run's credit limit. The media-use
skill, its HeyGen reference, the --max-credits help and the limit doc
strings now say so, and that a finished call's reported charge counts
toward the limit afterwards. Other models keep the "refuses what would go
past it" wording. No logic change.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(cli): hold a running GPT Image call at its headroom under the project limit
A reserved or still-running vendor-priced call was logged at its plain
estimate, so two concurrent calls could each pass the 10% headroom check
and together go over. Log the headroom amount until HeyGen reports the
charge.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(studio-server): history waits out a file a save has emptied, and rereads one written mid-copy
* style(studio-server): state the history copy's null result in the present tense
* style(studio-server): wrap the put doc comment
* style(studio-server): shorten the put doc comment to one line
* fix(studio-server): a file still changing as history opens starts at its first whole copy
* fix(producer): refuse a too-slow render only when its typical frame says it cannot finish
* fix(producer): keep the calibration estimate fields self-describing
* test(engine): split the frame extractor tests so each file stays under the flake gate budget
* test(engine): cut the comments the frame extractor test split carried over
* docs(studio-app): the Reference read is paid by Pro or a saved HeyGen API key
ReferenceAnalysis readGate: a saved usable key pays the read; without one
the plan gate opens the plans page (feature video_analysis). The page said
only the API key paid.
* docs(studio-app): a saved key comes first, and a used-up pro allowance opens plan and usage
* docs(studio-app): pro credits pay for the reference read first, a saved key when the plan can't
* fix(engine): a clip shows a new source frame on every output frame it covers
* refactor(engine): shorten the frame count doc to two lines
* style(engine): collapse the single-pass ffmpeg call the formatter wants on one line
* docs(studio-app): cloud exports come with the plan, not only an api key
The export page said cloud renders are always paid per minute from a HeyGen API balance. The app
now includes 5 cloud exports a month on Free and unlimited on Pro (plans.ts, cloudFit.mjs).
* docs(studio-app): export destination and api-key billing wording
* fix(engine): short clips from Apple-encoded videos keep their last frame
* refactor(engine): name the end-of-source hold and frame bound instead of commenting them
* fix(engine): frame ranges past a source's end stay empty with the held final frame
* test(engine): move the final-frame test into its own file