oxfmt 0.41 pins tinypool 2.1.0 (GHSA-5gmw-xhrv-c9v3, GHSA-85c8-ppgw-ccpr).
Every oxfmt release before 0.67 pins 2.1.0, and 0.67+ reformats 66 files,
so override tinypool to the drop-in 2.1.2 patch instead of bumping oxfmt.
Also bump vite ^6.4.2 -> ^6.4.5 and vitest/@vitest/coverage-v8
^4.1.11 -> ^4.1.12 (pulls @vitest/mocker 4.1.12).
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
puppeteer-core 25.13.0 moves chromium-bidi to 157.0.8090-0, which depends on
zod ^4.6.5 instead of ^3.24.1. Lifts the engine/producer puppeteer pin from
~25.11.0 to ~25.13.0, keeps one puppeteer-core and one @puppeteer/browsers
(3.2.4) across the workspace, and updates both Lambda runtime locks with a
targeted npm resolution so only the puppeteer subtree changes.
Clears GHSA-mrhx-c7xc-m3w5 in both runtime locks.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(studio): drag and resize draw live on an opaque preview over its channel
On a preview frame Studio cannot script, a drag moved only the selection
outline: the element stayed put until the save reloaded the preview. A
resize threw on every pointer move (it measured the frame's element for the
centre pin), saved its size without the centring shift, and then a drag or
resize save threw while re-syncing the preview's timeline, which stopped the
save queue and paused the preview.
The runtime answers a new `draft` request: it adds a gesture's translate to
the one the element had and sets its border box, the way the save writes
them, and an end either keeps what is drawn (the save landed) or puts back
what was there (a cancel, a tap, a failed save). Studio mirrors what a
gesture draws on an opaque selection's stand-in to the frame, one request in
flight per frame with later moves merged into the next. An opaque resize
grows the outline about its centre from the size it wrote rather than
measuring the frame. The timeline re-sync after a save reports a frame it
cannot reach, so its caller re-seeks or reloads instead of throwing.
A stand-in now starts with the inline translate and Studio size and offset
of the element it stands for, so a drag on a freshly reloaded preview starts
from where the element is. Before, a second drag after a reload saved only
its own distance and dropped the first.
Same-origin frames do not change: only an opaque selection's stand-in is
mirrored, and the re-sync change only catches a read such a frame refuses.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): draft writes test an element by its namespace, not its realm
The runtime preview guard bans instanceof HTMLElement/SVGElement in the
runtime, since a node from another realm fails it; the draft handler uses
isStylableElement from domRealm.ts, as other runtime style writes do.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): keep the opaque preview's gesture drafts in step with the saved edit
- Grabbing a layer again before its last save settles keeps that save's draft
on the frame and draws the new gesture from there; the movement probe's
restore no longer ends a draft it never drew.
- A move on an opaque preview starts from the px the frame renders the
translate at (%, em, var(), or a stylesheet translate), records the author's
own value for Reset, and refuses a % it cannot size instead of dropping it.
The frame's draft base resolves % to px, so a resize can't shift it again.
- The stand-in carries Studio's translate marks, so Reset after a reload
restores the author's translate.
- A resize with no offset member keeps its draft once saved.
- An undo painted over a pending move draws the move again when it is put back.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* chore(deps): update happy-dom to ^21.0.4
happy-dom 21 turns off iframe page loading by default. The player and
sdk test environments load same-origin iframe documents, so they opt
back in through their vitest happyDOM settings.
— Clippy
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test: adapt studio and cli tests to happy-dom 21
Studio tests load same-origin iframe documents, so they opt back in to
iframe page loading. happy-dom 21 adds Element.checkVisibility, which
reads the real styles rather than the mocked getComputedStyle, so the
motion-signature decoys are hidden in the DOM as well as in the mock.
— Clippy
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(studio): fix remaining studio tests on happy-dom 21
- happy-dom now implements getAnimations, so Base UI deferred popup
unmounts to animation frames; test setup sets Base UI's
BASE_UI_ANIMATIONS_DISABLED, matching the old synchronous behaviour.
- happy-dom 21 drops vendor-prefixed properties it does not list, so the
-webkit-text-fill-color tests move to a jsdom file with shared helpers.
- The scaled-iframe drag test builds its own Window, which now needs
enableIframePageLoading.
- NLEPreview.slowBoot's per-file environment options never applied the
disable setting and now wiped the config's iframe opt-in; drop them.
— Clippy
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(studio): inline fill-test helpers instead of a shared module
Keeps the moved -webkit-text-fill-color tests self-contained and leaves
the original test file's helpers untouched.
— Clippy
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(studio): drop the Base UI flag comment for the comment ratchet
— Clippy
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): local renders bring in only media, font, CSS and JS from outside the project
Local renders (`render`, range render, `benchmark`, the Studio server and the
Vite Studio adapter) run with allowOutsideProjectAssets, which copied every
existing file that markup named outside the project into compiled/hf-ext, of
any type and from any folder, and served project links that lead outside
without looking at where they lead. Publish already applies a policy here:
outside references are kept, private locations are left out, and only image,
video, audio, font, CSS and JS files are copied. Local renders now follow the
same policy.
The publish predicates (private location, copied file type, left-out wording)
move from the CLI to a new `@hyperframes/studio-server/outside-file` subpath,
since the producer cannot import the CLI and already depends on studio-server.
The CLI re-exports them, so publish behaves as before. The media extension
sets move with them because the copied-type list includes them.
The producer decides with one predicate, `outsideAssetRefusal` in
utils/paths.ts, and applies it wherever allowOutsideProjectAssets lets an
outside file in, so no entry point can skip it:
- collectExternalAssets: src/href/url() references, which covers <a href> and
<link href>
- dropMediaOutsideProject: video/audio/image sources in any spelling the media
resolver accepts (file: URLs, percent-encoding), so nothing probes or
extracts them
- the render file server: project links that lead outside
- the distributed plan's project copy: the same links (range render)
- GIF/HEIC prep and sub-composition links: private locations only, since
those inputs are converted or compiled rather than copied as they are
Each left-out file logs the publish wording with "left out of the render".
To reproduce on main: a project whose index.html references
../../.ssh/id_key through <link href>, <a href> and url(), with a project
link to a file in .ssh, rendered locally, gets those files copied into
compiled/hf-ext and served.
Comment lines: the four in studio-server's outsideFile.ts moved verbatim from
the CLI files they replace. Two are new, in utils/paths.ts. The one on
outsideAssetRefusal states the policy once, so its six call sites carry no
comment. The one on refusesOutsideLink says its boolean means "refused, and
already warned", which the name alone does not say. Comment ratchet is clean.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep outsideFileType as a re-export of the shared module
The base repository's deletion guard rejects removing a file that exists on
main unless git pairs it as a rename. outsideFileType.ts moved into
studio-server/outside-file with enough added around it that git no longer
pairs the two, so CI's "Reject accidental file deletions" step failed.
The file stays as a two-name re-export and publish keeps importing from it,
so publishProject.ts and its file-type test are back to main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): raise the unpacked size budgets for the outside-file policy
CI's packed-manifest check measured @hyperframes/producer at 3,244,665 bytes
unpacked (budget 3,210,000) and @hyperframes/studio-server at 653,506
(budget 646,000), both just past the 1% tolerance.
Both packages were already at the edge on main. Measured locally with
npm pack --dry-run, main is 3,237,162 for producer and 652,502 for
studio-server, so studio-server on main is already at its ceiling. This
branch adds about 7.9 KB unpacked to producer, because the new checks sit in
the compiler, render stages and file server, which each producer entry
bundles. It adds about 5.5 KB to studio-server for the new outside-file
entry and its declarations. No source maps, tests or assets were added to
either tarball.
The budgets go to 3,245,000 and 654,000, just above CI's measurements, the
same way #7579 raised producer's budget for the project-folder checks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): apply the outside-file policy to embedded local fonts
A project font file that links outside the project is now left out of
font embedding with the same warning the file server gives, instead of
being inlined into the compiled HTML.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): a file held open or read-only answers 423 or 403 with a reason, not 404 or 500
* fix(studio): valid workflow name for the Windows held-file test
* test(studio): release the held file before the held-file test removes its folder
* fix(studio): the code editor's save toast names a held or read-only file
Remotion 4's current studio already depends on zod 4, and the fixture's
schema uses only z.object, z.string, z.number and z.array.
— Clippy
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
A pointer move superseded by a newer move or a leave returned null, not just
skipped the hover update. The right-click path awaits that same lookup for its
target when nothing is selected, so on a sandboxed preview, where the lookup
crosses the frame's channel, a 1px jitter during the right-click bumped the
counter and the menu never opened. The stale hover is still dropped; the
result is returned either way.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(studio): layers panel and marquee read an opaque preview over its channel
The runtime answers a new layers request with the Layers walk: each layer's
handle, depth, child count, z-index and kind, by the rules Studio walks a
scriptable frame with, which move to core. On an opaque frame the Layers
panel lists, selects and drills in from it, and the marquee measures its
candidates over the channel and selects from their descriptions. An opaque
selection maps to a timeline clip known only by its clip id, so a marquee's
picks survive the timeline sync.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): opaque preview hover, layers drill-in, marquee paging and delete path
Review follow-ups for the opaque-preview Layers panel and marquee:
- Delete on an opaque selection runs the DOM delete again. The clip-id match
that lets a selection find a row known only by its clip id is now opt-in
(`clipIdScope`), passed only by selection sync and the Layers seek, never by
delete or group commits, which need a patch target that row lacks. A row
with no file reads as in the open composition, as the forward lookup does.
- The runtime's `layers` reports a drill-in group it no longer has
(`missingGroup`) and lists nothing, so the panel leaves the drill-in after a
reload as the same-origin branch does, rather than list the whole page.
- `layers` takes an `offset`, and the marquee pages through every layer, so
elements past one reply's 2,048 cap still band-select.
- A Layers refresh that lands while an opaque read is in flight runs once more
when it settles, instead of being dropped.
- A hover resolved for a pointer move that a leave or newer move superseded is
dropped.
- `pointer-targets` reads the hit stack once per request.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(core): keep the layers paging test inside the Windows runner's timeout
The paging test walked the 2,051-layer page three times with every row
mapped, which ran past 5 s on windows-latest. It now maps only the last
page's rows and has its own 20 s timeout.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(studio): canvas click, hover and timeline select read an opaque preview over its channel
The runtime answers a new pointer-targets request with the canvas pick and its
cycle stack; the hit-test moves to core so Studio picks by the same rule on a
frame it can script. A data: value under the description limit now arrives
whole, so a small data: image is selectable on an opaque frame. Drill-in,
hover, timeline clips known only by clip id, and the stand-in attribute reads
in double-click, ungroup, path-offset and the agent selection context work
there too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(core): raise the core unpacked size budget for the pointer-targets hit-test
The hit-test moves from Studio into core's editing runtime, which core ships
in its runtime bundles; CI measured the unpacked tarball at 4,329,030 bytes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): copy only media, font, CSS and JS files from outside the project
Publish, cloud render and feedback now copy an outside reference into _ext/
only when its extension is an image, video, audio, font, CSS or JS type,
taken from studio-server's MIME map (new ./mime subpath; .avif added).
Anything else outside the project is left out with a warning and a
left_out entry whose reason is file_type; telemetry counts it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep the new outside-type file under its package's comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): copy the outside media cloud render re-encodes or converts
The outside allowlist now also takes the video, audio and still-image
extensions cloud render re-encodes or converts (.avi, .ogv, .aiff, .tif,
.bmp and the rest), from one shared list offload imports too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): keep media ids that differ only by case in separate folders
macOS and Windows disks ignore case, and APFS ignores Unicode normalization,
but mediaIdPathSegment passed plain ids through as written. Two clips such as
`s12-vB1` and `s12-vb1` therefore shared one `__hyperframes_video_frames`
folder: whichever was staged first kept it, and the other clip read its
frames. A longer clip then failed mid-render with ENOENT on a frame past the
shorter clip's end; a same-length pair rendered the wrong footage silently.
Only a lowercase, NFC-normalized id now maps to itself. Any other spelling
gets the existing readable~digest form, so every per-id path (frame folders,
the tail probe, audio work files, distributed plans) stays distinct on a
case-insensitive disk.
* fix(engine): name the case-folding check instead of commenting it
Keeps mediaPathSegment.ts at or under its comment share at the merge base.
* fix(producer): a video bound to a link plays its sound once
The compile step downloads a link a variable binds to a video, then the
browser set the link back through data-var-src, giving the clip a second
name and its sound a second lane. The downloaded element now drops its
binding, so it has one name.
* test(producer): run the bound-link audio test in the integration lane
It makes its clip with ffmpeg, which the unit lane does not install.
The startup diagnosis rebuilt its env from process.env, so a launch that
dropped WAYLAND_DISPLAY or the SwiftShader Vulkan pins was diagnosed with
them restored. The engine and CLI now pass the failed attempt's env through
explainChromeLaunchFailure; process.env stays the fallback when no env is given.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): cloud render --json lists the files an upload leaves out
`cloud render --dry-run --json` now reports `left_out`: each file outside the
project that the upload leaves out, with the file that points at it, the
reference as written, its path from the project, the reason (blocklisted or
received) and how many folders above the project it is. A wrapper can ask
before uploading. A full `--json` run carries the same list in its result and
prints a `{"event":"left_out"}` line on stderr for each, beside the warning a
person reads.
Publish, cloud render and feedback's repro send `cli_upload_left_out` when an
upload leaves something out: counts and folder depths only, never a name or
a path.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(cli): keep the left-out report's comment share at its package's
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): launch Chrome with only the env it needs
Every Chrome HyperFrames starts (render, GPU probe, HDR capture, startup
diagnosis, version and shell probes, CLI browsers, inspector) now gets an
allowlisted environment from @hyperframes/core/chrome-env instead of the
whole process env. HYPERFRAMES_CHROME_ENV_PASSTHROUGH names any extra
variable a host needs.
Refs #7623
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): keep the Chrome env passthrough across repeat filtering
The CLI GPU probe filters its env twice, which dropped the names
HYPERFRAMES_CHROME_ENV_PASSTHROUGH adds, so the probe and the render
saw different envs. Keep the passthrough variable itself.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
When a sandboxed Linux launch fails and the no-sandbox retry also fails,
the startup diagnosis re-ran Chrome with the first attempt's flags, so it
described a launch that was not the one reported. The engine and CLI now
diagnose the flags of the attempt that produced the error.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): publish leaves out outside files that came in with an imported project
When the desktop app brings in someone else's project (a Cutroom link, a
sync of a teammate's version, a reference's source), it lists those files
in .hyperframes/received-files.json. Publish, cloud render and feedback
now leave out every file outside the project that a listed file
references or links to, and warn naming the file and the reference. Files
the person wrote keep copying their outside references into _ext/ as
before. A record that cannot be read counts every file as received.
A project inside a hidden or app-data folder now only shares that folder
with assets in the folder it sits in: an outside file further up, in a
hidden or app-data location, is left out with the existing warning.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): bake proxies only for media publish kept
A video that staging left out of the upload could still reach the
archive as a transcoded proxy. Skip any hostile source whose archive
key staging did not keep.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(studio): read overlay geometry from an opaque preview over its channel
The runtime's editing channel gains a `geometry` request: per element
handle its client rect, the corners it paints at when rotated, whether it
renders, its clip-path, its source boundary's size, a group wrapper's
member rects, and optionally one element's descendant boxes. On a preview
frame Studio cannot script, the selection, child, group and hover boxes,
the root scale (from the mirrored stage size) and a press held across a
preview change read that geometry, with one read in flight at a time.
Same-origin frames keep reading the DOM directly; the measuring code they
use now lives in core so both paths share one rule.
Also from the review of #7613: opaque selections carry `hasAudio` and
`src` read off the description, a description with a cut attribute or
inline style builds no selection, a failed computed-styles or root read
builds none either, and the group refresh threads its frame and leaves a
group the user changed meanwhile. `findClosestByAttribute`, left without
a caller by #7613, is removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): raise the packed size budget for the runtime's geometry read
The producer ships the preview runtime, which now carries the editing
channel's `geometry` request and the measuring code it shares with Studio.
The packed tarball measured 888,810 bytes in CI against an 880,000 budget.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* chore(tests): move gen-os-static asset links to static.heygen.ai
The gen-os-static S3 bucket stops serving public reads on Nov 20. The
producer regression fixtures and the kinetic-type example load test
videos and voice files from it.
The same objects, with the same keys and the same bytes, are now served
from https://static.heygen.ai/<key>. This swaps the host for 39 of the
40 keys, in the fixture inputs and in the compiled.html goldens, so they
stay in step.
The dogs-captions clip (uploaded_assets/12ca139c_...mp4) stays on the
old host for now. It is held until we decide to copy it or replace it.
17 compiled.html goldens were stored as plain git blobs although
.gitattributes routes them to LFS. Editing them moves them into LFS.
The two font URLs in urlDownloader.test.ts and htmlCompiler.test.ts are
unchanged. They are example strings and are never fetched.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(tests): move the dogs-captions clip to static.heygen.ai
The dogs-captions clip (uploaded_assets/12ca139c_...mp4) is now copied
to static.heygen.ai with the same bytes. This swaps its host in the
fixture input and in the compiled.html golden, which moves into LFS.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Core plus engine tests now take 8-10 minutes, so the 10 minute limit
cancels runs that are about to pass and dequeues their PRs from the
merge queue as failed checks. Match Test (studio)'s 15 minute limit.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): keep Chrome's sandbox on for local renders where the host supports it
Chrome launched with --no-sandbox on every host. Keep the sandbox on
macOS, Windows and non-root Linux outside containers; drop it as root,
in Docker/Podman/Kubernetes, on Lambda and Cloud Run, and where Linux
restricts unprivileged user namespaces. --no-zygote now ships only with
--no-sandbox, since Chrome refuses it while sandboxed. A sandboxed Linux
launch that fails at startup retries once without the sandbox and warns.
HYPERFRAMES_CHROME_SANDBOX=1|0 overrides the choice.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): cover the Linux sandbox retry in managed browser launches
The off-macOS closed-pipe case now passes --no-sandbox, so it still
pins "no seatbelt relaunch" rather than the new Linux sandbox retry,
which gets its own case.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): honor HYPERFRAMES_CHROME_SANDBOX=1 and latch the fallback on clear evidence only
With the override set to 1, a sandboxed launch Chrome refuses now fails
instead of retrying unsandboxed. A bare startup exit (TargetCloseError)
retries that launch without the sandbox but only latches the sandbox off
after a second one, so a single unrelated early kill no longer disables
it for the rest of a long-lived process. Chrome naming the sandbox in its
error still latches at once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
A mover that moves further than its own width between frames leaves gaps in a
trail built from whole-frame blur-off poses; the shutter's smear lands in them and
read as a leak outside the trail (nightly seed 63098). The mask now adds the
shutter's sub-frame poses, captured in time order. Seed 63098 joins the default
seeds as the regression case.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer,docs): motion blur's compile hint and preview claim say what is measured
The screenshot-mode hint said data-motion-blur="on" always draws with html-in-canvas;
since auto took the filter tier it usually draws with an SVG filter. The guide said 16
preview copies stayed within measurement noise of 32; they stayed under the render
tests' visible-defect threshold, which is a weaker claim.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(motion-blur): 16 preview copies are under the smallest measured defect, not a test threshold
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(studio): timeline select and selection refresh read an opaque preview over its channel
On a preview frame Studio cannot script, timeline select, a selection
refresh and a group refresh build the selection from the runtime's element
descriptions. The rules that pick the element (group capture and drill-in,
the clip ancestor, the walk to an addressable element, timeline-locked, the
lookups and the master-view root fallback) move to a pure module over an
ancestor chain, used by both paths, so both select the same element.
Same-origin frames keep their direct reads.
The editing port gains `ancestors` (each handle's chain, parent first) and
`query` (a selector's matches with their source facts), and
`computed-styles` also names its element by handle. An opaque selection
carries the element's handle; its `element` is a tag-only stand-in in a
document with no window.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(studio): keep the selection rules' comment share at the package's
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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