docs(e2e): update READMEs for the consolidated suite layout (#24518)

Updates every README in the e2e test section to describe the suite as it
will look once the nine open
round-2 consolidation PRs land. This is docs-only — no code, config, or
`bootstrap.sh` changes.

## What changed per README

- **`end-to-end/README.md`** (root): repointed the `LOG_LEVEL` example
off the deleted
`proving/empty_blocks.test.ts` to `proving/default_node.test.ts`; linked
the new p2p README from the
category table (the p2p row now reads "yes" and points at
`src/p2p/README.md`); and renamed the
`setupBlockProducer` submission-window literal `1024` to the named
constant `NO_REORG_SUBMISSION_EPOCHS`.
- **`end-to-end/src/single-node/README.md`**: rewrote the `cross-chain/`
row for the merged layout
(`CrossChainMessagingTest` + `message_test_helpers.ts`, and the
`l1_to_l2` / `l1_to_l2_inbox_drift` /
`l2_to_l1` / `token_bridge` files); folded
`public_payments`/`sponsored_payments` into
`private_payments.parallel` and fixed the stale `failures.parallel` name
to `failures`; replaced
`slasher_config`/`sequencer_config` with the merged `runtime_config`;
replaced
`world_state_pruning`/`empty_blocks` with the merged `default_node`;
added the previously-missing
`snapshot_sync` to the `sync/` row; and applied the
`NO_REORG_SUBMISSION_EPOCHS` rename.
- **`end-to-end/src/multi-node/README.md`**: named
`equivocation_offenses` in the slashing row (in place
of the separate `duplicate_proposal`/`duplicate_attestation` files) and
applied the
`NO_REORG_SUBMISSION_EPOCHS` rename in the
`MOCK_GOSSIP_MULTI_VALIDATOR_OPTS` preset.
- **`end-to-end/src/p2p/README.md`** (new): created with the content
added by #24500.
- **`end-to-end/src/automine/README.md`** and
**`end-to-end/src/infra/README.md`**: untouched — both are
behavior-level (no file names) or cover a directory none of the nine PRs
change, so they remain accurate
  as-landed.

---------

Co-authored-by: AztecBot <tech@aztec-labs.com>
(cherry picked from commit 1cc5f91)

Author: 2 people

yarn-project/end-to-end/README.md

@@ -14,15 +14,21 @@ Run a single test (spawns its own in-process anvil):
 
 ```bash
 yarn test:e2e src/automine/token/access_control.parallel.test.ts
-yarn test:e2e src/single-node/block-building/block_building.test.ts -t 'rejects double spend'
+yarn test:e2e src/single-node/block-building/block_building.test.ts -t 'rejects a private then private double-spend'
 ```
 
 Turn up logging with `LOG_LEVEL` (`verbose` is the useful default; `debug:sequencer,archiver` scopes it):
 
 ```bash
-LOG_LEVEL=verbose yarn test:e2e src/single-node/proving/empty_blocks.test.ts
+LOG_LEVEL=verbose yarn test:e2e src/single-node/proving/default_node.test.ts
 ```
 
+Each run spawns anvil on port 8545, so two tests can only run side by side if each gets its own
+`ANVIL_PORT` (p2p tests additionally bind fixed p2p ports and can never run concurrently — see
+[`src/p2p/README.md`](src/p2p/README.md)). To shake flakiness out of a test,
+`scripts/deflaker.sh yarn test:e2e <file>` reruns it up to 100 times and stops at the first failure
+(output lands in `scripts/deflaker.log`).
+
 Compose-based tests (those under `src/composed/`) need a running local network — see
 [Compose / HA / web3signer tests](#compose--ha--web3signer-tests).
 
@@ -37,7 +43,7 @@ its environment, so a test file only describes the scenario, not the wiring.
 | [`automine/`](src/automine/README.md) | One node, deterministic `AutomineSequencer` — one block per tx, no committee/prover/validator. Fast. | it exercises contract or protocol behavior that doesn't depend on real block-building or consensus (transfers, nested calls, note discovery, tx semantics). | yes |
 | [`single-node/`](src/single-node/README.md) | One node, production sequencer (interval block production), optional prover. | it asserts on sequencer, proving, partial-proof, L1-reorg, recovery, fee, or cross-chain behavior on a single sequencer. | yes |
 | [`multi-node/`](src/multi-node/README.md) | N validators on an in-memory mock-gossip bus. | it needs a committee: consensus, attestations, slashing, governance, or multi-validator block production. | yes |
-| `p2p/` | Real libp2p transport between nodes. | the networking transport itself is under test (gossip, rediscovery, req/resp). | — |
+| [`p2p/`](src/p2p/README.md) | Real libp2p transport between nodes. | the networking transport itself is under test (gossip, rediscovery, req/resp). | yes |
 | [`infra/`](src/infra/README.md) | Targets a deployed/external network (local anvil or a public testnet). | its concern is deployment or network targeting, not a specific protocol behavior. | yes |
 
 A handful of tests live **outside** this package, next to the code they test — see
@@ -78,7 +84,7 @@ Each category centralizes its environment in a base class. The hierarchy:
   (both wrap `fixtures/setup.ts:setup()`), but fixes the automine topology and makes `AUTOMINE_E2E_OPTS`
   the default. Exposes `markProvenAndWarp`, `registerContract`, `applyManualParentChild`.
 - `p2p/p2p_network.ts` → **`P2PNetworkTest`**. Real libp2p; node creation goes through
-  `setup_p2p_test.ts`.
+  `fixtures/setup_p2p_test.ts`.
 - `infra/` has no shared base — its tests target a network selected by `L1_CHAIN_ID` (local anvil in CI,
   a public testnet with credentials).
 
@@ -91,8 +97,8 @@ Categories expose thin factories over their base's static `setup`, named by what
 calls the factory instead of spreading option presets:
 
 - `single-node/setup.ts`: `setupWithProver` (fake in-process prover — the single-node default) and
-  `setupBlockProducer` (no prover; raises `aztecProofSubmissionEpochs` to `1024` so unproven blocks
-  aren't pruned, and points the PXE at `syncChainTip: 'proposed'`).
+  `setupBlockProducer` (no prover; raises `aztecProofSubmissionEpochs` to `NO_REORG_SUBMISSION_EPOCHS`
+  (1024) so unproven blocks aren't pruned, and points the PXE at `syncChainTip: 'proposed'`).
 - `automine` tests call `AutomineTestContext.setup({ numberOfAccounts })` directly.
 
 ### The harness pattern (domain setup on top of a category)
@@ -136,15 +142,20 @@ CI splits each `it` in a `.parallel.test.ts` file into its own docker job, runni
 
 ### CI test discovery — `bootstrap.sh`
 
-`end-to-end/bootstrap.sh` enumerates tests in two arrays, and a test must appear in the relevant one or it
-**won't run in CI**:
+`end-to-end/bootstrap.sh` enumerates tests in two arrays, and a test must resolve through the relevant one
+or it **won't run in CI**:
 
-- `test_cmds` (~line 37) — the standard run.
-- `compat_test_cmds` (~line 290) — the forward/legacy-compat run (a subset).
+- `test_cmds` — the standard run. Covers each category with a recursive glob (e.g.
+  `src/automine/!(simulation)/**/*.test.ts`, `src/multi-node/**/*.test.ts`), so a new file or sub-folder
+  inside an existing category is picked up automatically; only a new top-level category needs its own glob
+  line. Tests with bespoke handling sit outside the globs: the `single-node/prover/` lanes at the top of
+  the function (real proofs and custom resources under `CI_FULL`, `FAKE_PROOFS=1` otherwise) and
+  `avm_simulator` (below).
+- `compat_test_cmds` — the forward/legacy-compat run (a subset). This one enumerates **single-level leaf
+  globs** (e.g. `src/automine/token/*.test.ts`), so a new sub-folder whose tests should run against legacy
+  contract artifacts needs its own line here.
 
-Each leaf folder needs its own single-level glob line (e.g. `src/automine/token/*.test.ts`) in each array;
-globs are not recursive, so every sub-folder is listed explicitly. Folders that organize by behavior get
-one line per leaf. Bespoke handling to be aware of:
+Bespoke handling to be aware of:
 
 - **`avm_simulator`** (`automine/simulation/avm_simulator.test.ts`) has a dedicated line in `test_cmds`
   that sets `DUMP_AVM_INPUTS_TO_DIR` (feeds the downstream `avm_check_circuit` job) and is therefore
@@ -153,8 +164,8 @@ one line per leaf. Bespoke handling to be aware of:
 - **`kernelless_simulation`** is excluded from `compat_test_cmds` only.
 
 After editing the arrays, confirm every `*.test.ts` resolves through exactly one line (no duplicate, no
-omission). Per-test bash `TIMEOUT` overrides live in the `case` block in `test_cmds` and must stay in sync
-with the test's `jest.setTimeout`.
+omission — anything excluded via `!(...)` must be matched by its dedicated line). Per-test bash `TIMEOUT`
+overrides live in the `case` block in `test_cmds` and must stay in sync with the test's `jest.setTimeout`.
 
 ### Flaky tests — `.test_patterns.yml`
 
@@ -190,11 +201,12 @@ These run in their own package's test lane (both packages already run anvil-back
 
 ### Support directories (not test categories)
 
-- `fixtures/` — the shared `setup()`, option presets (`fixtures.ts`), `CrossChainTestHarness`,
-  `l1_to_l2_messaging`, and common utils.
-- `shared/` — shared test bodies and `timing_env.mjs`, a **custom jest `testEnvironment`** referenced from
-  this package's `package.json`. `yarn prepare` / the package-json check will try to revert it to the
-  default — don't let it.
+- `fixtures/` — the shared `setup()`, option presets (`fixtures.ts`), the named node-level waiters
+  (`wait_helpers.ts`), the span instrumentation (`timing.ts` — `testSpan`, zero-cost unless
+  `TEST_TIMING_FILE` is set), `l1_to_l2_messaging`, and common utils.
+- `shared/` — shared test bodies, the `CrossChainTestHarness`, and `timing_env.mjs`, a **custom jest
+  `testEnvironment`** referenced from this package's `package.json`. `yarn prepare` / the package-json
+  check will try to revert it to the default — don't let it.
 - `simulators/` — in-TS reference models (`TokenSimulator`, `LendingSimulator`) used to assert contract
   behavior.
 - `test-wallet/`, `bench/`, `spartan/`, `quality_of_service/`, `forward-compatibility/` — helpers,

yarn-project/end-to-end/src/multi-node/README.md

@@ -31,7 +31,8 @@ copy-pasted:
   `getPrivateKeyFromIndex(i + 3)`), passed as `initialValidators`.
 - `MOCK_GOSSIP_MULTI_VALIDATOR_OPTS` — a tight committee on the mock bus with no prover
   (`{ mockGossipSubNetwork, skipInitialSequencer, startProverNode: false, aztecProofSubmissionEpochs:
-  1024, numberOfAccounts: 0 }`). Tests that want a prover leave `startProverNode` explicit.
+  NO_REORG_SUBMISSION_EPOCHS, numberOfAccounts: 0 }`, the constant re-exported from `../single-node/setup.ts`).
+  Tests that want a prover leave `startProverNode` explicit.
 - `SLASHER_ENABLED_MULTI_VALIDATOR_OPTS` — the same committee with the slasher turned on, used by the
   offense-detection tests.
 - `defaultSlashingPenalties(unit?)` / `withOnlyOffense(offense, unit?)` — build the per-offense