2050 Commits
Author SHA1 Message Date
Miguel Ángel 79990aed9a chore: release v0.9.56 (#7915) 2026-11-16 03:29:27 +00:00
Miguel Ángel 846cce4891 fix(cli): the CLI trusts a preview only once it proves this user started it (#7899)
* 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
2026-11-16 03:15:26 +00:00
Xuanru Li 1e542956d9 fix(studio): take playback posts from a preview its server sandboxed (#7815)
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.
2026-11-16 01:23:09 +00:00
Michael Wang b650d0d198 fix(studio): keep a host's sandbox-origin seal on the preview frame (#7886) 2026-11-16 01:01:13 +00:00
Michael Wang 4067efc454 fix: present refuses other sites' framing; Studio preview reads only its own frame's messages (#7877)
* fix(studio): the preview reads hf-preview messages only from its own frame

The preview message router acted on a message with no sender window, and on
any message that arrived before the preview frame existed. It now takes an
hf-preview message only when the preview frame exists, the message comes from
that frame's window, and its origin is one the frame can have: the page's own
origin, or "null" for a sealed frame. The element picker checks the same.

* fix(cli): present sandboxes deck pages another site loads and refuses framing by other sites

present now applies the same another-site decision as play to its
/composition/* route: a load by another site gets a sandbox CSP, its
validators are dropped, and the document is marked so its runtime offers
that site no editing port. Every present response also sends
frame-ancestors 'self' and X-Frame-Options SAMEORIGIN, so only the
presenter page itself can frame the deck. The route setup moves into
buildPresentApp so tests exercise the server as run() builds it.
2026-11-16 00:30:46 +00:00
Miguel Ángel 894f0808b3 chore: release v0.9.55 (#7864)
* chore: release v0.9.55

* chore: release v0.9.55 notes include #7830

* chore: release v0.9.55 notes include #7859 and #7867

* chore: release v0.9.55 notes name the docs change and cloud render

* chore: release v0.9.55 notes include #7866 and #7801

* chore: release v0.9.55 notes match the style bar
2026-11-15 22:33:02 +00:00
Miguel Ángel 1f17b3dfeb fix(studio): a sealed preview's reload asks under one current frame token (#7862) 2026-11-15 20:22:28 +00:00
Miguel Ángel ae5829db7e fix(studio-server): a sealed preview's wait for a video's proxy copy passes its preflight (#7856) 2026-11-15 19:50:59 +00:00
Miguel Ángel 064c436557 chore: release v0.9.54 (#7850)
* chore: release v0.9.54

* chore: release v0.9.54 notes include #7827, #7825, #7845, #7848 and #7849

* chore: release v0.9.54 notes include #7853

* chore: release v0.9.54 notes include #7851 and #7855
2026-11-15 19:17:45 +00:00
Miguel Ángel 3a4f572523 feat(studio): hosts can share the preview's editing-port client (#7811) 2026-11-15 17:16:15 +00:00
Miguel Ángel a73ecff2be feat(studio): hosts can seal the preview frames NLEPreview draws (#7817)
* feat(studio): hosts can seal the preview frames NLEPreview draws

* refactor(studio): Player builds its frame src in a helper, keeping its complexity at main's
2026-11-15 17:15:24 +00:00
Miguel Ángel 5341d7255c feat(studio): the console errors panel reads a sealed preview over its editing port (#7824) 2026-11-15 17:14:34 +00:00
Miguel Ángel 39dc1e232d fix(studio): GSAP keyframe and 3D previews stop throwing on a sealed preview (#7833) 2026-11-15 17:13:42 +00:00
Miguel Ángel ce18c3a102 chore: release v0.9.53 (#7841)
* chore: release v0.9.53

* chore: release v0.9.53 notes include #7836 and #7839

* chore: release v0.9.53 notes include #7840 and #7843
2026-11-15 15:50:38 +00:00
Miguel Ángel ef42bef9c3 refactor(core): Studio's key combo and typing-target rules live in core (#7835)
* refactor(core): Studio's key combo and typing-target rules live in core

* chore(core): raise the packed size budget for the key-combo and typing-target subpaths
2026-11-15 15:42:04 +00:00
ClippyandClaude Opus 5.5 beeb17e85a fix(deps): bump @mcp-b/global to 6.1.0 to clear @modelcontextprotocol/server advisories (#7742)
* fix(deps): bump @mcp-b/global to 6.1.0 to clear @modelcontextprotocol/server advisories

@mcp-b/global 5.x and 6.0.x pin @modelcontextprotocol/server 2.0.0, which is
affected by GHSA-f897-62hf-6gxq, GHSA-46jr-4wx8-v453, GHSA-jm63-cq47-j5jp and
GHSA-rvq5-wwqv-78pq (>=2.0.0 <2.3.0). 6.1.0 is the first release that pins
server 2.4.0.

6.x installs the W3C WebMCP polyfill and passes { signal } to execute; the
real-package tests now drive the 6.x surface (secure context, MCP tools/call).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(studio): close the WebMCP polyfill after the real-package suite

6.x's BrowserMcpServer sends a tools-changed event on a timer after the
last tool unregisters. Without cleanupWebModelContext() it fired after jsdom
teardown and vitest failed the run on an unhandled rejection. Also scope the
transport test's header to the MCP transports it actually checks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 05:42:08 +00:00
Miguel Ángel ad3a2389ee chore: release v0.9.52 (#7800) 2026-11-14 21:38:34 -05:00
Miguel Ángel b5f5ab36a1 fix(studio): menu row highlight follows the menu's corner (#7791)
* fix(studio): menu row highlight follows the menu's corner

* fix(studio): keep the menu row's comment share flat

* fix(studio): export the menu row class so hosts reuse it
2026-11-14 21:20:03 -05:00
Miguel Ángel cb15cb0e54 chore: release v0.9.51 (#7799) 2026-11-14 21:09:12 -05:00
Miguel Ángel 5e0577f124 chore: release v0.9.50 2026-11-14 19:39:50 -05:00
Miguel Ángel fd7217c8af chore: release v0.9.49 (#7767) 2026-11-14 18:15:46 -05:00
Miguel Ángel f33f137b2d chore: release v0.9.48 (#7761) 2026-11-14 17:04:22 -05:00
Miguel Ángel 5aea6d5b68 Merge pull request #7754 from heygen-com/release/v0.9.47
chore: release v0.9.47
2026-11-14 14:48:31 -05:00
karl songcuan a03e85f43a feat(studio): press ? to open the keyboard shortcuts panel (#7478)
* feat(studio): press ? to open the keyboard shortcuts panel

Adds a rebindable `shortcuts` action bound to `?` (Shift+/) that toggles
the shortcuts panel; Esc still closes it. The key is ignored while focus
is in an input, textarea or contenteditable, and the panel lists `?`
under Panels.

Refs heygen-com/hyperframes#5580

* docs(studio): document the ? shortcut for the shortcuts panel
2026-11-14 18:55:54 +00:00
Miguel Ángel f7f2c535be fix(studio): a refused edit names the file and why, on every edit path (#7749)
* fix(studio): a refused edit names the file and why, on every edit path

* fix(studio): freeze frame and caption save name a refused file too
2026-11-14 18:44:45 +00:00
Miguel Angel Simon Sierra 2f46a88dea chore: release v0.9.47 2026-11-14 12:13:11 -05:00
Miguel Ángel b723874462 fix(studio): HEVC with long-term reference pictures keeps its pixel aspect ratio (#7739)
* fix(studio): HEVC with long-term reference pictures keeps its pixel aspect ratio

* style(studio): format the HEVC SPS test
2026-11-14 15:29:22 +00:00
Miguel Ángel 43132411c8 chore: release v0.9.46 (#7732) 2026-11-14 13:40:20 +00:00
Miguel Ángel fe8d93056c chore: release v0.9.45 (#7729) 2026-11-14 09:45:48 +00:00
Miguel Ángel 58ef24c6d8 chore: release v0.9.44 (#7708) 2026-11-14 06:22:47 +00:00
Miguel Ángel 690b07e455 feat(studio): toasts show as a centred pill that rises in (#7714)
* feat(studio): toasts show as a centred pill that rises in

* fix(studio): error toasts stay up on a click so their text can be copied
2026-11-14 04:15:03 +00:00
Miguel Ángel 062515bfa9 fix(studio): menus and popovers ease their scale in, not only their opacity (#7583)
* fix(studio): menus and popovers ease their scale in, not only their opacity

* style(studio): format the floatingMotion test
2026-11-14 03:37:05 +00:00
Miguel Ángel f207f612f1 perf(studio): scale timeline strip frames off the main thread (#7651) 2026-11-14 03:05:19 +00:00
Miguel Ángel cb072eb047 fix(studio): edit clips added to a project outside Studio (#7686)
* fix(studio): edit clips added to a project outside Studio

A clip written into a composition after its ids were last stamped (a hand
edit, an outside agent) has a data-hf-id only in the served preview. The
timeline's client-side patch looked that id up in the file's raw bytes, so
Hide, Mute, move, resize and attribute saves failed with "Unable to patch
timeline element ... (by hf-id; no file on the clip)".

Resolve the target against the file stamped in place the way the preview
stamps it, as the server's own saves and the GSAP save already do. The save
then persists that id.

* fix(studio): save volume on several clips added outside Studio

The multi-clip attribute save (gain or volume on a selection) patched each
clip in the file's raw bytes, so a clip with no ids on disk was skipped and
the save reported success with nothing written.

The by-target read and patch helpers now resolve a clip by the id the
preview served it with, so every caller finds it. The multi-clip save goes
through the same batch patch as the other timeline saves, which refuses a
clip the file does not hold; the error reaches the person instead of a
silent no-op. The preview picker finds the file holding an unstamped
element the same way.
2026-11-14 02:48:59 +00:00
Miguel Ángel 45882027bd feat(cli): check warns when text leaves the 9:16 social safe areas (#7680)
* feat(cli): check warns when text leaves the 9:16 social safe areas

* feat(core): safe areas owned by core; check adds --safe-zone standard

* style(cli): format

* refactor(core): name the safe-area band fields

* fix(cli): defects outrank safe-zone warnings at the issue cap

* style(cli): format

* test: read the safe-box constants from core
2026-11-14 02:00:15 +00:00
Miguel Ángel c727e890f2 chore: release v0.9.43 (#7664) 2026-11-13 22:42:53 +00:00
James RussoandClaude Opus 5.5 6bdf929164 feat(studio): drag and resize on an opaque preview start from one gesture-start read (#7657)
* feat(studio): drag and resize on an opaque preview start from one gesture-start read

A gesture on a preview frame Studio cannot script read nothing from the
frame as it started. A drag snapped to nothing; a layer GSAP holds moved by
a CSS translate that its save then dropped; a resize grew from the overlay
rect, the layer's GSAP scale included; and the pointer reached the element
only through the canvas zoom.

The runtime answers a new `gesture-start` request. For each pressed element
it gives the overlay geometry, the transform-free layout size, how far the
centre moves per px of translate (probed the way a draft draws it, every
transform above it applied), and GSAP's x/y when GSAP owns its position,
with whether a tween moves it. It also lists the boxes of the page the
gesture can snap to, walked by the rule Studio's own snap collection now
takes from core.

On an opaque preview every press waits for that one read, on the existing
waiting-press path, and the gesture starts from it: the snap targets, the
move route and GSAP base (so the save writes GSAP's x plus the drag, not the
drag alone), the pointer-to-offset matrix, and the resize's base size. A
layer a tween moves is refused with a notice, since saving that move still
reads the frame.

Same-origin frames do not change: their presses start at once from the
element, and their snap collection walks the same elements by the same rule.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(inspector): raise the packed size budget for the gesture-start runtime

The inspector bundles core's preview runtime. Main alone packs to 866206
bytes, 420 under the 1% tolerance on the old 858046 budget; the
gesture-start request adds 713 bytes (866919), which tipped the merge
queue's Build over. Set the budget to 880000 to leave room for the
remaining opaque-preview requests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 19:42:26 +00:00
Miguel Ángel 30c0935a24 chore: release v0.9.42 (#7655) 2026-11-13 17:54:21 +00:00
ClippyandClaude Opus 5.5 7603215f03 chore(deps): override tinypool to 2.1.2, bump vite and vitest patches (#7653)
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>
2026-11-13 17:30:24 +00:00
James RussoandClaude Opus 5.5 87c4a07dc9 feat(studio): drag and resize draw live on an opaque preview over its channel (#7646)
* 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>
2026-11-13 17:01:16 +00:00
ClippyandClaude Opus 5.5 d77731aab5 chore(deps): update happy-dom to ^21.0.4 (#7641)
* 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>
2026-11-13 16:56:15 +00:00
Miguel Ángel 0bce3315e6 fix(studio): a file held open or read-only answers 423 or 403 with a reason, not 404 or 500 (#7649)
* 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
2026-11-13 16:10:01 +00:00
James RussoandClaude Opus 5.5 d208281091 fix(studio): open the canvas context menu when a pointer move overtakes its lookup (#7643)
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>
2026-11-13 08:29:42 +00:00
James RussoandClaude Opus 5.5 be67089a80 feat(studio): layers panel and marquee read an opaque preview over its channel (#7639)
* 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>
2026-11-13 07:48:32 +00:00
Miguel Ángel 20084cbe67 chore: release v0.9.41 (#7632) 2026-11-13 04:26:22 +00:00
James RussoandClaude Opus 5.5 7e04f3cce8 feat(studio): canvas click, hover and timeline select read an opaque preview over its channel (#7637)
* 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>
2026-11-13 04:16:20 +00:00
James RussoandClaude Opus 5.5 faff4e16a8 feat(studio): read overlay geometry from an opaque preview over its channel (#7628)
* 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>
2026-11-13 00:26:30 +00:00
James RussoandClaude Opus 5.5 aed4c18feb feat(studio): timeline select and selection refresh read an opaque preview over its channel (#7613)
* 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>
2026-11-12 22:39:47 +00:00
Miguel Ángel f5476851dd chore: release v0.9.40 (#7617) 2026-11-12 21:52:46 +00:00
James RussoandClaude Opus 5.5 e1ddb2e162 feat(core): runtime element handles for the editing channel (#7603)
* 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>
2026-11-12 14:13:18 +00:00