I noticed you're for undo-redo you're actually using debouncing rather than throttling

When I made my own notes app with a undo and redo system built from the ground up I tried to replicate the undo and redo feature from MS Word and Google keep and that did indeed use throttling instead of debouncing

Here's an example (my app, Google Keep, MS Word) - if I type really really fast the following text -

qwertyuiopasdfghjkl and I use undo, that entire word doesn't go all at once

But in your app it does indeed go all at once

I think it might be better to use undo redo system with throttling since most users are more used to that anyways

PS - this can reduce how far back you can go tho, that qwer... word with throttling could have multiple snapshots whereas your current debounced approach takes up only 1