Commit Graph
2977 Commits
Author SHA1 Message Date
Vance Ingalls 4d1625fff5 fix(studio-server): drop leaked wav-path route + parent-pid from carve commit
packages/studio-server's routes/vst.ts, routes/vst.test.ts, and
vstSidecar.ts all had unrelated, uncommitted changes (a GET /vst/wav-path
route + its tests, and a --parent-pid sidecar spawn arg) sitting in the
working tree from an earlier separate session. A prior `git add <file>`
staged those files' entire current content, sweeping this unrelated work
into the carve-route commit alongside the intended POST /vst/carve
addition. Reverts wav-path and --parent-pid back out; the carve route
(this task's actual scope) and the resolveVstHostCommand export are
unaffected.
2026-07-16 18:53:19 -07:00
Vance Ingalls 482f44e7d3 feat(studio-server): add POST /vst/carve - voiceover carve-band analysis route 2026-07-16 18:53:18 -07:00
Vance Ingalls ef523e4399 fix(vst-host): drop unrelated serve --parent-pid leak from carve commit
packages/vst-host/src/hyperframes_vst/__main__.py's serve verb had
unrelated, uncommitted --parent-pid changes accidentally swept in by a
prior `git add` of the whole file. Reverts serve back to its
pre-existing committed form; the carve verb (this task's actual scope)
is unaffected.
2026-07-16 18:53:18 -07:00
Vance Ingalls 3da1bb8e17 feat(vst-host): carve CLI verb — voiceover analysis to bands JSON 2026-07-16 18:53:18 -07:00
Vance Ingalls 9515f74c17 feat(vst-host): spectral carve core — find voiceover presence bands 2026-07-16 18:53:18 -07:00
Vance Ingalls 78d7bbd933 fix(vst-host): route plugin loading through the pedalboard thread too
show_editor() failing with "Plugin UI windows can only be shown from
the main thread" turned out to be a symptom of a bigger constraint:
pedalboard requires every native VST3/AU load AND every show_editor
call in a process to happen on the exact same thread — whichever
thread first loads a plugin becomes that thread, and loading a second
plugin from a different thread raises RuntimeError outright; showing
an editor additionally requires that thread to be the true OS main
thread (a hard Cocoa constraint).

load-chain built its plugin chain via asyncio.to_thread (an arbitrary
pool thread), so by the time an editor's dedicated main-thread queue
tried to open a window, a different thread had already claimed
ownership. Route load-chain's build_chain call through the same
pedalboard-thread queue as show_editor whenever the chain contains a
non-builtin plugin (builtins never touch JUCE's native machinery, so
they keep using the thread pool — this also avoids requiring a
pedalboard-thread consumer for every test that only exercises
builtins).

Verified against a real installed VST3 (Valhalla FreqEcho): load +
open-editor no longer raises, previously reliably threw on every
attempt.
2026-07-16 18:53:17 -07:00
Vance Ingalls e7881ec537 fix(studio): suppress file-watcher reload for VST chain-file writes
VstSection's chain-file writes (add/remove effect, and the 2.5s
native-editor-state poll from the earlier persistence fix) never
stamped domEditSaveTimestampRef, unlike every other save path in the
app. The studio's file-watcher reloads the whole preview iframe for
any file change older than 4s relative to that stamp — so every
poll-triggered write reloaded the preview roughly every 2.5 seconds
while a plugin's native editor was open, re-issuing load-chain and
replacing the plugin instance the editor was still live-mutating with
a fresh default-state one. Parameter tweaks in the native GUI were
being silently discarded from the actually-streaming/rendering plugin.

Thread domEditSaveTimestampRef from StudioRightPanel through
PropertyPanel into VstSection and stamp it after every successful
chain-file PUT, matching the convention every other save path already
follows.
2026-07-16 18:53:17 -07:00
Vance Ingalls ce081d4b64 fix(studio): thread the sidecar auth token through the Vite dev adapter
startVstSidecar's Vite dev-mode adapter dropped the token field from
its response, so the browser's WebSocket handshake to the VST sidecar
was rejected under the auth check added for the security fix — the FX
panel and live preview both silently fell back to the "not available"
state. The CLI's embedded-mode adapter already passed the token
through correctly; this file's the missing sibling.

Found via manual end-to-end testing: packages/studio/vite.adapter.ts
sits outside packages/studio/tsconfig.json's `include: ["src"]`, so
`tsc --noEmit` never type-checked it and the missing field slipped
through review.
2026-07-16 18:53:17 -07:00
Vance IngallsandClaude Sonnet 5 acdec1310c fix(vst-host): require a shared-secret token on the sidecar WebSocket
Finding 2 of the final whole-branch review: the sidecar's loopback
WebSocket accepted any connection with no origin/auth check, so any
local process (or webpage that guessed/scanned the ephemeral port)
could drive load-chain to load arbitrary native plugin bundles or read
arbitrary files via wavPath.

server.py's VstServer now generates a per-process secrets.token_urlsafe
token, prints it alongside the ready line, and rejects the WebSocket
handshake via websockets' process_request hook unless the connecting
client presents it as a `?token=` query param. Threaded through:
studio-server's vstSidecar.ts (extended ready-line regex) and
routes/vst.ts (/vst/start response), the CLI adapter, and the studio
client's useVstHost.ts (connects with the token in the WS URL).
vstBounce.ts (the offline render path) is unaffected — it invokes the
sidecar's `bounce` CLI subcommand directly and never opens a WebSocket.

Also folds in two smaller final-review findings that touch the same
files:

- vstSidecar.test.ts's mid-spawn-kill test used a fixed 300ms sleep to
  wait for the child's PID file; replaced with a short-interval poll
  (waitForFile) to remove a CI-contention flake risk.
- useVstHost.ts's handleDisconnect doc-comment claimed trackIndexRef was
  kept "purely for the FX property panel's own direct loadChain calls"
  — false (the FX panel never calls loadChain; only useVstPreview
  does). Corrected to describe it as forward-defensive infrastructure
  with no current FX-panel caller.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 18:53:17 -07:00
Vance IngallsandClaude Sonnet 5 dce44d7bad fix(studio): persist native VST editor edits back to the chain file
Finding 1 of the final whole-branch review: opening a plugin's native
editor and tweaking a parameter only ever mutated the sidecar's live
in-memory plugin instance — nothing read the updated state back and
wrote it into the track's .vstchain.json, so `hyperframes render`
silently bounced stale/default state instead of what the user heard in
preview.

There is no "editor closed" event on the wire (the native window closes
via its own OS chrome), so VstSection now polls vstHost.getState every
2.5s while an editor is presumed open (since the last "Open editor"
click, until the track changes or the section unmounts) and PUTs the
chain file via the existing writeChainFile helper when state actually
changed. A best-effort final flush runs from the same effect's cleanup
on unmount/navigate-away.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 18:53:16 -07:00
Vance IngallsandClaude Sonnet 5 d804fef1c3 test(producer): add VST render parity integration test and sidecar docs
Adds an end-to-end integration test proving the whole VST render path
(composition HTML -> processCompositionAudio -> vst-host sidecar bounce
-> mixed output) works for real, using a deterministic builtin
pedalboard plugin. Skips when uv/vst-host aren't available.

Also adds packages/vst-host/README.md (install, WS protocol, exit
codes, manual E2E checklist) and closes a deferred Task 8 coverage gap
with a focused test for the lambda-render VST guard.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 18:53:16 -07:00
Vance IngallsandClaude Sonnet 5 1e2907e730 refactor(studio): replace per-track VST disconnect tracking with a permanent whole-hook suspend
Rounds 1 (621523c6f) and 2 (6e05901c9) each tried to enumerate, per track,
whether it was safe to re-stream after a sidecar disconnect/reconnect, and
each left a real gap on review (round 2's unsafeAfterDisconnectRef missed
tracks whose local AudioContext/AudioWorkletNode wiring was still in flight
when the disconnect fired). The sidecar's own trackIndex-assignment rule can
reassign colliding indices on any reload, and a WS disconnect doesn't reliably
tell the client whether the same stateful process answered the reconnect or
a fresh one did (server-side protocol flaw, out of scope here) — so no
client-side per-track tracking has proven complete.

Replace all of it with one suspendedRef in useVstPreview: the first
disconnect this hook instance ever observes permanently stops it from
loading ANY track — previously-loaded, previously-attempted, or never-seen
— for the rest of its mounted lifetime. Delete unsafeAfterDisconnectRef
entirely. Also fix the "Load chains" effect's cancellation branch to fully
teardownTrack() a load that resolves after a disconnect (unmuting the
element) instead of only closing its AudioContext, which previously left a
mid-flight track muted forever with no audio ever routed to it.

useVstHost's trackIndexRef mirror-clearing behavior is left unchanged: it's
still needed for the FX property panel's independent, direct loadChain
calls on the shared connection, which aren't gated by useVstPreview's
suspension.

Tradeoff, stated plainly: a single transient WS blip now permanently
disables VST preview for the rest of the studio session (recoverable only
by reloading the page) — accepted because two narrower recovery attempts
have each shipped with a real correctness gap, and a wrong/misrouted track
is worse than an honest, visible fallback to dry audio.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 18:53:16 -07:00
Vance IngallsandClaude Sonnet 5 a55f74353c fix(studio): don't blindly re-stream VST tracks after a sidecar reconnect
A WS disconnect does not imply the VST sidecar process was torn down —
startVstSidecar() is a singleton reused across reconnects in the common
case, so its server-side _tracks dict survives. useVstHost previously
cleared its trackIndex mirror on every disconnect on the false premise
that a reconnect always gets a fresh, empty sidecar, while useVstPreview's
crash-fallback auto-reconnect wiped its own "already loaded" bookkeeping
and silently re-issued load-chain for every previously-streamed track.
The server's real (never-reset) index-assignment rule could then hand
those re-loaded tracks a colliding trackIndex that the client's
freshly-recomputed mirror had no way to detect.

Stop clearing trackIndexRef on disconnect (it's a more accurate mirror
left as-is than reset to a false "confirmed empty" state), and track
which trackIds were streaming at disconnect time so the "Load chains"
effect never auto-reloads them again — they stay in dry fallback until
something explicitly re-triggers a load, matching this file's existing
"degrade to dry when index safety can't be guaranteed" pattern.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 18:53:15 -07:00
Vance IngallsandClaude Sonnet 5 e9b97b5097 fix(studio): unify VST sidecar connection and resync trackIndex on reload
Task 13b addendum: VstSection never received a real vstHost (PropertyPanel
defaulted it to null, StudioRightPanel never passed one), so the FX panel
was decorative. Naively fixing that with a second useVstHost() call would
have opened an independent WebSocket racing useVstPreview's connection for
the sidecar's per-track numeric trackIndex state.

Fix: mount ONE useVstHost() instance in NLEProvider (alongside useVstPreview,
moved there from useTimelinePlayer to keep it under the studio 600-LOC file
cap) and thread it through NLEContext so both useVstPreview and
StudioRightPanel's FX panel share the same connection. Add a chain-loaded
broadcast (onChainLoaded) plus a trackIndex-mirroring rule in useVstHost
that replicates the sidecar's pop-then-reinsert indexing exactly, so
useVstPreview can resync an already-loaded track's index when any caller
reloads its chain, and revert both sides to dry playback (with a toast)
instead of silently misrouting PCM when the sidecar's own indexing rule
collides two tracks.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 18:53:15 -07:00
Vance IngallsandClaude Sonnet 5 d78a708afd feat(studio): streamed VST preview with worklet playback and dry fallback
Adds VstRingBuffer (pure TS, unit-tested), the vst-stream AudioWorkletProcessor,
and useVstPreview — the transport bridge that mutes data-vst-chain <audio>
elements, streams the sidecar's processed PCM through a worklet, keeps it in
sync with play/pause/seek and a periodic drift check, and falls back to dry
audio with a toast + one auto-restart attempt if the sidecar disconnects.
Mounted from useTimelinePlayer with a one-line addition.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 18:53:15 -07:00
Vance Ingalls 48fba16c2f fix(studio): reject superseded loadChain/getState requests per trackId
loadChain and getState overwrote pendingTrackRef entries on a second
call for the same trackId, silently discarding the first call's
resolve/reject and leaving its promise hanging forever. Mirror scan()'s
existing supersede-and-reject pattern, scoped per trackId.
2026-07-16 18:53:15 -07:00
Vance Ingalls 2a41dbb24f feat(studio): useVstHost websocket client hook
Implements the real VstHostApi that propertyPanelVstSection.tsx (Task 11)
consumes but didn't provide: lazily POSTs /api/vst/start, opens a WS to
the returned port with binaryType=arraybuffer, and dispatches JSON
control-plane events (scan/load-chain/get-state/error) to pending
request resolvers keyed by trackId, while forwarding raw binary PCM
frames to onPcmFrame subscribers untouched for Task 13 to decode.
2026-07-16 18:53:14 -07:00
Vance IngallsandClaude Sonnet 5 60f4b88180 feat(studio): add VST FX property panel section with chain persistence
Adds the property-panel UI for attaching a VST effect chain to an <audio>
element (Task 11 of the VST plugin support plan):

- packages/core/src/editing/affordances.ts: resolveEditingSections gains
  vstFx (true only for facts.tag === "audio"), narrower than the existing
  media flag.
- packages/studio/src/utils/vstChainFile.ts: ChainFileJson/ChainPluginJson
  types + parseChainFile/serializeChainFile for the on-disk .vstchain.json
  contract shared with the Python sidecar.
- packages/studio/src/components/editor/propertyPanelVstSection.tsx: new
  VstSection component + the VstHostApi interface Task 12's useVstHost will
  implement. Renders an install hint when vstHost is null; otherwise lets a
  user add an effect (writes fx/<elementId>.vstchain.json via the existing
  files PUT endpoint, then commits data-vst-chain via onSetAttribute), list
  chain plugins, remove one, and open a plugin's editor.
- Wired into PropertyPanel.tsx gated on sections.vstFx, with an optional
  vstHost prop (defaults to null) on PropertyPanelProps for Task 12 to fill in.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 18:53:14 -07:00
Vance IngallsandClaude Sonnet 5 5db48c060e feat(studio-server): /vst/start and /vst/status routes with sidecar adapter
Adds registerVstRoutes (POST /vst/start, GET /vst/status) and the optional
startVstSidecar/getVstSidecarStatus StudioApiAdapter methods, wired into
both hosts (CLI embedded server + Studio Vite dev server).

Relocates the VST sidecar lifecycle module from packages/cli/src/vst/sidecar.ts
to packages/studio-server/src/vstSidecar.ts (exposed via a new
@hyperframes/studio-server/vst-sidecar subpath export) so both hosts can
import it without duplicating the resolver + spawn logic; the CLI module
becomes a thin re-export so hyperframes preview's existing import keeps
working unchanged.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 18:51:11 -07:00
Vance Ingalls c47ac058cd fix(cli): kill mid-spawn VST sidecar child in stopVstSidecar
stopVstSidecar() only checked the `running` variable, which is set after
the sidecar's ready handshake. Calling it while a spawn was still in
flight (e.g. Ctrl-C during the sidecar's boot window) was a no-op,
orphaning the child process. Track the in-flight child in a new
`spawningChild` variable from spawn() time so stopVstSidecar() can kill
it before the handshake arrives.
2026-07-16 18:51:11 -07:00
Vance Ingalls daea8d4281 fix(cli): close TOCTOU double-spawn race in VST sidecar singleton
startVstSidecar()'s singleton guard only checked the module-level
`running` variable, which is assigned inside the async ready-handshake
callback. A second concurrent call landing before the first child
became ready saw `running === null` and spawned its own child,
orphaning whichever process lost the ready race — exactly what
stopVstSidecar() and preview.ts's shutdown paths exist to prevent.

Track an in-flight `pending` promise, set synchronously before any
spawn/callback work, so concurrent callers share the same startup
attempt instead of double-spawning. Cleared via .finally() so a future
call after this attempt settles (success or failure) can retry.
2026-07-16 18:51:11 -07:00
Vance Ingalls 8bfc70e4cb feat(cli): spawn VST sidecar with ready handshake and shutdown
Adds packages/cli/src/vst/sidecar.ts: resolves the vst-host sidecar
command (HF_VST_HOST_CMD override -> monorepo uv run -> bare command
on PATH), spawns `<cmd> serve --port 0`, and resolves once stdout
announces VST-HOST-LISTENING port=<N> (30s timeout with an
`uv tool install` hint). startVstSidecar()/getVstSidecar() are a
per-process singleton.

Wires sidecar teardown into all three `hyperframes preview` launch
paths: registerChildTreeShutdown's signal handler (dev + local studio
modes) and embedded mode's own SIGINT/SIGTERM cleanup + last-resort
exit handler, since embedded mode has no child process to register
with registerChildTreeShutdown. stopVstSidecar() is a safe no-op when
no sidecar is running, so this holds even though the sidecar itself is
started lazily by a later API route (Task 10), not by preview.ts.
2026-07-16 18:51:11 -07:00
Vance Ingalls 8831d3ca74 feat(cli): reject VST-chain compositions in lambda render 2026-07-16 18:51:10 -07:00
Vance IngallsandClaude Sonnet 5 9b51615648 fix(engine): abort sibling VST bounces when a track's chain hard-fails
processCompositionAudio's per-element loop races each track's async chain
concurrently via Promise.all, which rejects as soon as the first element
fails without waiting for siblings still in flight. A VstChainProcessingError
from one track therefore let another track's VST sidecar subprocess (up to
BOUNCE_TIMEOUT_MS = 10 minutes) keep running after the finally block deleted
workDir out from under it.

Thread an internal AbortController's signal through every element's chain
(extract/prepare/applyVstChainToWav), aborting it in a catch around
Promise.all before workDir is removed, and abort it on the caller's own
external signal too. applyVstChainToWav now accepts { signal } and kills its
spawned sidecar on abort, following runFfmpeg's existing spawn-abort
convention.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 18:49:18 -07:00
Vance IngallsandClaude Sonnet 5 12f3626fd8 fix(engine): hard-fail processCompositionAudio on VST chain errors
A missing VST plugin or chain file was caught by the per-element try/catch
shared with every soft-degrading failure mode (missing source asset,
download failure, etc): the track was silently dropped and MixResult.success
stayed true, so a render with a missing plugin completed successfully with
no visible error anywhere.

Introduce VstChainProcessingError to mark VST-specific failures and let the
per-element catch rethrow it instead of swallowing it into the warnings
list. The rethrow escapes the Promise.all and rejects
processCompositionAudio itself, which (traced through audioStage.ts's
uncaught await and observability.ts's observeRenderStage, which rethrows)
surfaces as a real render failure through the CLI's existing error-handling
path — the same one every other hard pipeline failure already uses. Every
non-VST failure mode is untouched.

Fixed the two "hard-fails" tests to assert the promise actually rejects
(rejects.toThrow) instead of only checking tracksProcessed/error on an
still-resolved, still-successful result — the previous assertions would
have passed even with the bug present.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 18:49:17 -07:00
Vance Ingalls 3db9b6aaac feat(engine): apply VST chains to audio tracks during render mix
Spawns the hyperframes-vst sidecar (packages/vst-host) to bounce a
track's dry WAV through its VST chain before the volume-envelope bake
in processCompositionAudio. A missing plugin or sidecar failure is a
hard failure for that track (named plugin + track id), never a silent
fallback to unprocessed audio.
2026-07-16 18:44:23 -07:00
Vance Ingalls b79abcd15b feat(engine): parse data-vst-chain on audio elements 2026-07-16 18:44:22 -07:00
Vance Ingalls 2fad3843db fix(vst-host): scope pause transport action to its connection's play owner
An unrelated client sending {"cmd":"transport","action":"pause"} could
cancel another connection's active playback task, the same class of bug
the disconnect and play-takeover paths already guard against via
self._play_owner. pause now only cancels/clears the play task when the
sending connection is the current owner; otherwise it is a no-op.

Adds a regression test mirroring the existing disconnect-ownership test.
2026-07-16 18:44:22 -07:00
Vance Ingalls df07bd449b fix(vst-host): scope play-task ownership to its connection and don't crash on unknown trackId
Track which websocket connection owns the running play task so an
unrelated client disconnecting no longer cancels another client's
active playback. Broaden _dispatch's exception handling so any error
(not just PluginMissingError) — e.g. a KeyError from a command
referencing a not-yet-loaded/unloaded/unknown trackId — replies with
{"event":"error","code":"bad_command"} instead of crashing the
connection with a 1011 close.

Adds two TDD regression tests reproducing both bugs against the
pre-fix code before implementing the fixes.
2026-07-16 18:44:22 -07:00
Vance Ingalls d3bcaa9c50 feat(vst-host): websocket server with control lane, streaming, and editor hosting
Adds server.py (VstServer) implementing the full control protocol over one
websocket: load/unload-chain, set-param, get-state, scan, open/close-editor,
and transport (play/pause/seek) with realtime-paced binary PCM streaming via
Task 4's TrackStream/wire-frame codec. Wires up `hyperframes-vst serve
[--port N]` in __main__.py. Adds pytest-asyncio dev dependency and
asyncio_mode = "auto" pytest config for the new async websocket tests.
2026-07-16 18:44:22 -07:00
Vance Ingalls 52b80b112f feat(vst-host): track streaming engine with wire frame codec 2026-07-16 18:44:21 -07:00
Vance Ingalls 7dfc81aab4 feat(vst-host): crash-isolated plugin scanning with probe subprocess 2026-07-16 18:44:21 -07:00
Vance Ingalls 740753eff0 feat(vst-host): offline bounce engine and bounce CLI 2026-07-16 18:44:21 -07:00
Vance Ingalls e65c82d9fc chore(vst-host): add .gitignore for python build artifacts 2026-07-16 18:44:20 -07:00
Vance Ingalls 40e1d20da1 chore(vst-host): remove stray __pycache__ artifacts from git
These were committed accidentally alongside the chain spec module scaffold.
2026-07-16 18:44:20 -07:00
Vance Ingalls 51a6a46c0d feat(vst-host): scaffold sidecar package with chain spec module 2026-07-16 18:44:20 -07:00
Miguel Ángel d7b38da19d Merge pull request #2586 from heygen-com/carve/s1-asset-resolution
refactor(parsers): share local-asset resolution across lint and studio-server
2026-07-16 20:07:47 -04:00
Miguel Ángel 817a87056c Merge pull request #2585 from heygen-com/carve/hevc-base-rebased
refactor(parsers): single shared FFmpeg/FFprobe binary resolver
2026-07-16 20:07:14 -04:00
Miguel Ángel d4a29fd0c3 Merge pull request #2597 from heygen-com/carve/hevc-base-docs-lint
feat(lint): warn on HEVC video assets that browsers cannot preview
2026-07-16 20:06:35 -04:00
Miguel Angel Simon Sierra 053e1274b1 refactor(parsers): share local-asset resolution across lint and studio-server
Moves assetResolution.ts from packages/lint into @hyperframes/parsers behind
a ./asset-resolution subpath export, mirroring the ./ff-binaries shape, and
points lint's two importers at it. Pure move: no behavior change. Unblocks
studio-server consuming the same helpers without a dependency cycle (the CLI
already depends on lint, so importing lint from studio-server is not an option).
2026-07-16 19:16:43 -04:00
Miguel Angel Simon Sierra 7980479083 fix: preserve shared FFmpeg resolver behavior 2026-07-16 19:10:04 -04:00
Miguel Angel Simon Sierra 88c049f525 refactor(parsers): single shared FFmpeg/FFprobe binary resolver
The cli, engine, and lint packages each carried their own copy of the
ffmpeg/ffprobe lookup, annotated fallow-ignore code-duplication, and the
copies had drifted: the engine copy handled Windows PATHEXT and executed
which/where without a shell but lacked the Homebrew-dirs fallback for
GUI-spawned processes; the cli copy had the opposite. One resolver in
@hyperframes/parsers (the dependency-graph bottom) now carries the union
of both hardenings, and all three packages delegate to it. Every
consumer gets strictly more robust resolution; env-override semantics
per call site are preserved via configuredMustExist.
2026-07-16 18:36:40 -04:00
Miguel Angel Simon Sierra 247743fcdf refactor(lint): bound concurrent ffprobe processes in HEVC probe 2026-07-16 18:36:12 -04:00
Miguel Angel Simon Sierra 664c39db9e feat(lint): flag HEVC video assets with info-level preview note 2026-07-16 18:36:12 -04:00
Miguel Angel Simon Sierra 5f2819b1e7 docs: document HEVC input support and the preview-only codec caveat 2026-07-16 18:36:12 -04:00
Miguel Ángel 08dbb7db37 fix(engine): ignore benign media request aborts (#2423) 2026-07-16 18:20:25 -04:00
Miguel Ángel f0aee28551 fix(engine): reuse HyperFrames browser cache (#2459)
* fix(engine): reuse HyperFrames browser cache

* test(engine): isolate browser cache home on Windows
2026-07-16 18:20:21 -04:00
Miguel Ángel 428e571914 fix(skills): align TTS docs with CLI contract (#2483) 2026-07-16 18:20:17 -04:00
Miguel Ángel 406894061e fix(core): stop composition variables from shadowing authored CSS custom properties (#2553)
A composition variable mirrored as --<slug> for a mounted sub-composition
(default or an explicit data-variable-values value) previously overrode any
same-named custom property the document already authored elsewhere (e.g. a
:root theme token), since the mirroring had no "already defined" guard —
unlike the two other emission paths, which already skip re-emitting when the
name collides with an authored definition. Extend that guard to the
sub-composition mount path in both the compiler (htmlBundler.ts) and the
runtime loader (compositionLoader.ts / getVariables.ts), so an authored
definition always wins; render-time --variables overrides still always win.
2026-07-16 18:20:13 -04:00
James Russo 065f8c9c8d Revert "docs(changelog): weekly digest 2026-06-29–2026-07-06 (#1995)" (#2571)
This reverts commit 9dc7dcd7fb.
2026-07-16 17:34:47 -04:00