Commit Graph
282 Commits
Author SHA1 Message Date
Miguel Ángel ae5829db7e fix(studio-server): a sealed preview's wait for a video's proxy copy passes its preflight (#7856) 2026-11-15 19:50:59 +00:00
Michael WangandClaude Opus 5.5 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>
2026-11-15 06:35:32 +00:00
James RussoandClaude Opus 5.5 9320c44e13 fix: docs image upload publishes only regular files, and CI rejects new symlinks (#7776)
scripts/upload-docs-images.sh synced docs/images/ with the AWS CLI's default
of following symbolic links, so a link committed under docs/images/ would
publish whatever it pointed to on the machine running the upload. The script
now stops before any AWS call when docs/images is not a real folder in the
checkout or when anything under it is a link or not a regular file, and the
sync passes --no-follow-symlinks as well.

A new check, scripts/check-symlinks.mjs, fails CI when a tracked symbolic
link is not one of the two the repo already means to have.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 00:47:08 +00:00
Ular Kimsanov 0f6ed7d57b ci: publish the hosted HyperFrames MCP to the official MCP registry (#7676) 2026-11-13 23:05:34 +00:00
Miguel Ángel 0bce3315e6 fix(studio): a file held open or read-only answers 423 or 403 with a reason, not 404 or 500 (#7649)
* fix(studio): a file held open or read-only answers 423 or 403 with a reason, not 404 or 500

* fix(studio): valid workflow name for the Windows held-file test

* test(studio): release the held file before the held-file test removes its folder

* fix(studio): the code editor's save toast names a held or read-only file
2026-11-13 16:10:01 +00:00
James RussoandClaude Opus 5.5 d30f1f4ce4 ci: give Test (runtime) 15 minutes (#7627)
Core plus engine tests now take 8-10 minutes, so the 10 minute limit
cancels runs that are about to pass and dequeues their PRs from the
merge queue as failed checks. Match Test (studio)'s 15 minute limit.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 23:22:53 +00:00
WaterrrForeverandClaude Opus 5.5 33304cff04 refactor(skills): move the Python encoding guard out of the skills root (#7606)
skills/python-encoding.test.mjs was the only loose file in skills/, whose
top level otherwise holds one directory per skill. It checks every skill's
Python scripts, so it is a repo-level guard and belongs next to the others
of its kind in scripts/ (check-skill-import-boundaries,
check-media-use-copy-parity).

Renamed to scripts/check-skill-python-encoding.test.mjs. The test now
resolves skills/ relative to its new home. The skills CI job no longer
finds it with its skills/ glob, so it is appended to SKILLS_TESTS next to
the copy-parity guard and added to the skills path filter. The
test-reachability manifest is updated to match, keyed to skills/**/*.py.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 19:58:01 +00:00
Miguel Ángel 5d2914f7ce fix(ci): a release fails its checks when its notes miss a commit merged after the cut (#7601)
* fix(ci): a release fails its checks when its notes miss a commit merged after the cut

* fix(ci): shorten the release checks comment

* fix(ci): find the last release by subject and say to link a deliberate omission
2026-11-12 11:39:42 +00:00
terencecho 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
2026-11-11 06:26:24 +00:00
James RussoandClaude Opus 5.5 12d954a1fe ci(release): keep the publish job's write token out of the checkout (#7502)
The publish job's checkout persisted its contents:write token in
.git/config, where every later step, including the package install and
build, could read it. Check out without persisting credentials and give
the token only to "Create release tag", the one step that pushes. It
authenticates its own git calls through step-scoped GIT_CONFIG_* env and
masks the encoded value. The gh steps keep their own GH_TOKEN.

The workflow test now covers the checkout flag, which steps may receive
the token and under what name, the auth header the tag push actually
carries, and that nothing is written to .git/config.

— Rames Jusso

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-10 16:53:32 +00:00
James RussoandClaude Opus 5.5 265ec660b7 ci(publish): build the Lambda handler zip in a read-only job and verify its hash before release (#7495)
* ci(publish): build the Lambda handler zip in a read-only job and verify its hash before release

The handler zip build runs dependency install and bundling code. It moves out of the
publish job into its own job with `contents: read`, no secrets and no persisted git
credentials. The publish job downloads the artifact, checks its sha256 against the
build job's output, then pins and attaches it as before. A retried run still reuses
the zip already on the release.

Refs #7485

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(ci): cover the read-only Lambda zip build job and the pin step's hash check

The publish workflow test still looked for the old "Build Lambda handler zip"
step. It now checks the build job's read-only permissions and the publish job's
dependency on it, and runs the pin step for the retry, matching-hash,
mismatched-hash and empty-hash cases.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-10 14:42:13 +00:00
James RussoandClaude Opus 5.5 f9255e39a5 fix(aws-lambda): the handler ZIP installs its runtime from a committed lockfile with scripts off (#7485)
* fix(aws-lambda): the handler ZIP installs its runtime from a committed lockfile with scripts off

build-zip.ts ran `npm install --no-package-lock` in the publish job, so
transitive versions floated at release time and any dependency's install
script ran beside the release credentials. The ZIP now runs `npm ci
--ignore-scripts` from runtime-lock/<source>/package-lock.json (versions
and integrity for every package), and the build fails if that lock
disagrees with bun.lock instead of falling back to a range or "latest".
`bun packages/aws-lambda/scripts/lock-runtime.ts` regenerates it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(aws-lambda): check only direct runtime versions against bun.lock; Renovate refreshes the rest

The runtime lock's transitive tree is npm's own resolution, not bun.lock's (modern-tar
0.8.6 there vs 0.8.4 in bun.lock), so the parity claim now covers puppeteer-core and
@sparticuz/chromium only. Renovate's weekly lockFileMaintenance refreshes the transitive
tree; its direct-version bumps are off for these dirs because those follow bun.lock.

— Rames Jusso

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(aws-lambda): keep the maintainer-only lock-runtime script out of the package

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-10 10:41:20 +00:00
Vance IngallsandClaude Sonnet 5.5 7bf19ab5f9 test(engine): nightly motion blur run over generated compositions (#7437)
* test(engine): nightly motion blur run over generated compositions

A seeded generator of text-free compositions combines 19 features (nested
canvas, overflow, clip path, scroll container, callbacks, a last-child rule)
and checks the two pixel invariants on auto: outside the trail at two holds
and at a moving time, inside the trail at a moving time. The runtime lane
runs seeds 1 to 3; motion-blur-nightly.yml runs 200 a day on the Chrome 153
pin and on stable, and opens one issue per failing seed.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(engine): the nightly records every failure, ignores noisy references, caps its issues

A crash, a timeout or a launch failure is recorded before the job goes red; a
failing check whose blur-off reference disagrees with itself is reported as
unstable instead of failing; the report job moves into a tested script that
fetches open titles once, caps first, and opens one systemic issue above 5 seeds.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(engine): the nightly report resists injected failure text and keeps a crashed leg's record

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* fix(engine): nightly report escapes backslashes, test strips tags to a fixpoint

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-09 21:37:26 +00:00
Miguel Ángel 074de9dd1e ci: install ffmpeg through the GitHub API asset route with a cache (#7401)
* ci: install ffmpeg through the GitHub API asset route with a cache

* ci: the three jobs without a prepared ffmpeg stop downloading ffmpeg-static from releases

* ci: the ffmpeg install failure message counts its three downloads
2026-11-08 11:31:54 +00:00
James Russo 3151fd2133 fix(studio): bound recovery and verify full-quality playback (#7393)
* fix(studio): bound recovery and verify full-quality playback

* fix(studio): compare preview pixels with captured HTML clock
2026-11-08 02:29:57 +00:00
terencechoandClaude Opus 5.5 f54b2227fd feat(share): extract shared review kernel for local hosts (#7134)
* feat(share): extract shared review kernel for local hosts

* fix: recover completed shares and integrate kernel checks

* fix: terminate ffprobe options before share media input

* fix: verify executable imports without matching JSDoc types

* build: budget the published sharing package

* fix: publish NodeNext-compatible sharing declarations

* fix: invalidate shared renders when linked media changes

* fix: reserve share progress before awaiting upload lock

* fix: copy share build inputs before image dependency install

* fix(share): preserve Desktop snapshots and support portable locks

* fix(share): restrict video uploads to trusted origins

* fix(share): preserve review state across recovery and uploads

* fix(share): preserve review title and feedback attribution

* fix(share): accept legacy review records safely

* build(share): update measured package size budget

* fix(share): preserve feedback cutoff across export retries

* docs(share): describe only the storage origins the signer uses

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 04:35:33 +00:00
James RussoandClaude Opus 5.5 5259fd1120 chore(ci): close PRs and needs-info issues after three weeks without activity (#7280)
Mark stale at 14 days, close 7 days later. Drafts, keep-open, and Renovate
PRs (now labeled dependencies) are exempt, since closing a Renovate PR makes
it skip that update.

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-06 00:42:34 +00:00
Miguel Ángel 2f321e0b0b ci(studio): the studio-open journey counts the same thumbnails on every runner image (#7187)
At 900 px the root composition card sat on the edge of the list's thumbnail margin, so a small layout change between runner images decided whether it asked for a thumbnail. A 1400 px window puts every card well inside it.
2026-11-04 21:25:49 +00:00
Miguel Ángel 2679bcdee7 ci(studio): the timeline viewport gate runs one pinned Chrome build, not the runner's (#7180)
The runner image ships Chrome 156.0.8078.47 or .79 run to run, and .79 renders one more thumbnail on open, so the studio-open ceilings failed on changes that never touched Studio. The ceilings file now records the major it is measured on.
2026-11-04 19:44:23 +00:00
Vance IngallsandClaude Sonnet 5.5 d36cad7985 test(engine): pixel invariants and fixtures that guard default-on capture blur (#7108)
* test(engine): pixel invariants for capture blur against blur off

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(engine): fixtures for every capture blur failure class seen so far

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(engine): nested canvas fixture reproduces #6975, sharp-tile fixtures have no moving times

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(engine): capture blur must match blur off outside the trail and the shutter average inside it

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(engine): differential tests pin known bugs by symptom, history test checks the reference frame

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(engine): a playing preview keeps changing with blur on

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(producer): a multi-worker blur render must match blur off outside the trail

Renders five blur fixtures through the real producer as a PNG sequence with 4
workers (contiguous blocks, three of them starting mid-film, the #6967
condition): blur off twice, blur on once. Outside the trail of everything that
moved, blur on must equal blur off in every frame with two neighbours. The
callbacks and scroll-list known differences are pinned by symptom.

Import route: a relative import of blurDifferential.ts, fixtures.ts and
thresholds.ts from packages/engine/src/services/__fixtures__. The producer
tsconfig excludes test files, so I type-checked the file with a temporary
tsconfig (rootDir widened); no error. No package subpath was needed.

RENDER_OUTSIDE_MAX_MAE: render noise is 0 (blur off, twice, bit-identical), the
rewind mutation measured 111.085 when caught, so the 1.0 floor applies.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(producer): render callbacks with workers that start between its calls

With 4 workers the blocks started at 0, 15, 30, 45, each on a call, so the
rewind mutation showed in a render only 3 times in 5. Seven workers over 60
frames start at 0, 9, 18, 27, 36, 45 and 54, two of them strictly between the
calls at frames 16 and 30; the mutation then fails callbacks in 8 of 8 runs
(worst MAE 97.02), the clean build in none.

A new case checks the partition with distributeFrames. The #list and #label
rects now come from the fixture's markup, and MEASURED_RENDER_REWIND_MUTATION
is 97.02.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(engine): blur pins bound the symptom, liveness detector reports blindness, fixtures time out

Pinned known bugs now require every bad tile inside the pinned region and a worst
MAE within half to double of the measured one. tileTouches, Rect and the band check
move into blurDifferential.ts with a dpr 2 unit test. The blank-frame census counts
canvases it cannot read and asserts none, and names both readings when no blank frame
is seen. No console.info on passing runs. Fixtures cases get a 30 s timeout.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(producer): scroll-list render case bounds the race, pins share the engine helpers

The scroll-list loss depends on timing per worker block, so the case now requires
frames 2..27 clean and any later bad tile inside #list, without requiring the loss.
The callbacks pin keeps requiring its symptom, bounds it to the label and to half to
double of its measured size, and its message names the entry to delete. Wording says
multi-worker, not 4-worker.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* build(engine): keep the blur test helpers out of the published tarball

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(engine): print the worst outside tile of each arm to explain the CI text diff

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test: both arms draw grayscale text so host subpixel settings are not read as blur

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(producer): run the multi-worker blur render alone so it cannot skew other Chrome tests

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test: re-pin the producer lane runner after splitting out the heavy blur render

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(engine): read the blank-frame pin from a wrap observer, not an animation frame poll

The pin sampled in requestAnimationFrame, so it could miss the gap between the
wrap and the first draw. A MutationObserver now reads the output canvas the
moment the root is wrapped, which is deterministic, and every fixture must
report a wrapped root.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* test(engine): drop the blurs field no fixture could set to false

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* ci: give the flake gate 60 minutes, it budgets runs by file count not time

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-04 17:55:07 +00:00
Miguel Ángel 3bb0a9a5b5 perf(engine): skip the screenshot on frames the page reports unchanged in beginframe capture (#7027)
* perf(engine): skip the screenshot on frames the page reports unchanged in beginframe capture

* fix(engine): beginframe reuse never returns a frame older than a cross-frame page change

* fix(engine): the BeginFrame reuse test gets a headless shell in the flake gate

* fix(ci): run the headless shell installer through its package

* fix(ci): install the headless shell with bunx, npx finds no bin in the workspace
2026-11-02 19:17:31 +00:00
Miguel Ángel c06427b063 test(cli): run the real npx shim check only in its own CI job (#6969)
* test(cli): the npx command test builds the command instead of running a real npx

* test(cli): run the real npx shim check only in its own CI job
2026-11-02 02:18:03 +00:00
Miguel Ángel 8b029f4fb0 fix(parsers): resolve file URLs and Git Bash paths in media sources (#6956)
* fix(parsers): resolve file URLs and Git Bash paths in media sources

* fix(parsers): return a native path for a Git Bash media source
2026-11-01 22:22:54 +00:00
Miguel Ángel 2c1a10f3ad fix(core): Safari keeps playing edits' audio without seeks or rate changes (#6888)
* test(player): play the WebKit audio edits in real Safari on a macOS runner

* fix(core): Safari keeps playing edits' audio without seeks or rate changes

* fix(core): keep the 0.1 s audio sync bound outside WebKit

* fix(core): restore main's audio steering outside WebKit

* fix(core): tell WebKit from the test DOM's user agent

* fix(core): name WebKit's audio start lag instead of commenting it

* fix(core): count embedded WKWebViews as WebKit for audio sync
2026-11-01 03:08:27 +00:00
Miguel Ángel a2c5a8a024 ci: split the cli test job into two shards so each stays well under its limit (#6902)
* ci: split the cli test job into two shards so each stays well under its limit

* ci: map the sharded cli test run in the reachability audit

* ci: the reachability audit treats --shard as selection-neutral instead of a pinned mapping

* ci: map the sharded cli test run in the reachability audit (pinned), not a blanket --shard rule
2026-11-01 00:44:13 +00:00
Miguel Ángel b93c01c75a ci(studio): run the merge queue edit accuracy grid in 30 shards (#6804) 2026-10-30 07:05:16 +00:00
Miguel Ángel 2a9dd05983 ci(studio): split edit accuracy into 15 PR shards packed by measured case time (#6784)
* ci(studio): run the pull request edit accuracy slice in 10 shards

* ci(studio): run the pull request edit accuracy slice in 15 shards

* ci(studio): pack edit accuracy shards by measured case time so they finish together

* ci(studio): load shard timings with require so happy-dom tests can import the grid

* ci(studio): the slow runner stop judges runner speed, not how long a shard's first cases are

* ci(studio): keep the slow runner comment on one line under 120 characters
2026-10-30 05:11:50 +00:00
Miguel Ángel 6b7e2c96eb ci(windows): split the engine-cli test lane into two shards (#6670)
* ci(windows): split the engine-cli test lane into two shards

* test(cli): the agent-mode test runs alone, after the files it starved
2026-10-30 03:37:15 +00:00
Miguel Ángel c922591c6c ci: edit accuracy shards start once the CLI is built, not after all of Build (#6777) 2026-10-30 03:06:12 +00:00
James Russo 3e462f4277 feat(cli): use dedicated HyperFrames OAuth clients (#6687)
* feat(cli): use dedicated HyperFrames OAuth clients

* docs(cli): shorten credential store contract comment

* fix(cli): respect Windows modes in OAuth media test

* fix(cli): keep media workflows on HyperFrames OAuth

* test(cli): scope billing status assertions to wallet rows

* test(cli): align telemetry fixtures and CI auth inputs
2026-10-29 21:25:20 +00:00
Miguel Ángel 74f3234736 ci: one regression shard writes the test image cache (#6729)
* ci: one regression shard writes the test image cache, so it stops evicting the rest

* test(ci): each image cache has one writer, shard 0 of a main push
2026-10-29 07:53:07 +00:00
James RussoandClaude Opus 5.5 1c3fcf4d23 feat(telemetry): identify signed-in CLI users by their HyperFrames user id, and say signed-in usage is not anonymous (#6703)
* docs(telemetry): say signed-in usage is linked to your account, not anonymous

After hyperframes auth login the CLI sends a PostHog $identify with the
account email (username as fallback) and merges the install's earlier
anonymous usage; media-use does the same when it finds a signed-in
account. Several places still called all telemetry anonymous. Say it is
anonymous until you sign in, in the CLI reference (media-use, --skill,
feedback, events, telemetry), the hyperframes-cli skill references, and
the CLI help and notice strings.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* feat(telemetry): identify signed-in CLI users by their HyperFrames user id

The CLI and media-use identified a signed-in install by account email, so
CLI usage landed on a different PostHog person than the same account in
the HyperFrames web app, which keys on toUUID(username). Identify by that
same sha256-derived id instead, and $set email plus heygen_username on the
person. heygen_username is the cross-project join column for the Snowflake
event table (HeyGen's own project stores it as `name`). An account with no
username still falls back to the lowercased email.

Notices and docs now say usage is keyed on an id derived from the username
with email and username stored on it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* chore(telemetry): trim comments to the package's comment share

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* feat(telemetry): put heygen_username on every event while signed in

The Snowflake event sync may not carry PostHog person properties, so a
$set alone does not let an event row join across projects. The CLI now
adds the signed-in HeyGen username (raw, from ~/.heygen/credentials) to
every event and drops it once the credentials hold no user; media-use
does the same on each event it sends.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* ci: count auth/paths.ts as an edit-accuracy bench input

Telemetry now imports it to read the signed-in username.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* fix(telemetry): stat and read the credentials through one file handle

CodeQL flagged the stat-then-read as a file system race.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* fix(telemetry): key signed-in events on the account id; fix stale anonymity copy

Genesis review on #6703:
- telemetry --help listed 'Any personally identifiable information' as
  never collected, and media-use's meta.md still said anonymous.
- Installs already identified by email under an older CLI never merge
  into the new person, so send signed-in events with distinct_id = the
  account id (back to the install id after logout), in the CLI and in
  media-use, and stop claiming earlier usage always merges.
- A user block with no credential no longer counts as signed in.
- A UUID-shaped username passes through unhashed, as on the web.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-29 02:57:48 +00:00
Miguel Ángel 9830059bdb fix(engine): downloads refuse hosts that resolve to private addresses (#6571)
* fix(engine): downloads refuse hosts that resolve to private addresses

* fix(core): shorten the env proxy doc comment

* test(producer): remote-media tests stub the download fetch seam
2026-10-28 20:08:50 +00:00
Miguel Ángel 0e32ee9b56 ci: keep the bun cache warm and skip binary downloads in preflight (#6648)
* ci: keep the bun cache warm and skip binary downloads in preflight

* test(ci): pin the single cache writer and preflight's skipped downloads

* test(ci): keep the cache-writer scan out of the test body
2026-10-28 09:52:07 +00:00
Miguel Ángel 6cf4b56697 fix(engine): a render on Windows opens no console windows (#6613)
* ci(windows): probe that a render opens no visible window

* ci(windows): the probe names what opened each window

* ci(windows): the probe spawns each binary alone, with and without detached

* ci(windows): the probe logs the processes started during the render

* ci(windows): the probe also spawns Chrome one consoleless hop down

* ci(windows): the probe logs each child started without windowsHide

* ci(windows): the probe logs every child process with its windowsHide and detached

* fix(engine): Chrome keeps the CLI's console on Windows, so a render opens no window

* fix(cli): every child the CLI starts on Windows is hidden unless it opts out

* ci(windows): the probe bisects Chrome's flags and keeps each command's output

* ci(windows): the probe names the Chrome process behind each window

* ci(windows): the probe loads a page in Chrome directly and one hidden hop down

* ci(windows): the probe prints the Chrome main command line and renders with the reporter's flags

* ci(windows): the probe narrows the CLI's Chrome arguments to the ones that open a window

* ci(windows): the probe launches the CLI's Chrome arguments one hidden hop down

* ci(windows): the probe launches Chrome through the engine's browser pool

* ci(windows): the probe varies what the engine passes to Puppeteer

* fix(engine): renders on Windows launch Chrome with a Puppeteer that keeps it attached

* refactor(cli): hideChildConsoles copies its arguments and keeps one comment line
2026-10-28 07:48:40 +00:00
Miguel Ángel 7fea875ede ci: no change-detection or reachability checkout can run into the one-minute limit (#6577)
* ci: change detection fetches the history its diffs read, not every branch and tag

The Detect changes job checked out with fetch-depth 0, which fetches all 1,400
branches and 670 tags to diff two commits; twice that stalled for the whole
minute and took a pull request out of the merge queue. It now checks out the
commit and fetches its ancestry and main without file contents.

* ci: no change-detection or reachability checkout can run into the one-minute limit

The Detect changes jobs of four workflows and the reachability job kept a
one-minute checkout limit with a retry; two of them hit it together and took a
pull request out of the merge queue. Each now has one checkout with three
minutes, change detection shares one fetch-history step, and the reachability
job, which reads only the base commit, fetches two commits deep.
2026-10-27 19:28:56 +00:00
Miguel Ángel d94132e609 ci: a release PR runs a fast release check instead of the heavy suites (#6524)
* ci: a release PR runs a fast release check, not the heavy suites

* ci: keep the release check's header within the comment limit

* ci: shorten the release check's usage line

* ci: trim the release check's comments

* ci: the release check's classifier hands the manifest test to a helper
2026-10-27 07:39:56 +00:00
Abdullah M. Nazif d1b3471325 fix(cli): describe the restored skip-skills option (#6245)
* fix(cli): describe the restored skip-skills option

* docs(ci): describe the current skills opt-out
2026-10-26 14:58:35 +00:00
Xuanru Li a39f7b37d9 feat(cli): check-review inspect attaches the inspector's report to each framed finding (#6409)
* feat(cli): skipContrastInMotion moves to HF_TOOL_CONTEXT check-review

The --skip-contrast-in-motion flag and HYPERFRAMES_CHECK_SKIP_CONTRAST_IN_MOTION
env give way to a check-review capability in HF_TOOL_CONTEXT, so only a harness
turns it on. The skill text and manifest go back to main.

* feat(cli): check-review findingFrames saves one plain frame per finding time

With HF_TOOL_CONTEXT check-review.findingFrames, every error/warning finding in
layout or contrast with a real bbox gets frameTime (the middle sample of its
longest held run, by the heldMs gap rule) and frame (the absolute path of an
unannotated full frame shared by every finding at that time). One seek and
screenshot per distinct time, capped at 60 times with errors first, into the
run's snapshot folder; not listed in snapshots, history or events. Without the
capability, output is unchanged.

* docs(cli): finding-frame comments name the check-review capability, not a flag

* fix(cli): validate finding frame times and preserve cancellation

* fix(cli): count finding frame progress toward the check deadline

* feat(cli): check-review inspect attaches the inspector's report to each framed finding

With findingFrames on, the finding-frames page is served with the
inspector's GSAP hooks. After each frame is captured, every finding framed
at that time is inspected by its data-hf-id, else its selector, and the
inspector's own report is attached as the finding's inspect field. A failed
inspection becomes that finding's { error } and never fails the check.
Without the capability nothing changes.

Drops the unused @types/mime-types devDependency that the dependency audit
flags once packages/cli/package.json is touched.

* fix(cli): stop finding inspections after cancellation

* fix(cli): reject ambiguous finding inspection targets

* fix(ci): build inspector before Windows CLI smoke

* fix(cli): parse viewport HTML with explicit server parser
2026-10-26 10:02:49 +00:00
Miguel Ángel 1819276fc3 test: real-Chrome and CI smoke pages inline GSAP so they wait on no CDN (#6406)
* test(studio): real-Chrome tests inline GSAP so their page waits on no request

* test(ci): smoke projects inline GSAP so required checks wait on no CDN
2026-10-26 08:20:55 +00:00
Erik Hill c8876431e9 ci: guard the edit-accuracy gate against a failed changes job (#5182) 2026-10-25 23:16:08 +00:00
Miguel Ángel 35a28e913a ci: re-run changed test files to catch flaky tests before merge (#6339)
* ci: re-run changed test files to catch flaky tests before merge

* ci: give the flake gate the full test workspace setup

* ci: share the test workspace setup between the Test lanes and the flake gate

* ci: split the flake gate main for the fallow complexity gate and format

* ci: run node:test files with node, skip uncollected files, bound the gate's run time
2026-10-25 21:51:52 +00:00
Miguel Ángel 8214cdcd29 ci: run cli tests in their own job so runtime tests stop timing out (#6326)
* ci: run cli tests in their own job so runtime tests stop timing out

* ci: format the test aggregator needs list

* ci: keep the test aggregator needs on one line for the reachability check

* ci(reachability): read wrapped and block needs lists instead of rejecting them
2026-10-25 18:54:01 +00:00
Miguel Ángel e938e53ea6 ci(release): keep the packed release tarballs as an artifact on release pull requests (#6292) 2026-10-25 09:50:12 +00:00
Miguel Ángel 8d562a3d91 feat(aws-lambda): attach the arm64 video image to releases and pin it (#6070)
* feat(aws-lambda): attach the arm64 video image to releases and pin it

The release builds the arm64 video function image from the handler ZIP it
attaches, attaches it as an OCI layout tarball with its sha256, and pins it
in prebuilt/video-image.json, read through prebuiltVideoImage(). A retried
release reuses the image already attached.

* fix(aws-lambda): keep the release pin script out of the published package

pin-handler-zip.ts is run from a checkout by publish.yml; nothing in dist or the CLI imports it. Leaving it out keeps aws-lambda under its size budget with the video image reader added.
2026-10-23 03:52:35 +00:00
Miguel Ángel f6cbf87cdd feat(aws-lambda): arm64 video function image from the handler ZIP (#6064)
* feat(aws-lambda): arm64 video function image from the handler ZIP

The image is the release handler ZIP with its x86 ffmpeg and Chrome swapped for
the native ffmpeg tree and the sha256-pinned Sparticuz arm64 Chrome pack, so the
x86 and arm64 functions run the same handler code. The image stage only copies,
so any host builds it. CI builds it and runs ffmpeg, a real Chrome render and the
Lambda runtime on an ARM runner.

* fix(aws-lambda): launch Chrome in the image smoke the way Lambda does

@sparticuz/chromium inflates its AL2023 libraries only when AWS_EXECUTION_ENV
names a Node runtime; Lambda sets it, a bare docker run does not. The workflow
also runs on @sparticuz/chromium bumps and handler ZIP layout changes, which
re-stage the image.

* fix(aws-lambda): smoke the arm64 image through its own Lambda runtime

The smoke is now a handler invoked through the image's entrypoint, whose
bootstrap sets AWS_EXECUTION_ENV the way Lambda does, so @sparticuz/chromium
takes its Lambda branch with nothing set by hand. It returns the value it saw.

* fix(aws-lambda): agree the move of the ffmpeg build workflow into the image workflow

* fix(aws-lambda): build the Chrome pack URL from the pin and hand the checked pack to tar in memory
2026-10-23 02:41:18 +00:00
Miguel Ángel 03ed14615a feat(aws-lambda): run chunks on an optional arm64 image function (#6065)
* feat(aws-lambda): run chunks on an optional arm64 image function

A new VideoImageUri parameter adds an arm64 container-image function that only
renders chunks. Plan, audio and assemble stay on the x86 ZIP function, so audio
encodes are unchanged. Empty (the default) deploys exactly as before. The
reserved concurrency moves to whichever function renders the chunks.

* docs(aws-lambda): the template tags both render functions

* fix(aws-lambda): nest the arm64 video function so sam deploy needs no image repository

sam deploy refuses a template with any top-level image function unless it is given an image
repository, even when that function's Condition is false, so every deploy of the template failed.
The video function now lives in video-function.yaml, a nested stack created only when
VideoImageUri is set. The release ships it beside template.yaml and the CLI stages both.

A new workflow runs the CLI's sam deploy argv against the template with fake credentials and
requires it to reach the first upload.

* fix(aws-lambda): run the plan on the arm64 video function with the chunks it plans

* refactor(cli): name the staged template directory instead of commenting it

* docs(aws-lambda): say the arm64 image runs the plan as well as the chunks
2026-10-23 00:40:55 +00:00
Miguel Ángel 1d0a18c814 ci(windows): fail a hung engine-cli test step at its deadline and name the stuck process (#6100)
* ci(windows): fail a hung test step at its deadline and name the process that hung

* ci(windows): upload the test step log even when the step is killed
2026-10-23 00:36:08 +00:00
Miguel Ángel bb19f342d3 build(aws-lambda): pinned native ffmpeg build for an arm64 Lambda image (#6062)
* build(aws-lambda): pinned native ffmpeg build for an arm64 Lambda image

One recipe, run per architecture on the Lambda Node 22 base it ships on. Codec
libraries link statically; glibc and GnuTLS stay dynamic, with the two libraries
the bare base lacks bundled beside the binaries. A check stage on the bare base
proves every encoder, decoder, filter and protocol the engine calls, and the
artifact cannot be produced without it. CI builds it on two ARM runners and
requires byte-identical tarballs.

* fix(aws-lambda): link GnuTLS dynamically in the arm64 ffmpeg build

With --static pkg-config flags, gnutls.pc names a libgmp.a from its own RPM build
tree and configure rejected GnuTLS. The codec libraries exist only as static
archives, so they still link statically. The recipe moves to image/, which will
also hold the video function image stage.

* fix(aws-lambda): build x265 for arm64 with the base image compiler

x265 builds its SVE2 kernels with -march=armv9-a, which gcc 11 rejects. Turn
them off, and stop a failed x265 build from reaching ffmpeg configure as a
misleading "x265 not found".

* fix(aws-lambda): pin x264 to the revision the x86 ffmpeg uses

The x86 ffmpeg-static 7.0.2 encodes with x264 r3191 (4613ac3); match it.

* fix(aws-lambda): 10-bit x265 in the arm64 ffmpeg, checked by output format

x265 now builds the 10-bit library and links it into the 8-bit one, so HDR
renders get yuv420p10le instead of a silent 8-bit fallback. The check asserts
the encoded pixel format rather than a successful command, and its ffprobe calls
terminate options with -- like every other caller.
2026-10-23 00:13:50 +00:00
Miguel Ángel 27b9f68506 fix(ci): pin and reuse the docs validation CLI (#6080)
* fix(ci): pin and reuse the docs validation CLI

* fix(ci): pin and reuse the docs validation CLI
2026-10-22 19:43:26 +00:00