As
@pemerton just drew attention to, Baker says it's not about immediacy. Even parsimonious intents, if resolved are conflict resolution. If your intent of rolling for the blow is "does it land" and your method resolves that, it's conflict resolution.
player intentional act (strike with sword) > performance result (hit with sword) > intent resolved
But - and I think this will be the objection in your mind - that's not quite Baker's example
"I slash at his face, like ha!" "Why?" "To force him off-balance!"
Conflict Resolution: do you force him off-balance?
Roll: Loss!
"He ducks side to side, like fwip fwip! He keeps his feet and grins."
We resolve the slash landing to determine if we get the effect of force off-balance. And that is what players actually intend with their strikes in D&D combat. It's
"I strike at the troll, like ha!" "Why?" "To deal my weapon damage!"
Conflict Resolution: do you deal your weapon damage?
Roll: Loss!
"It ducks side to side! Avoids your slashes."
I guess I'm saying that I don't agree that players strike for the sake of striking. I've never seen that. Baker too, muses on this point. I feel like it is better not to make it about immediacy, so as to avoid blurred lines and better see the utility of task resolution to play. I want to use task resolution when I want to decide outcomes on some basis other than - players aimed to do it.