1567 Commits
Author SHA1 Message Date
Miguel Ángel 592a9feff9 chore: release v0.9.70 (#8234)
* chore: release v0.9.70

* chore: release notes for v0.9.70 link the 3 commits after the first cut
2026-11-19 06:55:39 +00:00
terencecho e5283f63b9 fix(render): keep segment checkpoints in the local cache (#8137)
* fix(render): keep segment checkpoints in the local cache

* fix(producer): read checkpoints through a validated descriptor

* fix(render): enforce cache and audio sidecar input policies

* fix(render): recapture unreadable segment checkpoints

* chore(parsers): remove redundant concat comment
2026-11-19 05:00:25 +00:00
terencecho a4995e9e6f fix(skills): raise the launcher minimum to 0.9.68 (#8232) 2026-11-19 04:51:58 +00:00
Michael Wang 4d17b71b4d fix(producer): raise the sub-composition expansion limit to 64 MB (#8096)
* fix(producer): raise the sub-composition expansion limit to 64 MB

A render may now inline up to 64 MB of composition HTML across its mounts,
four times the 16 MB per-file limit, so a project with several large
distinct scenes is no longer refused.

* test(producer): size the generated-output tests from the expansion limit
2026-11-18 23:49:15 +00:00
Michael Wang 8ace95ce94 fix(cli): a project .env provider key gives way only in a received project (#8099)
* fix(cli): a project .env provider key gives way only in a received project

Your own or a cloned project's .env provider keys are used as set again, as
the docs describe. Capture no longer drops a project .env vision key next to
a shell credential, and the audio scripts no longer drop an own project's
Gemini key next to the shell's other Gemini key. A received project's keys
still give way to your own credential, and the notes that name a project
key when it is used stay.

* test(cli): check the note for a cloned project's key; say when a received key is ignored
2026-11-18 22:45:29 +00:00
James RussoandClaude Opus 5.5 3229c3a8da chore: release v0.9.69 (#8220)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 22:28:58 +00:00
Miguel Ángel 3ae9e7302d chore: release v0.9.68 (#8214) 2026-11-18 20:50:58 +00:00
Michael Wang 855ad35c22 fix(skills): the launcher's floor is 0.9.67 (#8205)
* fix(skills): the launcher's floor is 0.9.67

The skill launcher now refuses any HyperFrames release older than 0.9.67, the latest
release and the oldest one the HyperFrames Desktop app will accept. This applies to
--cli-version, to HYPERFRAMES_STANDALONE_CLI_VERSION, to a helper started with --script and
to a plugin manifest pin. A standalone install's default npx range starts at 0.9.67. Every
plugin manifest in this repo already pins 0.9.67.

The skills guide and the plugin installation reference name the new floor.

* docs(skills): the launcher floor stays at or above Desktop's oldest accepted release

Desktop currently accepts 0.9.66 and later, and a pending Desktop change raises that to
0.9.67. The launcher's comment now says its floor stays at or above the oldest release
Desktop accepts, without naming a Desktop version, so it stays true when Desktop moves.
2026-11-18 19:34:12 +00:00
Miguel Ángel a2830467e4 feat(engine): renders send page traffic through the egress proxy in HYPERFRAMES_CAPTURE_PROXY (#8196)
* feat(engine): renders send page traffic through the egress proxy in HYPERFRAMES_CAPTURE_PROXY

* feat(engine): render media downloads go through the egress proxy in HYPERFRAMES_CAPTURE_PROXY

* fix(engine): downloads through the egress proxy keep undici's fetch, so gzip text and headers work
2026-11-18 18:35:41 +00:00
Michael Wang 43582dcb72 fix(producer): resume and proxy joins reuse only pieces this install made (#8089)
* fix(producer): resume checks the segment file the join reads, not the manifest's path

A resumed segmented render now validates each reusable segment at its own
computed path in the segment folder. It must be a plain file, not a link, and
match a slice of this render's plan. The path a manifest records is never
opened or probed.

* fix(engine,producer): concat joins open only the list and encoder containers

Both concat-demuxer joins (the engine's chunk and segment concat and the
distributed assemble join) now pass a format whitelist of concat, mov and
matroska. ffmpeg applies it to every file the list opens, so a listed file
that is a playlist or manifest cannot pull in other files, while mp4, mov and
webm joins work as before.

* fix(producer): resume reuses only segments this install recorded

Segment manifests are now signed with an HMAC keyed by a per-install secret
kept in the HyperFrames config folder, outside every project. Resume trusts a
manifest only when its signature checks out, so a segment folder copied from
another machine or shipped inside a project is captured again, while a
render's own interrupted run resumes as before.

* docs(producer): restore the segment path ordering comment and rewrap resume docs

* fix(producer): replace an empty or short resume key file

A key file too short to use is now replaced by a fresh key instead of
disabling resume for good. A missing key is still linked into place, so
renders that create it at the same time share one key; a test runs eight
processes against one path to check that.

* fix(producer): warn under --resume when no resume key is available

When the resume key can be neither read nor created, for example on a
read-only home folder, a file system without hard links or a serverless
runtime, --resume now logs one warning that every segment will be captured
again instead of only reporting zero complete segments.

* fix(engine): fail a concat join at a list entry ffmpeg refuses

The concat demuxer ends the stream at a listed file it cannot open and ffmpeg
still exits 0, which cut the output short without an error. -xerror on the
concat input makes the join fail instead. mp4, mov and webm joins still exit
0.

* fix(producer): resume checks each reused segment's SHA-256

Each finished segment's SHA-256 is now recorded in the signed manifest. The
hash is taken once when the segment closes, and on resume only the files
about to be reused are hashed again, so a file swapped for another of the
same size is captured again.

* docs(cli): note that resume re-checks segment hashes and recaptures older segments once

* fix(studio-server): proxy joins only its own pieces, through the shared concat input

Studio's chunked proxy copy now names its pieces with a tag keyed by the
user's preview token, so pieces that arrive inside a project folder sit at
names it never looks up and every piece is encoded fresh. A stopped copy of
the user's own still continues from its finished pieces.

The piece join uses concatListInputArgs, now in @hyperframes/parsers so the
engine, producer and Studio share it. It allows only local files in the
concat, mov or matroska formats and fails at a refused entry. The cache sweep
recognizes both tagged and older piece names.

* test(parsers): prove the concat protocol whitelist with a data: entry

ffmpeg already refuses http:// in a concat list opened from a file, so the
test passed without the whitelist. A data: entry opens by default; the test
now asserts it is refused as not on the 'file' whitelist.

* fix(studio-server): only the copy's own tagged pieces count as lock progress

The copy lock counted any .part-<key>- file as the owner's progress, so a
piece shipped with a future modified time kept a stalled lock looking active.
It now counts only names under the copy's own tagged piece prefix. The cache
sweep removes untagged pieces past the usual age even while that copy runs,
and measures age in both directions so a future-dated piece is swept too.

* fix(studio-server): say once when proxy pieces cannot be keyed to the user

Without a preview token, piece names use a per-process secret, so pieces are
reused only within that Studio process. Studio now logs that once, so a copy
restarting from its first piece after a restart has a visible cause.

* test(studio-server): name the proxy join test for what it checks

* fix(producer): derive the segment manifest key from the preview token

Sign segment manifests with an HMAC key derived from the per-user preview
token instead of a separate key file. The token is created with an exclusive
open, so concurrent renders never end up with different keys, and it is only
used when the file is private to this user.

Resume now checks a segment's SHA-256 before probing it, and a real-ffmpeg
test documents how the concat join treats an entry that is itself an ffconcat
list.

* docs(producer): describe the manifest key per user and the no-token case
2026-11-18 16:32:45 +00:00
Miguel Ángel 4a73363322 chore: release v0.9.67 (#8185) 2026-11-18 14:56:46 +00:00
Wenbo ZhuandClaude Opus 5.5 fc289b0dfc fix(cli): play and present answer unknown paths with an inert refusal (SECOPS-2642 part 3) (#8160)
* fix(cli): play and present answer unknown paths with an inert refusal (SECOPS-2642 part 3)

An OAuth return that lands on the play or present port was a 404 document on
the same origin as the composition frame, so project script could read its
?code=&state= through a frame, a popup or the authorize redirect. Unknown
paths, missing composition files and any request carrying code or state now
get a fixed text/plain 404 on an opaque origin (CSP sandbox) that cannot be
framed and drops its opener (COOP same-origin).

play's app setup moves into an exported buildPlayApp so tests can serve it.

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

* fix(cli): trim the inert refusal's comments to the package share

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 14:55:42 +00:00
Miguel Ángel 1a82f6e9d6 chore: release v0.9.66 (#8172) 2026-11-18 12:11:13 +00:00
James RussoandClaude Opus 5.5 ed3f05a05b fix(aws-lambda): pin the shell ZIP route, gate ZIP headroom, match arm64 fonts to x86 (#8170)
- build-zip --source=chrome-headless-shell stages only the repo's pinned
  build (managedChromeVersion) and only when its folder matches the pinned
  digest (isPinnedHeadlessShell), instead of the newest folder in the cache.
  The folder cannot fit a ZIP function, so lambda deploy refuses
  --chrome-source chrome-headless-shell up front on either arch, and the
  docs say the arm64 video image is where the shell runs.
- build-zip prints the headroom under the unzipped gate, and a new
  "Lambda handler ZIP" workflow builds the ZIP on PRs that touch the code
  it bundles, so growth fails before merge rather than in the release job.
- The arm64 image keeps @sparticuz/chromium's fonts and fonts.conf from the
  handler ZIP (FONTCONFIG_PATH=/var/task/fonts) instead of liberation-fonts,
  so text falls back to the same fonts as on x86. The image workflow renders
  a mixed-script page on both arches and fails when any line resolves to
  different platform fonts.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:21:01 +00:00
Michael Wang 140b701403 fix(skills): the launcher's floor is 0.9.65, the oldest release Desktop ships (#8159)
* fix(skills): the launcher's floor is 0.9.65, the oldest release Desktop ships

The skill launcher now refuses any HyperFrames release older than 0.9.65, the oldest release
the HyperFrames Desktop app ships. This applies to --cli-version, to
HYPERFRAMES_STANDALONE_CLI_VERSION, to a helper started with --script and to a plugin manifest
pin. A standalone install's default npx range starts at 0.9.65. Every plugin manifest in this
repo already pins 0.9.65.

The skills guide and the plugin installation reference name the current floor, and a test
keeps them in step with the launcher. Desktop's release checks read the floor from the
published launcher, so a comment asks that it stay a string literal.

* test(skills): a helper started with --script forwards a release at the launcher's floor

The accept loop now also starts a --script helper, so all four paths are shown accepting 0.9.65.
2026-11-18 09:26:49 +00:00
James RussoandClaude Opus 5.5 81d73d2278 fix(aws-lambda): chrome-headless-shell 158 in the arm64 video image, sparticuz 153 in the x86 ZIP (#8155)
* fix(aws-lambda): run chrome-headless-shell 158 in the arm64 video image

The arm64 video image now installs Chrome for Testing's linux-arm64 chrome-headless-shell
158.0.8127.36, pinned by sha256 and fetched with curl -f, as the whole shell folder. The Lambda
Node 22 base has none of the shared libraries the shell links and no fonts, so the image installs
them from the base's repository at the same pinned release. The image sets
HYPERFRAMES_LAMBDA_CHROME_SOURCE and HYPERFRAMES_LAMBDA_CHROME_PATH itself, and the nested video
function no longer passes ChromeSource, which would override them. stage-arm64-image.ts stops
fetching the sparticuz arm64 pack and drops the ZIP's x86 sparticuz Chrome instead.

The x86 handler ZIP stays on @sparticuz/chromium, bumped from 148.0.0 to 153.0.0. It builds at
258,502,222 bytes unzipped, under Lambda's 262,144,000-byte limit and the 248 MiB in-house gate.

Two fixes for --source=chrome-headless-shell:
- build-zip.ts staged only the executable, which exits at launch without its ICU data and .pak
  files. It now stages the whole shell folder at chrome-headless-shell-linux64/.
- Nothing set HYPERFRAMES_LAMBDA_CHROME_PATH, which src/chromium.ts requires for that source.
  The SAM template and the CDK stack now set it to the bundled shell when ChromeSource asks for it.

Drops the unused @types/aws-lambda devDependency, which the dead-code audit reports whenever this
package's manifest changes.

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

* ci(publish): build the Lambda arm64 video image on an ARM runner

The video stage now installs Chrome's system libraries with microdnf, so it runs code for arm64.
The pack job built that image on ubuntu-latest with no emulation, which it could do only while the
stage copied files. A new lambda-video-image job builds it natively on ubuntu-24.04-arm, from the
handler zip whose sha256 the zip job reported, and reports the OCI tarball's sha256. Pack downloads
that tarball, checks the sha256 against the job's, and pins it as before.

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

* chore(aws-lambda): fit the comment ratchet and the package size budget

chromium.ts loses the two doc lines on BUNDLED_SHELL_DIR and BUNDLED_SHELL_PATH; the names and the
SAM template's comment already say what they are.

@hyperframes/aws-lambda's unpacked budget goes from 290,508 to 298,000 bytes. The package unpacks to
295,324 bytes, up from the shared chrome-headless-shell staging module the ZIP and image scripts now
import and from the README and docs that describe the two Chrome sources.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 09:07:46 +00:00
James RussoandClaude Opus 5.5 7930525024 build(chrome): pin chrome-headless-shell 158.0.8127.36 wherever the repo installs it (#8145)
The engine ceiling moves from Beta 152.0.7977.30 to stable 158.0.8127.36, with its Chrome for
Testing digests. The places that installed `@stable` or an older pin follow it: the CI test
workspace, the regression test image, the k8s and Cloud Run examples, the CLI render image
(amd64) and the Lambda build hint. The motion-blur nightly keeps its pinned-versus-stable
comparison: the pin leg now uses the workspace's pinned shell, and a stable leg fetches stable.

The chat regression golden is regenerated on 158. Chrome 157 renders it pixel-identically to
158, so the previous golden recorded Chrome 152's paint of a background-clip:text phrase whose
word spans start at opacity 0.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 07:17:16 +00:00
3ee095bdec fix(player): keep the video playing when you jump to another moment (#7719)
Clicking or dragging the scrubber while a film played left it paused at
the new spot, and `paused` turned true without a `pause` event. The
controls now hold a playing film during the press and play on from where
it is released, like a <video>'s own controls; a paused film stays
paused. A touch scrub no longer replays as mouse events.

seek() gains an opt-in { keepPlaying: true } for hosts (keyboard seeks,
chapter jumps). A plain seek(t), and setting currentTime, still land
paused, so existing callers keep their behavior.

The packed player tarball grows 339 bytes (158705 to 159044, packed with
pnpm 10.17.1 as CI does). main sat 11 bytes under the 1% gate, so the
packed budget moves to 159100; the unpacked size stays within budget.

Co-authored-by: robinebers <16515780+robinebers@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
2026-11-18 05:21:17 +00:00
terencecho e99cd75b42 fix(cli): run global updates from the home directory (#8131)
* fix(cli): run global updates from the home directory

* fix(cli): skip self-updates inside package scripts and explain unsafe homes
2026-11-18 04:41:57 +00:00
a9b4745f1f feat(player): add customizable branding to the preview player (#7718)
A page that embeds <hyperframes-player> can now give it its own play,
pause and volume icons and its own loading logo, by putting elements with
a slot attribute inside the player. Anything the page leaves out keeps
today's HyperFrames look.

Co-authored-by: robinebers <16515780+robinebers@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
2026-11-18 04:10:18 +00:00
Michael Wang 63c8f8ef66 fix(skills): the launcher never starts a CLI older than its security floor (#8125)
The skill launcher raises its floor to 0.9.64, the oldest release with every
protection for projects received from someone else. The floor applies to a
plugin pin, to --cli-version and to HYPERFRAMES_STANDALONE_CLI_VERSION. A
release below it is refused with a message that names the floor.

The skill lifecycle reference no longer sends the agent back to the project's
pinned release after a failed check. The agent stops and reports, and runs
the old release only when the person asks for it. The CLI notice for a
project that pins a newer release now says the pin is the person's choice.
2026-11-18 00:56:38 +00:00
Michael Wang c27adb35ff fix(cli): media-use scripts read the host's kept record copy as the CLI does (#8119)
The media-use copy of the received-files rule now reads the host app's kept
copy of an expected project's record, as the CLI does. It adds back each kept
entry whose path still holds something, checks the folder identity for a
project found only by dev and ino, and counts every file as received when the
copy has no list, is doubted, a link, oversized, unparsable or another
project's.

In both the CLI and the copy:
- a kept copy whose identity names another folder counts every file as
  received instead of being ignored;
- a kept copy that fails its first read, for example because the app replaced
  it mid-read, is read once more before every file counts as received;
- a kept copy named both by path and by dev and ino is read once.

The docs no longer suggest that the app's next read restores a kept entry
whose file is gone.
2026-11-17 23:57:13 +00:00
Miguel Ángel 32ff8b3323 chore: release v0.9.65 (#8121) 2026-11-17 23:19:45 +00:00
Michael Wang 3f3fa67f9c fix(producer): charge generated mount scripts and scoped styles to the budget (#8094)
* fix(producer): charge generated mount scripts and scoped styles to the expansion budget

The expansion budget charged only the source bytes of each mounted file.
The inliner wraps every inline script in kilobytes of scoping code and
prefixes every style rule with the host's scope, so tiny scripts or a long
composition id over many rules assembled a page hundreds of times larger
than its source.

The inliner now reports what it generates through a chargeEmitted option.
Each wrapped script is charged once built. Each style rule reserves an upper
bound before it is scoped and settles to its real size after, so no rule is
built past the limit. Generated output has its own 32 MB allowance.

* fix(core): reserve the separator postcss re-joins scoped selectors with

The per-rule reservation summed a bound per selector but left out the
separator. postcss's selectors setter re-joins the list with the first
separator in the authored selector, so a wide first separator over many
selectors grew the rule past its reservation before it was charged.

* test(core): give the scoper bound test the same time limit as its neighbour
2026-11-17 22:53:11 +00:00
terencecho 414adffb82 fix(skills): select standalone CLI releases through the launcher (#8102)
* fix(skills): select standalone CLI releases through the launcher

* fix(cli): clarify release commands and share launcher validation
2026-11-17 21:41:22 +00:00
Michael Wang 183bf2a416 fix(cli): keep files received that a host's kept record still lists (#8100)
* fix(cli): keep files received that a host's kept record still lists

When the received-state file names a project as expected and the host
keeps its own copy of that project's record beside the state file, the
received-file checks read the record together with each entry that copy
lists whose path still holds something. A record shortened or emptied
outside the host no longer makes those files read as the person's own.
A kept copy with no list, a doubted one, a link or one that cannot be
read counts every file as received; with no kept copy, nothing changes.

* fix(cli): keep a record's own lines when the host's kept copy cannot be read

A kept copy with no list, or one that cannot be read, now counts every
file as received through its own entry, named by the kept copy's path,
instead of hiding the record's lines from Studio's rename and move
tracking. A copy found only by folder identity counts only when its
identity matches the folder, and a copy that disappears mid-read counts
as no copy.

* docs(cli): say a kept entry whose file is gone is not added back
2026-11-17 19:04:26 +00:00
Michael Wang 4a59fef2d0 fix(cli): say a listed received file is gone, and drop a media file's line on rename (#8098)
* fix(cli): say a listed received file is gone, and drop a media file's line on rename

Follow-up to the change that keeps a deleted received page listed.

- The render warning for a listed file that no longer exists now says it
  is gone and how to clear it.
- A listed file whose name was already a media name drops its old line
  when renamed to another media name, so repeated renames leave no
  dead lines.
- The docs say that any listed file that is not media by its first bytes
  stays listed after a delete, and that the line can sit in a record
  above or inside the project.
- A test restores content after a plain Studio delete and checks that
  outside files stay refused.

* test(cli): match the gone-file warning without a POSIX path, for Windows
2026-11-17 18:50:20 +00:00
Miguel Ángel f291b12598 chore: release v0.9.64 (#8097)
* chore: release v0.9.64

* chore: list #8090 and #8092 in the v0.9.64 notes
2026-11-17 18:25:31 +00:00
Michael Wang e099c7d0cb fix(cli): keep a deleted received page listed in the received-files record (#8090)
A Studio delete took a received page's line off the record, and files
created afterwards were not followed. A script in the preview could
delete every received page and create it again with new bytes, so the
project no longer counted as received and outside files were read.

A deleted page, stylesheet or script now stays listed, so whatever is
written in its place counts as received. A received page renamed to a
media name keeps its old line too. Deleted or renamed media, fonts and
images still drop off, so a media-only project keeps working.
2026-11-17 17:42:25 +00:00
Miguel Ángel 94cc7558e7 docs: say Desktop exports on your computer are unlimited on every plan (#8093)
Free's 5 cloud exports a month read as a cap on every export. One sentence in the FAQ's cost answer and on the Export page says local exports are unlimited.
2026-11-17 17:28:18 +00:00
WaterrrForeverandClaude Fable 5.2 820d63d7f9 feat(cli): check finds text over a face, measure cuts names resumed takes, measure hands (#8074)
* feat(cli): check reports text drawn over a face in a video

The layout audit reports text painted in front of an opaque video with its
word boxes and where the video's frame lands; Node finds the faces in the
video file with the detector `measure face` uses and adds a `text_over_face`
finding (info from 5% of the face covered, warning from 30%) with
`coveredFraction` and `faceRect`. `layout.faceCheck` in the report says
whether the pass looked. `data-layout-allow-on-face` waives it.

Also reads a two-token `object-position` whose first token is "50%" as the
horizontal one.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

* feat(cli): measure cuts names the shot a take resumes

A shot that returns to an earlier camera setup after at least one other
shot (a wide take, a close-up cut into it, the wide take again) carries
`continues`: the index in `shots` of the shot it resumes. It is read from
the signatures `cuts` already decodes, by the scene's edges, so a person
who has moved or an exposure that drifted does not hide the match.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

* feat(cli): measure hands follows a hand through a clip

`measure hands <video>` reports where a hand's palm (with the hand's
size), index fingertip or pinch is in each sampled frame of a stretch of
up to 15 s, from MediaPipe's hand landmarker. A frame with no such hand
is null, never filled in. The landmarker runs in the CLI's headless
Chrome on a page answered from disk; its code and model are not shipped
and are downloaded on first use, pinned by size and sha256, into the
trusted cache.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

* fix(cli): text_over_face is info only, and a stalled OpenCV download no longer stalls check

The face detector can take texture for a face, so text_over_face is
reported as info however much of the face is covered and never fails
--strict.

check passes its deadline and a 30 s limit into the detector's first-use
OpenCV download. A download that does not answer costs the face pass
only: faceCheck is { ran: false, reason }, the other findings are kept
and the process exits.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-17 17:16:20 +00:00
Miguel Ángel b22ca1a58e fix(release): count every pusher of a release, need a second maintainer, date approvals (#8076)
* 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
2026-11-17 16:55:33 +00:00
Michael Wang 90de9b6196 fix(cli): a project .env provider key prints a note when it is used (#8056)
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.
2026-11-17 16:52:55 +00:00
Miguel Ángel e86594759c chore: release v0.9.63 (#8080) 2026-11-17 15:55:44 +00:00
Miguel Ángel fbcdf4cad7 chore: release v0.9.62 (#8075) 2026-11-17 14:15:36 +00:00
Miguel Ángel c106793f79 fix(release): publish to npm with the job's OIDC token, not a stored token (#8070)
* 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
2026-11-17 12:20:49 +00:00
Miguel Ángel 3599623f92 chore: release v0.9.61 (#8051) 2026-11-17 10:56:12 +00:00
Miguel Ángel 4807799c4e fix(publish): a stable release needs a maintainer's approval, not any account's (#8062)
* 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
2026-11-17 09:33:45 +00:00
James RussoandClaude Opus 5.5 39347da9de fix(cli): leave files from outside the project out of Lambda and Cloud Run site uploads (#8060)
* fix(cli): leave files from outside the project out of Lambda and Cloud Run site uploads

A site upload for `lambda` or `cloudrun` followed every symlink in the project and
shipped what it pointed at, wherever that was on the machine. `publish` and `cloud
render` already ask first. Site uploads now leave a file or folder linked in from
outside the project out and name each one; `--include-outside-files` (or
`includeOutsideFiles` in the SDK's deploySite, renderToLambda and renderToCloudRun)
uploads them. publishProjectArchive called without a prepared archive now leaves
outside files out too, since nothing approved them.

— Rames

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

* fix(producer): drop the new option comments the comment ratchet refuses

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 09:25:25 +00:00
Xuanru Li 5ea86450a2 fix(cli): a host can name projects whose received files are expected or all received (#8025)
* fix(cli): a host can name projects whose received files are expected or all received

HYPERFRAMES_RECEIVED_STATE_FILE points at a JSON file a host app keeps,
listing project folders (by path, and optionally by device and inode) as
"expected" or "all". For an expected project, a missing received-files
record counts every file as received and is not started afresh; for an
all project, every file counts as received whatever the record lists. A
state file that is named but cannot be read counts every file as received.

A record lock dated in the future is taken over like a stale one.

* fix(cli): read host provenance state through one file handle

* fix(cli): canonicalize host state paths like record writes

* test(cli): expect canonical received warning paths
2026-11-17 08:54:39 +00:00
Michael Wang b29e40d707 fix(producer): cap a render's total sub-composition expansion (#8045)
* fix(producer): cap a render's total sub-composition expansion

The 16 MB limit checked each composition file alone, so a few small files
that mount each other many times assembled a page far larger, and the
pre-flight walk and sub-composition compile redid their work for every mount.

The pre-flight walk now reads each file once and charges every mount to one
budget: 32 MB of composition HTML across at most 10,000 mounts. Past either
limit the render fails with the existing non-retryable COMPOSITION_TOO_LARGE
error, before compiling. Sub-composition compilation handles each path once,
and the inliner charges each mount to the same budget as it builds the page.

* docs: describe the total sub-composition expansion limit

* fix(producer): check each mount path and read each fallback file once

The pre-flight walk resolved and checked a mount's path on disk for every
mount, and the inliner's disk fallback did the same for every mount it
inlined. Both now do it once per path, so a refused fan-out costs about
half a second instead of several. The test now covers both a fan-out the
pre-flight refuses and one inside templates, which only the inliner sees.

* fix(producer): the pre-flight charges mounts inside templates to the budget

The pre-flight walk could not see mounts inside a <template>, so a
template-wrapped fan-out was only refused by the inliner, after seconds of
work. The walk now charges those mounts to the same budget without
reporting them, since the inliner still only warns about a broken one.
The refusal now names which limit it passed, and the tests assert the
mount count instead of a time.
2026-11-17 07:55:06 +00:00
Michael Wang 14c4e4c268 fix(cli): a project .env provider key gives way to the person's own credential (#8041)
* fix(cli): a project .env provider key gives way to the person's own credential

A project .env could set OPENROUTER_API_KEY, GEMINI_API_KEY, GOOGLE_API_KEY,
the Vertex settings or ELEVENLABS_API_KEY and outrank a credential the person
set in their shell or saved settings. The earlier rule covered only received
projects; a cloned or downloaded project still won.

Now every project .env provider key is unset, with a note naming the file,
when a competing provider has a credential from a surer source: the shell or
saved settings first, then the person's own project .env, then a received
one. A project key with no competing credential is still used, model and
timeout settings still apply, and the media-use scripts note an ElevenLabs
key from any project .env before speech starts.

In the CLI process an own-project key yields only within the vision choice;
the media-use scripts remake the Gemini audio choice from the passed key
origins.

* fix(cli): weigh an own project's provider key only against credentials its feature can use

Review found that the global yield removed a person's own project keys where
the shell credential could not do the job: snapshot's Gemini key next to a
shell OpenRouter key, and a Gemini key that music needs next to a shell
service account.

- Startup keeps the received-project rule only.
- Capture drops a project .env vision key only when the shell or settings
  hold another complete vision credential; the two Vertex parts are one
  credential and are not weighed against each other.
- A key dropped once is not brought back when capture re-reads the same .env,
  so its note prints once.
- In the audio scripts, an own project's Gemini key gives way only to the
  other Gemini API key, which speech and music both accept, and an own
  ElevenLabs key stays for an explicit provider choice.
2026-11-17 07:20:22 +00:00
terencecho 8a13b2cafa feat(producer): enforce expected output dimensions before capture (#7871) 2026-11-17 05:37:05 +00:00
Miguel Ángel 5f6007ffc4 ci: publish a stable release from the push that merges its release PR (#8020)
* 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
2026-11-17 05:20:53 +00:00
Andy CheighandClaude Opus 5.5 19743ea094 fix(studio): the copied render command carries no composition text a shell can run (#8012)
* 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>
2026-11-17 05:05:28 +00:00
Michael Wang 8239fe4702 fix: the dev Studio's renders follow the received-project rule, and a received project's .env keys never replace the person's own (#8004)
* fix(studio): dev Studio renders apply the received-project rule for outside files

The Vite Studio adapter started every render with files from outside the
project allowed. It now asks the CLI's outsideAssetsAllowed, the same check
the CLI's embedded Studio, hyperframes render and benchmark use. A project
whose received-files record lists code files, or cannot be read, renders
without files from outside the project, and the reason prints with a
[studio] prefix.

The adapter loads the rule from the CLI source through the dev server, as it
already does for background removal. It runs only from a source checkout, so
studio takes no package dependency on the CLI.

* fix(cli): a received project's .env provider key never replaces your own credential

A received project's .env could set OPENROUTER_API_KEY, GEMINI_API_KEY,
GOOGLE_API_KEY or Vertex settings that outranked a vision or Gemini
credential the person set in the shell, so capture, snapshot describe and
media-use speech and music could send content to another account.

After the CLI and capture load a project .env, each provider key it set is
unset when that .env came with a received project (a received-files record
lists it, or a record cannot be read) and the person has their own
credential for a competing provider. One stderr line names the key, the
.env file and the credential used instead.

A person's own project .env keeps its keys and its current precedence, so
an OPENROUTER_API_KEY in a project .env still wins over a Gemini key in the
shell, as the docs describe. Voice needs no change: the person's HeyGen
credential already ranks above ElevenLabs.

* fix(cli,media-use): media-use scripts apply the received .env rule, ElevenLabs included

The media-use audio scripts read the project .env again, so a Gemini key the
CLI had left out came back. They now apply the same rule after loading: a
key from a received project's .env gives way to the person's own credential
for a competing provider. GEMINI_API_KEY and GOOGLE_API_KEY give way to the
person's Gemini key or service account. ELEVENLABS_API_KEY gives way to the
person's HeyGen sign-in, saved key or shell key. A dropped key gets one
stderr line that names the file and the credential used instead.

A received ElevenLabs key that is still used, because the person has no
competing credential, gets one stderr line naming the .env before speech
starts. hyperframes media-use tells the engine which keys it took from a
project .env (HYPERFRAMES_PROJECT_ENV_ORIGINS), so a key the CLI loaded is
not mistaken for the shell's.

When the project's folders are too many to scan for received-files
records, the CLI's note now says the project's origin could not be
checked, instead of calling it a received project.

* refactor(studio): check the shape of the CLI's outside-files rule before calling it

The Vite adapter loads outsideAssetsAllowed from the CLI source at run time.
It now checks that the export is a function and treats only a true result
as allowed, instead of casting the module's export.

* docs(auth): a received project's ElevenLabs key gives way to your HeyGen credential

* test(studio): load the received-project rule before render waits start
2026-11-17 05:04:15 +00:00
Michael Wang 9fae4ffd81 ci(publish): a prerelease tag publishes only to an allow-listed dist-tag (#7963)
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.
2026-11-17 04:35:57 +00:00
Michael Wang e58fb3249b fix(cli): render --docker applies the received-project rule on the host (#8016)
* fix(cli): render --docker applies the received-files rule decided on the host

The container mounts only the project, so it cannot see a received-files record
in a folder above it. The host now makes that check for single and batch Docker
renders and passes --refuse-outside-files into the container when it refuses
outside files.

* fix(cli): a Docker batch decides the received-files rule once

A batch render now applies the received-files rule once and hands the result to
every row, so it warns once instead of once per row. A test now drives renderDocker
itself and checks the docker run arguments it starts.
2026-11-17 04:10:20 +00:00
James RussoandClaude Opus 5.5 22b615f1a7 fix(cli): files from outside the project are uploaded only once approved (#7995)
* fix(cli): files from outside the project are uploaded only once approved

publish, cloud render and feedback --file-issue copied every image, video, audio,
font and CSS file a composition named from outside the project folder, and every
project file that links outside it, and only listed them. A project that came from
someone else could pull a file from anywhere on the uploader's disk into an upload.

Now each such file needs approval. In a terminal the command lists them and asks,
defaulting to no; a yes is remembered per project in the CLI's config folder
(~/.hyperframes/outside-files.json), never in the project. --yes, --json, --dry-run
and unattended runs leave them out with a warning naming each file and saying how
to include it. --include-outside-files uploads them without asking.

— Rames

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

* test(cli): check the approvals file mode only where files have POSIX modes

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 03:34:57 +00:00
Michael Wang 346579b6b9 fix(cli): compare and keyframes --shot serve only the files a bare HTML file names (#8006)
* fix(cli): compare and keyframes --shot serve only the files a bare HTML file names

A bare .html file given to compare or keyframes --shot is staged with
only the files its markup, stylesheets and sub-compositions name inside
its own folder, and only types a composition loads. Private files stay
out. A scene its project's index.html mounts is staged from the
project, so it keeps its shell.

* fix(cli): stage root-relative names, string imports, SVG links and grading tables

A bare HTML file's staging now also copies the files named by a
leading-slash URL (resolved against the staged folder), a string-form
CSS @import, an SVG xlink:href and the LUT of data-color-grading.
compare and keyframes --shot print one line naming any file they left
out. The CLI docs describe the single-file rule.
2026-11-17 03:27:12 +00:00