Hmm, because of the convenient-but-goofy options-grafting that grunt multiTask does, I think we'll need to come up with a way of providing those options to the deploy task. Perhaps setting the  transport task's config first to whatever the deploy tasks' is and then layering on its existing overrides. That way they'll have to mirror each other at runtime which will encourage folks to only set transport-specific task settings when they absolutely have to. (This is all doable btw, thanks to all the other config shenanigans I've had to do with lineman)