* test(release): the MCP listing publishes with heygen.com's key; io.github retires by hand
* fix(release): list the MCP server as com.heygen/hyperframes, signed by heygen.com's key
* fix(cli): a project .env provider key prints a note when it is used
A provider key from a project .env is still used when no own credential
competes. Capture vision (OpenRouter, Gemini, Google and both Vertex parts),
snapshot --describe, Gemini speech and Lyria music now print one note per key
before it is first used, naming the variable and the escaped .env path, as
the ElevenLabs note does. The ignoring notes escape the path too, and the
media-use skill gets a generated copy of the CLI's terminal-text helper.
* fix(media-use): the audio scripts read a received .env by the CLI's full rule
The audio scripts judged a project .env as received only from
received-files.json at or above it. They now use a generated copy of the
CLI's rule, which also reads the host's received-state file, nested records
and the received content hashes, and treats an unreadable one as received.
A parity test runs the CLI and the copy over the same projects.
A key the CLI unset from a .env is now passed to the scripts it launches,
so they do not load it again from the same file.
* fix(media-use): match the CLI's folder walk and judge a parent .env by itself
The received-rule copy now skips folders by the CLI's exact private-path rule,
so a hidden Studio folder with an asset-like name is walked as the CLI walks
it. A .env the scripts find in a folder above the working one is judged only
by records and host state at or above that folder, so a received sibling or
a large parent folder cannot flip the person's own key. Keys the CLI unset
are matched by the folder's real path.
* fix(media-use): match the received rule's narrowed private-file check
The CLI's private-file rule now treats a hidden file as private whatever its type,
and framework build-output folders and service-account key names as private.
The media-use copy of the rule follows it, so the parity cases for hidden
asset-named Studio folders agree again.
* test(studio): adding a keyframe at the playhead reads a sealed preview's GSAP values
* fix(studio): GSAP keyframe and value reads work in a sealed preview
* test(studio): run the sealed keyframe test's agent on a marked Studio preview page
* test(studio): a sealed preview's GSAP reply is checked before Studio holds it
* fix(studio): hold a sealed preview's GSAP reply only when it is in shape and within bounds
* style(core): keep the snapshot limits module within the comment share
* refactor(studio): check a GSAP reply's tween in small parts
* build: raise the core packed-size budget for the sealed preview's GSAP reader
* test(core): a sealed preview's GSAP read takes a real keyframes tween
* fix(core): a sealed preview's GSAP read leaves GSAP's live objects out of a tween's vars
* test(release): a release's approver must not have pushed it, and a second maintainer must have
* fix(release): count every pusher of a release, need a second maintainer, date approvals
* docs(release): who may approve a stable release, and the second maintainer it needs
* test(release): a push the activity log records with no account stops the release
* fix(release): a push recorded with no account stops the release
A provider key from a project .env is still used when no own credential
competes. Capture vision (OpenRouter, Gemini, Google and both Vertex parts),
snapshot --describe, Gemini speech and Lyria music now print one note per key
before it is first used, naming the variable and the escaped .env path, as
the ElevenLabs note does. The ignoring notes escape the path too, and the
media-use skill gets a generated copy of the CLI's terminal-text helper.
* test(release): a release merged in one push with other PRs is found and published at its own commit
* fix(release): a release merged in one push with other PRs publishes at its own commit
* test(studio): audio meters and group volume in a sealed preview
* fix(studio): audio meters and audio groups work in a sealed preview
* chore(inspector): raise the unpacked size budget for the preview's audio editing kinds
* test(studio): the sealed audio test serves a Studio-marked preview, as the editing port now requires
* 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
With the sub-composition expansion budget (#8045) on top of the probe
pre-check change (#8044), the producer packs to 930,774 bytes. That is
over its 921,000 budget by more than the 1% tolerance, so the merge
queue's Build step refuses #8045. The growth is the new expansion budget
class and pre-flight walk in the compiler.
* test(inspector): the inspector's Chrome follows the host sandbox rule, and probes retry without it
* fix(inspector): the inspector's Chrome starts as root or in a container
* test(producer): the page check and the inspector retry Chrome without the sandbox when it refuses
* fix(producer): the page check retries Chrome without the sandbox when it refuses, like the inspector
* chore(inspector): raise the packed size budget for the shared sandbox rule
* fix: refuse media paths that ffmpeg's image2 demuxer would read as a pattern
ffmpeg's image2 demuxer reads %d, %03d, %% and a % before a wildcard in an
input path as a pattern of other files, folders included. Every project,
private-file and received-file check approves the literal path, so a
composition could name a placeholder whose pattern reaches images outside
the project and get them back as video frames.
Every ffmpeg and ffprobe input built from a project file now goes through
assertLiteralMediaInput, which refuses such a local path before ffmpeg runs.
The engine's urlInputArgs, the parsers' mediaInputFormatArgs and the
studio-server's new mediaInputArgs all take the input path, so the CLI
snapshot and cloud offload, lint, core grade analysis and studio-server
callers are covered too. URLs and other percent signs, such as %20, are
read as before.
* build(parsers): declare the literal-media-input subpath
* build: raise the parsers packed-size budget for the literal-media-input subpath
The new subpath adds its own built entry, type file and export map rows,
about 2.7 KB packed. It is a separate module so test suites that mock
ff-binaries still run the real path check.
* test(parsers): a harmless name shaped like a pattern is refused too
The media-use TTS and captions references ran heygen-tts.mjs and
heygen-voice.mjs as skills/media-use/... paths relative to the working
directory. Agents run these commands from the user's project, so a project
that ships a file at that path would run instead of the bundled helper.
Name the helpers through <SKILL_DIR>, as the rest of media-use does, and add
a skill lint rule that fails when a code block or inline command runs node,
python, bash, sh, tsx or bun on a relative script path. Docs whose commands
run inside a HyperFrames checkout, or only on a checked template kit, opt out
with a marker that states the reason.
* 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
* fix(studio): the copied render command carries no composition text a shell can run
The Variables panel's "Copy render command" put every variable value inline,
quoted for POSIX shells only. A shared project's author chooses those values,
so in PowerShell, cmd.exe (including npx.cmd's re-parse) or fish a default
such as `x'; calc.exe; '` ran as commands when the command was pasted.
The command is now fixed text: `npx hyperframes render -c <composition>
--variables-file .hyperframes/render-variables.json`. Copying it saves the
previewed values to that file through a new PUT /projects/:id/render-variables
route, which refuses a link standing in for .hyperframes and replaces, rather
than writes through, a link at the file itself. A composition path that is not
one plain word in every shell (letters, digits, `_ . / -`) gets no command.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(scripts): the comment checker skips a template nested in a substitution
stripLiterals ended a template literal at the first backtick, including one
that opens a nested template inside `${...}`. On a line such as
`'${value.replace(/'/g, `'\\''`)}'` that left a backtick unmatched, so
scanCLike read the rest of the file as one template and counted none of its
comments. The ratchet then measured VariablesPanel.tsx on main at 1 comment
line instead of 31 and failed any change that removed that line.
A `${...}` is now scanned as code: strings, regexes and templates inside it
are skipped, and its closing brace returns to the outer template.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(studio-server): read the replaced render-variables record through one no-follow descriptor
The link test checked the record with lstat and then read it by path, two
lookups CodeQL reports as a file-system race. Opening it once with O_NOFOLLOW
fails if a link is still there and reads the file that open checked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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(studio-server): audio decodes are bounded, stop when nobody waits, and their cache is capped
The waveform and peaks routes each started a full-file ffmpeg decode per request, with no limit on how many ran
at once, no sharing on the waveform route, and no way to stop one after its request went away. Their cache
folder also grew without end.
- Both routes now decode through one shared queue of 4 slots, one decode per cache entry, shared by every
request that wants it. When the last request waiting on a decode leaves, its ffmpeg is killed (or it leaves
the queue).
- `.waveform-cache` keeps at most 500 entries; a write past that drops the oldest.
— Rames
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): trim comments to the package's comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(studio-server): raise the packed size budget for the audio decode limits
The bounded decode queue, the abort when nobody waits and the capped cache
add about 485 bytes to the packed tarball. Main had already reached 178,489
bytes against a 178,000 budget, so together they pass the 1% tolerance
(179,877 bytes). The new budget is the measured size plus the script's 5%
headroom.
— Rames
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): waveform decodes keep a fixed-size peak buffer, time out, and the cache is byte-capped LRU
- decodeAudioPeaks streams samples into a 65536-entry max-abs buffer that merges
neighbouring runs when full, instead of buffering and concatenating the whole decode.
- A shared decode is stopped after 10 minutes and its slot freed.
- .waveform-cache is capped at 256 MB as well as 500 entries; a cache hit marks its
entry used, so eviction drops the least recently used.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(studio-server): raise the unpacked size budget after rebasing onto main
Measured with pnpm pack after the rebase: 697160 unpacked bytes, over the
690000 budget by more than 1%. The new budget is the measured size plus 5%.
— Rames
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): an undo on a sealed preview shows in place, not after a reload
* fix(studio): split the sealed restore checks, and the inspector budget takes the new kind
* fix(studio-server): bound preview stills and keep proxy work to the Studio's own pages
- Queue at most 16 stills behind the 4 being made; past that, answer 503 with Retry-After.
- Refuse a still past the end of the source before starting ffmpeg (404).
- Refuse a ?hf-proxy request on a plain preview path when another site asks for it. The
Studio's own opaque frames already load through the frame-token path, and sandboxed
thumbnail captures now do too.
— Rames
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(studio-server): raise packed size budget for the still-queue and cross-site checks
The bounded still queue, the past-end refusal and the cross-site proxy
check add about 2.2 KB to the packed studio-server (180252 bytes in CI).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Every push to main starts its own Publish catalog run, so a run that finds
main ahead of its checkout has nothing left to do. It used to throw, which
marked 6 of the last 100 main runs red with nothing to fix.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The button puts the whole player, controls included, in fullscreen and follows every
fullscreen change. Set disable-fullscreen to hide it.
It raises the player's package size budget. With pnpm 10.17.1, main packs to 158,705 bytes
(544,891 unpacked) and this branch to 160,137 (549,402).
* 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(cli): own render-slot lock dir; refuse cache files other accounts can write
Sharing one render slot across accounts no longer means sharing HYPERFRAMES_CACHE_DIR,
which holds the browser, packages and helpers each account runs.
HYPERFRAMES_RENDER_LOCK_DIR names a folder of lock records only, created sticky and
writable by all (1777); the per-user lock folder is created 0700. Help text, errors and
docs no longer suggest sharing the cache or chmod 777.
foreignWritablePath (core/cache-dir) refuses a cached file whose path up to the cache
root is owned by another account or is group/world-writable. Chrome (CLI, engine,
inspector), optional packages (incl. the Sherpa runtime), the whisper.cpp build, the TTS
script, the Apple audio helpers, opencv.js and the Lambda handler reinstall or rebuild
instead of running such a file, and trustedCacheRoot moves their installs to
~/.cache/hyperframes when another account can write HYPERFRAMES_CACHE_DIR.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): seal own cache installs against umask 002 and repair old lock folder modes
sealCacheInstall (core/cache-dir) takes group and world write off what this account just
installed and the folders above it up to the cache root, so an install made under umask
002 passes foreignWritablePath on the next run instead of being refused and fetched again.
Chrome, optional packages, the whisper.cpp build, opencv.js, the TTS script, the Apple
audio helpers and the Lambda handler call it after installing.
ensureLockDir makes an existing per-user lock folder 0700 again when an older release left
it open, and adds the sticky bit to an existing HYPERFRAMES_RENDER_LOCK_DIR folder, warning
once with the folder's name when it cannot.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(cli): drop added comments to pass the comment ratchet
The explanations move into names: the mode bits in core/cache-dir are GROUP_OR_WORLD_WRITE
and WITHOUT_GROUP_OR_WORLD_WRITE, and the owner check is anotherAccountCanWrite. No change
in behaviour.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): verify the lock folder through a no-follow handle and stage installs owner-only
The render lock folder is opened with O_NOFOLLOW | O_DIRECTORY and checked and chmod-ed
through that descriptor: a link, or a folder another account owns (root may own a shared
one), is refused with RenderLockFolderRefused instead of being made world-writable or
used as is.
Chrome staging, the optional-package staging folder, the whisper.cpp build folder and the
opencv, TTS, Apple helper and Lambda handler folders are created 0700, and Chrome's staged
tree is sealed before it leaves staging, so nothing is group-writable while it installs.
foreignWritablePath accepts a sticky folder owned by this account or root, as /tmp is, and
tolerates a statSync without options; tests whose cache sat directly in /tmp, and tests
that mock statSync, failed on both. Docs note that a record naming a live process of
another account holds the shared slot.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): skip the uid-based Chrome cache refusal cases where there is no uid
Windows has no process.getuid, so the ownership check never runs there and the two cases
that expect a refusal cannot hold.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(core): raise the unpacked size budget for the cache ownership checks
core grew to 4418013 bytes unpacked with foreignWritablePath, sealCacheInstall
and trustedCacheRoot; the budget follows the usual 5% headroom over that size.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine,producer): media inputs refuse formats that open other files
Composition media read by ffprobe/ffmpeg now passes a format allowlist on every
input: the demuxers the installed ffmpeg reports, minus the ones that open other
files or URLs on their own (DASH, IMF and similar). hls and concat stay allowed,
since ffmpeg carries the list into every file they open. The HDR window,
alpha-plane, GIF, HEIC, audio-sidecar and snapshot reads that skipped it now use it.
The not-media check skips ID3v2 tags before it looks at the first byte, refuses a
playlist entry that is a document, and refuses JSON or non-SVG markup as an <img> src.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine,parsers,core,lint,cli): format allowlist reads old listings and covers every media probe
The demuxer listing is read from the binary that enforces the flag, accepts ffmpeg 4's
two-column output, and a failed listing is asked again next time. The lint HEVC probe,
the grade analyzer and the snapshot probes use it too. A nested playlist entry is refused
only for a real document signature, so encrypted segments and keys are kept; an image whose
prolog outruns the sniff window, or that is UTF-16, is no longer refused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(parsers,producer): trim comments added with the media format list
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(engine): keep the format-limit probe's argv in the shape the ffprobe contract reads
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): the image markup check reads a doctype without regex backtracking
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(parsers): raise the parsers size budget for the media format list
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(studio): a sealed preview frame forwards Studio's playback keys
* fix(core): a key held while Studio re-sends its watch list still forwards its keyup
* fix(core): the key watch adds and removes its listeners by name, as the runtime typecheck needs
* chore(producer): raise the unpacked size budget for the runtime's key forwarding
carve.mjs calls analyseCarveDynamics for the bed's carve lanes, but the
generated lib/audio-carve.mjs did not export it, so every real run failed
with "carveApi.analyseCarveDynamics is not a function" after detecting the
tracks. The generator now bundles it, and a test fails when carve.mjs calls
any function the bundle does not export.
Reproduce on main: node skills/media-use/audio/scripts/carve.mjs --comp index.html
in a composition with a music bed and a voice.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): the plan copy checks every project entry, whatever its name
A top-level name that starts with two dots, such as ..assets, is an ordinary
project entry. The plan copy treated it as outside the project and skipped the
link-resolving containment check, so a link with such a name had its target
copied into compiled/. Only the project folder itself now skips the check, and
the outside test compares whole path segments.
* fix(aws-lambda,gcp-cloud-run): untar leaves out symbolic links and special files
A project archive can come from another person. A symbolic link in it could
point anywhere on the render host, and the planner would copy its target. Untar
now unpacks only files, folders and hard links. node-tar already keeps a hard
link's target inside the destination folder. The CLI's site upload follows
symbolic links when it packs, so its archives hold none.
* fix(aws-lambda,gcp-cloud-run): untar turns hard links into separate plain files
The site upload packs two hard-linked project files as one file and a hard
link. Untar still unpacks both, then gives each hard-linked file its own copy,
so the extracted project holds no links of any kind and loses no file.
* fix(aws-lambda,gcp-cloud-run): copy hard-linked files without mkdtemp; untar test in its own file
* fix(cloud): keep the hard-link copy name short so long file names still unpack
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.
* fix(media-use): carve runs its own copy of core's analysis, never the project's
carve.mjs loaded @hyperframes/core from the composition's own node_modules, so carving
a project ran whatever that project shipped under that name. It now imports a bundle
of core's carve and audio-fx functions generated beside it, with a test that fails
when the bundle drifts from core's source.
* fix(media-use): lint and format skip the carve bundle on the CLI path too
* 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
* fix(studio): recovery drafts are kept by each project's own server, never the browser
* fix(studio): a restored draft stays offered when Studio settles which composition is open
* fix(studio): a draft read never waits on a pipe or loads an oversized record
* test(studio): the draft read's child fixture is an entry point, and its note sits in the test
* chore(studio-server): size budget covers the recovery-draft route
* chore(cli): unpacked size budget covers the recovery-draft route
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(engine): give each superset extraction a folder of its own
A superset group extracted into a folder named from the group index and the
process id, and deleted and recreated it by that name in the cache root that
every render shares. Two renders in one process could share the folder and
remove each other's frames.
Partial folders are now created with mkdtemp, so each extraction writes only
into a folder it made. A cache entry is published only when its frame count
is the one the extraction wrote.
* fix(engine): make the partial folders with createStagingDir; raise the engine size budget
* fix(producer): compile and render-telemetry tag scans run in linear time
The compiler's gsap script rewrite, crossorigin and preload strips, remote
media and image src scans and inline-script scan, and the render telemetry's
tag counts, now use forward scans that return exactly what the regexes they
replace returned. Those regexes rescanned to the end of the page from every
tag opener that never closed, or from every character of a long whitespace
run in one tag. The telemetry's script and style strip stops after 8 passes.
* test(producer): give the scan fuzz tests room on CI and raise the producer size budget
* test(lint): density warning ignores lanes
* fix(lint): count dense timelines per file so agents keep scenes on one lane
* chore(skills): make room for the lane pointer in the entry skill
* fix(lint): plain comment on the per-file density count
* chore(skills): say why the entry skill budget grew
* test(skills): pin the one-lane wording agents follow
* style(skills): format the lane wording test
* chore(skills): regenerate skills manifest
* docs(skills): overlapping sound effects take a second lane
* 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
Every skill now starts the CLI through hyperframes/scripts/plugin-cli.mjs, which starts npm in
the home folder. A standalone install, with no plugin manifest, runs the newest release that
moves into HYPERFRAMES_PLUGIN_CWD. The skills no longer prefer a project's own wrapper over the
CLI.
* 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.
* fix(parsers): bound canvas scaffold dimension extraction
* chore(parsers): raise packed size budget for linear scaffold scanners
The bounded scanners replace three regexes with a small amount of
procedural code; @hyperframes/parsers packs to 210414 bytes (+1.2%).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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