This is a request from @nventuro.

It's not really meaningful to run nargo compile on contracts as in order to deploy these you need to perform a post-processing step to transpile the public functions and generate vks. This ends up confusing users who don't use aztec tooling for their contracts as they "compiled" but don't have the finalised artifact.

The solution proposed for this is to require a flag to be passed for nargo to compile a contract confirming that the user understands that they're going to be doing "partial" compilation. Any tooling written around nargo for contracts then would provide this flag but if a user mistakenly uses vanilla nargo then it will raise an error:

• Suggesting that the user probably wants to use some external tooling, linking off to the docs which can forward people on to aztec-nr.
• Explaining about the CLI flag in order to force nargo to compile the contract.