So, first I’d disable auto_sync to make sure no hosts push bad history
atuin store purge
- this will delete all records in the store that cannot be decrypted with the current keyatuin store verify
- verify that the previous operation was successfulatuin store push --force
- this will delete all records stored remotely, and then push up local data. Run this on the machine that has been purgedatuin store pull --force
- this does the opposite to (3). Delete all local data in the store, and pull from the remoteatuin store rebuild history
- ensure your history.db is up to date after all these operations
Currently not possible, though with a similar set of steps to the above it could be. Due to the nature of sync, ensuring that those steps propagate properly is difficult