[FEATURE] Make `aztec compile` work with plain Noir circuits

[jasonxh]

Problem Statement

Our project involves both Aztec contracts and plain Noir circuits. Though they are maintained in separate Nargo workspaces, which means it's possible to use the plain Nargo toolchain for one and the Aztec toolchain for the other, we would prefer to consolidate them onto a single toolchain for a couple of reasons:

• To be able to share the same runtime dependencies (bb & noir), we need to ensure they are compiled with compatible toolchain versions. Using two separate toolchains introduces a potential discrepancy.
• To simplify dev requirement and IDE integration.

This was briefly achieved with the previous Aztec devnet.5 release thanks to the separation of aztec-postprocess-contract, but broken again in the latest devnet.20251212 release.

Proposed Solution

The simplest solution is to introduce a flag to aztec compile to optionally skip contract postprocessing, e.g. aztec compile --skip-postprocessing. This should make it usable with plain Noir workspaces. aztec test already seems to run plain Noir tests just fine.

Example Use Case

No response

Alternative Solutions

A more powerful alternative is to be more intelligent about which targets to run postprocessing on, so it doesn't produce an error for plain Noir circuits. This would support workspaces with mixed Aztec contracts and Noir circuits.

To fully support mixed workspaces, other commands such as aztec codegen would also need to updated with similar filtering. This would solve #14138.

Additional Context

No response

[alejoamiras]

Hey @nventuro - I thinks this is pretty valid, specially

"Using two separate toolchains introduces a potential discrepancy."

Can make the devex a bit awful. And the proposal for the skip flag seems fairly straight-forward to apply. Any chance we work on this, and maybe backport to devnet? Since we want to support Nyx's development pipeline as much as possible here.