Currently the MusicTxDigest daemon doesn't differentiates between operations created locally and the ones create remotely, which causes that changes created locally are reapplied, when found in Music during the periodic run of the thread.

This problem causes random glitches. An example:

Locally perform:

1. Create rows
2. Delete the rows

When applying the remote transactions, rows in step 1 are created again, and other operations may see it, even though step 2 already delete it.

This is hard to solve, so we need to architect a new solution.