Commit Graph
595 Commits
Author SHA1 Message Date
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
Michael Wang 5b2990fc10 fix(skills): locate.mjs reads the system font in place, not a shared /tmp copy (#8042)
locate.mjs copied a system font to the fixed path /tmp/locate-font.ttf and
trusted any file already there. Another local user could plant that path
first: a crafted font would mislabel the grid strips, a dangling link would
make the copy write through it, and an unreadable file would stop every run.

Pass the system font file to drawtext directly, quoted so a path with a
space parses. With no known font present, drawtext uses its default font.
2026-11-17 06:05:16 +00:00
Michael Wang 6115945cf4 fix(skills): run bundled TTS helpers from the skill folder, not the working directory (#8035)
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.
2026-11-17 05:52:10 +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 7623f4fa12 fix(cli): a received project's job log can't lower the credit limit, and publish names the project it updates (#7970)
* fix(cli): the credit limit counts no logged row below zero and resumes only keys this account sent

A job log row whose credits are negative or not finite now holds nothing,
so no row can lower the total spent against the limit. A logged job key
skips the limit check only when this account sent it before, as noted in
a per-account record in the config folder. A logged key it never sent is
priced as a new call, without the credits the log gives that key. Applied
to both copies of credit-limit.mjs.

* fix(cli): publish's prompt names the existing project it updates and says its visibility is kept

When the publish targets an existing project (an --update id, the folder's
.hyperframes/project.json, or this machine's earlier publish of the
folder), the confirmation now names that project and says it keeps its
current visibility, which may be public, instead of promising a private
upload. The id is shown as printable text only.

* docs(cli): credit-limit says a logged row never counts below zero

The earlier commit said no row can lower the total. That is not so: a
later row for the same key with credits 0 sets that key to zero, which is
how a refused call gives back its reservation and how a charge below the
estimate replaces it. What holds is that no row counts below zero.

* fix(cli): sent job keys are noted per account and project folder, privately and capped

A logged key now resumes unchecked only when this account sent it for the
same project folder, so a key sent for one project cannot skip the limit
in another. The record keeps its newest 10,000 keys, and the config
folder and key files are created readable by their owner only.

* fix(cli): publish's prompt names the existing project in every variant

Every prompt variant, --public included, now names the existing project a
publish would update. It says the update happens only when the person is
signed in and can access that project, and that otherwise a new project
is created, which is what a signed-out publish does.

* fix(cli): the credit limit reads this account's spending from its own ledger

Each account now keeps, in its config folder, a ledger of what its jobs in
each project folder hold: every charge, reservation and refund the CLI
logs is noted there too. The limit check counts this account's keys at
the ledger's value and ignores the project log's rows for them, so a row
a sync or a pull adds cannot lower them. Any other key in the project log
counts at the most it has been seen to hold, never less, and never lets a
call skip the check. This replaces the sent-key record; the ledger keeps
its newest 10,000 lines and is readable by its owner only.

* fix(cli): publish reads the sign-in before asking, so its prompt says what will happen

The credential is now read, and --update or --space without a login is
refused, before the confirmation prompt. The prompt names an existing
target project only for a login, which is the only case that updates it
in place; signed out or on an API key, the prompt describes the new
private upload that actually happens.

* fix(cli): creditsSpent skips a malformed or null job log line

One junk line in .hyperframes/heygen-jobs.jsonl no longer blocks every
priced call in the project; the reader skips it, as the account ledger
reader does. Applied to both copies of credit-limit.mjs.

* fix(cli): the credit limit refuses a paid call when it can't tell which account is signed in

Under a credit limit, a call whose signed-in account can't be named is
refused before anything is sent, since this account's ledger can't be
read or written then. With no limit set, nothing changes.

The ledger is trimmed through a temp file and a rename, and the project
being checked keeps its last line for every key it holds. A refusal that
counts credits from job log rows no longer in the project says so and
names the ledger file. The ledger scope notes that a moved or renamed
folder starts a new ledger. The private-mode check in the ledger test is
skipped on Windows, which has no POSIX modes.
2026-11-16 23:33:53 +00:00
Michael Wang 1463158a4b fix(lambda): uploads go only to a bucket the state machine's account owns (#7983)
The lambda commands read the bucket and state machine from
.hyperframes/lambda-stack-<name>.json, which arrives with any project
someone sends. A file naming another account's bucket made render,
render-batch and sites create upload the project there.

- renderToLambda pins ExpectedBucketOwner to the state machine ARN's
  account on every S3 request; deploySite takes expectedBucketOwner,
  which sites create and render-batch pass.
- The state file is read only as a plain file in a real .hyperframes
  folder, and its bucket, ARN, region and other fields are checked.
2026-11-16 23:17:54 +00:00
Michael Wang d5f0b1a5bf fix: nested .hyperframes stays private, capture page server checks Host, project manifests pin no CLI (#7927)
* fix(core): a .hyperframes folder in a subfolder stays private too

The private-file rule treated .hyperframes as the app's records folder only at
the project root. A project copied into a subfolder keeps its own
.hyperframes/, and its chat history, hand-off and other records there were
listed in the file tree and served by Studio's file and preview routes and by
the other file servers that share the rule.

A .hyperframes segment at any depth is now private, in every spelling Windows
opens. Studio's own files and the prepared-assets and requests folders stay
servable only at the root, the one place Studio reads and writes them. The file
tree also skips .hyperframes/backup at any depth.

* fix(cli): the capture --local-file page server answers only its own host

The page server that capture --local-file starts on a loopback port answered a
request whatever its Host header said. A site whose name resolves to 127.0.0.1
could then read the files it serves from the browser.

The server now refuses, before any file lookup, a request whose Host is not its
own loopback name and port, with the same isOwnLoopbackHost rule the static
project server and the engine file server use. Every response carries
X-Content-Type-Options: nosniff. The capture browser loads the page by
127.0.0.1 and its port, and fetchLocalPageUrl reads from disk, so both work as
before.

* fix(skills): a plugin manifest in the project pins no CLI release

The skills launcher read a plugin manifest from the folder above skills/
wherever the skills were installed. For a project-level install that folder is
the project itself or its .agents or .claude folder, so a plugin.json shipped
with a project could pin an old hyperframes release and turn off update checks
and standalone skill refreshes.

The launcher now reads a manifest only from a bundle of its own: a folder whose
name does not start with a dot and that is neither the folder the CLI works in
nor one that contains it. Plugin managers install bundles into their own
folders, so those keep their pin. A manifest anywhere else leaves the call the
same as with no manifest. A manifest that pins a release older than 0.9.34, the
launcher's floor, is refused. The agent-facing plugin rules and the skills
guide say the same.

* fix(skills): a plugin bundle inside the working folder pins only behind a dot folder

A package inside a monorepo could still pin the CLI: with the agent working at
the monorepo root, <mono>/packages/video/plugin.json sat beside a skills folder
the launcher took for a bundle.

The launcher now also refuses a bundle inside the working folder unless a
folder whose name starts with a dot lies between them, as .claude does in
~/.claude/plugins/cache when the agent works in the home folder. Bundles in
~/.claude/plugins, ~/.cursor/plugins and ~/.gemini/extensions keep their pin
from the home folder or a project. The plugin rules and the skills guide now
state the three conditions the launcher checks.

* docs(cli): a .hyperframes folder in a subfolder is left out and not served

The private-file rule now treats a .hyperframes/ folder at any depth as the
app's records. Files stored in one inside a subfolder, assets included, stay out
of uploads and are not served by Studio, preview or render. The cloud render
section now says so beside the rule it already describes.

* fix(cli): capture pages keep loading scripts with no or unlisted extensions

With nosniff on every response, a script the capture page server did not
know the type of (a .cjs file, or a file with no extension) was served as
application/octet-stream, and the browser refused to run it.

The server now names .cjs, .wasm, .xml, source maps, web manifests, CSV,
WebVTT, glTF and more audio, video and image types. A file whose type is still
unlisted is served without nosniff, so the browser sniffs it as it did before
and such a script runs. Every listed type and every empty error response keeps
nosniff.

* fix(share): sync and share leave out a .hyperframes folder below the root

The .hyperframes rules in the source path policy matched only at the project
root, so a copy's records in a subfolder, such as
sub/.hyperframes/agent-runs.jsonl, fell through to the default rule and
travelled with share and sync.

A new nested-hyperframes-state rule leaves out a .hyperframes folder at any
depth below the root. It sits before the first allow rule, as the contract's
rule order requires. The root folder's Studio files and other portable files
travel as before. Stored snapshot reads skip the new rule through
stored_manifest.legacy_rule_regexes, the shape the server and Desktop copies
already use, so snapshots and bindings captured earlier still read.
2026-11-16 07:18:57 +00:00
andybpanandClaude Opus 5.5 94e499d8cf fix(media-use): the carve bundle exports analyseCarveDynamics, so carve runs again (#7893)
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>
2026-11-16 06:42:11 +00:00
Miguel Ángel d796fd59ec docs(skills): style-sampling pulls the template every time, so a received copy is checked first (#7924)
* docs(skills): style-sampling pulls the template every time, so a received copy is checked first

* chore(skills): regenerate the skills manifest for the style-sampling change

* test(skills): style-sampling must pull before using a template, resuming included
2026-11-16 05:54:07 +00:00
Miguel Ángel 25c6035212 fix(media-use): carve runs its own copy of core's analysis, never the project's (#7926)
* 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
2026-11-16 05:52:09 +00:00
Michael Wang c2c6d8c599 fix(media-use): audio engine reads and writes only inside the project folder (#7897)
* fix(media-use): audio engine reads and writes only inside the project folder

A voice line id must be a plain file name and a recording path must stay
inside the project. The engine never writes through a link or into a folder
that leads outside the project. wait-bgm reads only the renderer's own log in
assets/bgm, and a carried-over BGM job keeps its pid and log only when that
log is the engine's own.

* fix(media-use): engine outputs and recordings stay inside the project

A recording that is a playlist or list naming other files is refused,
and ffmpeg is pinned to the probed format with file-only input. The
media manifest, its index, bgm_status.json and an in-project
audio_meta.json are never written through a link, and a .media folder
that leads outside the project is refused. Index cells keep each record
on one line. wait-bgm ignores a track path outside the project and
drops a pid whose log is not the engine's own.

* fix(cli): the published skills leave their test files out of the package
2026-11-16 04:42:30 +00:00
Miguel Ángel 98208241e7 fix(lint): keep agent-made scenes and sound effects on one timeline lane (#7775)
* 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
2026-11-16 01:50:04 +00:00
Michael Wang 756c2c6c1b fix(media-use): local models start outside the project folder (#7888)
* fix(media-use): local models start outside the project, so a model id never names a project folder

MusicGen, parakeet-mlx and the LTX video runner take Hugging Face ids that their loaders read as
a folder when one exists in the working directory. Each now starts in the home folder; transcribe
still resolves a ./ or ../ --model path against the caller's folder.

* fix(media-use): a relative runner override still names the caller's folder

HYPERFRAMES_PARAKEET and HYPERFRAMES_PYTHON values with a folder in them are made absolute
against the caller's folder before the runner starts in the home folder. Bare names keep their
PATH lookup.
2026-11-16 01:25:09 +00:00
Michael Wang 3fc3050bc3 fix(skills): run the CLI through the launcher for standalone installs too (#7879)
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.
2026-11-16 00:18:47 +00:00
Michael Wang de1ce68988 fix(cli): a project .env key is used only when nothing is saved (#7848)
A HEYGEN_API_KEY or HYPERFRAMES_API_KEY that a project .env sets now comes
after every credential the person saved or exported. The CLI resolver, the
media environment and the media-use skill use it only when there is no saved
login, no saved API key and no key in the shell. When one is used, a single
stderr line names the .env file.

An expired, foreign-client, unreadable or refused login now raises the login
error instead of switching to a project .env key, whether or not the folder
has a received-files record. A key exported in the shell, or set by the app
that launched the CLI, keeps its current place, and the host gateway path is
unchanged.
2026-11-15 17:59:08 +00:00
Michael Wang a7266e4c83 fix(cli): benchmark keeps received files' rule; a received .env key never replaces a login (#7837)
* fix(cli): benchmark applies the received-files rule for files outside the project

hyperframes benchmark now asks outsideAssetsAllowed() before it creates its
render jobs, the same check hyperframes render and the Studio render route
use. A project whose received-files record lists code files, or whose record
cannot be read, renders without files from outside the project.

* fix(cli): a received .env key never stands in for an expired login

A HeyGen key that a received project's .env set is now used only when no
login or API key is saved. When the saved login has expired, cannot refresh,
belongs to another OAuth client, or HeyGen refused its refresh, the CLI
resolver, afterRefreshFailure and the media-use skill's resolver raise the
login error instead of switching to that key. A person's own .env key and a
shell-exported key keep their current priority.

* fix(cli): a broken credentials file never gives way to a received .env key

A malformed or unreadable ~/.hyperframes/credentials now counts as a saved
credential when deciding whether a received project's .env key may be used.
The CLI resolver raises INVALID_STORE and the media-use skill says the file
can't be read. A person's own .env key keeps its current behaviour. The skill
now tells a person whose saved login belongs to another OAuth client to run
auth login rather than auth refresh.
2026-11-15 12:12:15 +00:00
Michael Wang 80b09cc94a fix(cli): nested received records only add; a received .env never picks the account; font names stay out of agent files (#7808)
* fix(cli): a file is received when any record at or above the staged folder lists it

A received-files record inside a staged subfolder could list nothing and
hide the project's own record, so outside references from received files
were copied into the upload again. Every record from the staged folder up
is now read: a nested record can add received files but never remove them.

* fix(cli): a HeyGen key from a project .env never replaces a saved credential

A HEYGEN_API_KEY or HYPERFRAMES_API_KEY that only the folder's .env set now
ranks after the person's stored login and saved API key, in the CLI resolver
(cloud render, publish, media helpers) and in the media-use skill scripts.
With no saved credential the project key still works, and the first use
prints one line naming the variable and the .env it came from. A key
exported in the shell keeps its current precedence.

* fix(cli): capture's agent files count the page's fonts instead of naming them

Font family names come from the captured page, and a short phrase passed the
plain-name check into AGENTS.md, CLAUDE.md and .cursorrules. The Brand Summary
now gives the number of font families and points to extracted/tokens.json,
which already holds the names as data.

* fix(cli): only a received project .env key gives way to a saved credential

A HeyGen key from a project .env now comes after the stored login and
saved API key only when that .env came in with a received project: a
received-files record at or above the folder lists it, or a record there
cannot be read. A person's own .env keeps its priority. The media-use skill
scripts read the same records and apply the same rule.

* fix(cli): a shell key wins over a received .env key under either name

* docs(cli): a received project's .env key comes after the saved login and key

* fix(cli): drop the duplicate font count from capture's agent files

The Brand Summary repeated the font count the file table already gives,
and counted entries that are not font names. The table row stays.

* fix(cli): name the received-files record in the skill comment without a path
2026-11-15 06:34:14 +00:00
ClippyandClaude Opus 5.5 27af0ac8e1 chore(skills): move the Remotion data-driven corpus fixture to zod 4 (#7642)
Remotion 4's current studio already depends on zod 4, and the fixture's
schema uses only z.object, z.string, z.number and z.array.

— Clippy

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

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

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 19:58:01 +00:00
James RussoandClaude Opus 5.5 748bfe3b2b docs(skills): name the model next to each media-use image price (#7592)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 05:58:04 +00:00
James RussoandClaude Opus 5.5 fc7cb1aad8 feat(cli): heygen generate defaults images to nano-banana-2.1 (#7591)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 05:28:02 +00:00
James RussoandClaude Opus 5.5 88e74e088f feat(cli): price and validate minimax-h3-image, and image models at 1.5x (#7589)
Adds minimax-h3-image (2K) and minimax-h3-image-4k to media-use generate,
refuses aspect ratios and reference counts each /v3/images model does not
take, and re-bases every image price on the live rows: an API key pays 1.5x
the vendor price, a HyperFrames plan the hf_image rows at x1.6545.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 04:42:38 +00:00
Michael WangandClaude Opus 5.5 9a048ac019 fix: find helper programs without a by-name lookup or the Windows working directory (#7562)
* fix(parsers): find helper programs by walking PATH in-process

The trusted lookup ran `which` by name through the full PATH before
applying the trusted-folder rule, so a relative or project-local PATH
entry could supply the lookup program itself. Walk the trusted PATH
folders in-process on every platform, as Windows already did, for
findTrustedExecutable, findFfBinary and the doctor's unzip check.

The walk keeps what `which` did for valid installs: first match in PATH
order, regular files only, and a leading `~` in a PATH entry read as the
home folder.

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

* fix(cli): start the media-use engine with the Windows working-directory lookup off

mediaUseEngineEnv now sets NoDefaultCurrentDirectoryInExePath for the
engine on Windows itself instead of relying on the CLI's own environment,
and keeps a value the person set. When no PATH folder passes the trusted
rule, PATH names a folder that is never created rather than an empty
value, which a shell or execvp reads as the working directory.

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

* fix(skills): helper scripts skip the Windows working-directory program lookup

On Windows a program started by name is looked up in the working
directory before PATH. The plugin launcher and the media-use, hyperframes
and figma helper scripts run inside project folders and start ffmpeg,
ffprobe, Python and other tools by name, either through the launcher or
directly from a standalone skill install.

Each skill now ships a small module that sets
NoDefaultCurrentDirectoryInExePath for the process (keeping a value the
person set), and every script that starts programs imports it first, so
the helpers and every program they start skip the working directory.
Tools installed on PATH resolve as before; macOS and Linux are
unaffected. A test checks that each such script loads the module.

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

* fix(cli): ship the Windows lookup guard with the CLI's media-use scripts

The CLI build replaces the published media-use scripts/lib folder with
packages/cli/src/media-use/lib. That folder had no windows-exe-search.mjs,
so every bundled media-use script that imports it, including the engine
behind `hyperframes media-use`, failed to load on every platform.

The guard is now a generated copy in the CLI lib, next to the skill copies.
A parity test checks that each scripts/lib module a published media-use
script imports exists in the CLI lib.

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

* test(skills): load the win32 stub by file URL so the launcher test runs on Windows

On Windows, `node --import D:\...` reads the drive letter as a URL scheme
and fails before the launcher starts. The test now passes a file URL and
reports the child's stderr when it exits non-zero.

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

* fix(skills): resolve the Python helper's ffmpeg and drop relative PATH entries

extract-audio-data.py ran ffmpeg by bare name, which Windows looks up in
the working directory first. It now runs the absolute path that
trusted_program.find_program finds in absolute PATH folders outside the
working directory. A miss raises the same FileNotFoundError as before.

On macOS and Linux the shared guard now drops relative and empty PATH
entries, which point into the project folder, and leaves absolute ones in
order. If none is absolute, PATH is unset rather than left empty.

The guard census now also requires every skill Python script that imports
subprocess to resolve programs through trusted_program.

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

* test(skills): satisfy the Python UTF-8 and ffprobe argv sweeps

trusted_program.py carries the same UTF-8 stdio pin as every skill Python
script. The guard test's planted-program probe uses a literal-only argv,
which the ffprobe argv contract test reads as a capability check.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 18:47:16 +00:00
James RussoandClaude Opus 5.5 a8fe3a5b68 fix(skills): plugin launcher and media helpers run the pinned CLI, not a project copy (#7552)
* fix(skills): plugin launcher and media helpers run the pinned CLI, not a project copy

The plugin launcher now starts npx from the home folder, so the project's
node_modules, package.json bin and .npmrc cannot choose which CLI npm runs or
how it starts it. It names the project in HYPERFRAMES_PLUGIN_CWD and the CLI's
bin moves into that folder before anything else runs, then drops the variable
so nested runs keep the folder their caller gives them.

In --script mode the launcher hands itself over as HYPERFRAMES_CLI_ENTRY. The
media helpers (Kokoro voice, transcription, the resolve shim) run the CLI they
were handed, and stop with an actionable message when none was, instead of
resolving `npx hyperframes` from the project.

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

* fix(skills): keep the project name and require a home folder for npx

The CLI bin now sets PWD to the project folder after moving into it, because
npm's shell resets PWD to the folder npx started in and preview names the
project from PWD. The plugin launcher no longer falls back to the temp folder
when there is no home folder; it stops with an error instead, and only when it
is about to start npx.

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

* test(cli): type the bin test environment

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 11:28:10 +00:00
James RussoandClaude Opus 5.5 84799bdc59 fix: take helper programs only from install locations, never the project folder (#7524)
* fix(cli,parsers): take helper programs only from install locations, never the project folder

FFmpeg, FFprobe, whisper-cli, parakeet-mlx, Python and system Chrome are now
found through one shared rule: an absolute PATH entry outside the working
directory, or a fixed install dir. A relative PATH entry and any folder
inside the working directory are skipped, on every platform. Windows walks
PATH itself instead of asking `where`, which lists the working directory
first.

FFmpeg discovery no longer falls back to `.hyperframes/bin` or to an
installer package in the project's node_modules; an installer package
installed next to HyperFrames still works. The env overrides are unchanged.
The CLI skill reference stops suggesting the project-local folder.

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

* test(cli): give the PATH-lookup tests a fixed PATH on Windows

Windows now walks PATH instead of running `where`, so tests that faked
`where` output found the runner's real python and cmake. Both tests now set
PATH to a temp folder holding only the programs they expect.

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

* fix: report a missing helper program instead of running it by bare name

When no trusted FFmpeg or FFprobe is found, the engine, the producer's
probes and Studio's waveform, peak and audio-track helpers now report
"not found" with the HYPERFRAMES_FFMPEG_PATH / HYPERFRAMES_FFPROBE_PATH hint
instead of handing the bare name to the OS lookup. Callers that degraded
on a missing binary still do: runFfmpeg returns a spawn_error result, the
GPU and version probes report none, and Studio's audio helpers fail soft.

The Lambda handler names its bundled ffmpeg and ffprobe by path, since
they live under the task root, which is the working directory.

brew, git and cmake for the whisper.cpp install, and the clipboard tool
for `hyperframes add`, run by the absolute path the trusted lookup
approved. The media-use engine gets a PATH holding only trusted folders.

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

* fix(engine): fail a missing FFmpeg the way a failed spawn always has

Throwing from getFfmpegBinary turned every caller's missing-binary path
into a synchronous throw: the streaming encoder's "failure result, not a
throw" contract broke, and unit lanes that run without FFmpeg crashed at
module load. With no trusted copy the getters now return an absolute path
inside HyperFrames' own install that is never created, named for the
override to set. Spawning it fails with ENOENT exactly as before, and the
OS still never looks the bare name up. The call-site guards and fixture
changes that the throw needed are reverted.

The whisper install tests match git and cmake by name and skip the brew
case on Windows, where the lookup walks the real PATH.

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

* test(engine): pin the found FFmpeg before the HDR test looks it up as macOS on Windows

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 09:46:52 +00:00
terencecho 04947d99f7 feat(cli): share rendered videos through unified reviews (#7135)
* feat(cli): share rendered videos through unified reviews (#7135)

* feat(share): attach editable project sources to reviews (#7137)

* feat(share): measure local sharing outcomes (#7138)

* feat(cli): stage the sixty-day publish transition (#7136)

* feat(studio): share review pages from local preview (#7140)

Advertise the CLI sharing bridge before bootstrapping it so standalone Studio does not
request unsupported routes. Preserve origin and session checks.

Budget the intended sharing artifact: clean main packs at 8,060,519 bytes versus
8,162,979 with sharing (8,169,168 in CI). Required policy and Unicode tables, bundled
sharing code, and Studio controls account for the growth. Set the packed-only budget
to 8,577,627, following the 5% headroom convention; retain the unpacked cap and all
package checks.

* fix(share): persist refusals and improve CLI retry feedback

* fix(ci): restore render diagnostics and include sharing workspace

* fix(cli): keep sharing owner error codes stable

* fix(share): clarify update feedback and align audience changes

* fix(share): clarify updates and avoid scratch-file rerenders

* fix(cli): report active shares and preserve update channels

* fix(cli): resolve update channel when checking registry

* fix(ci): refresh sharing package budgets after rebase

* fix(share): require consent before uploading project files
2026-11-11 06:26:24 +00:00
PaprikaChenandClaude Opus 5.5 1a9fb8acb6 feat: opt-in 4:4:4 chroma for SDR MP4 masters (#5820)
* feat(engine): decouple transparent background from png capture format

PNG capture used to imply a cleared page background. A new
CaptureOptions.transparentBackground lets lossless opaque PNG capture
(4:4:4 MP4 output) keep the page background. Absent, it still follows
format === "png", so alpha output and motion blur are unchanged.

Opaque PNG skips drawElement, whose verification and worker-encode
paths are JPEG-only.

Refs #5555

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

* feat(engine): add 4:4:4 chroma option to getEncoderPreset

getEncoderPreset takes an optional chromaSubsampling ("420" by
default). "444" returns yuv444p for SDR MP4, so libx264 encodes the
High 4:4:4 Predictive profile and odd sizes need no even padding.
WebM, MOV and HDR presets ignore it. The ChromaSubsampling type is
exported for the producer.

Refs #5555

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

* feat(producer): chromaSubsampling render option with lossless png capture

RenderConfig.chromaSubsampling ("420" by default) opts an SDR MP4
render into 4:4:4. "444" encodes libx264 yuv444p and captures every
frame as opaque PNG: Chrome's quality-100 JPEG is already 4:2:0 on
beginFrame and screenshot capture, and drawElement can fall back to
screenshot mid-render, so PNG is the only capture that keeps the
colour. drawElement is turned off for these renders.

The probe and main capture options share resolveCaptureSurface, so
they cannot disagree on format, quality or background.

Formats other than mp4, GPU encoding and HDR output are rejected
before any work starts, auto-detected HDR sources fail before capture,
and distributed requests refuse 444. The default render is unchanged.

Refs #5555

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

* feat(producer,studio-server): accept chromaSubsampling on render routes

The shared parseEncoderOptions validates chromaSubsampling and answers
400 for "444" with a non-mp4 format, gpu, or force-hdr, so a request
that would come back 4:2:0 never starts a render. The Studio render
route, both Studio adapters and the producer HTTP server forward it.
The producer server also refuses "444" with outputDynamicRange "hdr",
which parseEncoderOptions cannot see.

No Studio UI control; the option is route-level like crf and hdrMode.

Refs #5555

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

* feat(cli): add --chroma-subsampling flag

`hyperframes render --chroma-subsampling 444` opts an SDR MP4 render
into full-resolution chroma (yuv444p with lossless PNG capture). The
default stays 420. The plan rejects 444 with a non-mp4 format, --gpu
or --hdr before anything renders, with a usage error that names the
conflicting flag.

The value reaches the local render request and, only when it is 444,
the Docker argv, so default Docker invocations are unchanged.

Refs #5555

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

* docs: document 4:4:4 chroma subsampling

Add a "4:4:4 masters" section to the rendering guide: when to use
--chroma-subsampling 444, why it captures PNG, the measured chroma gain
(large for text and UI, none for footage and gradients), its limits,
and a player compatibility table to be filled in from testing.

Document the flag in the CLI reference, the built-in rendering docs and
the hyperframes-cli skill reference (with the regenerated skills
manifest), and the chromaSubsampling option in the producer docs.

Refs #5555

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

* docs: add 4:4:4 player compatibility results

Fill the 4:4:4 compatibility table from testing H.264 High 4:4:4
Predictive output. Chrome 155, Edge 155, VLC 3.0, Safari on iOS 26.6
and Safari 26.6 on macOS play it, and so does AVFoundation on macOS
26.6, the framework QuickTime Player plays through. Firefox 157 on
Windows and both Windows media players do not.

Refs #5555

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

* docs: note the measured render cost of 4:4:4 output

Replace the vague "slower capture" note with measured numbers: a text
and UI composition rendered in about twice the default time, full-frame
footage in about three and a half times, because PNG encoding cost grows
with image detail.

Refs #5555

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

* fix(producer): reject chromaSubsampling 444 in distributed render config

Distributed configs have no chroma field and validateDistributedRenderConfig
ignored unknown keys, so a JS caller passing chromaSubsampling: "444" to the
Lambda or Cloud Run SDK got a 4:2:0 file with no error. Reject it, and make
the rendering guide say so precisely.

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

* test(producer): check a 444 render reaches the encoder as yuv444p

Every helper had tests, but nothing checked the orchestrator passes
chromaSubsampling through, so dropping it from the encoder preset or capture
surface would turn 444 renders back into 4:2:0 with all tests green. Render a
small fixture with "444" and with the default and check pix_fmt with ffprobe.

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

* refactor(producer): move the 444 drawElement gate into a helper

Keeps runCompileStage under the fallow complexity threshold.

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

* chore: keep comment share at or below the merge-base

comment-ratchet failed on 11 files this PR touched. Keep the 4:4:4
rationale once in chromaSubsampling.ts, move the distributed-render
reason into its error message, and cut the rest.

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

* test(producer): check a 444 render captures full-resolution chroma

The encoder check alone passes when chromaSubsampling is dropped from the
capture surface: frames are captured as JPEG and encoded yuv444p with
4:2:0 colour. Put a red/blue edge at an odd x, inside a 4:2:0 chroma
pair, and require the two pixels to differ in Cb.

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

* chore(producer): trim the chromaSubsampling.ts header to the package comment share

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

* fix: finish switching to capturesAlpha from #6262

The merge that adopted main's transparent / capturesAlpha left these files
uncommitted, so resolveCaptureSurface still returned transparentBackground.

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

* refactor(engine): use transparent / capturesAlpha from #6262

main added CaptureOptions.transparent and capturesAlpha (#6262), which do
what this PR's transparentBackground did. Use them, keep the PNG check in
drawElementWorkerEncodeEligible, and re-pin test-classification.mjs and
the skills manifest against current main.

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

* chore(producer): cut the 4:4:4 comment blocks to one to three lines

The reasoning lives in the PR description with the measurements.

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

* refactor: reconcile 4:4:4 chroma with latest main

Keep main's video-layer capture overrides, template entry resolution,
ProRes profile parsing and blur-differential tests alongside the chroma
option, and fold the encoder sub-parsers into one loop.

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

* chore: keep main's compile-stage tests and regenerate the skills manifest

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 00:20:55 +00:00
Michael WangandClaude Opus 5.5 84c7d02a19 fix(cli): keep project folders from choosing the programs and config the CLI runs (#7511)
* fix(cli): resolve helper programs from PATH, never the working directory

On Windows a bare command name is looked up in the working directory before
PATH. The CLI now sets NoDefaultCurrentDirectoryInExePath at startup, which
Node's spawn and cmd.exe both honor and child processes inherit, so tools
such as powershell.exe, taskkill and npx.cmd always come from PATH.

The shared ffmpeg/ffprobe resolver no longer scans the working directory on
Windows and skips relative PATH entries.

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

* fix(cli): keep Python helpers from importing files in the working directory

`python -c` and `python -m` put the working directory first on sys.path, so
a file in the project named like a probed module ran instead of the
installed package. Inline helper code now drops that entry before any
import, and `-m` helpers (pip) run through runpy after the same step. Paths
and arguments are unchanged.

On Windows, findPython also skips a `where` match in the working directory.

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

* fix(cli): run the skills installer and nested CLI calls independent of the project

The global skills install ran `npx skills@<pin>` in the current folder, so
npm could take the package or registry from that project's node_modules or
.npmrc. It now runs from the home folder; the install is global either way.

When the CLI starts the media-use engine it hands over its own entry file.
The local voice fallback and the audio helpers then run that same CLI with
the same Node instead of resolving `npx hyperframes` from the project.
Without a handed-over entry they behave as before.

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

* fix(media-use): load only provider keys from a project .env

The audio scripts copied every key of a project .env into their environment
except two. They now take the same kind of short allowlist the CLI uses:
HeyGen, ElevenLabs and Gemini API keys plus a few harmless settings. Program
overrides, runtime options, credential files and the credential store path
come only from the person's own environment.

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

* fix(cli): build whisper.cpp only from a pinned, verified release

The source-build fallback cloned the upstream default branch. It now clones
the v1.9.5 release tag and refuses to build unless the checkout is the
reviewed commit for that tag.

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

* fix(cli): keep registry caches apart and refuse config install targets

Registry cache file names now include a digest of the exact registry URL,
and each entry records the URL it came from, so one registry's cached
manifest is never read for another. Entries from older versions are
refetched once.

Registry installs refuse targets inside .git or any hidden directory, hidden
configuration files, and package.json, hyperframes.json and
hyperframes.lock.json. An example installed by `init` may still bring its
own package.json and .gitignore.

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

* fix(capture): keep page text to one line in agent files and validate Vertex keys

Capture writes AGENTS.md, CLAUDE.md and .cursorrules from the page's title,
font names and colours. Page text is now flattened to one short line and
colours must be hex values. Existing agent files that capture did not write
are kept, with a warning.

HYPERFRAMES_VERTEX_SERVICE_ACCOUNT must now be a plain service-account key
with a Google token endpoint; other credential types skip captioning with a
warning.

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

* test(cli): find the digest-named registry cache and trim a new file's comment

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

* fix(cli): match registry targets as Windows names them; skills install without HOME

Windows drops trailing dots and spaces from a path segment and reads name:stream as
name, so package.json. or .git./hooks reached the files the target rules refuse.
The global skills install now falls back to the temp folder when HOME does not exist.

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

* fix(cli): turn off the Windows working-directory lookup in every program entry

The warm-check server and client are their own tsup entries and copied the
environment before cli.js set NoDefaultCurrentDirectoryInExePath, so the server
spawned a bare powershell.exe that Windows could take from the project folder.
Every entry that hides child consoles now also loads windowsExeSearch first.

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

* fix(cli): refuse Windows short-name registry targets

A segment like CLAUDE~1 or PACKAG~1.JSO opens the long name on NTFS, so it
reached the files the target rules refuse. The trailing-dot and stream-name
normalization is removed: publication already rejects those segments.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-10 20:01:19 +00:00
WaterrrForever 007664e25a fix(reverse): give agents the sign-in reason to say, and catch stale CLIs that know reverse (#7488)
* fix(reverse): give agents the sign-in reason to say, and catch stale CLIs that know reverse

- `reverse start`'s signed-out `next` now carries a sentence the agent can say as is
  (why HeyGen, and that the HyperFrames account is the HeyGen account), asks for it at
  the start of the sign-in message, and on remote terminals has the agent send the
  device link and code before it waits.
- references/start.md: same ordering, an example that fits both login routes, and no
  links to or quotes from the instructions themselves.
- An old global install that knows `reverse start` but predates `next` was never caught:
  agent runs get no update notice and no auto-install, so it stays frozen. The skill now
  also treats `_meta.updateAvailable: true` from `reverse start` as an old install and
  runs the rest with `npx -y hyperframes@latest`; every CLI that knows `reverse start`
  already reports that field.

* fix(reverse): send remote terminals straight to device sign-in, reason in every link message

- `reverse start` now knows when no browser can open (the check `auth login` uses, moved
  to attendedTerminal): `login_command` is `auth login --device` and `next` asks for one
  message with the reason, the link and the code. The two-step route (a refused browser
  login, then a bare follow-up with the code) is where the reason got lost.
- Every message that gives the sign-in link starts with the reason; agents say they are
  waiting rather than quoting the skill, and give no file paths.
- The out-of-date line for an old global install goes in the next message to the person.

* fix(reverse): flag an older global install that shadows npx, and pin the run's release

- installerDetection: `shadowingInstall` finds the older global `hyperframes` that a plain
  `npx hyperframes` runs instead of this npx copy (first on PATH outside the npx cache), with
  the command that moves it. `detectInstaller` takes the entry to classify.
- `reverse start` run through npx opens `next` with that line as words to say, signed in or
  not. Skill prose alone did not get agents to tell the person.
- Skill: a signed-out `reverse start` with no `reverse.next` is also an old install, which
  covers a cold update cache; the run pins the release `@latest` resolved to.
2026-11-10 11:26:45 +00:00
James RussoandClaude Opus 5.5 0ba8941235 feat(cli): label GPT image prices as estimates and show the charged credits (#7351)
* feat(cli): label GPT image prices as estimates and show the charged credits

GPT Image generations on a HyperFrames plan are moving to fal's reported
vendor cost, so the pre-run figure is an estimate. The --plan basis for
gpt-image-2.5, 2.6 and 2.6-flare now reads "about N credits (charged at
vendor cost)". Nano Banana is unchanged.

When the /v3/images job carries charged.amount, generate reports it as
charged_credits and records it in the media ledger's provenance. Without
it, nothing new is printed. --max-credits is unchanged.

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

* feat(cli): keep 10% headroom under --max-credits for vendor-priced images

gpt-image-2.5, 2.6 and 2.6-flare are charged at the vendor's cost, so
--max-credits now refuses one when its estimate plus 10%, rounded up to a
whole credit, is over the limit. A 16:9 gpt-image-2.5 image (about 40
credits) is refused at --max-credits 40 and passes at 44. Other models keep
the plain estimate check. The refusal and the --max-credits help say so, and
the help notes this is not a hard ceiling.

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

* fix(cli): count only HyperFrames-credit charges, and keep headroom under the run's limit

Review fixes for the vendor-cost image work:
- charged_credits is reported only when the job's charged.pool is
  hyperframes_credits. A charge to api_credits or any other pool is in
  that pool's own unit, so an API-key caller no longer sees it as HF
  credits.
- runJob logs that charged amount, not the estimate, on a job's completion
  row in heygen-jobs.jsonl, so later credit-limit checks see the real total.
  Without a HyperFrames-credit charge the estimate is kept.
- The run's credit limit (.hyperframes/credit-limit.json) uses the same 10%
  headroom rule as --max-credits for gpt-image-2.5, 2.6 and 2.6-flare,
  through one shared limitCheck helper, with the same refusal wording.

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

* docs(media-use): say the credit limit is not a hard ceiling for GPT Image

A GPT Image call is admitted at its estimate plus 10% but charged the
vendor's cost, so it can still go past a run's credit limit. The media-use
skill, its HeyGen reference, the --max-credits help and the limit doc
strings now say so, and that a finished call's reported charge counts
toward the limit afterwards. Other models keep the "refuses what would go
past it" wording. No logic change.

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

* fix(cli): hold a running GPT Image call at its headroom under the project limit

A reserved or still-running vendor-priced call was logged at its plain
estimate, so two concurrent calls could each pass the 10% headroom check
and together go over. Log the headroom amount until HeyGen reports the
charge.

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

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-10 07:41:52 +00:00
WaterrrForever 37f1819f32 feat(skills): route a style outside the templates instead of listing them (#7450)
* feat(skills): route a style outside the templates instead of listing them

A request to make a new video in some film's style reached style-sampling,
which only knows its five templates and answered any other style with that
list. Now it says the style is not one of them and offers the two routes
that fit: rebuild a short video and give it the person's content
(reverse-any-video), or a new film on their topic that takes the style's
grammar (look.md, "From a reference"). The hyperframes routing table points
the same request at look.md.

* fix(skills): keep the reverse-any-video Chinese trigger to videos

「照着做一个」 matched any "make one like this" request. 「照着这个视频做一个」
keeps it to a video, as review on #7445 suggested.

* fix(skills): ask for an example video when a style is only named

Both routes for a style outside the templates work from a video, so a
style the person only names needs one example first (review on #7450).
2026-11-09 15:21:36 +00:00
WaterrrForever ad6f7858f6 feat(skills): reverse-any-video and style-sampling install with the core set (#7445)
* feat(skills): reverse-any-video and style-sampling install with the core set

A skill only triggers when it is installed. On demand these two rarely
were, so a request to copy a video or make an episode in a proven style
seldom reached them, and the entry skill named only one of them, in its
closing line.

- isCoreSkill, FALLBACK_CORE_SKILLS and the marketplace `core-skills`
  entry include both, so `init` and `skills update` install them. The
  `hyperframes` plugin already bundled every skill.
- `/hyperframes` routes to both from the top of its table: a video to
  copy or remake, and an episode in a proven style. Its budget takes
  +64 B for those two rows.
- `/reverse-any-video` triggers on "remake" and on 「复刻这个视频」
  「照着做一个」, inside the 320 B description cap.
- Every catalog surface lists both in the core group: CLAUDE.md,
  AGENTS.md, README, the skills guide, skill-lifecycle and the two init
  templates (still byte-identical).

* refactor(cli): keep comment share at the base in skillsManifest
2026-11-09 13:05:30 +00:00
Vance IngallsandClaude Sonnet 5.5 c38ac5438c feat(producer): distributed and range renders honour page motion blur (#7311)
* feat(producer): distributed and range renders honour page motion blur

A film with data-motion-blur="on" blurs the same way however it is rendered. plan() no longer
forces the synthetic job to pageMotionBlur "off", so the plan locks screenshot capture for a
blurred film as a whole render does, and renderChunk() no longer defaults the page's off switch
to "distributed-render". An explicit pageMotionBlur "off" in the config still stands the page down.

Hosted renders pick this up after the next OSS release and a producer pin bump; a render of a
blur-on film that goes distributed changes output then.

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

* test(producer): the default tier blurs the same in chunks; docs agree distributed renders blur

Two files compare plan -> renderChunk -> assemble with the tier attribute removed, so `auto`
(the filter tier) decides, against a whole render: held-card and callbacks (the muted-callback
path). The skill's motion reference no longer says distributed renders are off. The rewritten
R19 plan test gets 60 s for its three plan() calls.

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

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-09 09:10:46 +00:00
5e8abd7574 feat(cli): add 1440p resolution presets to --resolution (#7418)
* feat(cli): add 1440p resolution presets to --resolution

Adds landscape-1440p (2560x1440), portrait-1440p (1440x2560) and
square-1440p (1440x1440) next to the existing 4K, 720p and 480p tiers,
with the aliases 1440p, 2k and qhd plus 1440p-portrait and 1440p-square.
1440p joins the aspect-agnostic aliases, like 720p and 480p.

Every validator derives from CANVAS_DIMENSIONS, so no logic changes: a 4K
composition renders down to 1440p through the existing smaller-preset
path, and a 1280x720 composition supersamples to 1440p at an exact 2x.
A 1920x1080 composition is still refused by the non-integer-scale check
(4/3); fractional scale factors are not part of this change.

Refs #6309

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

* fix(cli): clarify 1440p aliases and repair skill validation

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-authored-by: James <james.russo@heygen.com>
2026-11-08 23:16:17 +00:00
Miguel Ángel f5bde9533f feat(media-use): the voice credits line names the real source, your recording or any vendor (#7380) 2026-11-07 20:32:48 +00:00
Miguel Ángel 14e598e5a1 feat(media-use): your own voice recording is a voice line, and speed applies to it (#7377)
* feat(media-use): your own voice recording is a voice line, and speed applies to it

* fix(media-use): regenerate the skills manifest and keep audio.mjs's header at its limit
2026-11-07 20:10:38 +00:00
Michael WangandClaude Opus 5.5 896a77c307 fix(cli): open stops the project's background preview first (#7297)
The desktop app can't run an edit while a preview of the project is
running, because the preview holds the project's history lock. Following
the hint that `preview --background` prints therefore left the app's edit
waiting until someone stopped the preview by hand.

`hyperframes open` now stops a background preview of the same project
before handing it to the app, and prints one line saying so. It only
stops a preview it can prove it started (a saved session whose wrapper
process still owns the server). Any other preview is left running, and
`open` prints the exact `preview --stop --port N` command instead. With
--json the result carries a `preview` field.

The hint that `preview` prints now says that `open` stops a background
preview, or that a foreground one must be stopped first. The project
template and the CLI skill's preview reference say the same.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-07 17:24:14 +00:00
Miguel Ángel 9ac2a2387a feat(check): name the saved report file and print one stderr line per check step (#7344)
* feat(check): every check step prints a line on stderr and repeats it every 30 s while it runs long

* feat(check): name the saved report file on stderr and tell agents not to use npm run

* fix(check): print a step's line once when the step starts, not on every progress ping

* style(check): wrap two long lines for oxfmt

* fix(check): say the report file is written unless a not-recorded warning follows

* chore(skills): refresh the skills manifest hash for the check doc line

* fix(check): keep the start line free of the not-recorded warning text
2026-11-07 06:45:31 +00:00
James RussoandClaude Opus 5.5 ab50e9c148 fix(cli): price GPT Image 2.6 and every GPT Image reference picture (#7307)
* fix(cli): price GPT Image 2.6 and every GPT Image reference picture

The media-use image estimate priced every non-default model as GPT Image 2.5 and
charged references at $0.0082 after the first. fal bills every reference picture,
the first one too, at about $0.0125, and the price book now does the same. GPT
Image 2.6 and 2.6-flare take 2.5's prices; nano-banana-2.1 gets its own; any
other model is not priced ahead instead of guessed.

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

* chore(cli): drop the new pricing comments to keep the comment share flat

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

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-06 21:59:59 +00:00
WaterrrForeverandClaude Opus 5.5 318724f5f4 feat(studio): show the agent's storyboard in a Storyboard tab beside the preview (#7284)
* feat(studio): show the agent's storyboard in a Storyboard tab beside the preview

The board an agent writes per the storyboard recipe (boards/storyboard.html,
or a root storyboard.html) now shows in Studio the way HyperFrames Desktop
shows it: a Preview | Storyboard strip over the preview panel, only while the
project has a board. Studio reads the page's class="frame" boxes into a board
of stills, with acts, titles, times and words, and one frame at a time with
arrow keys. A page with no frames shows as written in a script-less iframe.

A board written while Studio is open brings its tab to the front, as Desktop
does at the agent's stop. A rewrite of the page, a still beside it or
STORYBOARD.md reloads it in place, and a dot marks a rewrite seen from the
preview. "Show in preview" goes back to the film at the frame's start.

Notes, drawings and the go belong to Desktop's agent, so the board's bar
carries the desktop-app button. Its funnel events now say which button was
pressed (placement: header or storyboard).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* refactor(studio): split the storyboard view and its frame reader into smaller parts

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* docs(skills): the agent's storyboard stop points at the Storyboard tab, not the file

With the board shown beside the preview in Studio as in Desktop, the recipe's
stop and style-sampling's stop 1 tell the person to look in the Storyboard
tab, and to start a preview and give its link when none is running, instead
of handing over boards/storyboard.html to open from disk.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* fix(studio): the storyboard listens on Studio's own file-change channel, and its notes are trimmed

The board opened its own /api/events stream, which the Vite dev server
behind the runtime smoke does not serve. It now subscribes through
subscribeFileChanges, the one channel picker the external-change
coordinator already uses (test adapter, Vite HMR, then SSE), so dev and
built Studio deliver the same changes to both.

The new files' comments are cut to the package's share, and the recipe's
Storyboard-tab line moves to the paragraph that names the board, leaving
the stop step as it was.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* fix(studio): the board hears file changes through the coordinator, not a second subscription

The external-change coordinator stays the one subscriber to the file-change
transport (HMR in dev, SSE when built), as externalFileChangeOwnership
asserts. It announces each decoded change through fileChangeFanout, and the
storyboard listens there. Mounting EditorShell alone, as its tests do, no
longer opens an EventSource, and the coordinator file stays under the line cap.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* feat(studio): the storyboard's Open in desktop app asks the app to open on the board, and its card says why

- The storyboard bar's button posts `doc: "storyboard"` with its page id. The preview server passes only that value
  on, and `openInDesktop` writes it into `.hyperframes/desktop-cta.json` beside the page id, so the app can open the
  project on its Storyboard tab with Build in sight (hyperframes-internal reads it).
- The guide card opened from the storyboard says "Approve this storyboard in the desktop app" and "Comment on a frame,
  draw on it, then press Build", and its last step says the app opens on this storyboard. The header's card is
  unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* feat(studio): approve the storyboard in Studio; comments on frames stay in the desktop app

A Studio user without the desktop app had no way to approve the board from the tab, and the bar said approval was
in the desktop app, so the tab read as a dead end. Studio talks to the person's own agent through their chat, so the
bar's Approve copies "The storyboard is approved. Build the video from it." for them to paste to it, and says so in
a toast (or spells the words out when the clipboard refuses). Commenting and drawing on frames stay in the desktop
app. The storyboard recipe tells the agent those pasted words are the person's go.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* fix(studio): the storyboard's desktop card offers commenting, since approving now happens in Studio

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* fix(studio): hand-off intent before dispatch, steady film under the board, stills outside the board folder

- openInDesktop writes desktop-cta.json before sending the folder, so a running
  app reads the storyboard ask on arrival; a plain or header open drops an
  earlier storyboard ask; a failed open puts the earlier record back.
- PreviewStage keeps the film at one place in the tree with or without a board,
  so a board appearing never remounts it; the automatic switch goes through the
  same pause as a click, and a play while the board is up is paused.
- The board reloads when a still it draws changes, including a root board's
  stills/ and a boards/ page's ../assets.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* chore(cli): fit the Storyboard tab in the CLI's size budget; reword a record helper's doc

The CLI tarball carries Studio's build, which now holds the Storyboard tab; merged
with main it measures 7,982,002 bytes packed, 7 bytes past the 1% tolerance.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* fix(studio): hold the player while the storyboard covers the film

A pause after the fact let J's reverse loop schedule its next frame, so the
hidden film kept seeking. The stage now takes the player's own hold while the
board is up (and only when no one else holds it), so J, Space and playback
requests are refused before they start; Preview releases it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 16:16:21 +00:00
WaterrrForeverandClaude Opus 5.5 410a516cee fix(skills): reverse hands billing commands to the person instead of running them (#7314)
* fix(skills): reverse hands billing commands to the person instead of running them

The Snyk audit on skills.sh still fails reverse-any-video on E004 because the skill has the agent run
`billing subscribe` and `billing add-credits` itself. media-use, which hands the person the billing command
instead, passes the same audit.

reverse now does the same: on Free it gives the upgrade link and the subscribe command for the person to run,
and mid-run it gives one add-credits command for the run's total. It waits until they say they're done, then
starts again or relaunches the refused steps.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXQjEiSeVmhvTbJvSAw

* test(skills): pin reverse's billing handoff per payment section

start.md's opening said the agent runs every command, which contradicts the billing sections below it.
It now excludes `billing` and says the person opens and pays on the upgrade and add-on credits pages.

The test now checks the handoff itself. Both payment sections must give the person the command and
forbid running billing. Neither may tell the agent to run, execute or launch a billing command, and
SKILL.md must keep its prohibition. Each of those mutations, and main's start.md, fails the test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXQjEiSeVmhvTbJvSAw

* fix(skills): reverse hands over one add-credits for the run when an amount is unknown

"If a refusal prints no amount, give plain `billing add-credits` for that one" let the agent hand over a
purchase for each step with no amount, on top of the aggregate one. Now, if any refusal prints no amount, the
total is unknown and the person gets one plain add-credits for the whole run, never one per step.

The test now requires that sentence and rejects a per-step fallback in the out-of-credits section, even when
the aggregate sentence is still there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXQjEiSeVmhvTbJvSAw

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 11:19:34 +00:00
WaterrrForeverandClaude Opus 5.5 fc0b53361b fix(cli): media-use voices says whose clones it lists, and --voice takes language codes (#7261)
* fix(cli): media-use voices says whose clones it lists, and --voice takes language codes

`media-use voices` lists every clone the account's workspace can use, a teammate's
included, and HeyGen does not say who made each one. The command's description and
output (`whose`) now say so, and the style-sampling remix rule no longer reads
"One clone: use it": a clone is used only when the person names it as their own.

`--voice en`, `en-US`, `zh`, `zh-CN` and `cmn` were sent to HeyGen as language names
it does not list, so it answered with a multilingual voice ("Gail in car") and the CLI
used it. Codes now map to the English language name HeyGen lists, and a multilingual
voice offered for a language the request did not name is refused with the fix.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* chore(skills): regenerate the skills manifest

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* refactor(cli): keep languageName and the voices note module-private

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* fix(skills): a clone's id is not consent; use one only when the person says it is theirs

The remix guide used a voice id the person gave, or a unique prefix of one,
without asking whose clone it was. The workspace list includes teammates'
clones, so either path could voice a film with someone else's clone. Both
paths, and the `whose` line of `media-use voices`, now use a clone only when
the person says it is theirs or that its owner agreed. An id that is not a
clone in the list is a stock voice and is used as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* fix(skills): an id missing from the voices list is not a stock voice

`media-use voices` returns one page of private voices (20 by default), so a
teammate's clone can be absent from it. The remix guide treated an absent id
as stock and used it without asking. Now a given id or prefix is used only
when the person says it is theirs, that its owner agreed, or that it is a
HeyGen stock voice; otherwise the agent asks in its one round of questions.
The `whose` line says the list is one page and absence proves nothing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 09:07:45 +00:00
WaterrrForeverandClaude Opus 5.5 41b7aeeafb fix(cli): cloud render logs a line a minute while a job holds its status (#7262)
* fix(cli): cloud render logs a line a minute while a job holds its status

Outside a terminal, `cloud render` printed one line per status change, so a 3D shot
that renders for 20 minutes showed "rendering 2.1s" and nothing else. Agents read
that as a hang and killed jobs that later completed. The log now repeats the status
with its elapsed time once a minute, and the style-sampling remix guide says the
cloud gives no frame count and how to check a job the client stopped waiting for.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* chore(skills): regenerate the skills manifest

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

* refactor(cli): keep the still-running interval module-private

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HebQXPiLcYKQfvPWB3Fgxy

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 07:50:22 +00:00
Vance IngallsandClaude Sonnet 5.5 e2bb7da25d feat(core): auto motion blur draws with the filter tier (#7288)
* feat(core): auto motion blur draws with the filter tier

Capture stays available as data-motion-blur-tier="capture". auto now draws with the
filter tier (reasonCode tier-auto), so the capture-only defects leave the default path.
Removes the translation-only hand-off and its Discovery field, adds a filter arm to the
differential, and updates the check, guide, skill and Blur panel label.

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

* docs(core): measured cost and known limits of the filter tier, the new auto default

spacex-launch (77 movers) takes 2.9x the CPU of no blur on the filter tier and 1.7x on
capture; say so, and list the filter tier's measured limits (sweep D, E, F, I, O, B).

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

* docs(core): word the filter tier's cost and limits as measured, not as mechanism

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

* docs(core): do not say every filter-tier limit is pinned by a sweep test

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

* test(engine): split the blur differential so each file fits the flake gate's 120 s run

The filter arm moves to its own file and skips fixtures that already draw with the filter
tier; inside cases get their own file; a fixture's blur-off page is opened once per file.
Shared helpers live in __fixtures__/motionBlur/differentialPage.ts.

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

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-06 05:27:36 +00:00
Miguel Ángel 0a6746e1d6 fix(cli): an unknown command answers in a few lines and says what to run instead (#7247)
* fix(cli): an unknown command answers in a few lines and says what to run instead

* fix(cli): shorten the captions pointer and drop the redirect doc comments

* fix(cli): point the captions hint at the hyperframes skill's guide, and test the path exists

* chore(cli): regenerate the skills manifest for the hyperframes-cli skill edit
2026-11-05 15:35:10 +00:00
Miguel Ángel 216395e98e fix(cli): every settings file follows HYPERFRAMES_CONFIG_DIR (#7229)
* fix(cli): every settings file follows HYPERFRAMES_CONFIG_DIR

* fix(cli): the media-use skill copy reads its config from HYPERFRAMES_CONFIG_DIR too

* test(cli): expect the config folder as a normalized path on every platform

* chore(skills): refresh the media-use manifest hash

* fix(cli): a moved settings folder starts from ~/.hyperframes, keeping an opt-out

* fix(cli): drop the updater's unused path import

* style(cli): keep the settings-seed comment under 120 characters
2026-11-05 11:34:36 +00:00
WaterrrForeverandClaude Opus 5.5 7bebcb9fcb fix(skills): reword the billing lines the Snyk audit reads as hiding cost (#7218)
Behaviour is unchanged: on Free the plans page opens straight away, a
mid-run shortfall goes to add-on credits for the run's total, and cost is
never brought up unprompted. Lines like "without asking or naming a price"
and "never tell the person prices" read as hiding cost, so the skills now
say the page shows the price and payment happens only there, by the
person, and that cost is not volunteered.


Claude-Session: https://claude.ai/code/session_01HebQXQjEiSeVmhvTbJvSAw

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 08:11:50 +00:00
James RussoandClaude Opus 5.5 d452a6fad4 feat(registry): add path-traced-3d example with raster preview and path-traced export (#7219)
* feat(registry): add path-traced-3d example with raster preview and path-traced export

An opt-in Three.js starter: previews with raster rendering and exports with
three-gpu-pathtracer, from one scene file. three 0.180.0, three-gpu-pathtracer
0.0.24 and three-mesh-bvh 0.9.5 ship as one local, pinned ES module with their
licences and a rebuild recipe, so renders make no network requests and 2D
projects never load the tracer.

Setup is one buildReady promise that awaits library readiness promises only
and ends with a throwaway frame and a one-pixel readback. Frames are drawn in
the hf-seek listener through waitUntil, each time from zero with a fixed
sample count. Math.random is seeded while the scene and tracer are built,
because object ids order light sampling and the tracer's noise textures come
from it.

Adds a skill reference and a docs guide for the setup and seek contract, the
frozen clock, why scheduler.yield() waits hang, and sample/bounce cost.

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

* fix(registry): list path-traced-3d in CLI docs and tighten its notes

Add the example's section to the CLI examples doc, which docs.test.ts
requires for every registry example. Throw if the tracer reports compiling
but exposes no compile promise, instead of spinning renderSample(). Say that
three's object uuids set the tracer's sort order, that later-created objects
need the seed too, and that Date and performance.now read the current seek
time during a render rather than staying at 0.

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

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-05 06:40:37 +00:00
Miguel Ángel e976fdbfa1 fix(lint): a video gets no timing from its wrapper, and the docs and hints stop implying it (#7210) 2026-11-05 04:46:11 +00:00
Miguel Ángel 924bb64da6 fix(cli): lint and check accept --lint-verbose, and two skills stop teaching --describe false (#7201) 2026-11-05 02:22:27 +00:00