TECH TASK: refactor `messenger`
STUB
after changes to execute
, we can catch up here. some ideas:
- rename to
router
- completely consume the
dispatchable
in theexecute
layer and only handle acommandResponse
at this layer - handle all messages in one flow instead of
handleBroadcast
andhandleCommandResponse
. will mean:- making the current
handleCommandResponse
the main workhorse of the module and handling all messages in it - dispatching on whether or not to respond as the main branching logic in taht function
- sending all "relayable message" notifications in sequence
- figuring out what we want to do about expiry times for all cases
- making the current