Commit Graph
7546 Commits
Author SHA1 Message Date
Miguel Ángel a82ee10c68 feat(producer): a failed render says which file was gone again, looking only in its own folders (#8168)
* feat(producer): a render that fails on a missing file says what was gone again

Restores the diagnostic the previous commit on main took out, as it was; the commits after it confine what it looks at.

* test(producer): render failure diagnostics never probe a path from error text or outside the render

* fix(producer): probe a missing path only from a real error, inside the render's folders

describeMissingPath now reads only the path Node set on an ENOENT error, never
one quoted in a message the page can write, and looks on disk only under the
render's temp root, extract cache or work folder. Any other path is named from
its text, so a network share is never contacted and the facts cannot tell an
existing path from a missing one.

* test(producer): a missing-path probe never passes an outside link or climbs above its folder

* fix(producer): walk down from the render's own folder and check each link before following it

* build(producer): give the packed size budget its 5% headroom with the missing-file diagnostic back
2026-11-18 13:41:39 +00:00
Miguel Ángel 579feb02ee fix(studio): sealed previews fill scene children, clip parents and first-frame counts (#8180)
* test(studio): a sealed scene's children and clip parents fill as an open preview's do

* fix(studio): a sealed preview's scene children and clip parents come from the editing port

* test(studio): a sealed preview's first-frame event carries its clips and length

* fix(studio): a sealed preview's first-frame event counts its clips from the document copy

* refactor(studio): drop two comments the names already carry
2026-11-18 13:35:14 +00:00
Miguel Ángel 67410727e6 perf(core): count an svg id scope's renames once, not on every stylesheet it rewrites (#8182)
* test(core): reading an svg id scope's size never walks its ids

* perf(core): count an svg id scope's renames once, not on every stylesheet it rewrites
2026-11-18 13:07:42 +00:00
Miguel Ángel 3db2da06c9 fix(cli): the very-many-files received-render test stops timing out on Windows (#8179)
* test(cli): time where the very-many-files case spends its time on each runner

* fix(cli): the received-render size tests cap the walk instead of writing 20,000 entries
2026-11-18 12:48:24 +00:00
Miguel Ángel f38e1e6def fix(studio-server): an inserted scene names its file from the project root, as the renderer reads it (#8150)
* fix(studio-server): an inserted scene names its file from the project root, as the renderer reads it

* test(studio-server): keep a test comment under the line limit
2026-11-18 12:47:29 +00:00
Miguel Ángel 2efb55ecb5 fix(studio): refused group, freeze frame and animation saves keep the server's status (#8178)
* fix(studio): refused group, freeze frame and animation saves keep the server's status

* refactor(studio): withStatus says what it does without a comment
2026-11-18 12:39:41 +00:00
Miguel Ángel 4bdf9181b4 fix(producer): fetch each remote script and stylesheet once, a few at a time, within the size limit (#8153)
* test(producer): remote scripts and stylesheets inlined at compile time stay within the size limit

* fix(producer): fetch each remote script and stylesheet once, a few at a time, within the size limit

Every inlined copy is charged to the render's expansion budget as it arrives;
going over fails the compile with COMPOSITION_TOO_LARGE and stops the
downloads still queued. Remote CSS is spliced in literally, so `$` sequences
in it are no longer expanded.

* fix(producer): drop the budget label comment the comment gate counts

* fix(producer): count a remote script when it arrives and stop the queue on an integrity mismatch

* test(producer): font normalization tests answer Google Fonts from a stub, not the network

* style(producer): wrap the stubbed font response
2026-11-18 12:16:51 +00:00
Miguel Ángel 75992d82ad fix(studio): a 3D slider drag previews live in a sealed preview (#8148) 2026-11-18 12:12:09 +00:00
Miguel Ángel 1a82f6e9d6 chore: release v0.9.66 (#8172) v0.9.66 2026-11-18 12:11:13 +00:00
James RussoandClaude Opus 5.5 c696c0e157 chore(aws-lambda): give the packed size budget its usual 5% headroom (#8176)
#8173 set the budget to 82,000 against 81,378 bytes measured, about 0.8%
over. The budget file's own rule is 5% above measured, so the next small
change would trip it again: ceil(81,378 × 1.05) = 85,447.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 12:09:00 +00:00
Miguel Ángel b90b8d1bb3 test(studio): edit accuracy waits for Studio to report the film loaded (#8175)
The bench's openStudio now waits in the page for Studio's own word that the
composition loaded (studio_look reports a duration) under the one 90 s boot
budget, instead of a separate 30 s poll that failed a case Studio was still
loading after a reload under load. A boot that never loads names Studio's last
report, and seekBound names the condition it was still waiting on.

hiddenTarget no longer throws on a preview frame detached mid-scan: puppeteer
throws that synchronously, so the per-frame .catch never ran.
2026-11-18 12:05:44 +00:00
Miguel Ángel 94d06663b1 revert(producer): a render that fails on a missing file stops naming what was gone, for now (#8174)
* revert(producer): a render that fails on a missing file stops naming what was gone, for now

This reverts commit cfea8cfff5 (#7955). The detail comes back in a follow-up that only looks inside the folders the render owns.

* revert(producer): name the files the #7955 revert removes in the deletion guard
2026-11-18 11:34:57 +00:00
James RussoandClaude Opus 5.5 61d65e7177 fix(aws-lambda): match the shell to its own pin, ship only hashed files, refuse the shell ZIP in CDK and SAM (#8173)
* fix(aws-lambda): match the shell to its own pin, ship only hashed files, refuse the shell ZIP in CDK and SAM

Review follow-ups to the pinned shell route:
- build-zip --source=chrome-headless-shell accepts the folder only when its
  digest is pinned for this version, not for any pinned build.
- It leaves out the files the digest skips (debug.log and chrome_debug.log,
  which Chrome writes as it runs), so nothing unhashed ships.
- The CDK construct throws on chromeSource "chrome-headless-shell" and the
  SAM template allows only sparticuz, as lambda deploy already refused it:
  a shell ZIP cannot fit a function. The CHROME_PATH wiring for that ZIP is
  gone with it.

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

* chore(aws-lambda): raise the packed size budget to 82,000 bytes

The shipped build-zip script now checks the shell against its own
version's pin and skips the files the digest leaves out. That takes the
tarball to 81,378 bytes in CI, over the 80,500 budget's 1% tolerance;
main was already within about 200 bytes of it.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 11:25:22 +00:00
Miguel Ángel 9acf268680 test(player): one hung Safari run no longer fails every Safari run after it (#8169) 2026-11-18 11:02:23 +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
Miguel Ángel b525686e7e fix(studio): property panel style and attribute edits show in a sealed preview (#8149)
* test(studio): property panel edits in a sealed preview reach the frame's element

* fix(studio): property panel style and attribute edits show in a sealed preview

* fix(studio): keep live property saves synchronous and use the runtime's realm-safe element check

* fix(studio): a sealed edit's put-back never replaces a newer edit

* refactor(studio): keep the sealed save wait private

* fix(studio): check a sealed edit's put-back reply without the helper main removed
2026-11-18 10:11:16 +00:00
Miguel Ángel 640cb37929 test(studio): share one sealed preview frame that delivers messages like a browser (#8165)
* test(studio): share one sealed preview frame that delivers messages like a browser

* test(studio): name the sealed frame's port wrapper instead of commenting it

* fix(ci): the capture check treats .test-helpers files as tests, like the rest of the repo

* test(studio): keep the sealed frame's delivery helper private

* fix(studio): keep test helpers out of Studio's typecheck, like core does
2026-11-18 09:57:22 +00:00
Miguel Ángel bb55c1ea7e fix(compiler): rebase composition asset paths from the file read and charge what they add (#8166)
* test(producer): a deep or query-stretched composition folder stays within the size limit

* fix(compiler): rebase composition asset paths from the file read and charge what they add

A mount's references now rebase from the project file the render read for
it, so a query or fragment in data-composition-src no longer lengthens every
rebased path. Every byte a rebased reference adds, including the entry file's
own rebase, is charged to the render's expansion budget as it is produced.

* test(producer): close the font embedding block after the rebase
2026-11-18 09:50:35 +00:00
Michael Wang 420f14d155 fix(cli): figma commands print manifest and folder text with visible escapes (#8126)
* fix(cli): figma commands print manifest and folder text with visible escapes

figma asset prints a manifest row's id, path and description, and the <img> snippet built
from them. These lines, the index.md regeneration warning and the tokens 'wrote' line now go
through terminalText, so control characters show as visible escapes. The manifest file and the
returned records are unchanged.

* test(cli): run the figma escape fixtures where file names may hold control characters
2026-11-18 09:35:03 +00:00
Michael Wang 3e788fb15a fix(cli): show control characters in printed names as visible escapes (#8008)
* fix(cli): project folder names print control characters as visible escapes

check, info, compositions, benchmark, play, present and preview printed the
project folder name, and in places the project path, straight to the
terminal. A folder name can hold escape bytes on Linux and macOS, so a
received project could move the cursor, rewrite earlier lines, set the
window title or write the clipboard. Those lines now go through
terminalText(), as validate, snapshot, layout and lint already do. This
covers the preview summary, --status, --stop, --list and --kill-all lines,
and the check report path. The CLI's own colours stay, and --json output is
unchanged.

The play page also HTML-escapes the name in its title and footer, as the
present page does.

* fix(cli): preview --selection and --context print Studio text as visible escapes

The human output of preview --selection and --context printed the selected
element's label, source file, target and thumbnail URL, and the preview
server's project name, straight to the terminal. These come from the
composition or from whichever preview server answers, so control characters
in them could move the cursor, rewrite earlier lines, set the window title
or write the clipboard. They now go through terminalText(), as do the
failure messages these commands print. The CLI's own colours stay, and
--json output is unchanged.

* fix(cli): cloud get, list and delete print server fields as visible escapes

The human output of cloud get printed render fields from the server, such
as the failure message, title, composition and URLs, straight to the
terminal. A failure message can quote text from the rendered project, so
control characters in it could move the cursor, rewrite earlier lines, set
the window title or write the clipboard. cloud get, cloud list (rows and
the next-page token) and cloud delete now pass those fields through
terminalText(). The CLI's own colours stay, and --json output is unchanged.

* fix(inspector): the live inspection stamp gives the page only the generation id

prepareLiveInspection wrote the project's absolute path into the preview
page as window.__hfLiveInspection.project. Nothing in the page reads it, but
any composition script on that page could, which told it the account name
and folder layout. The page now gets only the generation id; the project
path stays with the host that prepared the page.

* fix(skills): locate.mjs keeps its grid font in a private per-run folder

locate.mjs drew its grid labels with a font at the fixed shared path
/tmp/locate-font.ttf. It used whatever file was already there and copied a
system font onto that path otherwise, following any link in its place. On a
machine shared with other accounts, someone else could plant that file
first, so the grid showed wrong numbers, a file appeared where they chose,
or every run failed.

The font is now copied into a folder made with mkdtemp (mode 0700) for each
run and removed when the run ends, so no file another account can create is
read or written. The skills manifest hash is regenerated.

* fix: escape the check report path and lint warnings, and harden locate.mjs font cleanup

check's report path notice and its not-recorded warning, and preview's
"Lint did not finish" warning, now print control characters as visible
escapes, like the other lines that carry the project path.

locate.mjs escapes the font path for ffmpeg's filter syntax, so a temp
folder with ':', ',', quotes or brackets in its name still works, and it
removes its font folder when the run is stopped by SIGINT or SIGTERM before
re-raising the signal.

play and present share one HTML escape helper.

* refactor(cli): keep the shared HTML escape helper within the comment budget

* fix: one HTML escape helper for the CLI, and locate.mjs escapes its font path in one pass

The sign-in callback page uses the shared escapeHtml helper, which now also
escapes single quotes.

locate.mjs escapes the font path for ffmpeg's option list and filtergraph
in a single replacement with the same result as before, and removes its
font folder on SIGHUP as well as SIGINT and SIGTERM.

* fix(cli): escape render output paths and cloud upload names

A finished render printed its output path and the desktop app hint raw.
The default output path sits under the project folder and is named after
it, so the folder name reached the terminal on every render. Batch renders
printed row output paths and the manifest path raw, and cloud render
printed the archive name in its upload progress lines and walked file
names in its left-out warnings raw. These lines now go through
terminalText() or terminalLines(). --json output is unchanged.
2026-11-18 09:30: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
Miguel Ángel 3b79b1858e fix(producer): inline a local font only while the page stays within its size limit (#8152)
* test(producer): a font many rules name stays within the page's size limit

* fix(producer): inline a local font only while the page stays within its size limit

Only url() sources inside @font-face rules are replaced, and every inlined
copy is charged to the render's expansion budget. Once the budget is spent,
the remaining references keep loading the font from its file.

* fix(producer): keep the font anchoring test and name the fit-or-skip charge
2026-11-18 08:37:17 +00:00
Miguel Ángel e623031f3a fix(studio): a sealed preview's element reads are bounded, and a frame with no agent answers at once (#8055)
* fix(studio): a sealed preview's element reads are bounded, and a frame with no agent answers at once

* fix(studio): a sealed preview's sources and style names are bounded too, never cut
2026-11-18 08:36:06 +00:00
Miguel Ángel e95cdf7d76 fix(core): each editing client takes its own port, so a sealed preview answers Studio again (#8154)
* test(core): two editing clients of one preview frame each get their replies

* fix(core): each editing client takes its own port, so a sealed preview answers Studio again
2026-11-18 08:34:12 +00:00
Miguel Ángel 5bd3e3242c fix(core): keep SVG id renaming linear in the page size and within the render size limit (#8147)
* test(core): SVG id renaming shares its table, looks up only named ids, caps and charges what it adds

* fix(core): SVG id renaming shares one table, caps id prefixes and charges the bytes it adds

* test(core): a long namespace is hashed once per mount

* fix(core): sanitize and hash each mount's namespace once, before minting its ids

* test(core): page goldens carry the regenerated selector alias bundle
2026-11-18 08:31:56 +00:00
Miguel Ángel eb7dc14e89 chore(producer): keep the link read-through comment within the line limit (#8146) 2026-11-18 08:31:46 +00:00
Michael Wang 7ea0129530 fix(studio): check every file a folder move or delete takes along (#8143)
A folder move or delete in Studio checked each file inside only by its
name. A script that package.json runs from a subfolder could be moved
aside or deleted with its folder. A move could also land a file on a
path a direct write refuses, such as a script package.json runs or
mise/config.toml, by moving a folder onto the right name.

Now each entry in the folder is checked at its current path with the
same rules a direct delete or rename uses, including the package.json
scripts. For a move, it is also checked at the path where it would
arrive. Ordinary folder moves still work.
2026-11-18 08:31:08 +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
Miguel Ángel d574ded1ec fix(studio): a sealed preview takes its film's size from the player (#7967)
* fix(studio): a sealed preview takes its film's size from the player

A sealed preview frame refuses Studio's reads, so the size reader found no
document and Studio kept a 16:9 stage and no size for anything placed on
the picture. For a sealed frame it now reads the size its player got from
the runtime, once the player is ready, and the preview reads it again when
the player reports it.

* fix(studio): a sealed preview's size reader keeps its files' comment share

* refactor(studio): the player's size callback reaches its newest owner through one stable call

* fix(studio): a sealed preview reads its size once its film is ready to show, with no new player prop

* test(studio): the preview's mock player loads once, as a frame does
2026-11-18 06:59:47 +00:00
Miguel Ángel 12a2f83c49 fix(core): keep the styles of a composition whose id contains $ patterns (#8141)
* test(core): a composition id with $ patterns scopes as text, not as a replace pattern

* fix(core): scoping writes a composition id's $ as text, at compile time and in the runtime script
2026-11-18 06:53:30 +00:00
Vance IngallsandClaude Sonnet 5.5 c6e3f30bea fix(compiler): bound composition variable styles and variable media sources (#8144)
* fix(compiler): bound composition variable styles and variable media sources

Charge every compile-time composition-variable rule against a size budget
and stop emitting once it is exceeded. The render compiler shares one
CompositionExpansionBudget between mounts, variable styles and variable
media sources; other callers get a 32 MiB core default. Host
data-variable-values are now parsed once per host instead of once per
declarer. Bound media sources over 8 KiB or holding control characters are
refused, and every src written is charged.

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

* fix(producer): trim bound media sources and name the variable budgets in errors

Bind the trimmed value, as a browser does, so a trailing newline no longer
makes compile-time probing disagree with the runtime; refuse only interior
control characters or values over 8 KiB, and log the refusal as a warning.
The generated-bytes error now says which of variable styles or variable
media sources overran. Adds a with-mount test for the after-inline budget.

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

* fix(producer): trim comments added to htmlCompiler to keep its comment share down

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

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-17 23:11:40 -08:00
Miguel Ángel cfea8cfff5 fix(producer): a render that fails on a missing file says what was gone (#7955)
* fix(producer): a render that fails on a missing file says what was gone

* fix(producer): a failed look at what was missing never hides the render's own error

The missing-path probe now returns nothing when it throws, reads through at most four links and only
links that point into the temp root or the cache folder, names a removed folder by its own name, treats
a custom cache folder as the cache, and skips programs that could not start.

* refactor(producer): split the missing-path link walk into its own step
2026-11-18 06:36:23 +00:00
Miguel Ángel 01331014d8 fix(core): a clip that stops downloading no longer holds the preview in Buffering forever (#8138)
* fix(core): a clip that stops downloading no longer holds the preview in Buffering forever

* fix(core): the stuck-clip bound also holds in a hidden tab
2026-11-18 06:15:41 +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
Ular Kimsanov dcdd340715 test(lint): fail when a RegExp is built from text that is not escaped (#8128)
A tag name went into new RegExp unescaped, so a page could hang or crash
the linter (#8028). This test reads every RegExp the lint package builds
and fails when a template input is not escapeRegExp(...), an escaped*
name or an ALL_CAPS constant. Three inputs that cannot carry page text
are listed with the reason.
2026-11-18 04:15:53 +00:00
Ular Kimsanov 9a096d72f3 fix(media-use): escape control characters in the remaining resolve and cube-validate lines (#8059)
#8013 escaped resolve's results, recipes, stats and error lines, and
#8087 the adopt skip line. A few resolve lines still printed their
values raw: argument errors that repeat --type, --provider, --from,
--reuse and the --for path, the measured-grade note and the
similar-asset hint that repeats the intent. cube-validate's error can
quote a value from the LUT file. They now go through the same
terminalText copy, so a control character shows as \xNN. --json output
is unchanged.
2026-11-18 04:15:50 +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
andybpan ebddc42486 fix(media): keep each index.md row on one line and show control characters as escapes (#8127)
The .media/index.md generators (figma's mediaIndex.ts and media-use's
index-gen.mjs) turned only CR and LF in a record into a space. Vertical
tab, form feed, NEL, U+2028 and U+2029 still ended a row early for
readers that treat them as line breaks, and other control characters
(NUL, ESC, BEL, C1) reached the file as raw bytes.

- Every line-ending character now becomes a space.
- Other control characters are written as visible \xNN escapes through
  the existing terminalText helper; tabs stay as they are.
- Both generators and the skill copy change together, so their output
  stays byte-identical.
2026-11-18 03:05:02 +00:00
Miguel Ángel e6cee094b1 fix(cli): tests read opencv.js from a CI cache, never a CDN mid-test (#7968)
* fix(cli): tests read opencv.js from a CI cache, never a CDN mid-test

* chore(ci): re-pin the cli test job after its opencv cache step

* chore(cli): one-line note on the opencv cache copy
2026-11-18 02:02:15 +00:00
Miguel Ángel c569417bb5 fix(studio): crop and scale resize work in a sealed preview (#8005)
* test(studio): sealed preview crop and scale resize read the frame's values

* fix(studio): crop and scale resize work in a sealed preview

* test(studio): a sealed preview's crop lift and resize box survive lost or bad frame replies

* fix(studio): a sealed preview's crop lift and resize box survive lost or bad frame replies

* refactor(studio): the crop's stylesheet clip under a lift is read in its own step

* test(studio): the frame crop-lift helper answers the lift it just sent
2026-11-18 01:44:51 +00:00
andybpan 5f06e1b0a3 fix(core): treat files package managers run by default as tool-trusted (#8129)
npm, pnpm, yarn and bun run `node-gyp rebuild` on install when a binding.gyp
is present and package.json has no install script, and a .gyp file can include
any .gyp or .gypi. npm, pnpm and yarn run `node server.js` for start when
package.json has no start script. A project from `hyperframes init` has
neither script, so both defaults apply.

toolTrustedFileKind now classifies .gyp/.gypi files and server.js, in every
spelling projectPathSegments folds, so Studio's file routes and the registry
installer refuse to write them. Rename and duplicate refusals now report
why: protected_path when the destination is inside the project, as POST and
PUT already do.
2026-11-18 01:32:34 +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 59fbb22eba fix(cli): say when check's face pass stopped a source at its time limit (#8122)
When the 30 s limit stops a guarded ffprobe or ffmpeg run, the line check prints for the
skipped source now ends "stopped after 30 s" instead of a generic read failure. Every
other message is unchanged.

A new test decodes a text-art file through readSamples's guarded path and expects
ffmpeg to refuse it, so dropping the demuxer list from that run fails the suite.
2026-11-17 23:57:15 +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 80bf6a9ddb fix(studio): slideshow scenes, block stacking, drill-down and shortcuts work in a sealed preview (#8118)
* fix(studio): slideshow scenes, block stacking, drill-down and shortcuts work in a sealed preview

* fix(studio): sealed preview keys act only with the preview focused; frame replies are validated
2026-11-17 23:36:08 +00:00
Miguel Ángel d94aa5e309 docs(ci): say the npm-publish environment needs a reviewer's approval (#8123) 2026-11-17 23:34:46 +00:00
Michael Wang cb2b51525e fix(cli): a rename keeps the received-files record listing the moved file (#8112)
* fix(cli): a rename keeps the received-files record listing the moved file

On a disk that tells letter case or Unicode forms apart, a Studio rename to a
name differing only in case or form followed the old spelling, so the record
dropped the file's only line while the file moved to the new name.

- onDiskPath folds a requested name onto an existing entry only when the disk
  opens the same file under both spellings, so the record follows the exact
  path the rename creates, spelled as the move spells it.
- After a move, an old non-media line goes only when the file left its old
  path, sits at the planned path (same identity or content), and another line
  lists that path. Otherwise the line stays, as it does for a delete.
- A refused move keeps a new line for a file another move already put there.

* docs(cli): word a rename helper comment as what it checks now

* test(cli): build the rename test folder by its native real path

On Windows the temp folder can carry an 8.3 short name, which onDiskPath
spells in full, as the native real path does.
2026-11-17 23:27:17 +00:00
Miguel Ángel 32ff8b3323 chore: release v0.9.65 (#8121) v0.9.65 2026-11-17 23:19:45 +00:00