* 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(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>
* 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
* fix(cli): publish keeps Library files out for projects on iCloud Drive
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): treat Library/CloudStorage cloud drives like iCloud Drive when publishing
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): publish leaves out private files outside the project and says so
A project you open may come from someone else, and its markup can point at
files outside the project folder. Publish and cloud render now leave out an
outside file that sits in a hidden folder (any path segment starting with a
dot past the folders the project itself sits in) or under /etc, /proc, /sys
or /dev, checked both as written and after resolving links.
Whenever an outside reference is left out, for this reason or because it is
an env file or Git data, the CLI now prints which project file holds the
reference and the reference as written. Other outside references are copied
into _ext/ as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): feedback's repro publish also names files it leaves out
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): publish also leaves out project links to private outside files, and AppData/Library
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): only the home folder's AppData and Library count as private
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): a referenced project link to a private outside file stays out too
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): resolve both paths the same way and skip AppData/Library when the project sits there
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli,parsers): take helper programs only from install locations, never the project folder
FFmpeg, FFprobe, whisper-cli, parakeet-mlx, Python and system Chrome are now
found through one shared rule: an absolute PATH entry outside the working
directory, or a fixed install dir. A relative PATH entry and any folder
inside the working directory are skipped, on every platform. Windows walks
PATH itself instead of asking `where`, which lists the working directory
first.
FFmpeg discovery no longer falls back to `.hyperframes/bin` or to an
installer package in the project's node_modules; an installer package
installed next to HyperFrames still works. The env overrides are unchanged.
The CLI skill reference stops suggesting the project-local folder.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): give the PATH-lookup tests a fixed PATH on Windows
Windows now walks PATH instead of running `where`, so tests that faked
`where` output found the runner's real python and cmake. Both tests now set
PATH to a temp folder holding only the programs they expect.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: report a missing helper program instead of running it by bare name
When no trusted FFmpeg or FFprobe is found, the engine, the producer's
probes and Studio's waveform, peak and audio-track helpers now report
"not found" with the HYPERFRAMES_FFMPEG_PATH / HYPERFRAMES_FFPROBE_PATH hint
instead of handing the bare name to the OS lookup. Callers that degraded
on a missing binary still do: runFfmpeg returns a spawn_error result, the
GPU and version probes report none, and Studio's audio helpers fail soft.
The Lambda handler names its bundled ffmpeg and ffprobe by path, since
they live under the task root, which is the working directory.
brew, git and cmake for the whisper.cpp install, and the clipboard tool
for `hyperframes add`, run by the absolute path the trusted lookup
approved. The media-use engine gets a PATH holding only trusted folders.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): fail a missing FFmpeg the way a failed spawn always has
Throwing from getFfmpegBinary turned every caller's missing-binary path
into a synchronous throw: the streaming encoder's "failure result, not a
throw" contract broke, and unit lanes that run without FFmpeg crashed at
module load. With no trusted copy the getters now return an absolute path
inside HyperFrames' own install that is never created, named for the
override to set. Spawning it fails with ENOENT exactly as before, and the
OS still never looks the bare name up. The call-site guards and fixture
changes that the throw needed are reverted.
The whisper install tests match git and cmake by name and skip the brew
case on Windows, where the lookup walks the real PATH.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(engine): pin the found FFmpeg before the HDR test looks it up as macOS on Windows
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
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
* fix(parsers,lint,producer,cli): confine composition path lookups to the project
- The local asset resolver offers only files inside the project: a path
that is still absolute after its leading `../` is clamped (an encoded
`//`, a drive letter, a leading backslash) yields no candidate.
- Lint, the catalog-usage walk and `keyframes` read a
data-composition-src only inside the project. Lint and the catalog
walk resolve it with the render's own resolver, now shared from
`@hyperframes/parsers/asset-resolution`, and lint reports one outside
the project as the render pre-flight does.
- The render compile step does not look at a media, gsap script or image
path on another UNC or device root, and the GIF and HEIC preparation
treats a `//host/...` image src as a URL rather than a share.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(parsers,lint): keep Windows absolute asset paths that render copies in
The shared asset resolver now offers only files inside the project. On
Windows a drive-letter src such as C:\media\clip.mp4 used to reach the
real file through the old fallback, and render still copies that file in.
Lint now accepts such a file for media and for CSS written in the page,
so it raises no new missing_local_asset or texture_mask_asset_not_found
error. The media-treatment and normalize-audio commands find it again.
The check never looks at another computer's share, and on macOS and
Linux a src that starts with / is still a project URL, so nothing
changes there.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(parsers): expect a drive-letter sub-composition src to be refused on Windows
On Windows an absolute src outside the project is a drive-letter path,
which resolveCompositionSrc refuses, as the render pre-flight already
does. On POSIX the same src is a project URL and resolves inside the
project. The test now expects each platform's result.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(lint): do not report a missing timeline registry a script outside the project may hold
Lint no longer reads a script outside the project. When a root
composition loads such a script, lint cannot know whether the script
registers the timeline, so it no longer reports missing_timeline_registry
for that composition. Render still loads the script. A composition whose
scripts are all in the project is checked as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): give each test file its own home so renders never wait on another file's lock
* test(cli): pin the cli test config after adding the per-file home setup
* feat(engine): decouple transparent background from png capture format
PNG capture used to imply a cleared page background. A new
CaptureOptions.transparentBackground lets lossless opaque PNG capture
(4:4:4 MP4 output) keep the page background. Absent, it still follows
format === "png", so alpha output and motion blur are unchanged.
Opaque PNG skips drawElement, whose verification and worker-encode
paths are JPEG-only.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(engine): add 4:4:4 chroma option to getEncoderPreset
getEncoderPreset takes an optional chromaSubsampling ("420" by
default). "444" returns yuv444p for SDR MP4, so libx264 encodes the
High 4:4:4 Predictive profile and odd sizes need no even padding.
WebM, MOV and HDR presets ignore it. The ChromaSubsampling type is
exported for the producer.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(producer): chromaSubsampling render option with lossless png capture
RenderConfig.chromaSubsampling ("420" by default) opts an SDR MP4
render into 4:4:4. "444" encodes libx264 yuv444p and captures every
frame as opaque PNG: Chrome's quality-100 JPEG is already 4:2:0 on
beginFrame and screenshot capture, and drawElement can fall back to
screenshot mid-render, so PNG is the only capture that keeps the
colour. drawElement is turned off for these renders.
The probe and main capture options share resolveCaptureSurface, so
they cannot disagree on format, quality or background.
Formats other than mp4, GPU encoding and HDR output are rejected
before any work starts, auto-detected HDR sources fail before capture,
and distributed requests refuse 444. The default render is unchanged.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(producer,studio-server): accept chromaSubsampling on render routes
The shared parseEncoderOptions validates chromaSubsampling and answers
400 for "444" with a non-mp4 format, gpu, or force-hdr, so a request
that would come back 4:2:0 never starts a render. The Studio render
route, both Studio adapters and the producer HTTP server forward it.
The producer server also refuses "444" with outputDynamicRange "hdr",
which parseEncoderOptions cannot see.
No Studio UI control; the option is route-level like crf and hdrMode.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): add --chroma-subsampling flag
`hyperframes render --chroma-subsampling 444` opts an SDR MP4 render
into full-resolution chroma (yuv444p with lossless PNG capture). The
default stays 420. The plan rejects 444 with a non-mp4 format, --gpu
or --hdr before anything renders, with a usage error that names the
conflicting flag.
The value reaches the local render request and, only when it is 444,
the Docker argv, so default Docker invocations are unchanged.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: document 4:4:4 chroma subsampling
Add a "4:4:4 masters" section to the rendering guide: when to use
--chroma-subsampling 444, why it captures PNG, the measured chroma gain
(large for text and UI, none for footage and gradients), its limits,
and a player compatibility table to be filled in from testing.
Document the flag in the CLI reference, the built-in rendering docs and
the hyperframes-cli skill reference (with the regenerated skills
manifest), and the chromaSubsampling option in the producer docs.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: add 4:4:4 player compatibility results
Fill the 4:4:4 compatibility table from testing H.264 High 4:4:4
Predictive output. Chrome 155, Edge 155, VLC 3.0, Safari on iOS 26.6
and Safari 26.6 on macOS play it, and so does AVFoundation on macOS
26.6, the framework QuickTime Player plays through. Firefox 157 on
Windows and both Windows media players do not.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: note the measured render cost of 4:4:4 output
Replace the vague "slower capture" note with measured numbers: a text
and UI composition rendered in about twice the default time, full-frame
footage in about three and a half times, because PNG encoding cost grows
with image detail.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): reject chromaSubsampling 444 in distributed render config
Distributed configs have no chroma field and validateDistributedRenderConfig
ignored unknown keys, so a JS caller passing chromaSubsampling: "444" to the
Lambda or Cloud Run SDK got a 4:2:0 file with no error. Reject it, and make
the rendering guide say so precisely.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): check a 444 render reaches the encoder as yuv444p
Every helper had tests, but nothing checked the orchestrator passes
chromaSubsampling through, so dropping it from the encoder preset or capture
surface would turn 444 renders back into 4:2:0 with all tests green. Render a
small fixture with "444" and with the default and check pix_fmt with ffprobe.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(producer): move the 444 drawElement gate into a helper
Keeps runCompileStage under the fallow complexity threshold.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: keep comment share at or below the merge-base
comment-ratchet failed on 11 files this PR touched. Keep the 4:4:4
rationale once in chromaSubsampling.ts, move the distributed-render
reason into its error message, and cut the rest.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): check a 444 render captures full-resolution chroma
The encoder check alone passes when chromaSubsampling is dropped from the
capture surface: frames are captured as JPEG and encoded yuv444p with
4:2:0 colour. Put a red/blue edge at an odd x, inside a 4:2:0 chroma
pair, and require the two pixels to differ in Cb.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): trim the chromaSubsampling.ts header to the package comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: finish switching to capturesAlpha from #6262
The merge that adopted main's transparent / capturesAlpha left these files
uncommitted, so resolveCaptureSurface still returned transparentBackground.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(engine): use transparent / capturesAlpha from #6262
main added CaptureOptions.transparent and capturesAlpha (#6262), which do
what this PR's transparentBackground did. Use them, keep the PNG check in
drawElementWorkerEncodeEligible, and re-pin test-classification.mjs and
the skills manifest against current main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): cut the 4:4:4 comment blocks to one to three lines
The reasoning lives in the PR description with the measurements.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: reconcile 4:4:4 chroma with latest main
Keep main's video-layer capture overrides, template entry resolution,
ProRes profile parsing and blur-differential tests alongside the chroma
option, and fold the encoder sub-parsers into one loop.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: keep main's compile-stage tests and regenerate the skills manifest
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): resolve helper programs from PATH, never the working directory
On Windows a bare command name is looked up in the working directory before
PATH. The CLI now sets NoDefaultCurrentDirectoryInExePath at startup, which
Node's spawn and cmd.exe both honor and child processes inherit, so tools
such as powershell.exe, taskkill and npx.cmd always come from PATH.
The shared ffmpeg/ffprobe resolver no longer scans the working directory on
Windows and skips relative PATH entries.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep Python helpers from importing files in the working directory
`python -c` and `python -m` put the working directory first on sys.path, so
a file in the project named like a probed module ran instead of the
installed package. Inline helper code now drops that entry before any
import, and `-m` helpers (pip) run through runpy after the same step. Paths
and arguments are unchanged.
On Windows, findPython also skips a `where` match in the working directory.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): run the skills installer and nested CLI calls independent of the project
The global skills install ran `npx skills@<pin>` in the current folder, so
npm could take the package or registry from that project's node_modules or
.npmrc. It now runs from the home folder; the install is global either way.
When the CLI starts the media-use engine it hands over its own entry file.
The local voice fallback and the audio helpers then run that same CLI with
the same Node instead of resolving `npx hyperframes` from the project.
Without a handed-over entry they behave as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(media-use): load only provider keys from a project .env
The audio scripts copied every key of a project .env into their environment
except two. They now take the same kind of short allowlist the CLI uses:
HeyGen, ElevenLabs and Gemini API keys plus a few harmless settings. Program
overrides, runtime options, credential files and the credential store path
come only from the person's own environment.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): build whisper.cpp only from a pinned, verified release
The source-build fallback cloned the upstream default branch. It now clones
the v1.9.5 release tag and refuses to build unless the checkout is the
reviewed commit for that tag.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep registry caches apart and refuse config install targets
Registry cache file names now include a digest of the exact registry URL,
and each entry records the URL it came from, so one registry's cached
manifest is never read for another. Entries from older versions are
refetched once.
Registry installs refuse targets inside .git or any hidden directory, hidden
configuration files, and package.json, hyperframes.json and
hyperframes.lock.json. An example installed by `init` may still bring its
own package.json and .gitignore.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(capture): keep page text to one line in agent files and validate Vertex keys
Capture writes AGENTS.md, CLAUDE.md and .cursorrules from the page's title,
font names and colours. Page text is now flattened to one short line and
colours must be hex values. Existing agent files that capture did not write
are kept, with a warning.
HYPERFRAMES_VERTEX_SERVICE_ACCOUNT must now be a plain service-account key
with a Google token endpoint; other credential types skip captioning with a
warning.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): find the digest-named registry cache and trim a new file's comment
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): match registry targets as Windows names them; skills install without HOME
Windows drops trailing dots and spaces from a path segment and reads name:stream as
name, so package.json. or .git./hooks reached the files the target rules refuse.
The global skills install now falls back to the temp folder when HOME does not exist.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): turn off the Windows working-directory lookup in every program entry
The warm-check server and client are their own tsup entries and copied the
environment before cli.js set NoDefaultCurrentDirectoryInExePath, so the server
spawned a bare powershell.exe that Windows could take from the project folder.
Every entry that hides child consoles now also loads windowsExeSearch first.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): refuse Windows short-name registry targets
A segment like CLAUDE~1 or PACKAG~1.JSO opens the long name on NTFS, so it
reached the files the target rules refuse. The trailing-dot and stream-name
normalization is removed: publication already rejects those segments.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): lambda destroy runs SAM in a private folder and acts only on the selected stack
- sam delete outside a checkout runs in a fresh private temp folder,
removed afterwards, instead of the shared temp directory.
- A stack state file must name the stack it is selected by.
- destroy and deploy derive the video repository name from the stack
name instead of trusting the recorded value.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): snapshot keeps remote clips in a private folder and reads only allowed URLs
- A video URL the download policy refuses (plain http, or a private,
loopback or link-local host) is no longer handed to FFmpeg; the clip
is skipped instead, as render does.
- Remote clips are cached in a per-user, owner-only temp folder; a
folder open to other users is never reused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): upgrade --project writes package.json through an exclusive temp file
The rewrite now uses the shared atomic replace, which creates a fresh,
unpredictable sibling with exclusive creation, so an existing
package.json.tmp entry is never written through.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep env files, Git data and tool records out of served and uploaded projects
- play and present answer 404 for .env files, .git and the tools'
private .hyperframes records, as Studio's preview does for the records.
- publish and cloud render never stage an env file or tool record, even
when markup references it, and never pull in an env file from outside
the project.
- Cloud site uploads (Lambda and Cloud Run deploySite) leave env files out.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): lambda commands accept a state file whose stack name differs only in case
On a case-insensitive disk, deploy --stack-name=Demo and --stack-name=demo share one
state file, so a name that matches apart from case is the same stack the user deployed
and keeps working as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): snapshot's fallback media folder uses createStagingDir
The repository check forbids bare mkdtemp beside a caller-supplied path, because it
fails past 260 characters on Windows. Also trims a comment so the new helper file stays
within its package's comment share.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): snapshot never hands FFmpeg a remote URL
FFmpeg follows redirects and resolves hosts on its own, so a clip the downloader could
not fetch must not reach it as a URL. Snapshot now leaves such a clip out and warns,
as render does. A fallback media folder is removed when the process exits.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): cover .envrc, .env-local and .env_prod, and test present's private-file 404
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
A project-local node_modules/.bin/hyperframes can shadow plain npx hyperframes,
but npm install -g never updates it. Classify the shadowing copy like the
running one: global installs keep their manager's command, project-local
installs get the project's own manager (from its lockfile), and unknown
layouts stay quiet. The command pins the release the npx copy is running.
* fix(reverse): give agents the sign-in reason to say, and catch stale CLIs that know reverse
- `reverse start`'s signed-out `next` now carries a sentence the agent can say as is
(why HeyGen, and that the HyperFrames account is the HeyGen account), asks for it at
the start of the sign-in message, and on remote terminals has the agent send the
device link and code before it waits.
- references/start.md: same ordering, an example that fits both login routes, and no
links to or quotes from the instructions themselves.
- An old global install that knows `reverse start` but predates `next` was never caught:
agent runs get no update notice and no auto-install, so it stays frozen. The skill now
also treats `_meta.updateAvailable: true` from `reverse start` as an old install and
runs the rest with `npx -y hyperframes@latest`; every CLI that knows `reverse start`
already reports that field.
* fix(reverse): send remote terminals straight to device sign-in, reason in every link message
- `reverse start` now knows when no browser can open (the check `auth login` uses, moved
to attendedTerminal): `login_command` is `auth login --device` and `next` asks for one
message with the reason, the link and the code. The two-step route (a refused browser
login, then a bare follow-up with the code) is where the reason got lost.
- Every message that gives the sign-in link starts with the reason; agents say they are
waiting rather than quoting the skill, and give no file paths.
- The out-of-date line for an old global install goes in the next message to the person.
* fix(reverse): flag an older global install that shadows npx, and pin the run's release
- installerDetection: `shadowingInstall` finds the older global `hyperframes` that a plain
`npx hyperframes` runs instead of this npx copy (first on PATH outside the npx cache), with
the command that moves it. `detectInstaller` takes the entry to classify.
- `reverse start` run through npx opens `next` with that line as words to say, signed in or
not. Skill prose alone did not get agents to tell the person.
- Skill: a signed-out `reverse start` with no `reverse.next` is also an old install, which
covers a cold update cache; the run pins the release `@latest` resolved to.
* fix(cli): no macOS developer-tools prompt from git, xcrun or cc checks on a Mac without the tools
* fix(cli): treat Xcode.app as installed tools and only take executables from PATH
* test(cli): give skills tests a developer folder so darwin cases run on any host
* fix(cli): read macOS tool paths the same way on every host
Follow-ups from review on #7443 and #7444:
- The quote hint returned the first run of words that existed, so a
"Final Cut/" folder hid "Final Cut export.mp4". It now names the longest.
- "--compare=my clip.mp4" got no hint; the value after = now starts a run.
- The telemetry section lists the skill a reverse or templates command ran
for, and the HeyGen session id a recorded reverse run carries.
* feat(cli): reverse and templates report their own runs; commands say which skills are installed
Gaps in what skill telemetry can answer for /reverse-any-video and
/style-sampling:
- The skill's beacon fires only when the agent runs it, and agents often
skip it. `reverse start` and `templates pull` now send `skill_invoked`
with `source: command`; beacons carry `source: beacon`. A person counts
once.
- style-sampling renders were never tagged. A pull marks the project the
episode is built in (only a folder that is already a project).
- Installs of an on-demand skill were invisible. `cli_command` carries
`skills_installed` and `skills_outdated`, the names from the cached
background skills check, so "never triggered" and "not installed" can
be told apart.
- `auth status` signed out exits 1 with a bare "Command failed", which
reads like a login failure. It now carries `NotSignedIn`, and an auth
error its own cause.
And a step that gets lost: a reverse started signed out often goes on
without ever trying to sign in. `reverse start` signed out now prints
`login_command` and a `next` line in the JSON the agent reads, not only
in the skill's reference.
* refactor(cli): keep comment share at the base in the reverse telemetry files
* fix(cli): command runs get their own event, counted once per piece of work
Review on the first cut: `skill_invoked` from the commands doubled the
#7176 beacon's single observation, and it fired before any work.
- `reverse start` and `templates pull` send `skill_command_ran`, not
`skill_invoked`; the beacon is back to its #7176 shape.
- `reverse start` sends it after the probe, with `signed_in` and the
reverse `session_id` that keys a retry; a video it cannot probe sends
nothing.
- `templates pull` sends it only when it downloads; a re-pull or a
refused pull sends nothing.
- A skills check that finds no install forgets the installed names.
- `auth status` failures carry only a code, never the auth error's text.
* fix(cli): measure answers the four mistakes agents make most
The usage errors agents hit most on `measure`: no op named, a path it
cannot read, and a flag it does not take. Some agents never get past
them to a successful measure.
- `measure <video>` with no op (alone or with --json) runs `probe` and
says so on stderr. With other flags the op is a guess, so the
unknown-command hint asks for one; it now names a path that does not
exist yet too.
- When ffprobe cannot read a file, the error carries ffprobe's reason and
a matching fix: a cut-short download, a page saved as .mp4, a
permission.
- An unquoted path with spaces says to quote it, both where the extra
words are rejected and where the cut path is missing.
- Window flags take --from/--to, and folder flags take -o.
* refactor(cli): keep comment share at the base in the measure files
* test(cli): expect a spaced path as the shell split it, on Windows too
* fix(cli): a cut-short MP4 says download it again, read from its header and ffprobe's specific line
* fix(cli): an unquoted spaced path reaches probe or its quote hint wherever it falls
* feat(skills): reverse-any-video and style-sampling install with the core set
A skill only triggers when it is installed. On demand these two rarely
were, so a request to copy a video or make an episode in a proven style
seldom reached them, and the entry skill named only one of them, in its
closing line.
- isCoreSkill, FALLBACK_CORE_SKILLS and the marketplace `core-skills`
entry include both, so `init` and `skills update` install them. The
`hyperframes` plugin already bundled every skill.
- `/hyperframes` routes to both from the top of its table: a video to
copy or remake, and an episode in a proven style. Its budget takes
+64 B for those two rows.
- `/reverse-any-video` triggers on "remake" and on 「复刻这个视频」
「照着做一个」, inside the 320 B description cap.
- Every catalog surface lists both in the core group: CLAUDE.md,
AGENTS.md, README, the skills guide, skill-lifecycle and the two init
templates (still byte-identical).
* refactor(cli): keep comment share at the base in skillsManifest
* feat(cli): add agent markers other detectors use, verified upstream
Compared std-env, @vercel/detect-agent, am-i-vibing and agent-cli-detector
against our rules and kept only markers the agent itself sets on the
shells it spawns: Auggie AUGMENT_AGENT, Amp AMP_CURRENT_THREAD_ID, Cursor
CURSOR_CONVERSATION_ID and CURSOR_SANDBOX, Cline CLI CLINE_WRAPPER_PATH,
Muse MUSE_RELEASE_INFO, and Warp Oz OZ_RUN_ID (after the harnesses it
wraps).
Claude Code now keys on CLAUDE_CODE_CHILD_SESSION or
CLAUDE_CODE_ENTRYPOINT. Its IDE extensions also set CLAUDECODE in the
integrated terminal a person types into, so CLAUDECODE alone counted that
person as an agent: no prompts, agent-mode login.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* docs(cli): trim comments and fix citations the comment gates flag
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* chore: raise the cli packed size budget to its measured size
main already sat at the edge of the 1% tolerance; the new agent rules
put the packed CLI 842 bytes past it (8062664 vs 7982002 + 1%).
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat(cli): detect more agent runtimes in telemetry
Agent runtime rules:
- copilot_agent: key on COPILOT_AGENT=1 or AI_AGENT=github_copilot_*
(VS Code agent terminals) instead of the unverified Actions markers.
- copilot_cli: COPILOT_CLI=1 or COPILOT_AGENT_SESSION_ID, ahead of
copilot_agent.
- kilo (KILO=1, KILOCODE_VERSION), ahead of opencode.
- opencode (OPENCODE=1, OPENCODE_SESSION_ID).
- qwen_code (QWEN_CODE=1), junie (JUNIE_SHIM_PATH),
antigravity (ANTIGRAVITY_AGENT), qoder (QODER_AGENT),
kiro (AGENT_DISPLAY_OUT, AGENT_CONTEXT_OUT), openhands (AI_AGENT=openhands).
- AI_AGENT fallback after every vendor rule: known names map to their
runtime, any other slug-safe name becomes other_ai_agent. Bare AGENT
is not used.
Discovery hints: other_ai_agent keeps its hints, agent_hint prefers
AI_AGENT over AGENT, and AGENT_TOOLSDIRECTORY,
GSM_SKIP_SSH_AGENT_WORKAROUND and EDGE_METRICS_SESSION_ID are no
longer hint keys.
CI: name AWS CodeBuild (CODEBUILD_BUILD_ID) as codebuild.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat(cli): detect agents seen in discovery hints
Add rules for closed-source agents whose markers show up in the CLI's
own agent_env_hints on non-interactive runs: WorkBuddy, CodeBuddy, Trae,
Pippit, Doubao, Aily, Grok, Kimi, ZCode, SWE-agent and apps built on the
Claude Agent SDK. Qoder also matches its CLI and agent SDK keys.
The AI_AGENT name map now covers the names agents report (Devin, Amp,
v0, Rovo Dev, Base44, Trae, Antigravity, OpenHands, Copilot, and
hermes-agent), and a known name in the bare AGENT variable counts too.
Unknown AGENT values such as AGENT=1 still do not.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat(cli): detect the DeepSeek harness
Every dsh model shell call runs with DSH_SHELL=1 and the agent's
DSH_SESSION_ID. HyperFrames Desktop also runs dsh; its runs carry
HYPERFRAMES_CLIENT, so the client field separates the two.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* docs(cli): cite the Agent SDK source for claude_agent_sdk
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(cli): let the closest agent win over inherited markers
Copilot's COPILOT_AGENT / AI_AGENT and COPILOT_CLI pass down to the
agents it starts, and TERM_PROGRAM / REPL_ID only say where a shell runs.
Those rules now come after every other agent rule, so opencode or Qwen
started by Copilot, or Kilo in a Cursor terminal, report as themselves.
dsh keys on DSH_SHELL=1 only: it sets DSH_SESSION_ID on the terminal a
person types into too. Qoder drops its app-wide SDK and setting keys,
CodeBuddy drops CODEBUDDY_AGENT_RUNTIME (a setting it reads), and Kiro's
markers must be non-empty.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(cli): cloud render finds media whose file name is stored in another Unicode form than the page's
* fix(cli): keep the archive-key change from raising publishProject's comment share
* fix(cli): a page that names a decomposed file as the disk lists it still matches its archive entry
* feat(cli): check returns an unchanged project's last pass in about a second
* fix(cli): the check cache hashes files without a stat race and its tests run before the signal test
* test(cli): the warm check test compares two real runs, not a run and its cached pass
* feat(cli): check --no-craft skips the craft pass for a render preflight
* fix(cli): the check cache keys on timeout, env and large files and never replays a moved tree
* style(cli): format the check cache
* fix(cli): the large-file cache test waits for the clock tick it depends on
* fix(cli): the check cache keys on the browser and on scripts under .hyperframes
* fix(cli): the check cache ignores the video copies the check itself touches
* fix(cli): a media file referenced by its filesystem path goes into the cloud archive
* fix(cli): an absolute media path keeps its fragment and query, and the resolver is split
* fix(cli): a Windows drive-letter media path is a filesystem path too
* fix(check): lint and check skip compositions the project never mounts
* refactor(lint): let two new names stand without doc comments
* test(cli): lint tests that lint unmounted files say so
The desktop app can't run an edit while a preview of the project is
running, because the preview holds the project's history lock. Following
the hint that `preview --background` prints therefore left the app's edit
waiting until someone stopped the preview by hand.
`hyperframes open` now stops a background preview of the same project
before handing it to the app, and prints one line saying so. It only
stops a preview it can prove it started (a saved session whose wrapper
process still owns the server). Any other preview is left running, and
`open` prints the exact `preview --stop --port N` command instead. With
--json the result carries a `preview` field.
The hint that `preview` prints now says that `open` stops a background
preview, or that a foreground one must be stopped first. The project
template and the CLI skill's preview reference say the same.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(check): a Chrome that never becomes ready ends the check with a named error
* fix(check): name the Chrome start window in code instead of comments
* fix(cli): cloud render zip carries files the composition references under dot-folders
* fix(cli): a missing link href no longer fails the cloud zip; media refs still do
* chore(cli): shorten the referenced-file comment
* fix(cli): only a missing video, audio, img src or poster stops the cloud zip
* fix(cli): a stylesheet url() never stops the cloud zip; only the no-fallback media refs do
* feat(check): every check step prints a line on stderr and repeats it every 30 s while it runs long
* feat(check): name the saved report file on stderr and tell agents not to use npm run
* fix(check): print a step's line once when the step starts, not on every progress ping
* style(check): wrap two long lines for oxfmt
* fix(check): say the report file is written unless a not-recorded warning follows
* chore(skills): refresh the skills manifest hash for the check doc line
* fix(check): keep the start line free of the not-recorded warning text
* fix(check): count a Korean number and its counter as one word in line reading time
* fix(check): keep segmenting Thai, Lao, Khmer and Burmese when counting reading words
* feat(studio): show the agent's storyboard in a Storyboard tab beside the preview
The board an agent writes per the storyboard recipe (boards/storyboard.html,
or a root storyboard.html) now shows in Studio the way HyperFrames Desktop
shows it: a Preview | Storyboard strip over the preview panel, only while the
project has a board. Studio reads the page's class="frame" boxes into a board
of stills, with acts, titles, times and words, and one frame at a time with
arrow keys. A page with no frames shows as written in a script-less iframe.
A board written while Studio is open brings its tab to the front, as Desktop
does at the agent's stop. A rewrite of the page, a still beside it or
STORYBOARD.md reloads it in place, and a dot marks a rewrite seen from the
preview. "Show in preview" goes back to the film at the frame's start.
Notes, drawings and the go belong to Desktop's agent, so the board's bar
carries the desktop-app button. Its funnel events now say which button was
pressed (placement: header or storyboard).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy
* refactor(studio): split the storyboard view and its frame reader into smaller parts
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy
* docs(skills): the agent's storyboard stop points at the Storyboard tab, not the file
With the board shown beside the preview in Studio as in Desktop, the recipe's
stop and style-sampling's stop 1 tell the person to look in the Storyboard
tab, and to start a preview and give its link when none is running, instead
of handing over boards/storyboard.html to open from disk.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy
* fix(studio): the storyboard listens on Studio's own file-change channel, and its notes are trimmed
The board opened its own /api/events stream, which the Vite dev server
behind the runtime smoke does not serve. It now subscribes through
subscribeFileChanges, the one channel picker the external-change
coordinator already uses (test adapter, Vite HMR, then SSE), so dev and
built Studio deliver the same changes to both.
The new files' comments are cut to the package's share, and the recipe's
Storyboard-tab line moves to the paragraph that names the board, leaving
the stop step as it was.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy
* fix(studio): the board hears file changes through the coordinator, not a second subscription
The external-change coordinator stays the one subscriber to the file-change
transport (HMR in dev, SSE when built), as externalFileChangeOwnership
asserts. It announces each decoded change through fileChangeFanout, and the
storyboard listens there. Mounting EditorShell alone, as its tests do, no
longer opens an EventSource, and the coordinator file stays under the line cap.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy
* feat(studio): the storyboard's Open in desktop app asks the app to open on the board, and its card says why
- The storyboard bar's button posts `doc: "storyboard"` with its page id. The preview server passes only that value
on, and `openInDesktop` writes it into `.hyperframes/desktop-cta.json` beside the page id, so the app can open the
project on its Storyboard tab with Build in sight (hyperframes-internal reads it).
- The guide card opened from the storyboard says "Approve this storyboard in the desktop app" and "Comment on a frame,
draw on it, then press Build", and its last step says the app opens on this storyboard. The header's card is
unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy
* feat(studio): approve the storyboard in Studio; comments on frames stay in the desktop app
A Studio user without the desktop app had no way to approve the board from the tab, and the bar said approval was
in the desktop app, so the tab read as a dead end. Studio talks to the person's own agent through their chat, so the
bar's Approve copies "The storyboard is approved. Build the video from it." for them to paste to it, and says so in
a toast (or spells the words out when the clipboard refuses). Commenting and drawing on frames stay in the desktop
app. The storyboard recipe tells the agent those pasted words are the person's go.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy
* fix(studio): the storyboard's desktop card offers commenting, since approving now happens in Studio
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy
* fix(studio): hand-off intent before dispatch, steady film under the board, stills outside the board folder
- openInDesktop writes desktop-cta.json before sending the folder, so a running
app reads the storyboard ask on arrival; a plain or header open drops an
earlier storyboard ask; a failed open puts the earlier record back.
- PreviewStage keeps the film at one place in the tree with or without a board,
so a board appearing never remounts it; the automatic switch goes through the
same pause as a click, and a play while the board is up is paused.
- The board reloads when a still it draws changes, including a root board's
stills/ and a boards/ page's ../assets.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy
* chore(cli): fit the Storyboard tab in the CLI's size budget; reword a record helper's doc
The CLI tarball carries Studio's build, which now holds the Storyboard tab; merged
with main it measures 7,982,002 bytes packed, 7 bytes past the 1% tolerance.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy
* fix(studio): hold the player while the storyboard covers the film
A pause after the fact let J's reverse loop schedule its next frame, so the
hidden film kept seeking. The stage now takes the player's own hold while the
board is up (and only when no one else holds it), so J, Space and playback
requests are refused before they start; Preview releases it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): check_report counts the browser-playable copies a check waited for
* style(cli): shorten the copy facts comment under the line limit
* fix(cli): a check stopped by the copy wait stays browserSkipped; count only abort-caused unfinished
* style(cli): format the copy facts tests
* feat(core): auto motion blur draws with the filter tier
Capture stays available as data-motion-blur-tier="capture". auto now draws with the
filter tier (reasonCode tier-auto), so the capture-only defects leave the default path.
Removes the translation-only hand-off and its Discovery field, adds a filter arm to the
differential, and updates the check, guide, skill and Blur panel label.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* docs(core): measured cost and known limits of the filter tier, the new auto default
spacex-launch (77 movers) takes 2.9x the CPU of no blur on the filter tier and 1.7x on
capture; say so, and list the filter tier's measured limits (sweep D, E, F, I, O, B).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* docs(core): word the filter tier's cost and limits as measured, not as mechanism
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* docs(core): do not say every filter-tier limit is pinned by a sweep test
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): split the blur differential so each file fits the flake gate's 120 s run
The filter arm moves to its own file and skips fixtures that already draw with the filter
tier; inside cases get their own file; a fixture's blur-off page is opened once per file.
Shared helpers live in __fixtures__/motionBlur/differentialPage.ts.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* feat(cli): a line_unread finding carries the frames it measured around where the line was first read
* style(cli): shorten the measured field's comment
* feat(cli): measured frames at both ends of the line, with fewer comment lines
* fix(cli): an unknown command answers in a few lines and says what to run instead
* fix(cli): shorten the captions pointer and drop the redirect doc comments
* fix(cli): point the captions hint at the hyperframes skill's guide, and test the path exists
* chore(cli): regenerate the skills manifest for the hyperframes-cli skill edit
* feat(cli): check --budget stops the whole check in time and reports what it found
* fix(cli): keep check's comment share where it was
* fix(cli): a --budget that runs out before any check step is waiting is not an unhandled rejection
* feat(cli): info --media lists every clip the render hears, on the film's clock
* fix(cli): info --media leaves out a clip that starts past its media's end
* fix(cli): keep the heard-clips doc line within 120 characters
* fix(cli): every settings file follows HYPERFRAMES_CONFIG_DIR
* fix(cli): the media-use skill copy reads its config from HYPERFRAMES_CONFIG_DIR too
* test(cli): expect the config folder as a normalized path on every platform
* chore(skills): refresh the media-use manifest hash
* fix(cli): a moved settings folder starts from ~/.hyperframes, keeping an opt-out
* fix(cli): drop the updater's unused path import
* style(cli): keep the settings-seed comment under 120 characters
* fix(cli): a preview's session follows HYPERFRAMES_CACHE_DIR when it is set
* docs(cli): background previews follow HYPERFRAMES_CACHE_DIR
* test(cli): unstub the preview test's env in a block body
* test(cli): clear HYPERFRAMES_CACHE_DIR in the CLI's test home
* fix(cli): registry cache, search model, catalog and catch-up follow HYPERFRAMES_CACHE_DIR
* style(cli): format the media search cache test
* test(cli): compare the model path against an absolute cache folder on Windows too
* fix(cli): both catalog readers treat an empty HYPERFRAMES_CATALOG_ARTIFACT_DIR as unset
* fix(cli): capture takes a refused screenshot once more before naming it
* fix(cli): keep the screenshot retry's doc to one line
* test(cli): refuse the same capture shot twice now that one refusal is retried
* fix(cli): check skips a contrast sample measured over a layer that is mid-motion
* fix(cli): move the backdrop overlap read out of sampleOf, and add no comment lines
* fix(cli): shorten the measuredInMotion comment
Some hosts drop a connection to a closed loopback port instead of refusing it
(WSL 2 mirrored networking, a firewall in stealth mode). The Vite Studio probe
on 127.0.0.1:5190 then waits for fetch's 10 s connect timeout, and since
every render, check and snapshot looks for a Studio through the history owner,
each of them paid 10 s. Aborting the fetch does not help: the connect attempt
keeps its socket, and the process, alive for the full 10 s.
The default probe now connects with node:net under a 1 s bound and destroys
the socket, then fetches only from a host that accepted.
Co-authored-by: Whoosh <nhatkha1407@gmail.com>
README links to hyperframes.studio, hyperframes.heygen.com and heygen.com
carry utm_source=github&utm_medium=readme, the values the README's download
links already use. Three README links went through docs redirects that drop
the query string (/showcase, /guides/claude-design, /guides/open-design);
they now point at the pages themselves.
The docs navbar's Community and changelog links carry src=docs-navbar, and
the export page's reinstall link src=docs-export, beside the existing docs-*
tags.
Links the CLI prints to our sites (init's docs links, the Lambda docs, the
publish claim URL, the HeyGen API-key page) carry utm_source=cli. Discord
invites stay untagged.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(cli): remove OpenRouter as a vision provider for capture
* refactor(cli): tidy comment and formatting after OpenRouter removal
* refactor(cli): shorten the thinking-budget comment
* chore(skills): refresh the skills manifest for the film reference
* fix(cli): check stops after 2 minutes of video copies and says how to finish
* fix(cli): check copies only the stretch of a video the composition plays
* docs(cli): check copies only the played stretch of a long video
* docs(cli): shorten two comments on the copy window
* fix(cli): finding crops and frames get the same copy windows as the check
* fix(cli): drop a comment the ratchet counts
* refactor(studio-server): keep runFfmpeg under the complexity gate