Comment 8 for bug 1534103

Initial guess: it seems there's a path where we can load a uniter/operation.State file and send it down a code path that can't handle run-action.

Easy fix is to find that problematic switch and add handling to Do The Right Thing:

Hard fix is to properly isolate decision-making, so that the top-level resolver is responsible only for delegating *appropriate information* to other resolvers -- so that the other resolvers don't get passed global state, and only know what they need to.

(whatever resolver it is obviously never even considered the possibility that it might get invoked with action state, but the "let's make resolver an interface!" approach makes these bugs inevitable)