Currently persist the whole history, this includes origin / modified version of files. Kind of heavy! But my take is that it will be useful to prototype features like "revert" until we add versioning
added a versioning scheme to the history type since it's JSON in the DB, in case we need to run some migrations
Moved some types in shared. Don't love doing this but we have a client/server contract now so it's justified
The history is now persisted into SQLite DB.
Notes