feat(sandbox): support proposer pipelining in local network

[spalladino]

Motivation

The local network sandbox (aztec start --local-network) historically ran without proposer pipelining, so the compose-routed e2e suite (src/composed/*, src/guides/*, cli-wallet flows, docs examples, playground) never exercised the pipelined sequencer path. Turning pipelining on revealed that each L2 slot took a full real-time slot (~72 s) before the L1 multicall fired, blowing up sandbox boot from ~30 s to ~5 min, because the existing AnvilTestWatcher triggers don't fire in the pipelined-publish window.

Approach

First commit flips SEQ_ENABLE_PROPOSER_PIPELINING=true on the three sandbox-test compose envs so every compose-routed test runs through the pipelined path. Second commit teaches AnvilTestWatcher about the proposer's target slot by hooking the sequencer's block-proposed event in createLocalNetwork; when the proposer has built a block destined for a slot beyond L1, the watcher warps L1 (and, via cheatcodes.warp, the injected date provider) forward, waking the pipelined publisher's sendRequestsAt sleep and the upstream waitForValidParentCheckpointOnL1 wait. block-proposed is used rather than the cleaner state-changed → PUBLISHING_CHECKPOINT because the latter only fires after waitForValidParentCheckpointOnL1 unblocks — which is what we are trying to break — so it would be circular.

Changes

• yarn-project/end-to-end, docs/examples/ts, playground (compose): add SEQ_ENABLE_PROPOSER_PIPELINING=true to the local-network / aztec service env so every compose-routed sandbox test runs pipelined.
• yarn-project/aztec (AnvilTestWatcher): new setProposedTargetSlot setter and a warpTimeIfNeeded branch (gated on isLocalNetwork) that warps L1 to the target slot's timestamp when it's ahead of L1.
• yarn-project/aztec (createLocalNetwork): subscribe to the sequencer's block-proposed event and forward slot to the watcher.

Verified locally: sandbox boot drops from ~5 min back to ~27 s under pipelining, and e2e_local_network_example.test.ts (both tests) passes in ~33 s.

[spalladino]

Pipelining audit

Verified the sandbox tests in this PR's scope ran on CI with SEQ_ENABLE_PROPOSER_PIPELINING=true. Source CI runs:

• ci/x-fast: http://ci.aztec-labs.com/1778773769394493 (test-engine: http://ci.aztec-labs.com/05915e321cd71670)
• ci/x-full: http://ci.aztec-labs.com/1778778416696771 (test-engine: http://ci.aztec-labs.com/ab7d7da11109f10c)

Both runs are SUCCESS. All compose-routed sandbox tests under yarn-project-tests were marked SKIPPED in the latest test-engine list because each was satisfied by a test-cache hit — but every cache entry references a test log run on this PR's HEAD or its 2nd commit (commit 323a501a includes both the compose env flip and the watcher fix). The aztec-up shell tests have no test cache and ran fresh on the final commit 7582d53e (the one that exports SEQ_ENABLE_PROPOSER_PIPELINING=true in aztec-up/test/*.sh).

Direct config-dump evidence ("enableProposerPipelining":true seen on the sandbox node startup)

These tests stream the local-network/sandbox node stdout into the test log, so the node's startup config dump is directly visible:

Test	Ran	Pipelining=true in node config	Log
aztec-up/test/amm_flow.sh	yes (325s, PASSED)	yes	http://ci.aztec-labs.com/af2b68e7a1d884e1
aztec-up/test/bridge_and_claim.sh	yes (248s, PASSED)	yes	http://ci.aztec-labs.com/418776554c4dce4c
aztec-up/test/basic_install.sh	yes (283s, PASSED)	n/a — script sets LOG_LEVEL=silent, but exports SEQ_ENABLE_PROPOSER_PIPELINING=true (see basic_install.sh L11-L13)	http://ci.aztec-labs.com/47cd2a28761b8cd6
playground chromium	yes (1 passed, 7.9s)	yes (line 33: "l1ChainId":31337,"enableProposerPipelining":true)	http://ci.aztec-labs.com/928d273ed3d0849f
playground firefox	yes (1 passed, 21.0s)	yes (same config dump)	http://ci.aztec-labs.com/fcb032ebb35eac96
docs/examples runner (all 7 examples)	yes (all PASS: aztecjs_connection, aztecjs_getting_started, aztecjs_advanced, aztecjs_authwit, aztecjs_testing, example_swap, recursive_verification)	local-network stdout is not multiplexed into the docs-examples container log, but the compose env sets SEQ_ENABLE_PROPOSER_PIPELINING: 'true' (docs/examples/ts/docker-compose.yml L31)	http://ci.aztec-labs.com/8b68c8bc3be31e54

Sample config-line for amm_flow (line 89 of its log):

INFO: ethereum:deploy_aztec_l1_contracts Deploying L1 contracts with config: {... "l1ChainId":31337,"enableProposerPipelining":true,"archiverPollingIntervalMS":500, ...}

Compose-routed e2e/cli-wallet tests (yarn-project/end-to-end/scripts/docker-compose.yml)

run_compose_test only streams the end-to-end container stdout, so the local-network node's config dump isn't surfaced in these test logs. Pipelining is set via the compose env at docker-compose.yml L31 (SEQ_ENABLE_PROPOSER_PIPELINING: 'true'); all tests below are cached green from a run on commit 323a501a (the commit that carries the compose env change + watcher fix):

Test	Ran	Result	Log
src/composed/e2e_cheat_codes.test.ts	yes	6/6 PASS	http://ci.aztec-labs.com/baf7e7b8f90a29f0
src/composed/e2e_local_network_example.test.ts	yes	PASS	http://ci.aztec-labs.com/5e79c18b50c60b38
src/composed/e2e_token_bridge_tutorial_test.test.ts	yes	1/1 PASS	http://ci.aztec-labs.com/abaa477cdb607759
src/guides/up_quick_start.test.ts	yes	1/1 PASS	http://ci.aztec-labs.com/e1125c678f3e5b1b
cli-wallet/test/flows/basic.sh	yes	exit 0	http://ci.aztec-labs.com/fba0aab5fe57d92a
cli-wallet/test/flows/capture_authwits.sh	yes	exit 0	http://ci.aztec-labs.com/c12d62acfe072d8d
cli-wallet/test/flows/create_account_pay_native.sh	yes	exit 0	http://ci.aztec-labs.com/5cfacc59657f277e
cli-wallet/test/flows/no_alias.sh	yes	exit 0	http://ci.aztec-labs.com/ff7767636172afda
cli-wallet/test/flows/private_transfer.sh	yes	exit 0	http://ci.aztec-labs.com/5ce2ec286391d4ab
cli-wallet/test/flows/profile.sh	yes	exit 0	http://ci.aztec-labs.com/596834026cea9df8
cli-wallet/test/flows/public_authwit_transfer.sh	yes	exit 0	http://ci.aztec-labs.com/9c05d97fda12051c
cli-wallet/test/flows/shield_and_transfer.sh	yes	exit 0	http://ci.aztec-labs.com/c59e6a2cb8003643
cli-wallet/test/flows/sponsored_create_account_and_mint.sh	yes	exit 0	http://ci.aztec-labs.com/52313069797f12c9
cli-wallet/test/flows/tx_management.sh	yes	exit 0	http://ci.aztec-labs.com/bbf5788486697094

Watcher fix observed firing in CI

The new AnvilTestWatcher log line Warped L1 to target slot N for pipelined publish was observed in CI for every test whose log surfaces local-network stdout. A few examples:

• aztec-up amm_flow.sh (15 occurrences, slots 3,6,9,12,15,18,21,24,27,30,33,36,39,42,45): http://ci.aztec-labs.com/af2b68e7a1d884e1
  • [16:01:14.300] INFO: aztecjs:utils:watcher Warped L1 to target slot 30 for pipelined publish
• aztec-up bridge_and_claim.sh (9 occurrences): http://ci.aztec-labs.com/418776554c4dce4c
  • [16:00:54.144] INFO: aztecjs:utils:watcher Warped L1 to target slot 21 for pipelined publish
• playground chromium (≥5 occurrences): http://ci.aztec-labs.com/928d273ed3d0849f
  • aztec-1 | INFO: aztecjs:utils:watcher Warped L1 to target slot 2 for pipelined publish
• playground firefox (≥4 occurrences): http://ci.aztec-labs.com/fcb032ebb35eac96

(basic_install.sh runs at LOG_LEVEL=silent, and the e2e run_compose_test flow doesn't multiplex local-network stdout, so the line is invisible in those logs but pipelining is still ON per the compose env.)

Anything flagged

Nothing to flag.

• .test_patterns.yml has skip: true only for src/composed/uniswap_trade_on_l1_from_l2.test.ts (already out of scope per the SANDBOX.md exclusion list — "bricked in new version of anvil").
• All other compose/aztec-up entries in .test_patterns.yml carry error_regex (flaky-on-match) without skip, so they ran normally.
• The test-engine summary confirms No flaked tests found on both ci/x-fast and ci/x-full.
• The 3 aztec-up tests we deliberately skipped from this audit (counter_contract, default_scaffold, no_shadow_user_bins) do not start aztec start --local-network, so they have no sandbox to pipeline.