`git history` lands Jujutsu workflows in Git

While Jujutsu gets the developer hype for its first-class conflict handling and operation logs, `git history` shows that Git is quietly absorbing its competitor's best features to prevent developer migration.

• –The atomic execution model ensures that rewrites either succeed fully or fail safely, eliminating the risk of leaving the working tree in a broken mid-rebase state.
• –Because operations like `reword` and `split` work directly on the commit graph without touching the index or working tree, developers can rewrite history on other branches without disturbing their active workspace.
• –The tool's current inability to handle merge commits or support first-class conflicts means Jujutsu still holds a technical edge, but native integration makes `git history` highly practical for daily Git users.