fix(docs): update CLI commands, ABI fields, and tutorial fixes (#22160)

## Summary
- Update `aztec new` CLI syntax to remove deprecated `--contract` flag
in counter and recursive verification tutorials
- Rename `l2BlockNumber` to `checkpointNumber` in Inbox ABI
`MessageSent` event (token_bridge tutorial, example_swap, token_bridge
example)
- Remove unused `@aztec/test-wallet` package from token contract
tutorial install commands
- Fix import path and `#include_code` macro in recursive verification
tutorial
- Use approximate proof size (`~500`) instead of hardcoded `508`

## Test plan
- [ ] Verify `yarn build` passes in `docs/`
- [ ] Spot-check affected tutorial pages render correctly

Author: AztecBot

docs/developer_versioned_docs/version-v4.2.0-aztecnr-rc.2/docs/tutorials/contract_tutorials/counter_contract.md

@@ -22,7 +22,7 @@ This tutorial is compatible with the Aztec version `4.2.0-aztecnr-rc.2`. Install
 Run this to create a new contract project:
 
 ```bash
-aztec new --contract counter
+aztec new counter
 ```
 
 Your structure should look like this:

docs/developer_versioned_docs/version-v4.2.0-aztecnr-rc.2/docs/tutorials/contract_tutorials/recursive_verification.md

@@ -42,7 +42,7 @@ For example, consider a machine learning inference that needs 10,000 input featu
 
 1. Perform the computation offchain in a vanilla Noir circuit with no input limits
 2. Generate a proof of correct execution
-3. Verify only the proof onchain (115 fields for VK + 457-508 fields for proof + N public inputs)
+3. Verify only the proof onchain (115 fields for VK + ~500 fields for proof + N public inputs)
 
 This pattern transforms arbitrarily large computations into fixed-size proof verification.
 
@@ -68,7 +68,7 @@ flowchart LR
 
 Proof verification enables several patterns:
 
-- **Bypassing Input Limits**: Aztec private functions have strict input constraints. A proof verification call uses ~624 fields (115 VK + 508 proof + 1 public input), but can attest to computations with arbitrarily many inputs. For example, proving membership in a set of 10,000 elements becomes a fixed-size verification.
+- **Bypassing Input Limits**: Aztec private functions have strict input constraints. A proof verification call uses ~616 fields (115 VK + ~500 proof + 1 public input), but can attest to computations with arbitrarily many inputs. For example, proving membership in a set of 10,000 elements becomes a fixed-size verification.
 
 - **Cross-System Verification**: Verify proofs generated by external Noir circuits within your Aztec application. This enables composability: your contract can trust computations performed by other systems without those systems needing to be Aztec-native.
 
@@ -225,10 +225,10 @@ The contract demonstrates several important patterns:
 
 ### Create the Contract Project
 
-Use `aztec init` to generate the contract project structure:
+Use `aztec new` to generate the contract project structure:
 
 ```bash
-aztec init --contract contract
+aztec new contract --name ValueNotEqual
 ```
 
 This creates:
@@ -541,7 +541,7 @@ Create `scripts/generate_data.ts`:
 
 ```typescript title="generate_data" showLineNumbers 
 import { Noir } from "@aztec/noir-noir_js";
-import circuitJson from "../../../../target/hello_circuit.json" with { type: "json" };
+import circuitJson from "../circuit/target/hello_circuit.json" with { type: "json" };
 import { Barretenberg, UltraHonkBackend, deflattenFields } from "@aztec/bb.js";
 import fs from "fs";
 import { exit } from "process";
@@ -597,14 +597,14 @@ if (proofAsFields.length === 0) {
 const vkAsFields = recursiveArtifacts.vkAsFields;
 
 console.log(`VK size: ${vkAsFields.length}`); // Should be 115
-console.log(`Proof size: ${proofAsFields.length}`); // Should be 508
+console.log(`Proof size: ${proofAsFields.length}`); // Should be ~500
 console.log(`Public inputs: ${mainProofData.publicInputs.length}`); // Should be 1
 
 // Step 9: Save all data to JSON for contract interaction
 const data = {
   vkAsFields: vkAsFields, // 115 field elements - the verification key
   vkHash: recursiveArtifacts.vkHash, // Hash of VK - stored in contract
-  proofAsFields: proofAsFields, // 508 field elements - the proof
+  proofAsFields: proofAsFields, // ~500 field elements - the proof
   publicInputs: mainProofData.publicInputs.map((p: string) => p.toString()),
 };
 
@@ -659,7 +659,7 @@ Always verify locally before submitting onchain. Onchain verification costs gas/
 
 #### Field Element Conversion
 
-ZK proofs are arrays of bytes, but Aztec contracts work with field elements. We convert the proof and VK to arrays of 115 and 508 field elements respectively.
+ZK proofs are arrays of bytes, but Aztec contracts work with field elements. We convert the proof and VK to arrays of 115 and ~500 field elements respectively.
 
 ```typescript
 let proofAsFields = recursiveArtifacts.proofAsFields;
@@ -701,7 +701,7 @@ Expected output:
 Proof verification: SUCCESS
 Using deflattenFields to convert proof...
 VK size: 115
-Proof size: 508
+Proof size: 500
 Public inputs: 1
 Done
 ```
@@ -714,7 +714,7 @@ The generated `data.json` contains:
 {
   "vkAsFields": ["0x...", "0x...", ...],   // 115 field elements
   "vkHash": "0x...",                        // Single field element
-  "proofAsFields": ["0x...", "0x...", ...], // 508 field elements
+  "proofAsFields": ["0x...", "0x...", ...], // ~500 field elements
   "publicInputs": ["2"]                     // The public input y=2
 }
 ```
@@ -832,7 +832,7 @@ async function main() {
   const interaction = await valueNotEqual.methods.increment(
     accounts[0].item,
     data.vkAsFields as unknown as FieldLike[], // 115 field VK
-    data.proofAsFields as unknown as FieldLike[], // 508 field proof
+    data.proofAsFields as unknown as FieldLike[], // ~500 field proof
     data.publicInputs as unknown as FieldLike[], // Public inputs
   );
 
@@ -885,7 +885,7 @@ This single line triggers a complex flow:
 
 2. **Proof Generation** (client-side, in PXE):
    - Generate a ZK proof that the private execution was correct
-   - This proof doesn't reveal inputs (including the 508-field proof!)
+   - This proof doesn't reveal inputs (including the ~500-field proof!)
 
 3. **Transaction Submission**:
    - Send the proof + encrypted logs + public function calls to the network

docs/developer_versioned_docs/version-v4.2.0-aztecnr-rc.2/docs/tutorials/contract_tutorials/token_contract.md

@@ -44,13 +44,13 @@ cd bob_token
 yarn init
 # This is to ensure yarn uses node_modules instead of pnp for dependency installation
 yarn config set nodeLinker node-modules
-yarn add @aztec/aztec.js@4.2.0-aztecnr-rc.2 @aztec/accounts@4.2.0-aztecnr-rc.2 @aztec/test-wallet@4.2.0-aztecnr-rc.2 @aztec/kv-store@4.2.0-aztecnr-rc.2
+yarn add @aztec/aztec.js@4.2.0-aztecnr-rc.2 @aztec/accounts@4.2.0-aztecnr-rc.2 @aztec/kv-store@4.2.0-aztecnr-rc.2
 aztec init
 ```
 
 ## Contract structure
 
-The `aztec init` command created a workspace with two crates: a `bob_token_contract` crate for your smart contract code and a `bob_token_test` crate for Noir tests. In `bob_token_contract/src/main.nr` we even have a proto-contract. Let's replace it with a simple starting point:
+The `aztec init` command created a contract project with `Nargo.toml` and `src/main.nr`. Let's replace the boilerplate in `src/main.nr` with a simple starting point:
 
 ```rust
 use aztec::macros::aztec;

docs/developer_versioned_docs/version-v4.2.0-aztecnr-rc.2/docs/tutorials/js_tutorials/token_bridge.md

@@ -830,7 +830,7 @@ const INBOX_ABI = [
     type: "event",
     name: "MessageSent",
     inputs: [
-      { name: "l2BlockNumber", type: "uint256", indexed: true },
+      { name: "checkpointNumber", type: "uint256", indexed: true },
       { name: "index", type: "uint256", indexed: false },
       { name: "hash", type: "bytes32", indexed: true },
       { name: "rollingHash", type: "bytes16", indexed: false },

docs/docs-developers/docs/tutorials/contract_tutorials/counter_contract.md

@@ -41,9 +41,9 @@ Your structure should look like this:
 | | |-Nargo.toml            <-- test package config
 ```
 
-The `aztec new` command creates a workspace with two crates: a `counter_contract` crate for your smart contract code and a `counter_test` crate for Noir tests. The file `counter_contract/src/main.nr` will soon turn into our smart contract!
+The `aztec new` command creates a contract project with `Nargo.toml` and `src/main.nr`. The file `src/main.nr` will soon turn into our smart contract!
 
-Add the following dependency to `counter_contract/Nargo.toml` under the existing `aztec` dependency:
+Add the following dependency to `Nargo.toml` under the existing `aztec` dependency:
 
 ```toml
 [dependencies]

docs/docs-developers/docs/tutorials/contract_tutorials/recursive_verification.md

@@ -211,19 +211,13 @@ Use `aztec new` to generate the contract project structure:
 aztec new contract --name ValueNotEqual
 ```
 
-This creates a workspace with two crates:
+This creates:
 
 ```tree
 contract/
-├── Nargo.toml           # Workspace root
-├── contract/
-│   ├── src/
-│   │   └── main.nr      # Contract code
-│   └── Nargo.toml       # Contract configuration
-└── test/
-    ├── src/
-    │   └── lib.nr        # Test code
-    └── Nargo.toml        # Test configuration
+├── src/
+│   └── main.nr      # Contract code
+└── Nargo.toml       # Contract configuration
 ```
 
 ### Contract Configuration
@@ -460,7 +454,10 @@ The proof generation script executes the circuit offchain and produces the proof
 
 Create `scripts/generate_data.ts`:
 
-#include_code generate_data /docs/examples/ts/recursive_verification/scripts/generate_data.ts typescript
+```js
+import circuitJson from "../circuit/target/hello_circuit.json" with { type: "json" };
+#include_code generate_data /docs/examples/ts/recursive_verification/scripts/generate_data.ts raw
+```
 
 ### Understanding the Proof Generation Pipeline
 

docs/docs-developers/docs/tutorials/contract_tutorials/token_contract.md

@@ -44,13 +44,13 @@ cd bob_token
 yarn init
 # This is to ensure yarn uses node_modules instead of pnp for dependency installation
 yarn config set nodeLinker node-modules
-yarn add @aztec/aztec.js@#include_aztec_version @aztec/accounts@#include_aztec_version @aztec/test-wallet@#include_aztec_version @aztec/kv-store@#include_aztec_version
+yarn add @aztec/aztec.js@#include_aztec_version @aztec/accounts@#include_aztec_version @aztec/kv-store@#include_aztec_version
 aztec init
 ```
 
 ## Contract structure
 
-The `aztec init` command created a workspace with two crates: a `bob_token_contract` crate for your smart contract code and a `bob_token_test` crate for Noir tests. In `bob_token_contract/src/main.nr` we even have a proto-contract. Let's replace it with a simple starting point:
+The `aztec init` command created a contract project with `Nargo.toml` and `src/main.nr`. Let's replace the boilerplate in `src/main.nr` with a simple starting point:
 
 ```rust
 #include_code start /docs/examples/contracts/bob_token_contract/src/main.nr raw

docs/examples/ts/example_swap/index.ts

@@ -260,7 +260,7 @@ const INBOX_ABI = [
     type: "event",
     name: "MessageSent",
     inputs: [
-      { name: "l2BlockNumber", type: "uint256", indexed: true },
+      { name: "checkpointNumber", type: "uint256", indexed: true },
       { name: "index", type: "uint256", indexed: false },
       { name: "hash", type: "bytes32", indexed: true },
       { name: "rollingHash", type: "bytes16", indexed: false },

docs/examples/ts/recursive_verification/scripts/generate_data.ts

@@ -1,6 +1,6 @@
+import circuitJson from "../../../../target/hello_circuit.json" with { type: "json" };
 // docs:start:generate_data
 import { Noir } from "@aztec/noir-noir_js";
-import circuitJson from "../../../../target/hello_circuit.json" with { type: "json" };
 import { Barretenberg, UltraHonkBackend, deflattenFields } from "@aztec/bb.js";
 import fs from "fs";
 import { exit } from "process";
@@ -56,14 +56,14 @@ if (proofAsFields.length === 0) {
 const vkAsFields = recursiveArtifacts.vkAsFields;
 
 console.log(`VK size: ${vkAsFields.length}`); // Should be 115
-console.log(`Proof size: ${proofAsFields.length}`); // Should be 508
+console.log(`Proof size: ${proofAsFields.length}`); // Should be ~500
 console.log(`Public inputs: ${mainProofData.publicInputs.length}`); // Should be 1
 
 // Step 9: Save all data to JSON for contract interaction
 const data = {
   vkAsFields: vkAsFields, // 115 field elements - the verification key
   vkHash: recursiveArtifacts.vkHash, // Hash of VK - stored in contract
-  proofAsFields: proofAsFields, // 508 field elements - the proof
+  proofAsFields: proofAsFields, // ~500 field elements - the proof
   publicInputs: mainProofData.publicInputs.map((p: string) => p.toString()),
 };
 

docs/examples/ts/token_bridge/index.ts

@@ -162,7 +162,7 @@ const INBOX_ABI = [
     type: "event",
     name: "MessageSent",
     inputs: [
-      { name: "l2BlockNumber", type: "uint256", indexed: true },
+      { name: "checkpointNumber", type: "uint256", indexed: true },
       { name: "index", type: "uint256", indexed: false },
       { name: "hash", type: "bytes32", indexed: true },
       { name: "rollingHash", type: "bytes16", indexed: false },