* 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
* fix(studio): a host that shows a still gets a preview reload with one page at a time
A full reload kept the live page beside the reload's own until it was promoted, so a heavy project held two
whole pages at once. A host that can show the live frame as a still (holdPreviewStill) now has the live page
dropped behind it while the reload's page loads alone; the still goes once the new page shows the live time,
and a reload that gives up brings the live page back at its time. With no still, nothing changes.
* fix(studio): keep the reload hook's comment share at the base
* fix(studio): pause before the still so a held reload resumes from the frame it shows
* fix(studio): drop a give-up's still on the live page's own load, not a polled load event
* fix(studio): a host that throws while taking the still falls back to the two-page reload
* fix: warnings that name project files print control characters as visible escapes
The CLI already escaped control characters in the text its own commands
print, but warnings from core, producer and engine went to the terminal
raw. A composition whose sub-composition path held ESC or BEL still
drove the terminal through the bundler's "Skipping sub-composition"
warning in `info --media` and `snapshot`.
terminalText moves to core so there is one sanitiser, the CLI imports it
from there, and the library warnings that carry project text (the
bundler, the producer logger, the file server, render path skips, asset
load failures, FrameCapture, the import map, fonts, figma and atomic
file warnings) pass that text through it.
* fix: every library warning that carries project text escapes control characters
* ci(publish): reuse Lambda assets only from a release this run created (SECOPS-1217)
The pack job downloaded any Lambda handler zip or video image already on the release and pinned it
into @hyperframes/aws-lambda without checking where it came from, so anyone with contents write
could pre-stage both before a stable release.
A new step fails the run when the release exists but github-actions[bot] did not create it during
an earlier attempt of this run, or when a Lambda asset on it was uploaded by anyone else. The pin
steps reuse an asset only when that step allows it.
* fix: bind release retries to immutable run artifacts
* fix: fail release digest pipelines before side effects
* fix(studio): recovery drafts are kept by each project's own server, never the browser
* fix(studio): a restored draft stays offered when Studio settles which composition is open
* fix(studio): a draft read never waits on a pipe or loads an oversized record
* test(studio): the draft read's child fixture is an entry point, and its note sits in the test
* chore(studio-server): size budget covers the recovery-draft route
* chore(cli): unpacked size budget covers the recovery-draft route
* fix(media-use): audio engine reads and writes only inside the project folder
A voice line id must be a plain file name and a recording path must stay
inside the project. The engine never writes through a link or into a folder
that leads outside the project. wait-bgm reads only the renderer's own log in
assets/bgm, and a carried-over BGM job keeps its pid and log only when that
log is the engine's own.
* fix(media-use): engine outputs and recordings stay inside the project
A recording that is a playlist or list naming other files is refused,
and ffmpeg is pinned to the probed format with file-only input. The
media manifest, its index, bgm_status.json and an in-project
audio_meta.json are never written through a link, and a .media folder
that leads outside the project is refused. Index cells keep each record
on one line. wait-bgm ignores a track path outside the project and
drops a pid whose log is not the engine's own.
* fix(cli): the published skills leave their test files out of the package
The pack job no longer downloads Lambda assets already attached to the
release; it always pins the handler zip and video image this run built.
The publish job decides what the release keeps. Once
@hyperframes/aws-lambda is on npm for the version, the release must hold
exactly the assets that package pins. Before then, an asset this run did
not produce fails a first attempt, and a re-run of the same workflow run
replaces it. An asset identical to the bundle's is left alone, so a
re-run of only the publish job also works.
* fix(cli): batch outputs from a template that starts with a placeholder stay in the working folder
* fix(cli): the bare {path} template is named, not commented
* fix(hdr): bound HDR image decode and resample sizes
The native HDR image path sized its host buffers from the PNG header and
the element's page-measured layout box, with no ceiling.
- PNG decode checks IHDR dimensions and bit depth before allocating,
inflates with maxOutputLength = height * (stride + 1), and rejects image
data whose inflated length does not match the header.
- HDR images are limited to 8192x8192 pixels; resampleRgb48leObjectFit
refuses targets above that.
- A layout box larger than the output frame is shrunk uniformly to fit it.
- Decoded and resampled HDR image buffers count against the HDR extraction
budget (HDR_EXTRACTION_MAX_BYTES / cgroup limit) for the render's lifetime.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* build(engine): raise the packed size budget to 510000 bytes
The PNG header checks and bounded inflate add about 500 bytes to the
packed engine, which was already within a few hundred bytes of its
1% tolerance over the 500000-byte budget.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): the CLI trusts a preview only once it proves this user started it
* test(cli): a listener that cannot prove it is the user's preview is never trusted
* test(cli): stand-in previews answer the challenge as the user's own do
* style(cli): format the preview proof changes
* fix(cli): a preview's proof names its own endpoint and config, and the token file must be private
* style(cli): format the proof changes
* test(studio): the fake request in the host check has a socket, as every real one does
* fix(studio): a Studio started by hand proves it is the user's, so the CLI still finds it
* fix(cli): the challenge travels in a header, so Studio's routes keep their exact paths
* style(studio): keep the config producer compact
* fix(cli): fixed-name outputs and history turn records replace a link, never write through it
transcript.json, hyperframes.json patches, the grade-compare sheet, the batch manifest, diff and
measure outputs, lambda stack state and the history turn records are written through a temp file
renamed into place. A linked hyperframes.json is left alone, and the default .hyperframes/<tool>
output folder is used only when every folder on the way is real.
* fix(cli): measure and diff pictures and sbs.mp4 replace a link, never write through it
writeImage and the diff side-by-side now have ffmpeg write into a new private folder beside the
output, then rename the file over its name. measure frames already staged and renamed its PNGs.
* wip: paused before review
* test: cover credential files on the preview routes and the deploy notice
* refactor: name the inspector's file lookup for what it serves
* fix(cli): a link to a private file outside the project keeps its own left-out reason
* fix: escape the upload notice and skip private files from old manifests
* fix(inspector): the inspection page reaches only its own server and public hosts
* fix(inspector): release the page server when the proxy fails to start
* fix(inspector): open each source session in its own browser context
Image prep (HEIF and GIF, in renders and the Studio preview) now applies the
other-network-root test to every candidate path, whatever its leading
character, and decides whether a candidate is allowed before checking that it
exists. Outside-project asset collection leaves out paths on another network
root with the existing network_share reason before any file lookup.
Tests run both under Windows path rules and record every path the disk is
asked about.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
On Windows even a stat or realpath of a \\host\share path connects to that
host and signs in as the current user. Three readers looked such paths up
before refusing them:
- `hyperframes compositions` resolved a data-composition-src with
path.resolve, so an absolute or share src reached readProjectFile. It now
uses resolveCompositionSrc, the resolver preview and render use.
- The timeline reader (`timeline`, `audio`, measure) realpath'd a
sub-composition before its containment check. It now refuses a path on
another network root first.
- Artifact bookkeeping for render, check and snapshot looked up the paths
recorded in .hyperframes/video-state.json. A recorded path must now be
spelled inside a .hyperframes/artifacts/<kind> folder on the project's own
root before cleanup looks at it, and a record naming another share counts
as gone without a lookup.
* wip: partial security fix, paused before tests finished
* fix(cli): templates pull checks every file of a kit and moves a changed one aside
A template folder counts as pulled only when every path under it matches the
file list a verified download unpacked to: the same paths, sizes and SHA-256,
no extra files, links or hard-linked files. That list lives in the user's
cache, never in the project. A folder that differs is moved to a dated
templates/<slug>.changed-<time> sibling and a verified copy takes its place.
* test(cli): drop a test comment the helper's name already says
* wip: partial security fix, paused before tests finished
* fix(cli): a received-files record in a folder under the project counts for a render
The received-files lookup now also walks the project's folders for records,
skipping tool and output folders and never following links. A nested
record's entries are received files named from the project folder, so a
received scene copied in with its own record makes the render leave out
outside files, as a record at or above the project does. A walk that cannot
list every folder fails closed.
* fix(engine): give each superset extraction a folder of its own
A superset group extracted into a folder named from the group index and the
process id, and deleted and recreated it by that name in the cache root that
every render shares. Two renders in one process could share the folder and
remove each other's frames.
Partial folders are now created with mkdtemp, so each extraction writes only
into a folder it made. A cache entry is published only when its frame count
is the one the extraction wrote.
* fix(engine): make the partial folders with createStagingDir; raise the engine size budget
* fix(producer): compile and render-telemetry tag scans run in linear time
The compiler's gsap script rewrite, crossorigin and preload strips, remote
media and image src scans and inline-script scan, and the render telemetry's
tag counts, now use forward scans that return exactly what the regexes they
replace returned. Those regexes rescanned to the end of the page from every
tag opener that never closed, or from every character of a long whitespace
run in one tag. The telemetry's script and style strip stops after 8 passes.
* test(producer): give the scan fuzz tests room on CI and raise the producer size budget
* fix(studio-server): history restores stay inside the project and use only intact copies
* fix(studio-server): a history path's trailing dots and spaces are trimmed by a scan, not a regex
* test(lint): density warning ignores lanes
* fix(lint): count dense timelines per file so agents keep scenes on one lane
* chore(skills): make room for the lane pointer in the entry skill
* fix(lint): plain comment on the per-file density count
* chore(skills): say why the entry skill budget grew
* test(skills): pin the one-lane wording agents follow
* style(skills): format the lane wording test
* chore(skills): regenerate skills manifest
* docs(skills): overlapping sound effects take a second lane
* wip: paused before review
* test: cover credential files on the preview routes and the deploy notice
* refactor: name the inspector's file lookup for what it serves
* fix(cli): a link to a private file outside the project keeps its own left-out reason
* fix: escape the upload notice and skip private files from old manifests
* wip: paused before review
* fix(core): keep the flash fade, with a checked duration set per element
* fix(core): find stylable flash targets with the realm-safe predicate
* fix(media-use): local models start outside the project, so a model id never names a project folder
MusicGen, parakeet-mlx and the LTX video runner take Hugging Face ids that their loaders read as
a folder when one exists in the working directory. Each now starts in the home folder; transcribe
still resolves a ./ or ../ --model path against the caller's folder.
* fix(media-use): a relative runner override still names the caller's folder
HYPERFRAMES_PARAKEET and HYPERFRAMES_PYTHON values with a folder in them are made absolute
against the caller's folder before the runner starts in the home folder. Bare names keep their
PATH lookup.
A preview made opaque by its server (Content-Security-Policy: sandbox) under a
frame with no sandbox attribute posts as null. frameOrigins now accepts null
for such a frame, only from that frame's own window and only while its window
refuses reads.
* fix(cli): history turn ids from the project folder are checked and sent encoded
* test(cli): history turn fixtures use the id shape the CLI mints
* fix(cli): a turn's label and agent name are kept as written; only ids are checked
* style(cli): format the turn reader
* refactor(cli): the turn reader checks a marker through small predicates
* fix(ci): publishing workflows run only for main
A workflow_dispatch on any branch ran the ClawHub sync with CLAWHUB_TOKEN and the
MCP registry publish with an OIDC token, publishing that branch's skills/ or
server.json under heygen-com. Each publishing job now skips unless github.ref is
refs/heads/main and checks out the triggering commit without stored credentials.
* test: split the main-only publish check into small checks
* test: close main-only publishing policy gaps
* refactor: separate publishing push filter classification