feat(core): add deterministic keyframe ease runtime#2672
Draft
miguel-heygen wants to merge 1 commit into
Draft
Conversation
Collaborator
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jul 21, 2026
miguel-heygen
force-pushed
the
codex/studio-timeline-a-runtime-eases-v2
branch
3 times, most recently
from
July 21, 2026 05:50
67d3da0 to
b64c98d
Compare
miguel-heygen
force-pushed
the
codex/studio-timeline-a-runtime-eases-v2
branch
from
July 21, 2026 10:18
b64c98d to
73b793d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What
Add the deterministic easing runtime used by Studio-authored keyframes, including custom curves, hold, spring, and wiggle easing.
This is Family A, PR 1 of 4. It is rooted on
main; the next PR iscodex/studio-timeline-a-parser-intent-v2.Replacement review history: #2561. Golden reference: #2387.
Why
Studio must interpret and render every authored ease identically in preview and capture. Keeping the easing parser and runtime registration together gives the stack one deterministic owner for those semantics.
How
The runtime registers the supported custom-ease forms once, exposes the shared motion-ease model through Core, and adds focused coverage for parsing and runtime initialization. Current
mainalready contains the merged runtime bridge from #2558; this PR does not recreate it.Test plan