mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-18 16:08:56 +00:00
04202e8a4c2e7f334636bf1e3b07dd38c77e5b43
541
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
04202e8a4c |
fix(cli): uploads leave out outside scripts; .ts counts as video only when it is one (#7818)
* fix(cli): uploads leave out outside scripts; .ts counts as video only when it is one * chore(studio-server): raise unpacked size budget for the upload file-type rule * fix(studio-server): transport stream check never waits on a pipe and needs binary bytes |
||
|
|
ac02474105 |
fix(cli): play and present check the Host like preview; local render leaves out outside files for a received composition (#7792)
* fix(cli): a subfolder of an imported project keeps its received-files record Publish, cloud render and feedback now read the received-files record at the nearest folder at or above the one they stage, so staging a subfolder of an imported project still leaves out the outside files its received files reference. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): a received file counts under any spelling of the same file on disk The received-files lookup now also matches a project file that is the same file on disk as a listed path, so a name respelled in letter case on a case-insensitive disk keeps its received status. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): cloud render prepares only the GIFs staging kept The entry GIF prep before a cloud render upload now reads only the staged copies it is handed. An image whose source staging left out keeps its reference as written and is never read from disk. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli,studio-server): never hand a playlist named as media to ffmpeg A media file whose first bytes are an HLS playlist, an XML manifest or a concat script now stays out of ffprobe and ffmpeg: cloud render leaves it in the zip as authored, the media probe reports it as not media, and the proxy copy refuses it. Real media never starts with these bytes, so it probes and transcodes as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(studio-server): catch playlists with control bytes, and keep them from stills and audio probes A text playlist or concat script is detected whatever bytes follow its first line; only markup must be all text. A still frame and the audio probe behind waveforms, peaks and loudness now refuse a file the probe reads as not media, as the proxy copy already does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): a parent folder's state the CLI cannot read never marks a project received The walk up for a received-files record now skips a parent whose record cannot be reached. Only a record file that is there but cannot be read or parsed counts every file as received. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): a drive that reports no file ids matches no received file by identity Some network and virtual drives report a file id of 0 for every file, so the same-file match now gives such a file no identity instead of matching it to every listed file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * refactor(studio-server): read a media file's first bytes with a read stream The playlist check reads the first 64 bytes through a bounded read stream instead of a raw file descriptor, and the audio-track probe's doc comment sits on its function again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(studio-server): raise the packed size budget for the media playlist check Main packs @hyperframes/studio-server close to the 1% tolerance on the 168500 budget, and the playlist check adds about 320 bytes, which put the Build over. Set the budget to 172000. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli,studio-server): open media only through self-contained media demuxers Every ffprobe and ffmpeg input that cloud render offload, the publish proxy bake and Studio's media helpers open now carries a demuxer whitelist built from the supported media extensions: MP4/MOV/M4A/AVIF, Matroska/WebM, MXF, AVI, MPEG-PS/TS, FLV, ASF, Ogg, WAV, MP3, AAC, FLAC, AIFF and the still-image formats. Playlist, manifest and concat demuxers can no longer open, whatever a file's bytes say. The proxy's own concat step is left as it is. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli,studio-server): keep media probe argv flat, and expect the demuxer list in loudness args Two probe argv literals built from nested spreads are flat again, so "--" stays the visible second-to-last entry the argv contract checks. The normalize-audio test expects the demuxer list before the input. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): play and present answer only local host names and allowed hosts play and present listen on every interface. Each request now passes the same Host check preview uses: localhost, loopback addresses and this machine's own addresses and names are answered, and any other host name gets a 403 naming HYPERFRAMES_PREVIEW_ALLOWED_HOSTS until it is listed there. Phones and other machines on the network still open them by LAN address or .local name. * fix(cli): a local render of a received composition leaves out files outside the project When the composition a local render opens is listed in the project's received-files record, hyperframes render (full and range) no longer brings in files outside the project. It prints one line naming the references it leaves out and why. An unreadable record counts as received. A project whose entry is the person's own, or that has no record, renders exactly as before. * fix(cli): received-render scan reads safely and treats an unreadable record as unknown The scan behind the received-composition notice skips a file it cannot read, finds url() references with a linear forward scan, and reads at most 2 MB of each file. An unreadable received-files record no longer counts as everything received for local render: the render keeps outside files and names the record it could not read. Publish and cloud upload still treat it as received. The notice now says the render stops on a sub-composition outside the project rather than leaving it out. * fix(cli): the studio render of a received composition leaves out files outside the project The Studio render route applies the same rule as hyperframes render: when the composition it renders is listed in the received-files record, the job does not bring in files outside the project, and the server log names the references it refuses. * chore(cli): name the unreadable received-files record helper without a comment * fix(cli): local render refuses outside files when any composition it plays was received The received-file rule for local render (CLI and Studio) now checks every page and stylesheet the render pulls in, not only the entry, so an own index.html that plays a received scene also reads nothing outside the project, and the notice names the received file. An unreadable, truncated or empty received-files record refuses outside files too, as publish and cloud upload do, and the notice names the record it could not read. * fix(cli): decide a received render from the files the compiler reads Local render (CLI and Studio) now leaves outside-file handling as it is for a project with no received-files record or an empty one, without scanning anything. When the record lists files, the compiler's own read list for the composition decides: the bundler runs out of process with a deadline and reports every project file it reads, so stylesheet imports and files past any scan limit count. A received file in that list, a build that fails or runs past its deadline, or an unreadable record refuses outside files. The scan that names refused references in the notice is advisory only: it guards every file system call, tracks visited files by real path, and caps the files and bytes it reads. * fix(cli,producer): decide a received render with the render compiler's own composition traversal The producer exports renderCompositionFiles, which walks data-composition-src with the same resolution, normalization and private file rules the render's sub-composition pass uses; that pass now calls the same helper. The received-render decision adds those files to the bundler's read list, so leading-slash and percent-encoded references the render reads count. The advisory scan resolves compositions the same way and reads template contents. * fix(cli): refuse outside files in a local render whenever the project has received files A local render (CLI and Studio) reads nothing outside the project when the project's received-files record lists any file, or cannot be read. No static list matches what a render consumes: the page loads its stylesheets and scripts through the browser at capture time, and scripts can load more, so the decision no longer depends on one. The reference scan stays only to name what the notice says is left out. This drops the out-of-process bundler read list and the producer composition walk added for that decision. * fix(cli): refuse outside files only when a received file can load other files A local render (CLI and Studio) reads nothing outside the project when the received-files record cannot be read, or lists a received file that can reference others: an .html, .htm, .css, .js, .mjs, .cjs or .svg name, or content that reads as HTML, SVG or CSS. A project that only received images, video, audio or fonts keeps bringing in outside files as before. * fix(cli): keep outside files only when every received file is positively media, a font or an image A local render keeps bringing in outside files only when each file the received-files record lists has a known media, font or image extension and starts with that type's signature bytes. Any other received file, a listed file that is missing or unreadable, or a mismatch between name and content refuses outside files. An ancestor record's entries now match a subfolder whose name is spelled in another Unicode form; the entry keeps its own spelling on disk. * fix(producer,core): a sub-composition must be an .html file The render compiler and the runtime load a data-composition-src only when it names an .html or .htm file. Any other file, such as an image or video, is refused as a page: render stops naming it, and the runtime reports the load failure without fetching it. * fix(producer,cli): the render and static file servers forbid type sniffing Both servers send X-Content-Type-Options: nosniff with every response, so the browser loads a file only as the type its extension names: an image or video cannot run as a script or apply as a stylesheet. .cjs is served as JavaScript. * test(cli): a received media file in a composition slot is refused as a page * test(cli): an empty nested received-files record cannot hide an outer record's received page * fix(cli): a received media file reached under another name refuses outside files The received-render decision now compares file identities, not names. It walks the project once, bounded by entry count and time, and refuses outside files when a hardlink or a symlink with a name that is not media reaches a received file, or when the walk cannot finish. A received file with no identity matches nothing, as in the received files check. * fix(cli): compare received files by link target and keep outside files for an empty record A received media file and every other project name are now compared by the identity of the file they reach with links followed. A linked folder that leads outside the project, or a file whose identity cannot be read, counts as unchecked and refuses outside files. An empty received-files record keeps outside files without walking the project. * chore: raise the producer unpacked size budget for the composition file checks --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
6a7b4df7c8 |
fix(cli): add lists files from a received config's registry as received (#7820)
* fix(cli): add lists files from a received config's registry as received When a project's hyperframes.json is listed in .hyperframes/received-files.json and names a registry other than the public one, add now lists every file it is about to write in that record before writing any of them. This covers every caller of addToProject: add by name, by tag, several names, and Studio. The decision reads the config the install uses, so a byte-order mark or another spelling of the file on disk is handled the same way. A person's own config, the public registry and a record that cannot be read are left as they are. * fix(cli): list received files as they are written, under a shared lock add now lists each file in the received-files record just before it writes it, using the write-time decision, so a file kept because the person edited it during the download is never listed. When an install fails, it takes back the entries it listed but never wrote. Changes to the record take .hyperframes/received-files.json.lock, created exclusively. A writer retries for about 2 s, takes over a lock older than about 10 s, and always releases it. A writer that cannot take the lock in time fails with a clear error instead of writing past it. * fix(cli): an unreadable config counts as received; a failed install keeps what is on disk add now counts an install as received when hyperframes.json exists but cannot be read or parsed, since that config is not proven to be the person's own. When an install fails, it takes back only the entries it listed whose files are not on disk; files that landed stay listed. * fix(cli): the received-files lock resolves the project folder as the installer does The record's lock and write resolved the project folder with fs.realpathSync, while the containment check resolves targets with the native realpath. The two can spell the same folder differently: a Windows short name or a folder typed in another letter case. The target then looked outside the project and the change was refused. The record now resolves the folder with the installer's realProjectRoot, so the root and target compare in one spelling. The failed-install tests now fail the write by stubbing it, which works on every platform, instead of a read-only folder, which Windows ignores. |
||
|
|
c4d60c347f |
fix: Studio media routes refuse cross-site load, CLI escapes terminal text, batch outputs stay in their folder (#7779)
* fix(cli): batch render outputs stay inside the --output folder A row value may still name a subfolder of the folder written before the template's first placeholder, but a value that resolves outside it stops the batch before any folder is made or file is written. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): project text shows control characters as visible escapes compositions, lint, snapshot and info --media print composition ids, sources, element ids, lint messages and media paths through one helper that writes C0, DEL and C1 control characters out as \xNN, so they reach the terminal as text. The CLI's own colors are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(studio-server): waveform and peaks key one cache entry per file and refuse other sites Both caches are keyed on the resolved project-relative path, so another spelling of the same file (a doubled or trailing slash) reads the cached peaks instead of decoding again. Waveform and peaks requests that another site makes are refused the way thumbnail requests already are; the Studio page asks for both as itself. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(studio-server): preview stills run at most four at a time A video's stand-in still is made through a small job queue: four at once, 32 more waiting, and a 503 with Retry-After beyond that. A waiting request whose client goes away leaves the queue without starting ffmpeg. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): batch output folder check keeps backslash names and row-named paths A trailing backslash counts as a separator only where it is one, and the check compares path segments. A template that starts with a placeholder names no folder, so each row's value is the whole output path as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): lint header shows control characters in file names as escapes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(studio-server): a finished or in-progress still never waits for a still slot Only a still that is neither on disk nor already being made takes one of the four slots, through a hook resolveStill gives the route. Waiters queue without a cap and nothing answers 503, since a poster is never asked for again. A waiter whose client leaves still never starts ffmpeg; a request that shared that waiter's still tries again on its own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore: raise the studio-server packed budget to 172000 main already packs about 170 KB against a 168500 budget; the request guards, still slots and cache-key change here add about 550 bytes. * fix(core,studio-server): a preview served to another site offers no editing port When the Studio server answers a preview document to another site's request, it now marks the document, and the runtime's editing agent ignores every connect in a marked document. The Studio's own frames, which load the preview from the same origin, keep the editing port. The marked copy carries no ETag, so it is never revalidated in place of the unmarked one. * fix(studio-server): a media still stops when no request waits on it Each still job now counts the requests waiting on it. A request whose connection closes leaves the job, and when the last one leaves, the job's ffmpeg is killed and the job is forgotten, so the next request starts afresh. A caller that passes no signal keeps the job running, and a request that has already closed starts nothing. * test(studio-server): group the still cancellation tests after the real-ffmpeg still test * fix(studio-server): a preview framed by another site is never revalidated A frame load of a preview from another site now drops If-None-Match and If-Modified-Since before the route answers, so it always gets a fresh, marked document instead of a 304 that could reuse the unmarked copy a browser cached for the Studio's own page on the same site. Subresource loads keep their validators. * fix(cli): check findings and keyframes headers show control characters as escapes check prints each finding's message, source file, selector and fix hint, and keyframes prints each composition's name and source, through terminalText. * test(studio-server): a request sharing an abandoned still waiter gets its still * chore(studio-server): raise the unpacked size budget for the still job slots and cross-site guards * fix(cli): layout and contrast lines in check show control characters as escapes --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
a75e61f31c |
fix(cli): discover mounted scenes inside templates (#7822)
* fix(cli): discover mounted scenes inside templates * test(cli): cover recursive template scene discovery * test(cli): cover media edits in nested template scenes * test(cli): cover nested audio edits and duplicate targets * docs(cli): explain nested scene discovery and ambiguity |
||
|
|
ded5e3eec2 |
perf: CSS url, @import, @font-face, style and comment scans run in linear time (#7809)
* perf(parsers): find CSS url() references in linear time
A new css-url-scans entry finds what each CSS url( regex in the compile path
and the runtime finds, match for match and group for group, with forward
scans. The regexes restart from every unclosed url(, @import or background:
and read to the end of the text each time, so their time grows with the
square or cube of the input. The scans read each character a bounded number
of times.
rewriteCssAssetUrls uses the scan in place of CSS_URL_RE, which stays
exported for existing callers. A fuzz test checks 20,000 generated pages
against the regexes, and timed tests cover 1 MB of each unclosed form.
The parsers packed-size budget rises to cover the new entry.
* perf(core): bundler, SVG id namespacing and runtime find CSS urls in linear time
The bundler's url() inlining, CSS-file rebasing and @import inlining and
hoisting, the SVG url(#id) rewrite, the runtime's sub-composition url()
rewrite and the scene swap's url and @import list now use the
@hyperframes/parsers css-url-scans entry. Each returns the same matches as
the regex it replaces, in time linear in the CSS length.
* perf(producer): compile finds CSS urls, imports and backgrounds in linear time
Asset collection, head-style @import coalescing, the ancestor
background-image check, remote background and font-face url localization and
local font embedding now use the @hyperframes/parsers css-url-scans entry,
which returns the same matches as the regexes it replaces. A timed test
covers remote background discovery on 200 KB of unclosed background urls.
* perf(parsers): scan style blocks, font-face blocks, comments and mask urls in linear time
css-url-scans gains forward scans for `<style>` blocks, `@font-face { }`
blocks, `/* */` comments, the quoted-or-bare `url()` form and the
`mask-image: … url()` declaration. Each returns the same matches and groups
as the regex in its doc comment. The fuzz test now checks all fifteen scans
on 20,000 generated pages, and the timed tests cover 1 MB of each unclosed
form.
* perf(core): strip and restore stylesheet comments in linear time
Bundling a stylesheet finds its comments with the parsers comment scan and
puts them back in one pass over the placeholders. A comment comes back
verbatim, including text such as `$'` that a string replacement pattern
would expand.
* perf(producer): find style and font-face blocks in linear time
Remote font discovery and local font embedding read `<style>` blocks and
`@font-face` rules with the parsers scans, which return the same blocks as
the regexes they replace.
* perf(lint): read stylesheet and mask-image urls in linear time
The missing stylesheet asset and texture mask rules find `url()` values with
the parsers scans, including the mask-image fallback for a stylesheet that
does not parse.
* perf(cli): rewrite published CSS urls in linear time
Publishing rewrites stylesheet `url()` references with the parsers scan in
place of CSS_URL_RE, with the same matches.
* chore: size budgets cover the CSS scans in parsers and inspector
verify:packed-manifests measures parsers at 894,913 unpacked bytes and
inspector at 3,764,456, both just over 1% above their budgets once the
linear CSS scans are bundled. The budgets rise to 900,000 and 3,790,000.
* perf(parsers): scan stylesheet links and CSS rules in linear time
css-url-scans gains forward scans for `<link … rel="stylesheet" …>` tags and
`selector { declarations }` rules that return the same matches and groups as
the regexes in their doc comments. Both join the 20,000-page fuzz test and
the 1 MB timed tests.
* perf(core): restore stylesheet imports and list scene font faces in linear time
Bundling a stylesheet puts its comment and @import placeholders back in one
pass, so an imported sheet comes back verbatim and is not searched again.
fontFaceBlocks lists @font-face rules with the parsers scan. A fuzz test
checks the one-pass restore against the sequential one on 20,000 sheets.
* perf(producer): find stylesheet links, CSS rules and font-face blocks in linear time
Font stylesheet inlining and project font discovery find stylesheet links,
and the ancestor background check finds CSS rules, with the parsers scans.
extractFontFaceBlocks matches every brace in one pass instead of counting
depth again from each @font-face; a fuzz test checks it against the depth
count on 20,000 sheets.
* test(core): time the CSS placeholder restore directly
The bundle test with 6,000 imports was timed mostly on 6,000 file reads,
which took 2.7 s on the Windows runner. The restore is now timed on its own
over 20,000 placeholders, and a short bundle test still checks that every
import of a sheet is inlined.
|
||
|
|
a07d4cf738 |
fix(cli): printed Windows commands read folder names literally in every shell (#7769)
* fix(cli): printed Windows commands read folder names literally in PowerShell, cmd and Git Bash shellArg's Windows branch wrapped any non-plain name in double quotes, where PowerShell and Git Bash still expand $ and backticks. Names with those characters (or PowerShell's curly quotes) are now single-quoted, which both shells read literally; a name that cmd.exe would also split on & | < > ^ gets no printed path, and the hint says to run the command from the project folder. A bare comma or leading @ is quoted so PowerShell does not read an array or a splat. Ordinary names with spaces, accents and apostrophes print as before. The background preview's stop footer uses the same helper instead of JSON quoting, which left $(...) live in POSIX shells and PowerShell. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): printed Windows paths with backslashes keep them in Git Bash A Windows word containing a backslash printed bare, and Git Bash strips unquoted backslashes, so C:\Users\Bob\film reached the CLI as C:UsersBobfilm. Such words now take double quotes, which PowerShell, cmd.exe and Git Bash all read as written; trailing backslashes are doubled so they do not escape the closing quote. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): open --json gives a null stopCommand when the folder has no safe spelling When no spelling of the project folder is safe to paste in every Windows shell, the left-running preview's stopCommand held prose. It is now null, and stopCommandFromProject names the command to run from inside the project folder. The printed line is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(cli): drop a comment the nullable return type already states Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): a Windows name with no spelling common to every shell prints no path PowerShell single quotes do not group a word in cmd.exe, and Git Bash reads 'it''s' as its, so the single-quoted form printed for names with $, a backtick or a curly double quote was wrong in two of the three shells. Those names now take the existing null fallback, and the hint says to run the command from the project folder. Round-trip tests check that every printed Windows word reaches the program unchanged: through Git Bash everywhere, and through cmd.exe and PowerShell on Windows, where the CLI's Windows CI job now runs them. The names cover apostrophes, typographic quotes, mixed quotes, cmd operators and trailing backslashes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(cli): run the cmd.exe round-trip through spawnSync execFileSync's options type has no windowsVerbatimArguments, so the Windows-only cmd.exe test failed typecheck. spawnSync takes the option, and the test now also checks the exit status. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(cli): expect the quoted Windows path in the relative open command On Windows a relative path holds a backslash, which shellArg now prints in double quotes so Git Bash keeps it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): a Windows name with %NAME% or ! prints no path cmd.exe expands %NAME% inside double quotes, and interactive Git Bash history-expands ! there, so neither name reads literally in every Windows shell. Both now take the null fallback. A lone % such as 100% still prints. --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
80b09cc94a |
fix(cli): nested received records only add; a received .env never picks the account; font names stay out of agent files (#7808)
* fix(cli): a file is received when any record at or above the staged folder lists it A received-files record inside a staged subfolder could list nothing and hide the project's own record, so outside references from received files were copied into the upload again. Every record from the staged folder up is now read: a nested record can add received files but never remove them. * fix(cli): a HeyGen key from a project .env never replaces a saved credential A HEYGEN_API_KEY or HYPERFRAMES_API_KEY that only the folder's .env set now ranks after the person's stored login and saved API key, in the CLI resolver (cloud render, publish, media helpers) and in the media-use skill scripts. With no saved credential the project key still works, and the first use prints one line naming the variable and the .env it came from. A key exported in the shell keeps its current precedence. * fix(cli): capture's agent files count the page's fonts instead of naming them Font family names come from the captured page, and a short phrase passed the plain-name check into AGENTS.md, CLAUDE.md and .cursorrules. The Brand Summary now gives the number of font families and points to extracted/tokens.json, which already holds the names as data. * fix(cli): only a received project .env key gives way to a saved credential A HeyGen key from a project .env now comes after the stored login and saved API key only when that .env came in with a received project: a received-files record at or above the folder lists it, or a record there cannot be read. A person's own .env keeps its priority. The media-use skill scripts read the same records and apply the same rule. * fix(cli): a shell key wins over a received .env key under either name * docs(cli): a received project's .env key comes after the saved login and key * fix(cli): drop the duplicate font count from capture's agent files The Brand Summary repeated the font count the file table already gives, and counted entries that are not font names. The table row stays. * fix(cli): name the received-files record in the skill comment without a path |
||
|
|
477a3aea13 |
fix(cli): upload archives always leave out env files and private records (#7796)
publish, cloud render and feedback --file-issue build their archive from a walk of the project folder that only consulted .hyperframesignore, so a rule re-including dotfiles also uploaded .env files. The walk now leaves out env files, Git data and Studio's private records whatever the ignore rules say, and reports each one as left out with the reason "private". Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
83eae240fb |
fix(cli): start helper programs only from trusted PATH folders on every platform (#7787)
* fix(cli): start helper programs only from trusted PATH folders on every platform At startup the CLI and its worker entry points rewrite their own PATH to absolute folders outside the working directory, on every platform, so a program planted in the project (a relative or empty PATH entry, node_modules/.bin, or any folder inside the cwd) is never run by name. Child processes inherit the trimmed PATH. media-use reuses the same helper instead of its private copy. doctor resolves docker with findTrustedExecutable and runs it by absolute path with execFileSync, no shell. A docker found only in the project's node_modules/.bin is reported as not found, with a hint that it was skipped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): keep stale-install detection and Windows system folders after PATH trim The stale hyperframes check for reverse start reads the PATH the process started with, so an older copy in the project's node_modules/.bin is still reported. It only reads the filesystem and never runs that copy. On Windows the trim now keeps %SystemRoot%, System32, System32\Wbem and the WindowsPowerShell folder even when the CLI starts inside them, so an elevated prompt in C:\Windows\System32 can still run cmd, taskkill, tasklist, powershell and tar. PATH entries wrapped in double quotes are unquoted before the check instead of being dropped. PATH order is kept. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): resolve the empty-PATH placeholder only when it is needed Computing it at import threw in test environments where import.meta.url is not a file URL. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
870b1fa4dc |
fix(cli,studio-server): received-file guard covers subfolders and spellings; playlists named as media never reach ffmpeg (#7771)
* fix(cli): a subfolder of an imported project keeps its received-files record Publish, cloud render and feedback now read the received-files record at the nearest folder at or above the one they stage, so staging a subfolder of an imported project still leaves out the outside files its received files reference. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): a received file counts under any spelling of the same file on disk The received-files lookup now also matches a project file that is the same file on disk as a listed path, so a name respelled in letter case on a case-insensitive disk keeps its received status. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): cloud render prepares only the GIFs staging kept The entry GIF prep before a cloud render upload now reads only the staged copies it is handed. An image whose source staging left out keeps its reference as written and is never read from disk. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli,studio-server): never hand a playlist named as media to ffmpeg A media file whose first bytes are an HLS playlist, an XML manifest or a concat script now stays out of ffprobe and ffmpeg: cloud render leaves it in the zip as authored, the media probe reports it as not media, and the proxy copy refuses it. Real media never starts with these bytes, so it probes and transcodes as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(studio-server): catch playlists with control bytes, and keep them from stills and audio probes A text playlist or concat script is detected whatever bytes follow its first line; only markup must be all text. A still frame and the audio probe behind waveforms, peaks and loudness now refuse a file the probe reads as not media, as the proxy copy already does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): a parent folder's state the CLI cannot read never marks a project received The walk up for a received-files record now skips a parent whose record cannot be reached. Only a record file that is there but cannot be read or parsed counts every file as received. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): a drive that reports no file ids matches no received file by identity Some network and virtual drives report a file id of 0 for every file, so the same-file match now gives such a file no identity instead of matching it to every listed file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * refactor(studio-server): read a media file's first bytes with a read stream The playlist check reads the first 64 bytes through a bounded read stream instead of a raw file descriptor, and the audio-track probe's doc comment sits on its function again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(studio-server): raise the packed size budget for the media playlist check Main packs @hyperframes/studio-server close to the 1% tolerance on the 168500 budget, and the playlist check adds about 320 bytes, which put the Build over. Set the budget to 172000. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli,studio-server): open media only through self-contained media demuxers Every ffprobe and ffmpeg input that cloud render offload, the publish proxy bake and Studio's media helpers open now carries a demuxer whitelist built from the supported media extensions: MP4/MOV/M4A/AVIF, Matroska/WebM, MXF, AVI, MPEG-PS/TS, FLV, ASF, Ogg, WAV, MP3, AAC, FLAC, AIFF and the still-image formats. Playlist, manifest and concat demuxers can no longer open, whatever a file's bytes say. The proxy's own concat step is left as it is. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli,studio-server): keep media probe argv flat, and expect the demuxer list in loudness args Two probe argv literals built from nested spreads are flat again, so "--" stays the visible second-to-last entry the argv contract checks. The normalize-audio test expects the demuxer list before the input. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
603395c89a |
fix: render file servers refuse env and Git files; shown-box sampling stays within the render (#7765)
* fix(producer): shown-box sampling stays within the validated render duration Sampling where each oversized video is drawn stepped through the authored start and end in 0.25 s float steps with no bound, before the render duration was checked. An enormous start never advanced the step, and an unbounded end grew the sample set until memory ran out. The render duration is now validated first, each window is cut at the composition's end, a window that is not finite is skipped, and the loop counts integer steps. Building the sample list happens inside the measurement's try, so any failure falls back to full-size extraction. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix: render and capture file servers refuse env files and Git data The producer render file server, the engine file server and the CLI static project server served every regular file under the project to the page, including `.env*` files and anything under `.git`. Compile already refuses to inline those files, and Studio preview and play refuse to serve them. All three now answer 404 for them through the shared isVcsOrSecretPath rule, checked on the requested name and on a link's target, with the case and Windows spelling variants it already covers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
cb52dcf646 |
fix(cli): an unknown flag's error leaves out hidden rename shims (#7746)
* fix(cli): an unknown flag's list leaves out hidden rename shims The list pointed agents at init's --template, --video-legacy and --agent, which only print an error. It now shows the flags --help shows. * fix(cli): an unknown flag never suggests a hidden rename shim The did-you-mean search still used every spelling, so '--templat' on init was pointed at the hidden --template. It now uses the same visible flags the list shows. |
||
|
|
d26ec25385 |
fix(cli): check still reports a film's other GL driver notes (#7745)
The filter for check's own readback stalls matched every GL driver Performance note. It now matches only the ReadPixels stall. |
||
|
|
88beb282f2 |
fix(cli): an unknown flag lists the command's real flags (#7740)
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. |
||
|
|
35d145157b |
fix(cli): check no longer reports GPU stalls from its own pixel reads as the film's warnings (#7736)
check copies each canvas into a 2D context to see whether it moved. On WebGL that readback makes Chrome log a GL driver Performance note, which check then listed as a console warning from the composition. |
||
|
|
c31e7dd08c |
fix(cli): check times a line held across a split clip as one hold (#7733)
* fix(cli): check times a line held across a split clip as one hold A clip split in two hands its line to a second element at the same place. line_unread timed each element alone, so the first half warned while the same text stayed on screen. * refactor(cli): name the split-clip line hand-off instead of commenting it |
||
|
|
213f7c5383 |
fix(cli): quote the project name in init's printed cd commands (#7608)
`hyperframes init --non-interactive` closes with `cd <name> && npm run …` lines for the person or agent to paste. The name went in as typed, so a name with a space or a quote printed a command that fails as written: `cd my first video` (bash: "cd: my: No such file or directory", zsh: "too many arguments") and `cd it's mine` (an unterminated quote). A new `shellArg` quotes a word only when a shell would split or expand it: double quotes, or single quotes when the text holds `$`, a backtick, `\`, `"` or `!`; on Windows, double quotes, with `\` paths left bare. `hyperframes open` / `preview --stop` hints (desktopApp's `shownDir`) already quoted whitespace with JSON.stringify and now use it too, so a name like `it's` or `a&b` is covered there as well. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
45882027bd |
feat(cli): check warns when text leaves the 9:16 social safe areas (#7680)
* feat(cli): check warns when text leaves the 9:16 social safe areas * feat(core): safe areas owned by core; check adds --safe-zone standard * style(cli): format * refactor(core): name the safe-area band fields * fix(cli): defects outrank safe-zone warnings at the issue cap * style(cli): format * test: read the safe-box constants from core |
||
|
|
f01209d4ae |
fix(deps): bump tar, hono, @hono/node-server, adm-zip, sharp and postcss-selector-parser (#7656)
Raise the direct ranges so the workspace and published packages resolve patched releases: tar 7.5.22, hono 4.13.16, @hono/node-server 2.1.6, adm-zip 0.6.1, sharp 0.35.5 and postcss-selector-parser 7.1.7. The CLI's on-demand sharp install moves to 0.35.5 with them. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
2c2b399bfa |
fix(producer): local renders bring in only media, font, CSS and JS from outside the project (#7647)
* fix(producer): local renders bring in only media, font, CSS and JS from outside the project Local renders (`render`, range render, `benchmark`, the Studio server and the Vite Studio adapter) run with allowOutsideProjectAssets, which copied every existing file that markup named outside the project into compiled/hf-ext, of any type and from any folder, and served project links that lead outside without looking at where they lead. Publish already applies a policy here: outside references are kept, private locations are left out, and only image, video, audio, font, CSS and JS files are copied. Local renders now follow the same policy. The publish predicates (private location, copied file type, left-out wording) move from the CLI to a new `@hyperframes/studio-server/outside-file` subpath, since the producer cannot import the CLI and already depends on studio-server. The CLI re-exports them, so publish behaves as before. The media extension sets move with them because the copied-type list includes them. The producer decides with one predicate, `outsideAssetRefusal` in utils/paths.ts, and applies it wherever allowOutsideProjectAssets lets an outside file in, so no entry point can skip it: - collectExternalAssets: src/href/url() references, which covers <a href> and <link href> - dropMediaOutsideProject: video/audio/image sources in any spelling the media resolver accepts (file: URLs, percent-encoding), so nothing probes or extracts them - the render file server: project links that lead outside - the distributed plan's project copy: the same links (range render) - GIF/HEIC prep and sub-composition links: private locations only, since those inputs are converted or compiled rather than copied as they are Each left-out file logs the publish wording with "left out of the render". To reproduce on main: a project whose index.html references ../../.ssh/id_key through <link href>, <a href> and url(), with a project link to a file in .ssh, rendered locally, gets those files copied into compiled/hf-ext and served. Comment lines: the four in studio-server's outsideFile.ts moved verbatim from the CLI files they replace. Two are new, in utils/paths.ts. The one on outsideAssetRefusal states the policy once, so its six call sites carry no comment. The one on refusesOutsideLink says its boolean means "refused, and already warned", which the name alone does not say. Comment ratchet is clean. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): keep outsideFileType as a re-export of the shared module The base repository's deletion guard rejects removing a file that exists on main unless git pairs it as a rename. outsideFileType.ts moved into studio-server/outside-file with enough added around it that git no longer pairs the two, so CI's "Reject accidental file deletions" step failed. The file stays as a two-name re-export and publish keeps importing from it, so publishProject.ts and its file-type test are back to main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(producer): raise the unpacked size budgets for the outside-file policy CI's packed-manifest check measured @hyperframes/producer at 3,244,665 bytes unpacked (budget 3,210,000) and @hyperframes/studio-server at 653,506 (budget 646,000), both just past the 1% tolerance. Both packages were already at the edge on main. Measured locally with npm pack --dry-run, main is 3,237,162 for producer and 652,502 for studio-server, so studio-server on main is already at its ceiling. This branch adds about 7.9 KB unpacked to producer, because the new checks sit in the compiler, render stages and file server, which each producer entry bundles. It adds about 5.5 KB to studio-server for the new outside-file entry and its declarations. No source maps, tests or assets were added to either tarball. The budgets go to 3,245,000 and 654,000, just above CI's measurements, the same way #7579 raised producer's budget for the project-folder checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(producer): apply the outside-file policy to embedded local fonts A project font file that links outside the project is now left out of font embedding with the same warning the file server gives, instead of being inlined into the compiled HTML. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
89a7aa3004 |
fix(cli): copy only media, font, CSS and JS files from outside the project (#7636)
* 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> |
||
|
|
2591abfbf0 |
feat(cli): cloud render --json lists the files an upload leaves out (#7631)
* 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>
|
||
|
|
a810a8b002 |
fix(cli): publish leaves out outside files that came in with an imported project (#7598)
* 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> |
||
|
|
97df93fb07 |
fix(cli): check hears a WAV whose header misstates its byte rate, as render plays it (#7618)
* 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 |
||
|
|
83b34cbe49 | fix(cli): 'hyperframes registry search' runs catalog (#7610) | ||
|
|
f7bf5f0c42 |
fix(cli): publish keeps Library files out for projects on cloud drives (#7582)
* 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> |
||
|
|
b4bd8b0739 |
fix(cli): publish leaves out private files outside the project and says so (#7577)
* 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> |
||
|
|
84799bdc59 |
fix: take helper programs only from install locations, never the project folder (#7524)
* 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> |
||
|
|
04947d99f7 |
feat(cli): share rendered videos through unified reviews (#7135)
* 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 |
||
|
|
5a88c9938e |
fix(parsers,lint,producer,cli): confine composition path lookups to the project (#7534)
* 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> |
||
|
|
2b86c49dc2 |
test(cli): give each test file its own home so renders never wait on another file's lock (#7526)
* 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 |
||
|
|
1a9fb8acb6 |
feat: opt-in 4:4:4 chroma for SDR MP4 masters (#5820)
* 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> |
||
|
|
84c7d02a19 |
fix(cli): keep project folders from choosing the programs and config the CLI runs (#7511)
* 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> |
||
|
|
c96ff540c4 |
fix(cli): harden lambda destroy, snapshot media, upgrade and project file serving (#7509)
* 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> |
||
|
|
b28bd2b348 |
fix(cli): only name a shadowing install whose manager can move it (#7499)
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. |
||
|
|
007664e25a |
fix(reverse): give agents the sign-in reason to say, and catch stale CLIs that know reverse (#7488)
* 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. |
||
|
|
c149730819 |
fix(cli): no macOS developer-tools prompt from git, xcrun or cc checks on a Mac without the tools (#7257)
* 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 |
||
|
|
3a24da8a8e |
fix(cli): spaced-path hint takes the longest path and reads --flag=value; telemetry docs name the reverse session id (#7452)
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. |
||
|
|
448f88ff3a |
feat(cli): reverse and templates report their own runs; commands say which skills are installed (#7444)
* 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. |
||
|
|
eb0a52c298 |
fix(cli): measure answers the four mistakes agents make most (#7443)
* 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 |
||
|
|
ad6f7858f6 |
feat(skills): reverse-any-video and style-sampling install with the core set (#7445)
* 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 |
||
|
|
7bf65995b3 |
feat(cli): add agent markers other detectors use, verified upstream (#7425)
* 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> |
||
|
|
c14f258907 |
feat(cli): detect more agent runtimes in telemetry (#7423)
* 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> |
||
|
|
91ad7fb6ee |
fix(cli): cloud render finds media whose file name is stored in another Unicode form than the page's (#7419)
* 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 |
||
|
|
070b964d7b |
feat(cli): check replays an unchanged project's last pass and takes --no-craft (#7398)
* 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 |
||
|
|
e0c11bf09a |
fix(cli): a media file referenced by its filesystem path goes into the cloud archive (#7381)
* 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 |
||
|
|
7b79ab4290 |
fix(check): lint and check skip compositions the project never mounts (#7369)
* 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 |
||
|
|
896a77c307 |
fix(cli): open stops the project's background preview first (#7297)
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> |
||
|
|
e827de256f |
fix(check): a Chrome that never becomes ready ends the check with a named error (#7360)
* 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 |