docs(l1): state that the generic deploy scripts are the test/testnet deployer, not the mainnet path

[AztecBot]

Summary

Comment-only change. l1-contracts/script/deploy/ (DeployAztecL1Contracts.s.sol, DeployRollupForUpgrade.s.sol, DeployRollupLib.sol, RollupConfiguration.sol) is the env-driven deployer for tests, spartan/CLI and testnets. Nothing in the tree says so, and a reader who finds REAL_VERIFIER defaulting to a mock verifier or genesis roots defaulting to zero can reasonably conclude that mainnet is one unset variable away from a bad deployment.

It is not. Mainnet's one-off contracts were deployed from AztecProtocol/ignition-contracts, and each mainnet rollup version is deployed by a bespoke pinned script, DeployRollupForUpgradeV<N>.s.sol, that hard-codes and re-verifies that deployment's configuration: v5 from DeployRollupForUpgradeV5.s.sol on the v5-next branch, v6 from DeployRollupForUpgradeV6.s.sol (#25496).

Change

• A doc comment on each of the four generic script files stating what they are for, that mainnet uses the pinned per-version scripts, and that the env defaults are test-network conveniences.
• One sentence on the root CLAUDE.md line that introduces l1-contracts/, so agents working in the tree do not classify generic-script defaults as mainnet findings.

No bytecode, behaviour, gas or test changes. forge fmt --check passes on the four files.

---

Created by claudebox · group: slackbot · requested by Mike (@iAmMichaelConnor) · Slack thread

[AztecBot]

Flakey Tests

🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (8;;http://ci.aztec-labs.com/6a27ff87182d0f97�6a27ff87182d0f978;;�): cd labs && export root= ci3= &&  yarn-project/end-to-end/scripts/run_test.sh simple src/single-node/cross-chain/inbox_bot.test.ts (345s) (code: 0) group:e2e-p2p-epoch-flakes