TagFS now provides durability on most changes to metadata through the use of SQLite transactions. Creations, deletions, and modifications of the backing files are not atomic and TagFS will not make any attempt to detect or correct inconsistencies between the database and the backing files. Happily, only an uncompleted file create operation could cause a problem in file system operation (i.e., a 'ghost' file without data), and that is easily fixed by creating a file with the extra ID as its name in the data directory under 'copies'.
Per-file values for a tag, a feature which existed but could not be utilized previously, has not yet been added to the new SQLite database. Release 2 will probably see this functionality restored and made available. A script for migrating to the new database table structure should be provided.