Remaining in terms of priorities for final polish, summarizing what I'm thinking from the discussion above:
top priority: some way to tell user when "the constraints you requested are impossible to satisfy" which I think is an important part of this workflow. looks like this may need some JSON handling and a message in the UI somewhere (trace text areas?) indicating this result
updating the equivalence condition display as discussed above (keep orig equiv cond, maybe display other info on user constraints when present, reuse existing equiv cond textbox?)
minimizing confusion with replay. I think this is lowest priority since replay isn't a core part of the workflow. I think the smallest simplest thing we could do here is maybe just change the button text from Constrain Trace to Constrain Trace (replay) when we're in replay mode
Basically working. From Ben's message in MM:
Remaining in terms of priorities for final polish, summarizing what I'm thinking from the discussion above: