* test(release): npm publishes with the job's OIDC token, no stored token named
* fix(release): publish to npm with the job's OIDC token, not a stored token
* test(release): catch a secret named by index or inherited, not only secrets.X
* test(publish): a stable release counts only maintainers' reviews, never the approver's own push
* fix(publish): a stable release needs a maintainer's approval, not any account's
* fix(publish): only approvers and change requesters are looked up, and a failed lookup always refuses
* style(publish): the release gate's comments and lines fit the 120-character limit
* fix(cli): audio and media-use print control characters from project files as visible escapes
hyperframes audio, audio --read and media-use resolve (including
--candidates) printed file names, element ids, transcript words, model
descriptions and media manifest fields as they were. They now pass
through terminalText, so a control character shows as a visible \xNN
escape. The media-use engine runs without the CLI's packages, so it
carries a small copy of the helper. --json output is unchanged.
* fix(engine): playlist check refuses drive-relative and other colon-prefixed entries
ffmpeg reads an HLS or ffconcat entry with a colon before its first
separator as a URL or a drive, and opens it apart from the list's
folder. The folder check read entries such as C:Videos\a.mp4 or c:x.mp4
as names inside the folder and approved them. It now refuses any entry,
raw or percent-decoded, whose colon comes before its first /, \, ? or #,
as it already refuses absolute and parent-folder paths. http and https
segments are still kept.
* fix(cli): background-removal and Kokoro TTS model files are pinned to a sha256
The u2net_human_seg weights and the Kokoro model and voices files were
downloaded from release URLs and used whatever bytes arrived, and any
cached copy was trusted because it existed. Each file now has a pinned
size and sha256. A cached copy is checked before it is loaded and
downloaded again when it does not match. A download that does not
match is discarded with a message that names the file.
* fix(engine): playlist check reads entries from the folder ffmpeg uses
ffmpeg resolves a list's entries against its path cut at the first ? or
#. A list at proj/h#z/list.m3u8 naming ../h#z/x.ts was judged against
proj/h#z and approved, while ffmpeg opened proj/../h#z/x.ts. Entries are
now judged against the same cut folder. A list in a folder such as
"Take #2" still passes when its entries resolve inside that folder.
* fix(cli): a pinned model's cached copy is checked and removed under the download lock
ensurePinnedFile removed a cached copy that failed its check before the
download lock was taken, so a concurrent run could delete a file another
run had just published. downloadFile now takes a keepExisting check and
runs it under the lock: a copy that passes is kept, one that fails is
removed and downloaded again. The mismatch error now says the file does
not match its expected checksum, and that a retry helps only if the
download was interrupted or corrupted.
* fix(cli): audio escapes each field's line breaks, and media-use escapes recipe and stats output
The audio formatters escaped their output line by line, so a newline
inside a src, warning or transcript still printed as a real line break.
Each output line is now escaped whole with terminalText, which shows a
newline inside a field as \x0a. media-use resolve also escapes its
recipe lines and its --stats lines, which print recipe names, paths and
missed intents.
* fix(cli): media-use error messages show control characters as visible escapes
resolve printed error messages as they were, and some name project or
cache data, such as the known recipe names when a recipe is not found.
Every error: line now passes through terminalText, as the success lines
already do.
* ci: the edit accuracy filter includes the CLI model file check
The CLI's pinned model download now imports whisper/modelFile.ts, so a
change to it must run the edit accuracy bench too.
* test(cli): pinned model tests use private temp folders and rename like downloadFile
The tests wrote fixtures under fixed names in the shared temp folder,
and their download stand-in checked for a file before replacing it.
Each test now works in its own mkdtemp folder, and the stand-in asks
keepExisting directly and renames the part file into place, as
downloadFile does.
* test(cli): the media-use terminalText copy is checked against core's
The media-use engine keeps its own copy of terminalText. A CLI test now
compares the two over U+0000 to U+00A0, so a change to either fails
until both match. keepsDest moves above downloadFile's doc comment,
which belongs to downloadFile.
* ci: publish a stable release from the push that merges its release PR
* test(ci): read the publish job's own concurrency, where a publish in flight now waits
* ci: a stable release needs another person's approval of its final commit
* ci: only a person's approval counts for a stable release
The publish job took the npm dist-tag from the pushed tag's suffix and refused
only an exact "latest". A tag such as v1.2.3-LATEST.1, or one with a new suffix,
still named its own dist-tag. The job's channel check now accepts only alpha,
beta, rc, next, canary, hdr, native and desktop, matched exactly.
* fix(publish): upload only what npm reads as checked, and tag-publish only main commits
npm reads tarballs with node-tar, which can resolve a header differently from the GNU tar
check. A dry run of the same npm now has to agree on name, version and files before anything
is written. A v*-* tag now builds only a commit already on main.
* fix(publish): a v*-* tag publishes a commit on main, next or alpha
Alphas stay cut from next or alpha as release-channels.mdx says; a commit on none of them is
refused before any job builds it, and the error names it as not an ancestor of those branches.
* style(publish): wrap the npm check comment under the 120-column limit
* fix(core): a graded video's opacity animation reaches its export
* fix(core): a graded clip keeps its own clip-path, so it never renders black
* test(producer): golden render of graded video dissolve and wipe
* fix(core): a graded clip stays clickable in the preview, hidden by a filter not a clip
* chore(studio): drop an import the reader no longer uses, and format the graded fixture
The publish job now refuses a packed tarball that holds anything but plain files
under package/ with one package/package.json, or whose publishConfig sets more
than access, registry, exports, main and types. npm publish pins the registry,
and a prerelease tag can no longer publish to the latest dist-tag.
* ci(publish): reuse Lambda assets only from a release this run created (SECOPS-1217)
The pack job downloaded any Lambda handler zip or video image already on the release and pinned it
into @hyperframes/aws-lambda without checking where it came from, so anyone with contents write
could pre-stage both before a stable release.
A new step fails the run when the release exists but github-actions[bot] did not create it during
an earlier attempt of this run, or when a Lambda asset on it was uploaded by anyone else. The pin
steps reuse an asset only when that step allows it.
* fix: bind release retries to immutable run artifacts
* fix: fail release digest pipelines before side effects
The pack job no longer downloads Lambda assets already attached to the
release; it always pins the handler zip and video image this run built.
The publish job decides what the release keeps. Once
@hyperframes/aws-lambda is on npm for the version, the release must hold
exactly the assets that package pins. Before then, an asset this run did
not produce fails a first attempt, and a re-run of the same workflow run
replaces it. An asset identical to the bundle's is left alone, so a
re-run of only the publish job also works.
* fix(ci): publishing workflows run only for main
A workflow_dispatch on any branch ran the ClawHub sync with CLAWHUB_TOKEN and the
MCP registry publish with an OIDC token, publishing that branch's skills/ or
server.json under heygen-com. Each publishing job now skips unless github.ref is
refs/heads/main and checks out the triggering commit without stored credentials.
* test: split the main-only publish check into small checks
* test: close main-only publishing policy gaps
* refactor: separate publishing push filter classification
* ci(publish): publish prebuilt tarballs from a job that runs no release-commit code
Builds, lifecycle scripts and packing move to a pack job with a read-only
token and no secrets. The publish job, which holds the npm token and the
write token, checks each tarball's name and version against the release and
uploads it with lifecycle scripts off. A version already on npm with other
contents fails the first attempt instead of being skipped.
* ci(publish): prerelease tag pushes publish only after a maintainer approves
A prerelease tag can come from any prerelease branch, which no PR review
covers. Tag-push runs now use the npm-prerelease environment, which requires
a maintainer's approval. Merged release PRs keep the npm-publish environment.
* ci(publish): keep every publish in the approval-gated npm-publish environment
npm's trusted publishers are pinned to npm-publish, and that environment now
requires a maintainer's approval with self-review prevented. A second
environment would fail npm auth, so the workflow keeps npm-publish for every
trigger. The docs and test name it as the approval gate.
Builds, lifecycle scripts and packing move to a pack job with a read-only
token and no secrets. The publish job, which holds the npm token and the
write token, checks each tarball's name and version against the release and
uploads it with lifecycle scripts off. A version already on npm with other
contents fails the first attempt instead of being skipped.
* fix(engine): a cached browser is used only when its files match the pinned build
* ci: install the pinned headless shell for the engine and producer test jobs
* ci: record the producer test job's new setup step for test reachability
* 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>
scripts/upload-docs-images.sh synced docs/images/ with the AWS CLI's default
of following symbolic links, so a link committed under docs/images/ would
publish whatever it pointed to on the machine running the upload. The script
now stops before any AWS call when docs/images is not a real folder in the
checkout or when anything under it is a link or not a regular file, and the
sync passes --no-follow-symlinks as well.
A new check, scripts/check-symlinks.mjs, fails CI when a tracked symbolic
link is not one of the two the repo already means to have.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(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
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>
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>
* 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
* 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
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>
* 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>
* 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>
* 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>
* 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
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>
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.
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.
* 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>
* 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
* 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
* 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
* 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
* 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