* fix(studio): a reload requested while a canvas save is in flight loads again once it lands
* test(studio): type the late-reload drag helper for every edit kind
* fix(core): a composition made only of a set shows it at a seek in the preview
* chore(core): keep the comment share of the runtime init file level
* test(studio): bank the four resize-hold rows the preview now gets right
* fix: a save's temp file no longer reaches Studio as an outside change
* refactor: the project file walk and its tests carry no new duplication or complexity
* test(studio): the edit accuracy gate judges the two nudge sequences again
* fix(studio): a hand edit after a preview reload draws on the element now on screen
* fix(studio): a preview reload waits for the gesture on screen to end
* fix(studio): a marquee after a reload selects from the preview on screen
* fix(studio): a reload requested before a canvas save loads again once the save lands
* feat(studio-server): a write receipt names the version the write replaced
* test(studio-server): route receipts carry the version each write replaced
* refactor(studio-server): the receipt's from field needs no comment
* fix(studio): the preview serves a same-size edit written right after the last one
* chore(studio): keep the comment share and complexity gates green
* refactor(studio): keep the project signature doc comment on the function it describes
* fix(studio): the preview re-reads files written in the last two seconds, whoever wrote them
* feat(studio): paste and duplicate can keep a clip's own time, on the next free track
* fix(studio): an in-place paste uses the copied time only in the composition it was copied in
* test(studio): an in-place duplicate inside a sub-composition keeps its local time
* refactor(studio): the paste anchor is its own function, and the in-place tests share their setup
* refactor(studio): paste names its undo step and note in one place, and two paste tests share their steps
* feat(studio): the code editor follows studio's light and dark theme
Replaces One Dark with a Studio editor theme whose colours are theme.css variables: eight syntax role tokens (One Light and One Dark hues held at 4.5:1), editor surfaces from Studio's roles, all measured by the contrast ratchet.
* test(studio): the code editor theme takes every colour from a theme.css token
* fix(studio): code stays at 4.5:1 when a selection or search match sits on the active line
Syntax tokens are tuned for the selection over the active line, which the ratchet now measures; matches are outlined rather than stacking another wash; the search panel's pressed button and special characters follow the theme; unused tooltip rules go.
* fix(studio): code matches carry no background, and types read apart from constants
Search and selection matches are outlined only, so CodeMirror's lime match wash and stacked washes are gone; type and constant tokens split by hue in both themes.
* fix(studio): the current search match reads apart by width, not colour alone
A 2px accent outline on the current match and a muted 1px outline on other copies of the selected word.
* test(studio): catch teleports and multi-step edit bugs in the edit accuracy bench
* test(studio): share the edit accuracy case harness between single gestures and sequences
* test(studio): keep edit accuracy helpers private unless shared
* test(studio): score plain-CSS edits on pages that load GSAP for other elements
* test(studio): add an idle GSAP axis value so plain-CSS edits are scored on GSAP pages
* test(studio): report a slow undo save as late with its latency, apart from a lost one
* test(studio): sample the gap between back-to-back drags and allow one frame of lag
* test(studio): read the edge from the element's fractional size, so a crop edge is exact
* test(studio): keep waiting for a late save until an undone file stays put for 3 s
* ci(studio): run the edit accuracy grid in 12 shards to stay near 25 minutes each
* test(studio): read edit bench frames just before paint, so unpainted states never count
* test(studio): scope the edit bench frame sampler so page globals cannot clash
* test(studio): let a lagging box catch up the pointer travel it owes, so a held frame is no jump
* test(studio): record every save a sequence makes, even two that land 10 ms apart
* test(studio): end a drag's teleport scoring at its pointer-up, not at the next element's press
* test(studio): bank for each edit accuracy case a run that agrees with the gate's verdict
* test(studio): fail the edit accuracy gate on a teleport or an unmeasured drag
* test(studio): fail the edit accuracy gate when a text edit is not saved or shown
* test(studio): measure but do not gate the edit accuracy cases a known Studio race flips
* test(studio): bank the edit accuracy cases that newly pass with the teleport metric
* test(studio): quarantine the two nudge sequences whose redo write sits at the 2 s limit
* style(studio): cut three bench comments to one line each
* feat(studio): a light and dark theme toggle in the header that remembers the choice
The sun and moon button flips Studio between Graphite light and dark with a
circular reveal, saves the choice, and follows the system until one is made.
* fix(studio): studio opens light the first time, then keeps the saved theme
* fix(studio): drop the theme field's comment, the theme owner states the rule
* fix(studio): the theme toggle shows only in studio's own app and follows the theme on screen
A host that embeds StudioApp gets no toggle; the button reads the document's theme, the reveal drops the default crossfade, and reduced motion skips it.
* fix(studio): the theme reveal leaves other view transitions alone; one default for the toggle
The crossfade rule applies only while the toggle's own transition runs, StudioApp passes the header's single default through, and the reveal's reduced-motion and keyboard paths are tested.
* fix(studio): a second theme click mid-reveal keeps the crossfade off
Only the latest reveal clears the document marker; tests pin the marker while a reveal runs and the circle's radius.
* refactor(studio): the theme toggle shares its icon props and reads as plain functions
Simplify pass: one icon props object for the sun and moon, no useCallback around a handler nothing memoises, cannotReveal named for what it answers, the test reuses the theme reader.
* fix(studio): studio's own app turns the theme toggle on through context; tests parse index.html
App.tsx stays at main's size: main.tsx provides ShowThemeToggle and the header reads it, default off for hosts. The boot-script tests read index.html through DOMParser instead of an HTML regex.
* fix(studio-server): a folder rename past an unreadable folder or file answers ok
* fix(studio-server): a rename skips only folders and files it may not read
* fix(studio-server): the rename's skip helpers say it by name
* test(studio-server): the rename tests share one request
* perf(studio): load the font lists when the font picker first opens
Selecting an element no longer fetches and dedupes the 1.7k-name Google font list, so the response cannot land inside a drag frame. The lists are fetched once per session on the first open.
* test(studio): expect the font lists to load on the first picker open
* perf(studio): load the font lists at session start and process them when input is idle
* style(studio): drop a comment the font list names already carry
* perf(studio): process the font lists in idle slices of at most 3 ms
* perf(studio): join the font lists without iterating them when they arrive
* feat(studio): fade handles ride the fade's end and the waveform shows the fade
* refactor(studio): read fade handle keys from one lookup
* fix(studio): fade handle keys stay with the handle and snap past the clip's own edges
* fix(studio): Cmd shortcuts keep working on a focused slider and fade boxes stay on their tabs
* fix(studio): keep a fade handle while it is in use and restore the viewport gate's Chrome path
* fix(studio): a fade's draft clears with its own save and grow drags never shrink it
* fix(studio): saved fades reach the timeline store so the handle stays where it was dropped
* fix(studio): a fade longer than its clip starts a drag or key from the clip's end
* fix(studio): fade comments state the rule, not its history
* feat(studio): graphite colour system with a light theme that passes contrast
Studio's tokens take the Graphite values: a lifted dark, a light set behind
data-theme="paper", the player dark in both. Every text role clears 4.5:1 and
every icon and ring 3:1 on the fills it sits on, held by the contrast ratchet.
* fix(studio): every studio surface follows the light theme and passes contrast
The dock no longer inherits dockview's forced dark scheme, popovers sit on the
raised surface, stock white, red and amber text map to roles, the keyframe
diamonds and track headers use roles, and the contrast ratchet measures every
pair in both themes (150 pairs).
* fix(studio): stock white, red and amber stay colours; studio text and fills use roles
Round-two review: white, red and amber are colour content as well as text, so
they keep Tailwind's values and hosts keep their palettes. Text, toasts, the
feedback card, the FX popover, destructive buttons, category labels and the dock
take Graphite roles instead; the contrast gate rejects an unparseable colour.
* fix(studio): every light-theme ink, icon, dot and focus ring holds its contrast
Stock white, red, amber and file-type hex left in Studio chrome now use roles or a light-dark pair; the file tree icons carry a contrast test.
* chore(studio): drop two comments the names already carry
* fix(studio): red marks, teal outlines and colour curves hold contrast in both themes
Danger graphics use the danger ink, file tree outlines use the accent ink, the colour-curve well stays dark like the scopes, and six timeline token pins come back.
* fix(studio): invalid readouts, the curve focus ring and editor dots stay distinct in both themes
The invalid readout border is dashed as well as red, the curve graph's ring sits inside its dark well, the radius dots and ease handle centre follow the theme.
* refactor(studio): ease and radius editors use colour classes; the dashed invalid border has a test
Simplify pass: the ease editor's inline accent styles become stroke and fill classes, the radius dot class is computed once, the ratio check is one expression, and the alias table is named for what it holds.
* fix(studio): the timeline viewport gate judges p95 over every measured scroll step
* fix(studio): format the pooled p95 lines in the timeline viewport gate
* test(studio): pin the timeline viewport gate's pooled verdict with tests
* refactor(studio): share one Chrome launcher across the timeline and fade-handle gates
* fix(studio): undo and redo are no longer held behind thumbnail renders
* test(studio): composition card tests share one mount, and the bench's 2 s undo rule is tested
* fix(studio): a composition card and its timeline clip share one thumbnail render
* test(studio): bank opening a film at 15 thumbnail requests, one per composition
* fix(studio): composition cards load near the viewport and keep their last frame until the next
* fix(studio): a composition card keeps its last frame under cache pressure, and loads 200 px early
* fix(studio): a rotate GSAP does not own saves where you let go, as the element's own CSS rotate
* fix(studio): a rotate keeps a transform-centred element in place
* fix(studio): a plain rotate shows its angle in the panel and turns inline elements too
* fix(studio): a rotate turns a mirrored or stretched centred element with the cursor
* fix(studio): keep the rotate's panel readout within the comment budget after the move landed
* fix(studio): an inline element's turn saves the inline-block it was drawn with
The overlay passes the rotate target it read at press into the commit, so the
save draws and patches exactly what the draft did instead of re-reading an
element the draft already made inline-block. The GSAP-aware commit also routes
on that press-time decision.
* test(studio): bank the 27 rotate cases a GSAP-free rotate now passes
baseline.json is the edit-accuracy-gate artifact of the CI run at cb75cc37,
copied byte for byte: 530 to 557 passing, all rotate-none cases, none
regressed.
* fix(studio): a word an older Studio turned keeps its inline-block and whole angle on a new rotate
Clearing the legacy rotation marks puts the element back to inline and drops
their turn, so the save reads the target again instead of using the one the
press read before the clear. A test also pins that a turn the press drew as CSS
stays on the CSS writer.
* test(studio): bank the edit accuracy baseline from the rebased rotate run
* fix(studio): a move keeps the route it chose at press through drop and save
* fix(studio): a refused move drops the transform GSAP folded it into, so the layer goes back
* fix(studio): a group refuses a GSAP takeover before writing any member, and only a real fold refuses
* fix(studio): resize an element without GSAP by its own width, height and translate
A corner resize of an element GSAP does not size or position now saves plain CSS:
its inline width and height, the scaled crop, and the translate that keeps its
centre where it was, in one save and one undo step, with no animation read and
no preview reload. It used to write a GSAP script into a file that had none, and
the box snapped back to its old size on release.
The anchor that keeps the centre planted is the same plain px translate a move
writes, kept to a thousandth of a pixel, and a percent translate is held as px
from the press so a growing box cannot drag it along on the first frame.
* fix(studio): a resize leaves a box to GSAP when GSAP tweens anything the CSS box writer sets
gsapWritesBox now reads its channels from BOX_SIZE_STYLE_PROPS, the writer's own
property set, instead of width and height alone. A host-level test pins the
GSAP-free resize route through useDomGeometryCommit.
* fix(studio): a GSAP scaleX or scaleY tween also keeps a resize on the GSAP route
They are GSAP's names for parts of the one CSS scale the box writer sets.
* test(studio): bank the edit accuracy cases a plain-CSS resize now passes
baseline.json is the edit-accuracy-gate artifact of the CI run at 5ae51f1d,
copied byte for byte: 494 to 530 passing, the 36 resize cases without GSAP,
none regressed.
* fix(studio): fade handles show a real tooltip and a 24 px target
A sound clip's fade-in and fade-out dots now open Studio's tooltip
("Fade in 0.3 s") instead of a native title the clip's own title
competed with, take a 24 px hit box, and paint an opaque white dot that
reads on the audio clip in both timeline themes.
* fix(studio): fade handles sit at the clip's top corners, above its content
The fade-in and fade-out dots now pin to the clip's top-left and top-right
corners instead of the end of each fade, paint above the waveform and
thumbnail layers, and share a short clip's width without overlapping. The
fade ramps are clipped to the clip's rounded corners, and the tooltip
uses the same seconds format as the slider's value text.
* fix(studio): fade dots keep their 10 px size on a very narrow clip
On a clip narrower than two fade hit boxes the flex row squeezed each dot
below 10 px. The dot no longer shrinks and no longer takes the pointer, a
browser check measures its box on a 0.1 s clip in CI, and two drag test
comments now describe the corner handles.
* fix(studio): the Escape key cancels a fade drag wherever keyboard focus is
A press on a fade handle never focuses it, so Escape only reached the
handle's own key handler when something else had focused it, and the
release then saved the dragged fade. The drag now listens for Escape on
the window for as long as it lasts, restores the fade and saves nothing.
* test(studio): trim the fade handle browser check header to what the code cannot say
* fix(studio): a translate written with min(), max() or clamp() moves without a jump at press
* fix(studio): refuse out loud a translate Studio can't read, and resolve percent against the transform box
* fix(studio): one refusal per held arrow key, and the panel reuses the offset it already read
* fix(studio): open projects whose folder name has a colon
* fix(studio): open projects named with a colon or '#' in Studio and its preview
* fix(studio): refuse a Windows stream id reached through a session alias
One adapter rule, isServableProjectId, now guards the requested id, a
session's projectId and the folder listing. The bundler-failure preview
places its <base> inside an attributed <head>, and the media metadata
cache keys on the encoded URL so ids with ':' can't collide.
* fix(studio): the properties panel no longer hands GSAP an element it does not position
* refactor(studio): drop the comment the comment-share ratchet counts
* fix(studio): the panel also skips GSAP's transform-origin channels on an element GSAP does not position
* refactor(studio): delete the unused second list of GSAP transform channels
* feat(studio): hosts can apply the canvas menu's z-order through useDomEditZOrder
* style(studio): format useDomEditZOrder
* docs(studio): trim the z-order hook's moved comments
* fix(studio): a read-only preview never reorders or deletes, from any host control
The session's z-reorder and delete commits now refuse in a read-only preview, so the lane mirror is skipped too. useDomEditZOrder is off in read-only and for a detached element, apply reports false when nothing is saved, a same-class sibling keeps its selector index, and the hook returns a stable object.
* fix(studio): read-only stops canvas and host z-order only, and a reloaded selection
The session's z-reorder and delete commits no longer refuse in a read-only preview: the timeline's lane-to-z sync goes through the same commit and stays editable. The refusal stays in useDomEditZOrder and the overlay. A selection from before a preview reload, whose document no window shows, gets no z-order.
* fix(studio): one Cmd+Z pressed inside the preview takes one undo step, not three
* fix(studio): one undo per key press, tracked, with the preview's extra history listener removed
* fix(studio): start timeline drops on an empty lane at 0 and snap to clip edges
A file, asset, block or composition dropped on an empty lane, a new lane, or an empty timeline now starts at 0 instead of the pointer time. On a lane with clips the start snaps to the nearest clip edge within TIMELINE_SNAP_PX. The drop preview and the committed drop share the placement.
* fix(studio): keep the drop file's comment share flat
* fix(studio): a drop snaps to clip edges only while the timeline magnet is on
* fix(studio): undo and redo show on the next frame instead of after the server answers
* fix(studio): an undo pressed before the history caught up still restores in place
* fix(studio): undo and redo of an edit inside a nested composition apply in place
* fix(studio): undo of a nested edit reloads when its composition has a GSAP script
* refactor(studio): a nested restore with a GSAP script has no in-place scope
* fix(studio): an undo after an outside write shows the file the server restored
* feat(studio): a host app can mount the dock with its own panels, storage key and width
* refactor(studio): the dock keeps a host layout through Studio's own preference storage
* fix(studio): a dock reopens a panel beside the preview only when its usual neighbour is not in the dock
* fix(studio): move and nudge an element without GSAP by its own CSS translate
* fix(studio): route a GSAP-free move through the on-element writer and meet the file checks
* fix(studio): a drag press on a GSAP page leaves an element GSAP does not position alone
* fix(studio): a press reads a percent or calc translate without touching the element
* refactor(studio): import POSITION_CHANNELS from its owner instead of a re-export
* test(studio): share the drag press helper in the start gesture tests
* refactor(studio): split the translate length reader into term and sum
* test(studio): cover each translate form the reader resolves or hands to Chrome
* test(studio): bank the edit accuracy cases plain-CSS moves now pass
baseline.json is the edit-accuracy-gate artifact of the CI run at 2a84c103, copied byte for byte: 60 newly passing cases, none regressed. The commits since change no behaviour (a reader split and tests).
* fix(studio): a text edit saves to the element that was edited, or says why it could not
* fix(studio): saving a text edit keeps whatever else is selected as it was
* test(studio): gate edit accuracy against the base branch baseline
Work in progress: the ratchet and its tests; the CI job follows.
* test(studio): run the edit accuracy gate in CI across eight shards
Shares the built CLI from the Build job, re-runs twice each case that passes on the base branch and failed, and posts one sticky comment from the gate job.
* test(studio): mark the ratchet accuracy check as intentionally branchy for fallow
* test(studio): confirm newly passing edit accuracy cases 2 of 3 before banking them
The shards re-ran only regressions, so one lucky pass of a base-failing case failed the gate as unbanked and was never listed as unstable. Every case whose verdict differs from the base branch, either way, is now re-run twice and judged 2 of 3. A render error fails the gate like an unsettled snapshot, a malformed baseline.json fails the job instead of reading as empty, and the header is 3 lines.
* ci(studio): run the edit accuracy gate for every package the bench builds or imports
* ci(studio): also run the edit accuracy gate for lint, sdk and the Studio and CLI build inputs
* ci(studio): run the edit accuracy gate when a bench package's manifest or exports change
* test(studio): bank the 120 edit accuracy cases that sub-pixel dragging now passes
* fix(studio): keep sub-pixel position and size while dragging and on drop
* test(studio): expect three-decimal rotation in the manual edits rotation test
* fix(studio): keep resized boxes on whole pixels so a centred element stays put
* test(studio): measure render drift against a producer frame in the edit accuracy bench
Finds the target's box in a producer-captured frame by its flat colour, with sub-pixel edges from area moments, and compares it with the reloaded preview. The baseline gains the render column from the same full run on main.
* test(studio): mark the pixel box scan as intentionally complex for fallow
* test(studio): regenerate the edit accuracy baseline with render drift on main
Same full run on main 14e87005d as #4760's baseline, with the render column: render passes 618/660, 70/660 pass, 314/660 pass everything but smoothness.
* test(studio): fail only render drift when the producer cannot render a case
A producer capture failure used to turn the case into a harness error that wiped every accuracy metric. It now sets render to null with renderError, fails render alone, and is counted in the table.
* test(studio): shorten the render drift box comment to two lines
* test(studio-server): history prune tests allow a file time a moment past Date.now()
* ci: temporary probe for the history prune test flake
* fix(studio): timeline scroll-end timer no longer fires after unmount
* ci: remove the temporary history prune probe
* test(studio): check the virtualizer teardown with a spy and a 200 ms wait
Page-side shader transitions clone the outgoing and incoming scenes,
ids included, into staging layers. Color grading grades the copied
<video> too, and findInjectedRenderFrame looked its frame up with
getElementById, which returns the live scene's <img>. The live and the
copied grading entries then both kept their canvas right after that one
<img>, moving each other on every mutation, and the loop blocked the
page: a graded <video> inside a transition stopped the render at the
transition's first frame.
Look through the element's following siblings first, where the injector
puts the frame, and fall back to the id lookup only when it isn't there.
Miguel Ángel