fix(ci): extend AVM check-circuit timeout

[AztecBot]

Summary

• increase the AVM dumped-input check-circuit timeout from 30s to a 60s default
• expose AVM_CHECK_CIRCUIT_TIMEOUT so CI can tune the per-input budget without another script edit

Root Cause

The failed AVM Circuit Inputs Collection and Check run did not hit an AVM constraint failure. The avm-check-circuit job was killed by the harness timeout: the single-node/block-building/multiple_blobs input avm-circuit-inputs-tx-0x0992d31d...bin reached Running check (with skippable) circuit over 700560 rows, then timeout sent TERM at the hard-coded 30s limit and the command exited 124. The detailed sublog is http://ci.aztec-labs.com/6b7315a17391a6e7.

Testing

• cmake --preset clang20-assert
• ./bootstrap.sh build_native in avm-transpiler (cache hit for libavm_transpiler.a)
• cmake --build --preset clang20-assert --target bb-avm
• bash -O extglob -n yarn-project/end-to-end/bootstrap.sh
• sourced avm_check_circuit_cmds against the downloaded CI artifact and confirmed the failing input now emits TIMEOUT=60s
• /usr/bin/time -f 'elapsed=%E exit=%x' timeout -v 60s taskset -c 0,1 barretenberg/cpp/build/bin/bb-avm avm_check_circuit -v --avm-inputs /tmp/avm-inputs-repro.tMBt4p/dumped-avm-circuit-inputs/single-node/block-building/multiple_blobs/avm-circuit-inputs-tx-0x0992d31d74300f54d349ea662a6d1c369d9feca1ac0ea04a6b1ef2b738d078bd.bin (passed, elapsed=0:22.75 exit=0)

---

Created by claudebox · group: slackbot

[AztecBot]

Superseded by #24959, which makes the same avm_check_circuit budget fix, is rebased on current next (so its CI is meaningful), and carries the evidence from the latest failure (run 30266937162).

Five open PRs plus ~50 stale branches all propose this same one-line change and none has ever landed. Consolidating on #24959 — safe to close this one.

---

Created by claudebox · group: slackbot

[AztecBot]

Closing in favour of #24959, which carries the same fix rebased onto current next plus the consolidated evidence.

Worth calling out: this PR had the best verification of the batch — an actual local repro against the downloaded CI artifact measuring elapsed=0:22.75 exit=0 on two pinned CPUs. That measurement is now quoted in #24959 (attributed here), and it is what justifies the chosen budget rather than a guess.

This is a consolidation, not a rejection. Six identical open drafts were competing for the same review, and each was expiring to the stale-draft closer before anyone looked. Please review and merge #24959 to break the loop.

---

Created by claudebox · group: slackbot