* fix(docs): check catalog link values by type and isolate the preview
A catalog page restores its variable values from the query string, so a
shared link decides what the preview composition is given. Values from a
link are now kept only when they fit the variable they name: a finite
number, a boolean, one of an enum's options, a colour, an image address,
or text with no angle brackets. Anything else opens at its default.
The preview player now runs the composition with an opaque origin
(sandbox-origin="opaque"), so a composition cannot reach the docs page.
The bootstrap already drives the player only through its API and
postMessage, and every docs asset is served with CORS, so playback,
seek-on-remount and edits behave as before.
chatgpt-exchange sets its editable text with textContent instead of
building innerHTML from it. A new check, check:registry-innerhtml, fails
any registry file that reads variables and adds markup writes; the files
that do so today are listed with their current counts and may only go
down.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(docs): keep a link's text out of copied commands until the reader sets it (#7785)
A catalog page restores tuned values from its link, and the install
command, the render command and the agent request carried those values
as if the reader had typed them. The commands quote only for bash and
zsh, and the agent request is pasted as the reader's own words.
The page now tracks which variables the reader set on it. A value that
only came with the link goes into a command when it is a number, a
boolean, or short text of letters, digits, spaces and plain punctuation,
and into the agent request only when it is a number, a boolean or one of
the item's own options. A page opened with values from its link says so
and offers "Reset to defaults", and the install command wraps instead of
scrolling so the whole line is visible.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
scripts/upload-docs-images.sh synced docs/images/ with the AWS CLI's default
of following symbolic links, so a link committed under docs/images/ would
publish whatever it pointed to on the machine running the upload. The script
now stops before any AWS call when docs/images is not a real folder in the
checkout or when anything under it is a link or not a regular file, and the
sync passes --no-follow-symlinks as well.
A new check, scripts/check-symlinks.mjs, fails CI when a tracked symbolic
link is not one of the two the repo already means to have.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(aws-lambda): Lambda renders reach only public addresses unless the function opts out
* chore(aws-lambda): drop a comment the function name already says
* fix(engine): renders reach only public addresses from every part of the browser
* fix(engine): renders reach only public addresses from every part of the browser
* fix(engine): renders reach only public addresses from every part of the browser
* fix(engine): renders reach only public addresses from every part of the browser
* 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
* fix(engine): hold the render page to the asset download address rules
With PRODUCER_RESTRICT_PAGE_NETWORK=true the render page reaches only its own project server and public addresses, checked by host and by resolved address, the rule asset downloads already follow. Unset, nothing changes for local renders.
* fix(engine): keep the page network filter comment within four lines
* 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
The error only said to run --help, so an agent guessed another flag. It now
names every long flag the command declares, and --search points to --query.
capture read --timeout with parseInt, so `--timeout 1s` became a 1 ms
page-load timeout. grade-compare dropped an invalid value without a
warning. Both now use the shared parseTimeoutMs helper that check and
snapshot already use, keeping their defaults of 120000 ms and 5000 ms.
Fixes#7671
duplicate_audio_track said two overlapping clips on one data-track-index
"cause layered audio playback" and suggested moving one to another track.
The render's mixer never reads data-track-index (every audible clip is its own
amix input) and the docs call the attribute a Studio lane only, so the two
clips are layered whatever their tracks: rendering a whoosh and a hit on
track 6, then with the hit on track 7, gives byte-identical audio. The message
now says both play and that the overlap is two clips sharing one Studio lane;
the hint says splitting tracks leaves the mix unchanged, and that a leftover
duplicate should be removed or moved. lint-rules.mdx said the audio "doubles
up"; it now says the same as the message.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* 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(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>
* 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>
* 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>
* 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>
* docs: every link to hyperframes.studio carries where the visit began, shared with the homepage
The visit's first source now lives in the homepage's 30-day hf_hub_landing
cookie (.heygen.com) instead of a per-tab sessionStorage key, so a visit that
moves between the homepage and the docs keeps it either way. Pricing,
changelog and community links carry it too; ph_id stays on downloads only.
Tags over 64 characters are left out, as hyperframes.studio drops them.
* docs: tag studio links when the context menu opens; cap saved tags on read
Open in new tab and Copy link take the href as the menu opens, so the source
goes on then (never ph_id). Saved campaign values get the same 64-character
cap as fresh ones.
* docs: a right-click no longer makes a Card's next click drop the source
The menu left the source on the Card's DOM href, so the next click found
nothing to add and returned before following the Card itself, which opens its
own untagged href prop. Compare against the address the link had before the
menu tagged it.
* 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>
0.9.35 made snapshotProject and snapshotFiles fall back to scratch-only
exclusions when .hyperframesignore can't be read. That is right for change
detection, but a host that builds an archive from the same snapshot then
includes files the ignore file meant to exclude, including ones named on its
valid lines.
The snapshot is strict again by default and throws invalid_source_ignore.
Change detection opts in with { lenientIgnore: true }, and projectFingerprint,
which names no files, always reads leniently.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(core): motion blur preview draws fewer filter copies at lower preview quality
The filter tier's preview draws 16 copies at preview quality 1/2 and 8 at 1/4 and
below; renders keep 32. Preview facts now list those levels in lighterAt once the
filter tier has movers, so a host that steps quality down on choppy playback can do
so for a film whose only load is blur.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(core): name the blur preview copies instead of commenting them
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* chore: release v0.9.35
* docs(release): note the render stop and container 403 from #7563 in v0.9.35
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix: track local Studio sharing CTA intent
* fix: tag local Studio and CLI share upgrade links with where they came from
The local Studio share modal's Upgrade to Pro link opens
/pricing?from=cli&entry=local_studio_share, and hyperframes share's source-files
notice links /pricing?from=cli&entry=cli_share, so the pricing page can tell
which link a visit came from and return the visitor to their terminal. The
modal accepts its own pricing page with any query, still only on
hyperframes.dev's two origins. share_upgrade_clicked carries
cta=share_modal_upgrade.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: name the local Studio upgrade CTA and drop the explaining comments
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep the local Studio upgrade link's return page unchanged
Only entry=local_studio_share is added to the local Studio share window's
Upgrade to Pro link. from=cli would have told these buyers to go back to their
terminal after checkout, but they return to a browser tab. hyperframes share's
link keeps from=cli, as the CLI's other upgrade links do.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(share): keep change detection working with a gitignore-style .hyperframesignore
The project scan used by change detection now reads .hyperframesignore
through the strict source reader. Cloud render reads the same file as
gitignore syntax and its docs show /exports/, which the strict reader
refuses, so the scan threw and hosts lost change detection, export
freshness and share status for that project.
Change detection now falls back to scratch-only exclusions when the file
cannot be read. Source capture keeps the strict reader and still refuses it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(share): check snapshotFiles tracks the file, not just names it
snapshotFiles returns every requested path, keying an excluded one as
undefined, so key presence alone did not prove the file was tracked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Local Studio mode runs Vite in the resolved @hyperframes/studio folder, so the
project folder decided which config and binary ran. Use it only when the
project resolves to the same Studio the CLI itself resolves (a source checkout
running its own build) or when HYPERFRAMES_LOCAL_STUDIO=1 is set; otherwise
serve the embedded Studio.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): share rendered videos through unified reviews (#7135)
* feat(share): attach editable project sources to reviews (#7137)
* feat(share): measure local sharing outcomes (#7138)
* feat(cli): stage the sixty-day publish transition (#7136)
* feat(studio): share review pages from local preview (#7140)
Advertise the CLI sharing bridge before bootstrapping it so standalone Studio does not
request unsupported routes. Preserve origin and session checks.
Budget the intended sharing artifact: clean main packs at 8,060,519 bytes versus
8,162,979 with sharing (8,169,168 in CI). Required policy and Unicode tables, bundled
sharing code, and Studio controls account for the growth. Set the packed-only budget
to 8,577,627, following the 5% headroom convention; retain the unpacked cap and all
package checks.
* fix(share): persist refusals and improve CLI retry feedback
* fix(ci): restore render diagnostics and include sharing workspace
* fix(cli): keep sharing owner error codes stable
* fix(share): clarify update feedback and align audience changes
* fix(share): clarify updates and avoid scratch-file rerenders
* fix(cli): report active shares and preserve update channels
* fix(cli): resolve update channel when checking registry
* fix(ci): refresh sharing package budgets after rebase
* fix(share): require consent before uploading project files
* docs(variables): say what can be a variable, including a video or sound per account
* docs(variables): render the per-account example from index.html and keep the outline