Suggestion: Optional jj-inspired workflow

I have been following this project with enthusiasm in hopes it enables CICD operations with flexo! A suggestion if I may be so bold:

Since flexo operates as a centralized, server-coordinated, versioned graph system rather than a truly distributed VCS, much of the complexity in the proposed git-style workflows is inherited rather than necessary - these patterns primarily solve distributed coordination problems that flexo doesn't face.

In contrast, jj-style (Jujutsu) workflows, with continuous editing, mutable commits, automatic snapshotting, first-class history rewriting, align well with flexo's graph-native, semantic model backend. An optional jj-inspired workflow mode layered on top of the existing CLI could significantly reduce cognitive overhead for MBSE users who aren't typically git-fluent (I've personally experienced this firsthand training "systems engineers" to use git).

The CLI could mirror jj's approach of namespacing legacy compatibility under flexo git <command> while making the more intuitive jj-sytle workflow the default.

Happy to discuss further on Slack or Google Groups, and I'd also love to get involved in flexo development, particularly this project.

No files or tests are named. Start by reviewing the existing flexo CLI workflow and its graph model, then compare the proposed optional jj-inspired mode with the current git-style commands; done should be a defined, agreed scope for the workflow and its compatibility behavior.