skills/python-encoding.test.mjs was the only loose file in skills/, whose
top level otherwise holds one directory per skill. It checks every skill's
Python scripts, so it is a repo-level guard and belongs next to the others
of its kind in scripts/ (check-skill-import-boundaries,
check-media-use-copy-parity).
Renamed to scripts/check-skill-python-encoding.test.mjs. The test now
resolves skills/ relative to its new home. The skills CI job no longer
finds it with its skills/ glob, so it is appended to SKILLS_TESTS next to
the copy-parity guard and added to the skills path filter. The
test-reachability manifest is updated to match, keyed to skills/**/*.py.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): check hears a WAV whose header misstates its byte rate, as render plays it
A PCM WAV whose header byte rate is wrong (some speech generators write 2x) sent the silence decode's input seek past the file's end, so every clip past the middle was reported audio_clip_silent. Render already cuts such a file by decoded time (#7541); the byte-rate rule now lives in parsers and the CLI decoder seeks after decoding starts for those files.
* test(cli): keep the misstated byte-rate case with the other single-clip checks
* style(cli): format the WAV test helper
* style(parsers): keep the byte-rate rule's comment within the line limit
Co-authored-by: Joel Gallardo <joel.gallardo@heygen.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: heygengenesis[bot] <262951085+heygengenesis[bot]@users.noreply.github.com>
* feat(core): runtime element handles for the editing channel
The runtime gives each element a numeric handle for one page load and
answers two new editing-port requests: `elements-at-point` (the stack under
a viewport point) and `describe` (handles to plain-data descriptions). Each
description carries the element's stable selector, the source facts Studio
resolves to a file, earlier class-selector matches counted per source,
attributes, inline styles, text, child handles and its client rect.
The stable-selector rule and source-attribute read move to core so Studio
and the runtime address elements one way; Studio re-exports them and
resolves a description's source file and selector index with its own map.
Studio adds `PreviewElement` (a checked description) and client helpers.
Every channel read now gives up after the agent probe when the frame's
runtime has no editing agent, as the seek wait already did. `computed-styles`
accepts custom property names with any case or `_`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): per-load element handles and a light elements-at-point reply
Handles are now "<load>:<n>" strings, where the load id is random per page
load, so a handle from an earlier load reads as null like a removed
element. `describe` checks the exact format.
`elements-at-point` returns only {handle, tag, rect}; callers describe the
one they keep. Descriptions cap each attribute and inline-style value, keep
only a `data:` value's header, leave <script> and <style> text out, and say
when anything was cut. A handle's entry goes once its element is collected
or found disconnected.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): draw the element-handle load id on first use
A render seeds crypto.getRandomValues from virtual time, so drawing the
load id when the runtime loads shifted every random value the composition
drew after it, and the random-stagger-workers render no longer matched its
baseline. The id is now drawn the first time a handle is made, which a
render never does.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): keep a parked element's handle, and cut data: headers only from values
A scene the preview parks and puts back keeps its element handles: an entry
now goes only once its element is garbage-collected. Text that starts with
"data:" is no longer cut to a header; that rule applies to attribute and
inline-style values.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(studio): show the move, resize and rotate readout as a chip under the element
The chip now sits below the element, then beside it, then above the text toolbar, and keeps its side for the whole gesture. It uses the toolbar's own material and reads X / Y, W / H or an angle, so the floating text toolbar no longer covers it.
* fix(studio): keep the rotate readout clear of the turned element
While rotating, the chip was placed under the element's own box, so it overlapped the rotated text. It now clears the rotated bounding box.
* fix(studio): keep the readout chip inside the preview stage at the edges
The chip was bounded by the whole canvas area, so near the bottom it hung past the stage's edge. It is now bounded by the stage itself.
* refactor(studio): split the readout chip placement into small steps
The placement function scored over Fallow's complexity limit and added comment lines the comment ratchet refuses. The placement now lives in its own module of small functions, and the added comments are gone.
* fix(studio): keep the position readout chip clear of the preview toolbar
* fix(studio): keep side readout chips on the stage and clear of rotated elements
* style(studio): format the readout test file
* fix(studio): place the readout chip from the painted angle under rotated parents
* fix(ci): a release fails its checks when its notes miss a commit merged after the cut
* fix(ci): shorten the release checks comment
* fix(ci): find the last release by subject and say to link a deliberate omission
* feat(studio): add a light @hyperframes/studio/keys subpath for key parsing and defaults
parseCombo, matchCombo and DEFAULT_STUDIO_KEYS, with their types, from an
entry that imports nothing else, so a host can read Studio's keys without
loading the editor. The defaults move to a module of their own, which
studioShortcuts re-exports as before.
* fix(studio): declare the keys subpath in package-subpaths.json and regenerate the manifest
* test(studio): read the keys import graph with platform paths so it passes on Windows
First slice of moving Studio's selection and overlay readers off the
preview frame's DOM. Same-origin frames keep their direct reads; only a
frame Studio cannot script takes the new paths.
- Runtime editing port: a validated computed-styles request, answered
with the same logical opacity Studio reads (moved to core).
- Element picker: on an opaque frame, the picked element's computed
styles come from the runtime. Picker posts are taken only from an
origin the posting frame can have.
- Composition rect: an opaque frame's declared size comes from the
runtime's stage-size post, mirrored only for registered frames and
their origins.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): a later connect from the preview parent gets a fresh editing port
A parent that disposes its editing client and creates a new one for the same
frame (a remount that keeps the iframe) used to wait forever: the runtime
handed its port over once per page load. Each valid connect from the parent
now closes the previous port and hands over a new one. Connects from any
other sender are still ignored.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(studio): playback and timeline reads go over the preview's message channel
Prepares Studio's preview to run on an opaque origin, where the parent cannot
read the frame's window.
- previewChannel: one editing-port client per frame load, plus the loop start,
seek-painted and clip-manifest reads over it.
- bridgePlayback: a playback adapter that sends play, pause and seek as
control-bridge messages and mirrors the runtime's state and timeline posts.
It is used only for a frame Studio cannot script; a same-origin frame keeps
the direct adapter.
- The loop start and the state-tick manifest recovery now always use the
editing port. The shadow reload's seek-painted wait uses it for a frame
Studio cannot script.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(core,studio): trim comments back under each file's comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): keep the direct loop-start and manifest reads for frames Studio can script
A host can pair this Studio with a runtime older than the editing port. The
loop start and the state-tick manifest recovery now read a same-origin frame
directly, exactly as before; only a frame Studio cannot script uses the port.
previewFrameOpaque replaces previewFrameScriptable and treats a frame with no
window as not opaque, so a detached frame keeps its old no-op path too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core,studio): keep every editing port the parent receives working on an opaque preview
The runtime posts ready before it installs its editing agent, so a client can
connect twice and receive two ports. Closing the earlier port on each connect
left a client that took the first one with a dead channel for the rest of the
frame load. The agent now keeps earlier ports open (a disposed client closes
its own end) and closes all of them on teardown.
For an opaque preview:
- the restore-seek wait gives up after a 1 s probe when no editing port
arrives, so a runtime without the agent no longer holds a reload for 15 s;
- the bridge playback mirror keeps a seek until the runtime confirms it, so
a state posted before the seek cannot undo a quick frame step;
- sceneSwapFor returns no swap instead of reading the frame's window, so a
reload falls back to a full reload.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): call a frame opaque only when its window refuses a read
previewFrameOpaque treated any frame whose contentDocument was null as opaque.
A same-origin window can still report a null contentDocument (an iframe that is
not in the document), and that sent it down the opaque path. A frame is opaque
now only when reading its window's document throws, as it does across origins.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): mirror playback only from preview frames Studio built, at frame precision
The bridge playback mirror took a state or timeline post from any window and
made a mirror for it. It now takes a post only from a frame Player registered
(watchPreviewFrame, called before the frame loads, so the boot-time timeline
is not missed), and only when the post's origin is one that frame can have:
null for an opaque sandbox or a data: URL, the parent's origin for srcdoc,
about: or no src, else the origin of its src.
A pending seek now counts as confirmed by the frame the runtime lands it on,
the frame at or before it, rather than by a 1 ms match. An off-grid seek used
to drop every state post for 500 ms, freezing the playhead and its play state.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(studio): keep the editing-client tests' fake frame detached from the document
Main's test harness now attaches its fake iframe, and happy-dom then fires
that frame's about:blank load on its own, which ends the editing client's
frame load mid-test. These tests build their own detached frame instead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(studio): share the detached fake frame with the manifest router test
The manifest router test had the same race: the attached harness frame's own
about:blank load ended the editing client before the port answered, which
lost on the slower Windows runner. The harness now exports
detachedFakeIframe, which makeFakeIframe builds on, and both opaque-frame
test files use it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): a preview reload survives its pane unmounting mid-load
When the preview pane unmounted while a shadow reload was loading, its
Player removed the shadow frame but the reload kept timing it, so the
edit was dropped with "Its page had got to: no-page" and the previous
preview stayed. The reload now pauses while its frame is off the page
and starts its budgets again when the pane mounts a new frame.
The Player's comment on callback refs said the mutable-ref branch was
the only one in use; the shadow reload passes a callback ref, so the
comment now says why those are left alone.
* refactor(studio): name the left-page flag instead of explaining it in comments
* style(studio): format the shadow reattach guard
Ten rules each parsed the same <style> block with postcss, so a large
style block cost ten parses and ten trees for the garbage collector.
The 40 000-rule linear-time test ran close to its 2 s limit on CI and
failed there by chance. One shared parse per block brings that lint
from about 400 ms to about 60 ms.
* fix(core): show a paused video frame with the same color as the playing video on Mac
On macOS Chromium the video layer shows 8-bit SDR video with Apple's video gamma while a canvas shows the decoded pixels as sRGB, so a paused frame looked lighter-to-darker than the playing video. One module now owns the conversion and the paused stand-in canvas is displayed through it.
* fix(core): drop a comment line to keep the file's comment share down
* fix(core): correct a paused frame only for a source the scan reports as 8-bit, on both hold paths
Source facts now come from the shared media lookup (origin-aware, exact then longest suffix then normalized), unknown depth is left alone, and the native-only seek hold gets the same display helper.
* fix(core): shorten two comments to the line limit
* feat(studio): record the layer name on each history entry's target
* feat(studio): record the clip's name on timeline move and resize entries
* chore(studio): drop doc comments the names already carry
The media panel's Volume slider wrote a keyframe at the playhead, so a clip with a fade (or none) changed only around where the playhead sat. Volume now sets the clip's gain, the whole fade moves with it, and the keyframe toggle still adds automation on purpose. The separate Gain slider is folded into it, and the Audio Gain dialog no longer refuses clips that have a volume lane.
Adds minimax-h3-image (2K) and minimax-h3-image-4k to media-use generate,
refuses aspect ratios and reference counts each /v3/images model does not
take, and re-bases every image price on the live rows: an API key pays 1.5x
the vendor price, a HyperFrames plan the hf_image rows at x1.6545.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* docs: every link to hyperframes.studio carries where the visit began, shared with the homepage
The visit's first source now lives in the homepage's 30-day hf_hub_landing
cookie (.heygen.com) instead of a per-tab sessionStorage key, so a visit that
moves between the homepage and the docs keeps it either way. Pricing,
changelog and community links carry it too; ph_id stays on downloads only.
Tags over 64 characters are left out, as hyperframes.studio drops them.
* docs: tag studio links when the context menu opens; cap saved tags on read
Open in new tab and Copy link take the href as the menu opens, so the source
goes on then (never ph_id). Saved campaign values get the same 64-character
cap as fresh ones.
* docs: a right-click no longer makes a Card's next click drop the source
The menu left the source on the Card's DOM href, so the next click found
nothing to add and returned before following the Card itself, which opens its
own untagged href prop. Compare against the address the link had before the
menu tagged it.
* fix(cli): publish keeps Library files out for projects on iCloud Drive
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): treat Library/CloudStorage cloud drives like iCloud Drive when publishing
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): render servers only load assets from inside the project
The HTTP render handlers and the distributed planner now compile with
outside-project imports off: markup that reaches a file beyond the project
directory (through ../, an absolute path, a file: URL or a symlink) is no
longer copied into the compiled directory, served to the page, probed or
extracted. Local `hyperframes render`, `--start/--end` range renders,
`hyperframes benchmark` and Studio renders pass allowOutsideProjectAssets
and keep importing outside files exactly as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): render the symlinked-assets fixture as a trusted local render
The render-symlinked-assets fixture links src/shared to a sibling folder
outside the project to keep local renders working like preview. The
regression harness now reads renderConfig.allowOutsideProjectAssets from a
fixture's meta.json and passes it to the in-process and
distributed-simulated renders, and this fixture sets it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): render servers read compositions and media only from inside the project
Without the trusted-local opt-in, a sub-composition or entry file that
leads outside the project once symlinks resolve is refused, the same as a
../ sub-composition already is. Local media that resolves outside the
project, compiled and download folders, including absolute paths, file:
URLs and percent-encoded ../ paths, is reported as a missing source and
never probed or extracted. Remote media fetched during the render keeps
working. A missing file is no longer probed for the compile-time advice.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): raise the unpacked size budget for the project-folder checks
The producer tarball grows by about 12.5 KB unpacked: the new checks live
in the compiler and render stages, which the index, public-server and
distributed bundles each include. No test files ship in the package.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* chore: release v0.9.37
* docs(release): add #7576 to v0.9.37 notes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): publish leaves out private files outside the project and says so
A project you open may come from someone else, and its markup can point at
files outside the project folder. Publish and cloud render now leave out an
outside file that sits in a hidden folder (any path segment starting with a
dot past the folders the project itself sits in) or under /etc, /proc, /sys
or /dev, checked both as written and after resolving links.
Whenever an outside reference is left out, for this reason or because it is
an env file or Git data, the CLI now prints which project file holds the
reference and the reference as written. Other outside references are copied
into _ext/ as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): feedback's repro publish also names files it leaves out
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): publish also leaves out project links to private outside files, and AppData/Library
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): only the home folder's AppData and Library count as private
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): a referenced project link to a private outside file stays out too
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): resolve both paths the same way and skip AppData/Library when the project sits there
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): templates pull unpacks only plain files and folders
`templates pull` already refuses entries that climb out of the target
folder. It now also reads the archive's long listing and refuses any entry
that isn't a plain file or folder (a symlink, hard link or device), the
same rule Desktop applies when it unpacks example films and templates.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(cli): name the templates pull entry-type check instead of commenting it
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
0.9.35 made snapshotProject and snapshotFiles fall back to scratch-only
exclusions when .hyperframesignore can't be read. That is right for change
detection, but a host that builds an archive from the same snapshot then
includes files the ignore file meant to exclude, including ones named on its
valid lines.
The snapshot is strict again by default and throws invalid_source_ignore.
Change detection opts in with { lenientIgnore: true }, and projectFingerprint,
which names no files, always reads leniently.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The audio-missing check resolved every <audio src> on disk, including a
src naming a share on another host (\\host\share, //host/share). On
Windows that lookup opens a connection to that host, and Studio runs lint
as soon as a project opens. The check now skips a src whose root is a
network share other than the project's own, as the other lint rules
already do. Media on the project's own share, local absolute paths and
project files are checked as before; the render still reports a file it
cannot find.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(core): motion blur preview draws fewer filter copies at lower preview quality
The filter tier's preview draws 16 copies at preview quality 1/2 and 8 at 1/4 and
below; renders keep 32. Preview facts now list those levels in lighterAt once the
filter tier has movers, so a host that steps quality down on choppy playback can do
so for a film whose only load is blur.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(core): name the blur preview copies instead of commenting them
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* chore: release v0.9.35
* docs(release): note the render stop and container 403 from #7563 in v0.9.35
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix: track local Studio sharing CTA intent
* fix: tag local Studio and CLI share upgrade links with where they came from
The local Studio share modal's Upgrade to Pro link opens
/pricing?from=cli&entry=local_studio_share, and hyperframes share's source-files
notice links /pricing?from=cli&entry=cli_share, so the pricing page can tell
which link a visit came from and return the visitor to their terminal. The
modal accepts its own pricing page with any query, still only on
hyperframes.dev's two origins. share_upgrade_clicked carries
cta=share_modal_upgrade.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: name the local Studio upgrade CTA and drop the explaining comments
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep the local Studio upgrade link's return page unchanged
Only entry=local_studio_share is added to the local Studio share window's
Upgrade to Pro link. from=cli would have told these buyers to go back to their
terminal after checkout, but they return to a browser tab. hyperframes share's
link keeps from=cli, as the CLI's other upgrade links do.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(share): keep change detection working with a gitignore-style .hyperframesignore
The project scan used by change detection now reads .hyperframesignore
through the strict source reader. Cloud render reads the same file as
gitignore syntax and its docs show /exports/, which the strict reader
refuses, so the scan threw and hosts lost change detection, export
freshness and share status for that project.
Change detection now falls back to scratch-only exclusions when the file
cannot be read. Source capture keeps the strict reader and still refuses it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(share): check snapshotFiles tracks the file, not just names it
snapshotFiles returns every requested path, keying an excluded one as
undefined, so key presence alone did not prove the file was tracked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): keep git metadata and env files out of bundled HTML
The bundler now checks every file it reads against the project's private
paths (git metadata and env files, spelled directly or through a link)
and leaves a refused reference as authored instead of inlining it.
Bundle options gain a canRead predicate; Studio's preview passes its own
private-file rule so the preview document matches what the file routes
serve.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): check capture read grants against the decoded path
A capture page's read grant now looks at the path the way the static
preview route decodes it, including encoded separators, so a URL that
resolves to a dotfile or into a dot-folder gets no CORS grant. Ordinary
project files keep loading in thumbnails.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): accept local share requests only from loopback connections
The local share routes already require loopback Host and same-origin
headers. They now also require the connection itself to come from this
machine, so a Studio bound to a network address still keeps sharing
local to the person running it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): ask the bundler for Studio's private-file rule as plain data
The preview route passed a fresh `canRead` callback on every build. A host that builds on a
worker thread cannot send a function across, so it built on its own thread, and it could no
longer share one build between two same-content requests.
The bundler now takes `privateFiles: "studio"`, a plain string, and applies Studio's
private-file rule itself. That rule (git metadata, env files, and the app's records under
`.hyperframes/`) now lives in `@hyperframes/core/safe-path`, and studio-server reuses it.
The `canRead` option is removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): do not serve a preview main file linked to a private file
When index.html (or <id>.html) is a link to an env file or into git metadata, the
bundler refuses it and the route falls back to reading the main file from disk. That
fallback now skips a candidate that is a private project file, by the same rule the
file routes use. A main file linked from outside the project is still served.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): never inline git or env files as render sub-compositions
The render compiler resolved data-composition-src and inlined the file it named, so
`data-composition-src=".env"` put the env file's text into the render page. It now
refuses git metadata and env files with the same shared rule the bundler uses. The
pre-render check names the refused reference and stops the render.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: raise the inspector unpacked size budget to 3,722,000 bytes
The inspector already sat about 36.8 KB over its 3,684,092 budget, just inside the 1%
tolerance. Moving Studio's private-file rule into core added a few hundred bytes to the
bundles it ships, which pushed it to 3,721,419 bytes and over the tolerance.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(parsers): find helper programs by walking PATH in-process
The trusted lookup ran `which` by name through the full PATH before
applying the trusted-folder rule, so a relative or project-local PATH
entry could supply the lookup program itself. Walk the trusted PATH
folders in-process on every platform, as Windows already did, for
findTrustedExecutable, findFfBinary and the doctor's unzip check.
The walk keeps what `which` did for valid installs: first match in PATH
order, regular files only, and a leading `~` in a PATH entry read as the
home folder.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): start the media-use engine with the Windows working-directory lookup off
mediaUseEngineEnv now sets NoDefaultCurrentDirectoryInExePath for the
engine on Windows itself instead of relying on the CLI's own environment,
and keeps a value the person set. When no PATH folder passes the trusted
rule, PATH names a folder that is never created rather than an empty
value, which a shell or execvp reads as the working directory.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(skills): helper scripts skip the Windows working-directory program lookup
On Windows a program started by name is looked up in the working
directory before PATH. The plugin launcher and the media-use, hyperframes
and figma helper scripts run inside project folders and start ffmpeg,
ffprobe, Python and other tools by name, either through the launcher or
directly from a standalone skill install.
Each skill now ships a small module that sets
NoDefaultCurrentDirectoryInExePath for the process (keeping a value the
person set), and every script that starts programs imports it first, so
the helpers and every program they start skip the working directory.
Tools installed on PATH resolve as before; macOS and Linux are
unaffected. A test checks that each such script loads the module.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): ship the Windows lookup guard with the CLI's media-use scripts
The CLI build replaces the published media-use scripts/lib folder with
packages/cli/src/media-use/lib. That folder had no windows-exe-search.mjs,
so every bundled media-use script that imports it, including the engine
behind `hyperframes media-use`, failed to load on every platform.
The guard is now a generated copy in the CLI lib, next to the skill copies.
A parity test checks that each scripts/lib module a published media-use
script imports exists in the CLI lib.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(skills): load the win32 stub by file URL so the launcher test runs on Windows
On Windows, `node --import D:\...` reads the drive letter as a URL scheme
and fails before the launcher starts. The test now passes a file URL and
reports the child's stderr when it exits non-zero.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(skills): resolve the Python helper's ffmpeg and drop relative PATH entries
extract-audio-data.py ran ffmpeg by bare name, which Windows looks up in
the working directory first. It now runs the absolute path that
trusted_program.find_program finds in absolute PATH folders outside the
working directory. A miss raises the same FileNotFoundError as before.
On macOS and Linux the shared guard now drops relative and empty PATH
entries, which point into the project folder, and leaves absolute ones in
order. If none is absolute, PATH is unset rather than left empty.
The guard census now also requires every skill Python script that imports
subprocess to resolve programs through trusted_program.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(skills): satisfy the Python UTF-8 and ffprobe argv sweeps
trusted_program.py carries the same UTF-8 stdio pin as every skill Python
script. The guard test's planted-program probe uses a literal-only argv,
which the ffprobe argv contract test reads as a capability check.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
formatDuration rounded seconds after splitting off minutes, so 59.96s printed
"60.0s" and 119.97s printed "1m 60.0s". formatBytes compared KB against the MB
threshold before rounding, so 1,048,575 bytes printed "1024.0 KB". Round first,
then split or compare.
Takes over #5817 by @rudycelekli, whose commits could not be merged unsigned.
Co-authored-by: Rudy Celekli <rudy@gradiahq.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(core): give the preview parent a typed editing port to prepare for an opaque frame
Studio reads the preview frame's window and document directly, which stops
working once the preview runs in an opaque origin. This adds the runtime half
of the replacement, with no Studio consumer changed yet:
- runtime/editingPort.ts: a versioned request/reply protocol, a validator
that turns any bad request into a typed error, and a promise-based parent
client with request ids, timeouts and dispose. Exported as
@hyperframes/core/runtime/editing-port.
- runtime/editingAgent.ts: on the parent's connect, the runtime hands
window.parent a MessagePort once and answers hello, runtime-snapshot,
wait-for-seek and set-loop-start on it. A connect from anything but the
parent is ignored and does not use up the handoff.
Playback transport stays on the existing control protocol.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): type the handed-off port under the runtime's strict index checks
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): emit the editing-port module so the published subpath resolves
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): raise the packed size budget for the runtime's editing agent
The producer ships the preview runtime, which now carries the editing agent
and its request validator. The packed tarball measured 878,763 bytes in CI
against an 870,000 budget.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): let opaque preview frames load project fonts and module scripts
A preview framed with an opaque origin, such as the Compositions hover
preview, makes its font and module-script loads in CORS mode with
`Origin: null`. Without a CORS grant they failed: the frame fell back to a
system font and module scripts never ran.
The preview asset route now answers those two loads with
`Access-Control-Allow-Origin: null`, `Vary: Origin` and
`X-Content-Type-Options: nosniff`. The grant is chosen by `Sec-Fetch-Dest`,
which the browser sets and page script cannot: `font` for a font file and
`script` for a .js/.mjs file, served with the matching content type. A
page's own `fetch()` is always `empty`, so it still gets no grant and
composition script still cannot read project files.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(studio-server): keep opaque-frame grant comments within the package share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): let opaque preview frames load project fonts
Narrow the opaque-frame grant to fonts. Every sandboxed frame sends the
same `Origin: null` and fetch metadata, so a CORS grant for module
scripts could not be limited to frames the Studio itself serves. Module
scripts stay unloaded in the hover preview for now; fonts keep their
grant, and `Sec-Fetch-Dest: script` loads of .js/.mjs get none.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): load fonts and modules only in the Studio's own preview frames
A CORS grant to `Origin: null` reaches every sandboxed frame, whichever
page it sits in. The grant now lives on a per-project path instead:
`/projects/:id/preview/~<token>/...` serves exactly what `/preview/...`
serves, and only there do font loads (`Sec-Fetch-Dest: font`, a font file
served as `font/*`) and module-script loads (`script`, a .js/.mjs file
served as `text/javascript`) from an opaque frame get
`Access-Control-Allow-Origin: null`. The plain path gets no grant.
The token is an HMAC-SHA256 of the project id under a random per-server
secret, compared in constant time. The Studio reads it from
`/projects/:id/frame-token`, which refuses cross-site and same-site
requests, and the Compositions hover preview frames its composition at
the token path. Documents served there are re-based under the token and
carry `Referrer-Policy: no-referrer`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(studio-server): raise the packed size budget for the preview frame tokens
The per-project frame-token path adds server code to the package, and the
packed tarball measured 166941 bytes in CI against a 164800 budget. Set the
budget to the measured size plus about 1% headroom.
— Rames Jusso
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(skills): plugin launcher and media helpers run the pinned CLI, not a project copy
The plugin launcher now starts npx from the home folder, so the project's
node_modules, package.json bin and .npmrc cannot choose which CLI npm runs or
how it starts it. It names the project in HYPERFRAMES_PLUGIN_CWD and the CLI's
bin moves into that folder before anything else runs, then drops the variable
so nested runs keep the folder their caller gives them.
In --script mode the launcher hands itself over as HYPERFRAMES_CLI_ENTRY. The
media helpers (Kokoro voice, transcription, the resolve shim) run the CLI they
were handed, and stop with an actionable message when none was, instead of
resolving `npx hyperframes` from the project.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(skills): keep the project name and require a home folder for npx
The CLI bin now sets PWD to the project folder after moving into it, because
npm's shell resets PWD to the folder npx started in and preview names the
project from PWD. The plugin launcher no longer falls back to the temp folder
when there is no home folder; it stops with an error instead, and only when it
is about to start npx.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): type the bin test environment
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Local Studio mode runs Vite in the resolved @hyperframes/studio folder, so the
project folder decided which config and binary ran. Use it only when the
project resolves to the same Studio the CLI itself resolves (a source checkout
running its own build) or when HYPERFRAMES_LOCAL_STUDIO=1 is set; otherwise
serve the embedded Studio.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli,parsers): take helper programs only from install locations, never the project folder
FFmpeg, FFprobe, whisper-cli, parakeet-mlx, Python and system Chrome are now
found through one shared rule: an absolute PATH entry outside the working
directory, or a fixed install dir. A relative PATH entry and any folder
inside the working directory are skipped, on every platform. Windows walks
PATH itself instead of asking `where`, which lists the working directory
first.
FFmpeg discovery no longer falls back to `.hyperframes/bin` or to an
installer package in the project's node_modules; an installer package
installed next to HyperFrames still works. The env overrides are unchanged.
The CLI skill reference stops suggesting the project-local folder.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): give the PATH-lookup tests a fixed PATH on Windows
Windows now walks PATH instead of running `where`, so tests that faked
`where` output found the runner's real python and cmake. Both tests now set
PATH to a temp folder holding only the programs they expect.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: report a missing helper program instead of running it by bare name
When no trusted FFmpeg or FFprobe is found, the engine, the producer's
probes and Studio's waveform, peak and audio-track helpers now report
"not found" with the HYPERFRAMES_FFMPEG_PATH / HYPERFRAMES_FFPROBE_PATH hint
instead of handing the bare name to the OS lookup. Callers that degraded
on a missing binary still do: runFfmpeg returns a spawn_error result, the
GPU and version probes report none, and Studio's audio helpers fail soft.
The Lambda handler names its bundled ffmpeg and ffprobe by path, since
they live under the task root, which is the working directory.
brew, git and cmake for the whisper.cpp install, and the clipboard tool
for `hyperframes add`, run by the absolute path the trusted lookup
approved. The media-use engine gets a PATH holding only trusted folders.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): fail a missing FFmpeg the way a failed spawn always has
Throwing from getFfmpegBinary turned every caller's missing-binary path
into a synchronous throw: the streaming encoder's "failure result, not a
throw" contract broke, and unit lanes that run without FFmpeg crashed at
module load. With no trusted copy the getters now return an absolute path
inside HyperFrames' own install that is never created, named for the
override to set. Spawning it fails with ENOENT exactly as before, and the
OS still never looks the bare name up. The call-site guards and fixture
changes that the throw needed are reverted.
The whisper install tests match git and cmake by name and skip the brew
case on Windows, where the lookup walks the real PATH.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(engine): pin the found FFmpeg before the HDR test looks it up as macOS on Windows
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>