Actions watcher redux

Make sure Actions queued before a watcher starts are picked up when the watcher does start.

Also slight refactoring to prepare for Actions being queued on Services as well as Units
I think it would be clearer to name it based on what you want to do with it, rather than just whatever it happens to implement. Like we call it "Entity" not "Tagger".
Is there a reason you need "Name" beyond just using the "Tag" that you already have from Entity?
I guess we want to not use Tags in the database documents, so we would want something else to refer to them by. (Id comes to mind, but that might be scoped without enough context, Name might just be the correct thing.)