right now all ui representations of session state are badges that reflect the status of the underlying socket pulling session events, but we have actual session state information from coral server that needs to be accounted for (pending_execution, executed, closing).
NOTE that we still want to reflect the state of the underlying socket, since if that takes a while to connect, or dies somehow - we want the user to tell
right now all ui representations of session state are badges that reflect the status of the underlying socket pulling session events, but we have actual session state information from coral server that needs to be accounted for (pending_execution, executed, closing).
NOTE that we still want to reflect the state of the underlying socket, since if that takes a while to connect, or dies somehow - we want the user to tell