question: so if the AWS plugin had its own bevvy of options, a user would override them like any other task? meaning that they might define a set of `deploy` properties for the project deployment scheme but a set of `linemanDeployAws` properties for the AWS plugin's task?

That seems all right, but I wonder whether or not that would confuse folks, especially if they use AWS for both staging & production and the options they want to give the linemanDeployAws task differ between staging and production? How would a user pull that off?