* fix(studio-server): save an edit Windows briefly holds without freezing the app
* fix(studio-server): keep later edits behind a held one, one backup per replay
* fix(studio-server): send a held cut again, and keep the sync retry for rollbacks
* fix(studio-server): check and render keep their history on a drive without hard links
The history lock had its own list of the errors that mean a drive cannot
hard-link, and it lacked EISDIR, which Windows returns on a Google Drive
folder. Every check report and render record there failed. The lock now
uses core's list, the one owner, which also gains ENOSYS from the lock.
* fix(engine): downloads and plan blobs publish on a drive without hard links
The producer's plan publisher kept a third list of no-hard-link errors
without EISDIR, and the downloader had no fallback, so both failed on a
Google Drive folder. Both now use core's cannotHardLink; the downloader
copies into an exclusively created file, so it still never overwrites.
* fix(engine): a download on a drive without hard links publishes atomically
Instead of copying into an exclusively created file, the fallback renames
the staged download into place under the cache path lock when nothing is
there yet, so a killed run never leaves a truncated file to reuse.
* feat(core): a folder with index.html is one a step can work on, apart from finding projects
isHyperframesProject needs index.html and a marker file, which is right for finding projects on a computer (a
website's folder must not be listed) but not for what a step works on. isCompositionFolder says that: any folder
whose index.html is the composition.
* build(core): raise core's unpacked size budget for the step folder rule
* fix(studio-server): an edit to a read-only project file is refused and leaves it unchanged
* test(core): read the refused file without a stat check first
* fix(core): at full quality a 4K clip plays a copy at the size the preview shows it
* fix(core): names carry the copy rule, not comments
* fix(core): a clip whose copy fails is left held as it was, so its decoder is still freed when idle
* fix(core): the copy hold lives with the copy code, keeping core inside its size budget
A caller that runs several renders at once sets HYPERFRAMES_OWNER to a per-run id; every browser the CLI or
engine launches and the warm check server carry --hyperframes-owner=<id>, so the caller can tell one run's
leftovers from another's.
* fix(core): stop a cancelled audio envelope from crashing the page
cancelParamLane held the value with AudioParam.cancelAndHoldAtTime. In
Chromium before 160 that call hits NOTREACHED in
AudioParamHandler::EventToString and takes the page down when the hold
lands inside a value curve whose end marker sits before it. The lane now
reads the value it reached, clears the param and writes that value back.
* fix(core): keep the audio automation comment share flat
* fix(core): fold the cancelParamLane doc comment to two lines
A paused preview's loadedmetadata handler put a reloaded video back at the playhead by resyncing every clip and re-deciding every timed element in the film. It now syncs and decides only the video that reloaded.
* 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
* fix(core): free a preview clip's decoder when the playhead leaves it
* fix(core): keep audio buffered when the playhead leaves it, free only video decoders
* fix(core): leave Safari's loaded video alone when the playhead leaves it
* 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>
* fix(core): a looping preview keeps playing when a scene reloads during a hold for data
A Studio preview unloads scenes far from the playhead. On a long film, the
loop's wrap back to the start lands while the first scene is reloading: the
film holds for its video, then the scene swap re-seeks with keepPlaying. The
seek read the held film as paused, dropped the hold and parked the film at the
start, so the loop stopped after its second pass.
A seek that keeps playing now counts a hold for data as playing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(core): name the playing-or-held check and drop history from its test comment
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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>
* 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>
* 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
* 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(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>
* 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>
* 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>
* 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>
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(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
* 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>
* 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(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>
* 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>
* feat(producer): fail a render whose variables the page does not declare
* chore(producer): keep the comment share and the dead-code audit clean for the variables check
* fix(core): fall back to a direct write when link() is denied with EACCES
On Android app data (Termux, SELinux enforcing), link(2) fails with
EACCES in a folder the temp file was just written to. createFileAtomically()
and the studio history owner lock treated that as fatal, so
`hyperframes init` left a half-scaffolded project and every render logged
a recordRenderSuccess failure. Both now take their existing exclusive
direct-write path, as they already do for EPERM.
Fixes#7473
* fix(share): treat EACCES as no hard links in the project share lock
Same Termux/SELinux link() denial as core and the studio history lock:
the share lock's link-then-exclusive-create fallback now covers it too.
Folds the Android note into the existing comment so no file's comment
share rises.