add txgen zone e2e spam

[0xalpharush]

Summary

• add txgen YAML workloads for L1 deposits, L2 withdrawals, TIP-403 policy updates, and policy-gated TIP-20 transfers
• add exact receipt, balance-delta, policy-enforcement, and L1 batch-settlement assertions
• add a single-sequencer CI workload that attempts 5,000 transfers at a 1,000 TPS target with eight senders
• publish concise measured throughput in the workflow summary and a sticky PR comment, with reports and node logs attached

Why

The existing smoke flow did not provide a repeatable way to load the Zone through txgen or distinguish sequencer admission rate from sustained execution throughput. A single sender also hits the default per-account txpool limit before exercising the sequencer.

The CI wrapper starts an isolated Tempo-mode Anvil and Zone, installs TIP-1091's fixed-address ZoneFactory into the fresh Anvil process, widens only the benchmark node's per-account txpool slots, and preserves the default Zone block gas limit.

Impact

Developers can run all bridge/policy workloads or one throughput attempt through just txgen-e2e-spam. CI reports accepted transactions, verified TIP-20 execution TPS, and total Zone TPS without embedding orchestration shell in the workflow YAML.

A local 5,000-transaction run accepted all transactions at the requested 1,000 TPS submission rate and verified:

• 5,000 successful receipts and zero failures
• 79.37 TIP-20 transfer TPS
• 80.48 total Zone TPS including system transactions
• exact recipient balance delta
• L1 settlement through the ending Zone block

Validation

• full local 5,000-transaction throughput run with exact receipt, balance, and L1 settlement checks
• fresh-Anvil ZoneFactory bootstrap and idempotent second invocation
• bash -n for all added shell scripts
• workflow and txgen YAML parsing
• ABI JSON parsing with jq
• git diff --check

[github-actions]

Txgen L2 transfer spam

✅ Passed — 5000/5000 accepted at a 1000 TPS target; submission 75.62 TPS; Zone 80.49 TPS.

Workflow run