FinishMessenger has a lot of methods that are dupes of code in ManagerMessenger. I think this is because various other manager routines ended up needing features originally intended for Finishing.
All this is a big artificial as there is no distinct "finisher" user (and no plans to be).
- remove FinisherManager altogether, moving the remaining non-dupes into ManagerMessenger
- make FinisherManager a subclass of ManagerMessenger: this is good for deduping code but I'm not sure it offers much practical benefit.
There are related things (which probably nudge towards the first option), for example I'm currently looking at calling a
plom.finish function within the Manager UI but the function wrapped in a