When an <audio> clip's source failed to load (a 404, a format Chrome
can't play), the slot-fit audit put it with the clips whose metadata
was still loading and told the person to re-run with a longer --timeout,
next to the http_error for the same file. The audit's probe already
stops waiting on the error, so the timeout was never the cause. Record
whether the element or its probe errored, and report those clips as
failed to load, without the timeout advice.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
citty's help appends "(Default: <value>)" to every arg whose `default` is
set, and 22 descriptions also spelled the default out, so `--help` read
"(default: 5) (Default: 5)". Drop the hand-written copies, reword the
lint-verbose and `measure extract --audio` flags whose "(default: a
one-line summary)" sat next to "(Default: false)", and add a test that
fails when a description with "(default:" has a `default` too.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): render --json gives each missing tool, a held slot and an old Node its own code
Every failed `render --json` answered with `error.code: "runtime_error"`, so a
script could only tell a missing FFmpeg from a busy render slot by matching the
human message. A CliRuntimeError now carries a code, as CliUsageError does, and
the envelope reports it: chrome_not_found, ffmpeg_not_found, ffprobe_not_found,
render_locked. A Node older than 22 prints the envelope too
(node_version_unsupported) when the run asked for --json. Other failures keep
runtime_error.
Refs #7408
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(cli): give the bin entry test's runtimeVersion stub the new JSON export
bin/hyperframes.mjs now imports runtimeVersionJson, so the stub dist file
binEntry.test.ts writes must export it too, or the bin fails to load.
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
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>
vite.config.ts imported createFsAdapter from @hyperframes/sdk/adapters/fs.
Vite leaves a bare import in a config file to Node, and that export points at
src/adapters/fs.ts, so Node had to load a .ts file itself. Node only does
that without a flag from 22.18, and on 22.0 to 22.17 build, dev and test all
stopped with ERR_UNKNOWN_FILE_EXTENSION, which also failed the last step of
the root build.
The config now imports the adapter by its relative source path, which Vite
bundles with the config on every Node version.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The Contrast section printed every finding with the error mark, so a
failure seen at a single sample (a warning) read as "✗ ... 0 error(s),
1 warning(s)". It now uses the same severity icon as the other sections.
A finding on an element without an id is named by an nth-of-type path,
which does not say which text failed. The line now quotes the text the
audit judged, as `validate` already does.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* fix(core): a clip the preview lets go of stays unloaded in Firefox
Releasing a clip dropped its src, called load() and set the src again.
Firefox treats preload="none" as "metadata" while an explicit load() is
pending, so every release fetched the clip's metadata and first frame. The
runtime then saw a far clip loading and released it again, in a loop: about
20,700 media requests over one 2:16 film, with 2-4 s stalls at cuts.
Setting src already runs the media load algorithm, which ends the fetch, so
the release now sets it again without load(). Chrome and Safari behave as
before: Blink clears its ignore-preload-none flag when src is set, and
WebKit's src set cancels the prepareToPlay that load() queued.
To reproduce: in Firefox, give a <video> with a src preload="none", then call
removeAttribute("src"), load() and setAttribute("src", src) in one task. It
loads to readyState 4; with the src set in a later task it stays at 0.
* fix(player): a film cut from one long recording plays through in Chrome and Firefox
A film whose clips are cut from one or two long recordings froze a few
seconds in, in Chrome and Firefox. Both keep a paused clip's request open
with its unread bytes, and every request to one host shares one HTTP/2 or
HTTP/3 connection window. With every clip of the file loading at parse, those
idle streams fill the window, and the request for the clip coming up is never
answered.
The player's frame now holds clips back on every engine, as it already did on
WebKit: each file keeps the clip on screen and the next one loading, and
frees the rest. The player also names its frame, because a composition in an
opaque sandbox cannot read frameElement to find the player's mark.
To reproduce: play a film of 37 clips cut from a 363 MB and a 180 MB .mov
served over HTTP/3 in <hyperframes-player>. On main it stops at 0:17 in
Chrome and at 0:09 in Firefox and never recovers.
* chore(player): raise the packed size budget for the frame name
Naming the player's frame adds 44 bytes to the packed player (158,706 to
158,750 bytes with pnpm 10.17.1). main was already 10 bytes under the 1%
tolerance of its 157,145-byte budget, so any growth fails the check. The
budget moves to 5% above the new measured size, as the check suggests.
* fix(core): seeking in the player stays as it was in Chrome and Firefox
Holding clips back in every player frame also moved Chrome and Firefox
player frames onto Studio's paused-seek path, which keeps the old picture
until every clip on screen has its new frame. In the player's scrub
benchmark the inline p95 rose from about 1.0 s on main to 1.9 s in CI,
and a seek could miss the benchmark's 1 s limit. In Firefox a paused seek
to a clip the player had let go showed no frame for about 5 s, because the
clip was released again each time it loaded.
Chrome and Firefox player frames now hold clips back and seek as they did
on main. Studio and Safari player frames keep the path they already had.
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).
* fix(engine): video warnings show control characters in the src as visible escapes
The missing-source and opaque-alpha warnings pass the authored src, and the path
built from it, through terminalText before writing them to stderr.
* fix(cli): snapshot never probes or decodes a private project file for a page video
projectLocalFile applies the same private-file rule as the render readers, judged as written
and with links resolved, so held-video probes and frame injection skip those files. Studio's
own prepared-assets and requests folders still resolve.
* fix(parsers,engine): media inputs never select a text-art demuxer
The media format allowlist leaves out tty, bin, xbin, idf and adf, so ffmpeg and ffprobe
cannot draw a text file as a video frame, whether or not ffprobe is installed. ffprobe's
refusal of one of these formats still reports the source as a text file.
A link inside the project whose target is outside it is still read by snapshot: links a
person puts in their own project are accepted, imported projects cannot carry links, and
render reads them the same way.
* fix(cli): registry warnings show control characters as visible escapes
A project's hyperframes.json can name the registry, so item names and deprecation text
from it pass through terminalText before the studio install, remote template and
item-loading warnings write them to stderr.
* fix(cli): failed render and frame read messages escape control characters
The render failure box escapes each line of the message, keeping its line breaks, and
snapshot's frame read errors escape the path and the ffmpeg or ffprobe text they quote.
* test(cli): probe a missing path with control characters instead of creating it
Windows cannot create a file with those characters in its name; the failed probe's
message still carries the path.
* 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
The bypass entry for a restricted browser's page server now always names its
port, so a default port no longer admits every port on the host. Studio
thumbnails take the server's own origin, not a request's Host header. A stop
signal that lands while the temp profile is being made removes it and launches
no Chrome. The wiring test follows renamed and namespaced calls, requires the
callback to pass on the network's args and profile, and refuses an unset
pageServerUrl.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(core): describe replies carry the picker's element label, and studio exports standInHandle
* fix(core): label an element by its rendered text, and read a describe reply without a label
* style(core): format the rendered-text walk
* fix(studio): beat analysis never picks a recording longer than a song
* fix(studio): a long music track keeps its saved beats; the cap judges the file alone
* fix(studio): a music track's beat edits survive its file length arriving
* 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>
* fix(cli): never write project records through symlinks under .hyperframes
The committed team descriptor (.hyperframes/project.json) and the HeyGen job
log (.hyperframes/heygen-jobs.jsonl) were written with path-based mkdir/write/
append calls that follow links, so a cloned project could point either file,
or .hyperframes itself, at a file outside the project and have publish or a
paid HeyGen job overwrite or append to it.
- projectRecords: add appendRecord (O_NOFOLLOW open, same plain file checked
by fstat/lstat, real folders from .hyperframes) and recordKind.
- writeTeamProject goes through writeRecord (exclusive temp + rename), so a
link at project.json is replaced, never written through, and a linked
.hyperframes is refused.
- readTeamProject refuses a linked or non-plain descriptor (or a linked
.hyperframes) instead of reading it as absent, which stops publish before it
would write one.
- The job log and project voice picks go through appendRecord and fail with
a Fix when refused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): route every remaining .hyperframes write through link-refusing helpers
Writers that still made or wrote into a project's .hyperframes with
path-based mkdir/write calls now refuse a linked or non-folder .hyperframes
and never write through a link:
- project lock: folder via recordFolder (the exclusive lock create stays)
- lambda stack state: writeRecord
- received-files record: recordFolder + writeRecord, so a link to another
project file is replaced instead of overwritten
- check reports: folder via recordFolder (the wx create stays)
- check and snapshot frame folders: new projectFolder, which holds a folder
inside .hyperframes to recordFolder and makes one elsewhere as asked
- template pull staging: recordFolder
- share render record: writeRecord
- studio server state folder: recordFolder
- share storage: the atomic JSON temp file is opened with wx
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli): drop doc comments the comment ratchet counts
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): refuse to append to a project record with more than one hard link
A hard link at .hyperframes/heygen-jobs.jsonl names an outside file as a
plain file, so the O_NOFOLLOW open and the same-file check let the job log
append to it. The append now refuses a file whose link count is above one.
Whole-file record writes go through a temp file renamed into place, which
replaces the name rather than writing to a linked inode.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): check and info --media leave remote media sources unprobed
mediaPath handed an http(s) src to ffprobe, so check's HDR and sound
probes and info --media's clip lengths opened composition URLs from the
CLI process. Remote sources are now left unprobed, as timeline and
check's clip audit already do. check's report lists the remote video
and image sources HDR inspection skipped under hdr.remoteNotInspected,
and a remote video that may carry sound keeps the film from being
reported as silent.
* fix(cli): drop credentials from remoteNotInspected and document unprobed remote media
* fix(cli): open starts the desktop app in the home folder, not the folder it runs in
* style(cli): keep launchApp's note on one comment line
* fix(cli): open starts the desktop app without the project's .env values
* fix(cli): studio thumbnails and Ctrl-C cleanup under a restricted page network
Studio's thumbnail browser now gets the preview's server as its page server, so
with PRODUCER_RESTRICT_PAGE_NETWORK on the proxy no longer refuses the Studio's
own preview. A restricted CLI browser's proxy and temp profile are released by
the CLI's stop-signal handler, which waits for them before exiting.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): every composition Chrome launch goes through the page-network fence
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep the follow-up inside the package's comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): a host that built a page on the build worker can exit
* test(studio-server): a dead build worker's exit code is left to the platform
* refactor(studio-server): every build-worker queue change sets its ref in one place
* fix(cli): commands that open a composition honor PRODUCER_RESTRICT_PAGE_NETWORK
check, snapshot, compare, grade-compare, layout, validate and the motion shot
launched Chrome with no page-network restriction, so a composition page
could reach loopback, the LAN and link-local addresses even when the caller
set PRODUCER_RESTRICT_PAGE_NETWORK=true, as a render honors it.
Every composition browser now launches through launchWithPageNetwork. When
the flag is on, it starts the engine's public-only capture proxy and profile,
the same ones a render uses. The page server is the only direct host, and the
proxy and profile live as long as the browser. The prelaunch path, which
starts Chrome before the page server exists, is skipped when the network is
restricted. A restricted launch without a page URL throws instead of running
unrestricted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep the page-network change inside the package's comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* 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>
* 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
* fix(engine): check the resolved address of a restricted download under Bun too
Bun maps a bare undici import to a built-in whose fetch ignores the dispatcher,
so the download lookup that refuses private addresses never ran there.
Load the package by file path.
* refactor(engine): the undici package import says why in its name
* fix(parsers): the timeline inliner stops at a whole-script expansion budget
* fix(parsers): charge bound arguments to the inliner budget and size it from the corpus
A large argument used many times in a helper body is cloned once per use,
which the body count did not cover. Charge the bound node's size for each
reference, set the budget to more than 10x the largest measured real script
(20,760 nodes), and test the hostile shapes from SECOPS-1698.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(parsers): trim inliner budget comments to keep the comment share from rising
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(parsers): charge default expressions and empty expansions to the inliner budget
Default parameter expressions were cloned before the budget was charged,
and once more during the droppable-helper preflight. Empty bodies spent
nothing although each expansion allocates a block. Charge both, and let
the preflight check only for spread arguments instead of building bindings.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Miguel Ángel <miguel.sierra@heygen.com>
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(core): a .hyperframes folder in a subfolder stays private too
The private-file rule treated .hyperframes as the app's records folder only at
the project root. A project copied into a subfolder keeps its own
.hyperframes/, and its chat history, hand-off and other records there were
listed in the file tree and served by Studio's file and preview routes and by
the other file servers that share the rule.
A .hyperframes segment at any depth is now private, in every spelling Windows
opens. Studio's own files and the prepared-assets and requests folders stay
servable only at the root, the one place Studio reads and writes them. The file
tree also skips .hyperframes/backup at any depth.
* fix(cli): the capture --local-file page server answers only its own host
The page server that capture --local-file starts on a loopback port answered a
request whatever its Host header said. A site whose name resolves to 127.0.0.1
could then read the files it serves from the browser.
The server now refuses, before any file lookup, a request whose Host is not its
own loopback name and port, with the same isOwnLoopbackHost rule the static
project server and the engine file server use. Every response carries
X-Content-Type-Options: nosniff. The capture browser loads the page by
127.0.0.1 and its port, and fetchLocalPageUrl reads from disk, so both work as
before.
* fix(skills): a plugin manifest in the project pins no CLI release
The skills launcher read a plugin manifest from the folder above skills/
wherever the skills were installed. For a project-level install that folder is
the project itself or its .agents or .claude folder, so a plugin.json shipped
with a project could pin an old hyperframes release and turn off update checks
and standalone skill refreshes.
The launcher now reads a manifest only from a bundle of its own: a folder whose
name does not start with a dot and that is neither the folder the CLI works in
nor one that contains it. Plugin managers install bundles into their own
folders, so those keep their pin. A manifest anywhere else leaves the call the
same as with no manifest. A manifest that pins a release older than 0.9.34, the
launcher's floor, is refused. The agent-facing plugin rules and the skills
guide say the same.
* fix(skills): a plugin bundle inside the working folder pins only behind a dot folder
A package inside a monorepo could still pin the CLI: with the agent working at
the monorepo root, <mono>/packages/video/plugin.json sat beside a skills folder
the launcher took for a bundle.
The launcher now also refuses a bundle inside the working folder unless a
folder whose name starts with a dot lies between them, as .claude does in
~/.claude/plugins/cache when the agent works in the home folder. Bundles in
~/.claude/plugins, ~/.cursor/plugins and ~/.gemini/extensions keep their pin
from the home folder or a project. The plugin rules and the skills guide now
state the three conditions the launcher checks.
* docs(cli): a .hyperframes folder in a subfolder is left out and not served
The private-file rule now treats a .hyperframes/ folder at any depth as the
app's records. Files stored in one inside a subfolder, assets included, stay out
of uploads and are not served by Studio, preview or render. The cloud render
section now says so beside the rule it already describes.
* fix(cli): capture pages keep loading scripts with no or unlisted extensions
With nosniff on every response, a script the capture page server did not
know the type of (a .cjs file, or a file with no extension) was served as
application/octet-stream, and the browser refused to run it.
The server now names .cjs, .wasm, .xml, source maps, web manifests, CSV,
WebVTT, glTF and more audio, video and image types. A file whose type is still
unlisted is served without nosniff, so the browser sniffs it as it did before
and such a script runs. Every listed type and every empty error response keeps
nosniff.
* fix(share): sync and share leave out a .hyperframes folder below the root
The .hyperframes rules in the source path policy matched only at the project
root, so a copy's records in a subfolder, such as
sub/.hyperframes/agent-runs.jsonl, fell through to the default rule and
travelled with share and sync.
A new nested-hyperframes-state rule leaves out a .hyperframes folder at any
depth below the root. It sits before the first allow rule, as the contract's
rule order requires. The root folder's Studio files and other portable files
travel as before. Stored snapshot reads skip the new rule through
stored_manifest.legacy_rule_regexes, the shape the server and Desktop copies
already use, so snapshots and bindings captured earlier still read.
* test(studio-server): a sub-composition build past its deadline is refused off the request thread
* fix(studio-server): sub-composition previews build off the request thread within a deadline
* fix(studio-server): every parse of a sub-composition page runs on the build worker
* test(studio-server): a page built inside its deadline keeps the request thread free
* test(studio-server): a refused page leaves the next one built whole, hf-ids and all
* chore(studio-server): the build worker's comments fit its package's share
* fix(core): a graded video's opacity animation reaches its export
* fix(core): a graded clip keeps its own clip-path, so it never renders black
* test(producer): golden render of graded video dissolve and wipe
* fix(core): a graded clip stays clickable in the preview, hidden by a filter not a clip
* chore(studio): drop an import the reader no longer uses, and format the graded fixture
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>
* 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
* fix(producer): render compile never inlines private project files named by @font-face
* fix(producer): a font link leading outside still warns before the private-file check
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.
* fix(studio): the preview picture takes a new box size in the same frame
The preview stage measured its box in a ResizeObserver and stored the size
in React state, which rendered a frame later. A box that grows at once (the
window going full screen) painted one frame with the old, small picture, and
macOS animated that frame for its whole full-screen transition.
* fix(studio): the preview picture takes a new box size in the same frame
* fix(studio): the preview picture is sized from its box's layout, not its on-screen rect
* style(studio): format the preview stage size test
* fix(engine,producer): render media readers treat private project files as missing
A video, audio, GIF or HEIC src that names a file the file servers refuse
(git metadata, env, credentials, tool state, app records), as written or
through a link, is now treated as missing by every render-time reader:
the compile-time duration probe and keyframe advisory, GIF and HEIC prep,
the media drop step, the HDR probe, frame extraction and the audio mixer.
The engine's isPrivateUnderAssetRoots judges a path from every asset root
that holds it, so a render's own work folder inside the project's
.hyperframes/ keeps its downloaded and prepared files.
* fix(engine): probe refuses a text file that ffmpeg reads as text-art video
ffmpeg's tty and bintext demuxers turn a text file (such as .asc or .nfo)
into a video stream that draws the text into frames. Every probe now
refuses an input whose container is tty or whose video codec is ansi,
bintext, xbin or idf, as not media. Probing, frame extraction and audio
reads all go through the same probe, on every render. No demuxer for real
video or audio produces these, so local renders keep every other format.
* fix(engine,producer,cli): playlist entries and check probes skip private files
- A media playlist (HLS segment, key or map URI, ffconcat file) that names a
private file inside its own folder is refused as not media, like one that
names a file outside it.
- `hyperframes check` no longer probes a media source outside the project or
private in it: mediaPath returns null for such a file and the audio,
heard-clip and HDR checks skip it.
- The compiler's duration probe and keyframe check judge privacy from every
asset root, as the render-time readers do.
* docs(skills): style-sampling pulls the template every time, so a received copy is checked first
* chore(skills): regenerate the skills manifest for the style-sampling change
* test(skills): style-sampling must pull before using a template, resuming included
* 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