* perf(core): Safari clips open at their in-point and are fetched ahead
* perf(core): Safari opens a long file's clips at their in-point and leaves short files as they were
* perf(core): Safari holds a long file's later clips with no source until each one is due
* perf(core): Safari plays a long file's sound from its element instead of fetching the whole file
* perf(core): Safari holds a later clip of a long file even when WebKit began reading it at parse
* style(core): fit the long-file comments to the comment budget and the formatter
* refactor(core): one proxy trigger path, and the producer budget at its measured size
* perf(core): Safari opens a later clip WebKit read at parse at its in-point rather than holding it
* build: the producer size budget at its measured 3162274 bytes
* refactor(core): name the condition that holds a long file's later clip
* fix(cli): staging folders beside a project path no longer fail past 260 characters on Windows
mkdtemp does not get the long-path prefix that mkdir does, so every staging folder
made beside a project or output path failed once its full path passed 260 characters.
They now come from one helper, createStagingDir in @hyperframes/core/atomic-file, and a
scan test fails on a new mkdtemp beside a path.
* fix(cli): give mkdtemp the long-path form instead of replacing it
CodeQL treats mkdtemp as the safe way to make a folder under the system temp dir and
flagged every file written into a folder from the mkdir-based helper. createStagingDir
now calls mkdtemp with the long-path form of the path on Windows, so both hold.
* fix(cli): leave non-Windows paths alone when making a staging folder
The long-path form is now chosen by the shape of the path, not process.platform,
so tests that pretend to be Windows keep working and the comment share does not rise.
* fix(core): a staging folder keeps a Windows path that already names its namespace
* fix(core): a staging folder keeps a Windows device path as the caller gave it
* fix(core): the staging folder helper's comment fits the line limit
* fix(core): detect template entries structurally
isTemplateEntry only matched a raw file that starts with <template>, so the
full-document sub-composition shape (<!doctype html><html><body><template>
<div data-composition-id>...</template></body></html>) was not recognised and
resolveEntryHtmlPath compiled the raw file, whose root sits in an inert
template: no timeline, no duration, "Composition has zero duration".
A template entry is now a document whose <template> holds the composition
root with no live composition root outside it. Detection and extraction share
one lookup (locateSceneRoot), the same one readSceneRoot uses.
— Jerrai
* fix(core): drop comments from the template lookup
The comment ratchet allows no net rise in a file's comment share; the PR
description carries the explanation.
— Jerrai
* fix(core): find the scene template among several templates
locateSceneRoot read only the first <template>, so a scene template that
follows another template was treated as not a template entry. Scan every
template and take the first whose content holds a composition root.
* fix(core): drop the added comment (comment ratchet)
* chore: raise the inspector unpacked size budget by 0.5%
The inspector bundles core; the multi-template scene lookup added a few
hundred bytes and put it 10 bytes over the 1% tolerance.
* fix(core): refuse a file with several scene templates, naming them
* chore: trim the inspector size budget bump to what is needed
* fix(core): render the first scene template and lint the ambiguity instead of failing
A file with several scene templates and no live root rendered its first one
before; locateSceneRoot threw and stopped such projects rendering. It returns
the first again, and the multiple_scene_templates lint warning names each.
Co-authored-by: Jerrai <jerrai@heygen.com>
* chore(core): drop the locateSceneRoot comment line the comment ratchet counts
Co-authored-by: Jerrai <jerrai@heygen.com>
* fix(core): one shared scene-template pick for the compiler, the inliner and the loader
A scene template after a card template was detected by locateSceneRoot but
mounted from the first template of any kind, so it rendered blank.
findSceneTemplate picks the first template holding a composition root and
locateSceneRoot, resolveSubCompositionContent and the loader all use it.
Co-authored-by: Jerrai <jerrai@heygen.com>
* fix(core): a video held on its tail is seeked once, not every frame
* fix(core): seek a held tail again when the element was moved off it
* fix(core): the held-tail skip applies only while playing
* style(core): format the held-tail change
* refactor(core): drop a comment that repeats its neighbour
* 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>
* fix(core): a muted video's picture no longer waits on its own audio track at a cut
A muted video takes its clock from its audio track in Safari; a late start of that track stalls the picture after the cut. The runtime now switches the track off.
* test(core): a video muted by script and unmuted later keeps its audio track
* fix(core): type the audio track loop so it passes the strict index check
* fix(core): a set written before its tween no longer erases the tween's end
* fix(core): shorten two comment lines to the limit
* fix(core): the stamp takes any GSAP the runtime types, so the runtime typecheck passes
* fix(core): Safari video picture lands on the cut again, undoing the hidden pre-roll
Reverts the one-second hidden video pre-roll (#7265): on Safari the pre-rolled video is still behind at the cut and trails it by 30 to 150 ms in every measured run, and some cut flashes never show.
* fix(core): shorten a restored comment line to the 120-column limit
* fix(producer): page timers during a render run on film time
* test(producer): a regression film whose timer bars must follow film time
* test(producer): schedule the timers regression film in CI shards
* fix(producer): keep setup timers on the wall clock until the page reports ready
* fix(producer): keep the renderer's own waits and deadlines on the wall clock
* test(engine): fail CI on a bare timer in code the engine runs in the page
* fix(core): type the wall-clock timers like the global timers they replace
* chore(engine): drop the comment on the shim's window type
* fix(core): skip a video the browser can't decode instead of freezing the film
* fix(core): keep waiting on a clip whose play the browser refused; drop the codec-map skip
* feat(core): motion blur reports what a composition holds, as counts
The runtime scans a composition once per blur scan, on both tiers, and reports
counts of what it holds (canvases, video, frames, custom elements, clips, masks,
scroll containers, 3D, blend modes, and movers that overflow, sit under other
content, hold fixed children or carry pseudo-elements outside their box), plus
whether pose reads need callbacks. Counts only: no ids, classes, text or URLs.
The engine puts the non-zero counts on its [motion-blur] line and hands the
parsed report to the perf summary; the producer aggregates workers (first report
wins, failed frames sum) and the CLI sends motion_blur_* properties on
render_complete, from the CLI and from Studio renders.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(cli): disclose blur counts in telemetry docs, raise inspector budget
The runtime fingerprint code is bundled into @hyperframes/inspector, which
puts its unpacked size 2.2 KB past the 1% tolerance. The telemetry docs now
list the composition counts the CLI sends with a blur render.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(core): video starts a second early and catches up hidden, so the picture meets the cut
* fix(core): a video that plays from the start of its file also starts early
* fix(core): a from-file-start clip leads by half the lead hold so a fast start is not paused
* fix(core): steering for hidden video is its own function; trim comments and format
* chore(player): raise the packed size budget for the picture pre-roll
* 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>
* fix(core): a mover holding a fixed child stays sharp in the filter tier
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(core): a fixed-child mover is skipped only on frames it is not already a containing block
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(core): blur quiets discrete callbacks instead of undoing what they wrote
#7191 undid the DOM a callback wrote during the blur scan with a mutation journal. That
regressed once-guarded and memoized timeline callbacks: the callback ran, its guard flipped,
and the journal put the DOM back, so the real seek never wrote it again.
Mute GSAP's onStart, onComplete, onReverseComplete and onRepeat for the scan and for eventful
pose reads, then restore them. onUpdate keeps firing, so movers driven from it are still found.
muteDiscreteCallbacks replaces a callback with a no-op rather than clearing it
(hasZeroDurationCallbackTween reads typeof vars.onComplete), walks tween.timeline for staggers
and keyframes, and skips an animation already muted because scene timelines nest in the root.
The journal (journalDom, landThenUndoDom, putBack) is deleted. The loud rewind through 0 stays.
Measured in the spike (mute-spike-report.md, "Probe matrix and fresh worker"): every GSAP
pattern matches blur off in label and fire count; 8 of 300 comparisons differ, all the non-GSAP
row, against 248 of 300 on main. This supersedes the limit #7191 accepted. Mute and restore over
2002 animations is 0.2 ms.
Limits:
- A mover that exists only because a muted callback set it up is found only if that callback
fired before the scan. A worker starting before the call leaves that mover sharp while a later
worker blurs it; positions stay right.
- tl.call(() => gsap.to(...)) movers are never found and stay sharp.
- A non-GSAP adapter that ignores suppressEvents (adapters/animejs.ts) and writes DOM on a
once-only completion shows it early. Pinned by a KNOWN LIMIT test.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(producer): drop the once-guard-label block-start guard that pins a block that cannot fail
The guard required a block start in [1, 15], the worker at frame 9, and the comment said it
paints on both sides of the call at 16. Its frames after the call (16, 17) sit inside the
trail mask at the label, so that block cannot show the bug. The outside-the-trail case on the
7-worker partition is what catches the mutant; the fixture stays in FIXTURE_NAMES.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): split the callbacks matrix in three and share one blur-off run per row
The matrix file took 247 s on an idle Mac and timed out at the flake gate's 120 s in all 10 reruns.
Each row now compares the arms against one blur-off page painted in order and one fresh page, not
a new blur-off page per arm and sequence; the in-order sequence is the first paints of the page that
goes back to the first time; rows run their pages together; the paint skips the full-frame PNG that
only the pixel tests read. Only the two arms with an onUpdate mover stay (both tiers): they run the
scan's mute and the per-frame mute, which the arms without a mover do not.
The rows and harness move to __fixtures__/motionBlur/callbackRows.ts and the matrix is split over
three files so each run fits the gate. Rows a to y, the three sequences, both tiers, row y and the
KNOWN LIMIT test are all kept; no assertion changed.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(core): snapshot and preview show a clip on the frame render shows it
* fix(cli): snapshot pulls a video's frame on the same on-screen rule
* refactor(cli): drop two doc lines the names already carry
* fix(core): the bundle's contract check reads a timeline registered in a local script
* fix(lint): collectExternalStyles is internal now that linkedSources is the export
* fix(core): hlg footage tone-maps to sdr at the bt.2408 reference white
* fix(core): an HLG clip whose stream leaves its transfer unset keeps HLG's white
An SPS with an unspecified transfer takes the stream's tag, as its frames do; a failed keyframe read is not cached; the grey test needs ffmpeg 8.
* fix(core): keep long WebKit sources and unloaded clips on the audio clock
* fix(core): drop the comments the ratchet counts
* fix(core): shorten the decode helper comment
* fix(cli): a preview's session follows HYPERFRAMES_CACHE_DIR when it is set
* docs(cli): background previews follow HYPERFRAMES_CACHE_DIR
* test(cli): unstub the preview test's env in a block body
* test(cli): clear HYPERFRAMES_CACHE_DIR in the CLI's test home
* fix(cli): registry cache, search model, catalog and catch-up follow HYPERFRAMES_CACHE_DIR
* style(cli): format the media search cache test
* test(cli): compare the model path against an absolute cache folder on Windows too
* fix(cli): both catalog readers treat an empty HYPERFRAMES_CATALOG_ARTIFACT_DIR as unset
* fix(core): a multi-worker render replays overlapping tweens behind the timeline stand-in
The overlap and landing-mark walks compared tween parents with the stand-in the producer's GSAP stub hands out, never met it, and lost the overlaps and step times. Both now compare with the real timeline behind the stand-in.
* fix(core): drop the moved helper's comment so the file's comment share holds
* fix(core): blur scan and eventful reads put back the DOM a timeline call changed
With data-motion-blur-events on, the mover scan runs the timeline to the end with
callbacks on and rewinds with callbacks on. GSAP fires a tl.call on a backward
crossing too, so the rewind left the earliest call's DOM effect in place: the
callbacks fixture showed label "B" from frame 0, before its 0.5 s call.
Calls cannot be un-fired, so the scan (and eventful per-frame reads) now journal
DOM mutations with a MutationObserver, land on the frame with callbacks on as
before (keeping JS-side call parity), then undo the journal back to the
pre-scan DOM, which is what a plain seek to the frame produced.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine,producer): callbacks label-early pins become ordinary outside cases
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* perf(core): the DOM undo skips attributes and text already back at their old value
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(core): a scrolled list keeps its offset when blur moves the root
Chrome resets a scrolled container's offset when the root leaves or enters the
document, so the first blurred frame of a fresh page or render worker drew the
list at offset 0. Offsets are read at move time and put back before the re-seek,
so a container that became scrollable after the scan is covered too.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* test(engine): scroll-list is an ordinary outside case, not a pinned known bug
The scroll offset now survives the root's move, so the three engine differential
cases and the multi-worker render case expect blur on to equal blur off, and the
measured constants for the old symptom go.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* chore(core): drop the scroll-offset comment, the comment-share ratchet may only fall
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
A rejected window.__hf.buildReady hold now sets window.__hfStartupError naming the key and the
reason, so render, snapshot and check fail instead of capturing a scene that was never built.
Fixes#5603
* feat(core): data-motion-blur-phase sets when the shutter opens
Page motion blur always centres the shutter on the frame. Add a phase in degrees of a
frame, -360 to 360: the window starts at t + phase / 360 / fps and lasts shutter / 360 /
fps. Unset stays centred, so a page without the attribute renders the same bytes.
Both tiers take the window from one place, shutterTimes in frames.ts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(core): the motion blur report carries the shutter phase
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* chore(core): drop the phaseDeg doc comment, the comment-share ratchet may only fall
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(fonts): stop failing cloud renders on var() shorthands, font-X-400 names and linked font sheets
* style(producer): shorten the project font sheet comment
* style(core): shorten the field font families test header
* fix(fonts): split font size parsing and fit the CLI size budget
* fix(producer): read project font sheets for family names only, never fetch from them
* fix(producer): a wedged effect scan or screenshot-session open trips the 60 s stall watchdog
The sequential streaming watchdog raced only the capture call. Session init
(where the fast-capture effect scan runs) and opening the screenshot session
for effect frames waited on CDP's protocol timeout instead, which scales with
output area up to 30 minutes, so a starved page hung a render for ~25 minutes
before the watchdog saw the next frame. The effect scan now gives up when a
chunk outlasts its 120 s budget, opening the effect-frame session gets its own
no-progress window, and session init gets a 300 s one; each trip retries on a
fresh session like any other stall.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): one local render at a time per machine; a second waits and says for whom
Renders started side by side from different sessions starve each other until
frames stop landing. `hyperframes render` now takes a machine-wide slot (a lock
file in the HyperFrames cache directory, held by pid) after its preflight and
holds it for the render or the whole batch. A second render waits and prints
the pid and project it is waiting behind; `--no-wait` fails at once instead.
A holder whose process is gone is taken over, and HYPERFRAMES_RENDER_LOCK=off
restores side-by-side renders. `--workers` is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(lint): flag fonts a cloud render cannot resolve, including the font shorthand
Lint read only `font-family`, so `font: 500 16px "PingFang SC", sans-serif`
passed while the renderer, which reads the shorthand too, drew the installed
Mac font locally and the cloud refused it. The shorthand now counts for
font_family_without_font_face (its parser moves to @hyperframes/parsers so
core and lint share one), and a new font_face_local_only warning names an
@font-face whose only sources are local(): it renders here and falls back in
the cloud. The rule's hint and the format reference stop recommending local()
for OS fonts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): a cloud render that refuses a font says which project files use it
The cloud's "fonts that could not be resolved: PingFang SC" named no
composition. For a render submitted from a local project, the failure now
lists each refused family with the project files that name it, and says how
to ship the font so the cloud can use it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(cli): keep comment shares and exports within the gates, and split the single-render notes out of executeHeldRender
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(parsers): read a spaced line-height slash and var() before the size in the font shorthand
`font: 16px / 1.5 Inter` was read as the family `/ 1.5 Inter`, and
`font: var(--weight) 16px Inter` as `16px Inter`, because a var() counted as
the size. The parser now follows the shorthand grammar: optional style,
variant, weight and width keywords (or var()), then a length, percentage,
keyword or calc() size, then a `/ line-height` in any spacing. When no size can
be told apart from a var(), it says so: lint skips that declaration instead of
reporting a missing font, and the renderer keeps its best guess.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): say the render slot is one per user account, not per machine
The lock lives in the account's HyperFrames cache folder, so renders by two
user accounts never queued behind each other while the messages, flag help and
docs said "this machine". They now say "per user account" and that
HYPERFRAMES_CACHE_DIR set to a shared folder shares the slot across accounts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): reclaim a render lock or takeover file left half-written
A lock or `.break` file that exists but cannot be parsed (a crash mid-write
where hard links are unavailable) was never reclaimed: a waiting render waited
forever and --no-wait refused forever. Once such a file is older than any real
write (5 s by mtime) it counts as abandoned: the lock goes through the same
`.break` takeover as a dead holder's, and a takeover file is removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): opening the capture session counts against the setup stall budget
The sequential streaming attempt opened its own capture session (Chrome launch
and new page) before the setup watchdog and outside the attempt's cleanup, so a
wedged launch still waited for the protocol timeout. Opening now shares the
300 s setup window with session initialisation, a trip fails the attempt like
any other sequential stall, and a session that finishes opening after its
attempt gave up is closed instead of leaking a browser.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(parsers): keep the shorthand result type module-private
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): reclaim an unreadable render lock only when its writer is provably gone
Where hard links are unavailable the lock is created by an exclusive open and
then written, so a contender paused between the two leaves an unreadable lock
while it is still alive. The 5 s mtime grace took such a lock over, and both
processes then held the slot. Each contender now writes an owner marker under
a name only it can take (pid plus random suffix, holding its process identity)
before it creates the lock, keeps it while it holds the slot, and removes it
otherwise. An unreadable lock or `.break` is reclaimed only when no other
contender's marker belongs to a live process; markers of dead processes, or of
a reused pid, are deleted. No reclaim is decided by time alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: split acquireRenderLock and the streaming-stage session stub under the complexity gate
acquireRenderLock hands contender setup and a single marked claim to their own
functions, and the test stub for createCaptureSession splits its held-open
cases from the fake session it builds, so neither exceeds Fallow's cognitive
or CRAP thresholds. Behaviour is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(ci): raise the CLI and engine size budgets for the watchdog, lock and font-lint additions
Main's CLI unpacked size was already ~0.99% over its budget; the render lock and
owner markers push it past the 1% tolerance. The CLI unpacked budget takes the same
value as #7169 and #7170 (25,159,107) so the PRs merge cleanly. The engine's packed
size grows by about 4.7 KB for the effect-scan and session-open watchdogs; its packed
budget moves to 5% above the measured 467,097, as the budget file's headroom rule sets it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(parsers): a var() size glued to its line height is the shorthand's size
`font: 700 var(--size)/1.1 "Inter"` read as no family at all: the token was
tested whole against var(), and the slash after it hid that it was the size,
so the renderer injected no face for Inter. A var() followed by `/ line-height`
(glued or spaced) can only be the size, and is now read as one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(parsers): split the shorthand size search out of parseFontShorthand
Keeps parseFontShorthand under Fallow's cognitive-complexity gate; behaviour is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): render lock never removes another render's takeover, knows a reused pid, works in a shared folder and on Windows
- A `.break` takeover file is removed only by the render that wrote it. One
whose writer is gone stops the render with the file to delete, instead of
being removed on an earlier reading, which could remove a live `.break`
written since and let two renders hold the slot. The takeover re-reads the
lock under its own `.break` right before replacing it.
- The lock record keeps its holder's process start time, so a pid that now
belongs to another process (an OOM-killed render in a container with a
persisted cache) no longer holds the slot forever.
- The `locks` folder is created writable for every account, so accounts
sharing HYPERFRAMES_CACHE_DIR take turns instead of the second failing with
EACCES; a folder this account cannot write in says how to fix it, and
another account's file that cannot be removed is left, not fatal.
- Windows: no PowerShell start-time lookup per check (pid liveness only), a
file another handle holds (EPERM/EBUSY/EACCES) reads as held, a lock that
vanished is retried once instead of in a tight loop, and a wait stops when
its signal aborts. The tests end every acquire they start before removing
their folder, and the paused contender writes through its open descriptor.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(ci): raise the lint packed size budget for the font-shorthand rule
With main's audio-attribute rule (#7169) merged in, the font-shorthand and
local()-only font findings take @hyperframes/lint's packed tarball to
181925 bytes, over the 179338 budget. The new budget is that measurement
plus the usual 5% headroom.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): cloud render stops before upload when the cloud lacks a font
* refactor(cli): shorten the font preflight comments
* feat(cli): cloud render carries the system fonts a project uses in its zip
* fix(cli): say only what is known when a system font's file is not found
* fix(core): find a system font by the family names inside its file, including .ttc faces
* fix(core): look inside font files only when asked, keep regular and bold, cut comments