Issue tracker for worst case benchmark

This tracker documents missing coverage in the full benchmark test suite:

- [ ] Nested call-frame stack for call family. Ex: recursive contract, depth ∈ [1,16,64,256,1024] × inner_op ∈ [SLOAD_warm, SLOAD_cold, SSTORE_dirty, TLOAD]
- [ ] Grows memory across sibling call frames.
- [ ] `JUMPDEST` analysis is only benchmarked on initcode
- [ ] Chain of calls until out of gas (call -> call -> call -> ...)
- [ ] State gas dominates the block gas limit while execution gas reaches state gas.
- [ ] Overlapping `MCOPY`: replace the shared `src_dst` expression with overlap ∈ [self, +1, +31, +copy_size//2, disjoint]; extend copy_size past 1024
- [ ] transient-storage rollback benchmark (TSTORE-heavy)

Start by locating the full benchmark test suite and its existing call-frame, JUMPDEST, gas, MCOPY, and transient-storage benchmarks. Choose one unchecked scenario, compare it with the nearest existing benchmark, and verify that the new coverage exercises the stated worst case.

Written by the indexing model from the issue text.