One way to look at this is from a "server/client" relationship. The more control the GM exerts, the more work he has to do and the slower things can get. Trying to micromanage every attack attempt for eight pilots could quickly become a full time job.
Another way to handle it would be to push back some of the work to the "clients". Instead of small, frequent information bursts, the GM might put together mini-design documents for each situation. This is whats in front of you, this is what I would like to happen. If you do this, then maybe this. If not, then that.
I will admit, I didn't fire on that Commando because I didn't know how you all wanted to do this. But if Wolf hadn't been there and my pilot was a better shot, I probably would have lit him up too. I really don't have a good feel for how much control we should be exerting on the battlefield or on hostile NPCs. If I blast that Commando but good, his immediate response is going to depend on factors that I don't know. Are there other hidden 'Mechs backing him up, or is he alone? I have the option of ending my post with the hit or not firing. But if the hidden units are part of the design notes I get as part of the contact report, I can work a bit of that into my post, even if my character has no idea why the target is doing what he's doing. There's a control vs speed balance here-- we're going to have to kind of feel things out as we go along.
And taken in the context of workload and bandwidth, I can see why Wolf did what he did. We
were kind of poking him to resolve his contact and given his access constraints he did just that. Just. . .maybe more communication next time.
I'm going to go quiet for a bit and give others the opportunity to get their 'Mech on. Anyone in my general area (Shepherd, it seemed like you should be crossing close to me here soon) will see Virgil "sit down" hard and eat sod. No obvious damage, but Spokes has had her bell rung.
Wolf, this looks like a great time for a flashback or a "questions his life choices" post.