* 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
* 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
* 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
* 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
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>
* 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>
* 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>
* 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>
* 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>
* chore: release v0.9.17
* chore(producer): raise the unpacked size budget for windowed video frames
The new modules and this version bump put the unpacked package 49 bytes
past the 1% tolerance. No tests or source maps are in the tarball.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>