Design Lottie/Rive state-machine workflow

[Sportinger]

Migrated from issue #90, which was removed from the issue tracker to keep workflow design questions in Discussions.

Topic

Design an intuitive timeline workflow for Lottie/Rive state machines.

Context

MasterSelects already supports Lottie files. The missing workflow is a way to render or switch between different animation states from the same Lottie/Rive track on the timeline.

A comment suggested allowing the LottieTab to keyframe the state machine.

Possible Goals

• Let users change Lottie/Rive animation states over time from the timeline.
• Make state changes keyframeable or clip-segment-based.
• Support a clear UI in the properties panel/LottieTab.
• Keep playback and export behavior deterministic.
• Preserve existing Lottie timeline behavior while adding state control.

Open Questions

• Should state changes be keyframes, markers, clip segments, or a dedicated state lane?
• How should Rive state machines map to Lottie-style animation controls, given the formats differ?
• Should state transitions have durations/easing?
• What should happen if a file has no explicit state machine?
• How should this serialize in projects?

Recommendation: use this discussion to settle the UX model, then open focused implementation issues for the first supported format and control style.